# Unable to receive 433MHz RF signal **URL:** \ **Category:** Developers\ **Tags:** rf-433\ **Created:** [September 23, 2021, 3:39pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117 "2021-09-23T15:39:04Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Rutger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rutger/32/3736_2.png) [@Rutger](https://community.homey.app/u/Rutger)\ **Post date:** [September 23, 2021, 3:39pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/1 "2021-09-23T15:39:04Z")
Hi all, I’m developing an application using the **[node-homey-rfdriver](https://github.com/athombv/node-homey-rfdriver)**. At this stage, I can send RF signals but I can’t receive RF signals. Receiving of RF signals is needed to extract the address of the RF signal (pairing). The receiving / extraction of the RF signal should probably be done in `createPairCommand()`, but I don’t know how. Can someone provide me with example code or give me a direction? Regards, Rutger ---
**Author:** ![Rob\_Veenis](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rob_veenis/32/30144_2.png) [@Rob\_Veenis](https://community.homey.app/u/Rob_Veenis)\ **Post date:** [September 23, 2021, 3:53pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/2 "2021-09-23T15:53:22Z")
Hi Rutger, Sorry, I can’t help you with that. The whole forum is full off frustrated people (like me) which are not able to learn and reproduce RF signals in the Homey. If you seriously want to find a solution for this, please include 868 MHz as well. (I have 9 devices that I would love to control) When you manage to find a solution you’ll be considered a hero!! ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [September 23, 2021, 4:07pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/3 "2021-09-23T16:07:50Z")
> **[Getting Started](https://apps.developer.homey.app/the-basics/getting-started)** > > How to create your first Homey app. > **[433 MHz](https://apps.developer.homey.app/wireless/rf-433mhz-868mhz)** > > Homey is capable of sending and receiving 433 MHz and 868 MHz radio-signals for controlling remote appliances like wireless switches and thermostats. You can test receiving / emulating signals: [https://tools.developer.homey.app/tools/signals](https://tools.developer.homey.app/tools/signals) You can view a working example of a Homey App that uses 433 MHz at: [GitHub - athombv/nl.klikaanklikuit-example: KlikAanKlikUit — Example code to inspire your own Homey app.](https://github.com/athombv/nl.klikaanklikuit-example) ---
**Author:** ![Rutger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rutger/32/3736_2.png) [@Rutger](https://community.homey.app/u/Rutger)\ **Post date:** [September 23, 2021, 6:08pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/4 "2021-09-23T18:08:33Z")
Hi Rob, It’s unfortunate that we just can’t simply use the record and emulate signal in Developer Tools. First of, I want to finish my specific application (it works, but I want to make it possible to have dynamic addresses instead of a fixed one) and after that maybe a generic recorder / bridge (if possible). If you want to control your devices, you could use a logic analyzer and a 868 MHz receiver to decode the signal and then make a signal definition in Homey, but it could be difficult if you don’t have technical knowledge. ---
**Author:** ![Rutger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rutger/32/3736_2.png) [@Rutger](https://community.homey.app/u/Rutger)\ **Post date:** [September 23, 2021, 6:15pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/5 "2021-09-23T18:15:28Z")
Hi JPe4619, Thank you for the URLs. I have already a working application but it can only send a signal with a fixed address. I have also seen the 433 MHz example, but it only generate a radom bit string for a couple of parameters and I want to be able to read the value of my remote. CreatePairCommand from the example: ```auto static createPairCommand() { return { address: RFUtil.generateRandomBitString(26), group: false, state: true, channel: RFUtil.generateRandomBitString(2), unit: RFUtil.generateRandomBitString(2), }; } ``` ---
**Author:** ![JPe4619](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/jpe4619/32/9017_2.png) [@JPe4619](https://community.homey.app/u/JPe4619)\ **Post date:** [September 23, 2021, 8:02pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/6 "2021-09-23T20:02:08Z")
OK, so you have already analyzed the signal and found the sof: the eof: the data length and the words values. Then you probably need: [https://apps.developer.homey.app/the-basics/devices/pairing](https://apps.developer.homey.app/the-basics/devices/pairing) I have not used this (yet) / until now. ---
**Author:** ![robertklep](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/robertklep/32/160628_2.png) [@robertklep](https://community.homey.app/u/robertklep)\ **Post date:** [September 24, 2021, 6:08am UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/7 "2021-09-24T06:08:24Z")
> [@Rutger](#): > > and after that maybe a generic recorder / bridge (if possible). Not possible. An app needs to provide a fixed signal definition up front, which rules out “generic”. ---
**Author:** ![Rutger](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/rutger/32/3736_2.png) [@Rutger](https://community.homey.app/u/Rutger)\ **Post date:** [September 29, 2021, 5:07pm UTC](https://community.homey.app/t/unable-to-receive-433mhz-rf-signal/52117/8 "2021-09-29T17:07:13Z")
That’s unfortunate… I just came across the following text which confirms this and which is also an answer to my question: > The Homey Signal Manager receives all incoming raw transmissions and attempts to match these block-waves to a registered signal definition. When an incoming signal matches a registered signal definition, the signal is automatically decoded and the contained data is routed to the corresponding app. To transmit, data travels the reverse path which means the data is encoded using the same signal definition and then transmitted."