# Help with 433Mhz signal definition for Homey

**URL:** <https://community.homey.app/t/help-with-433mhz-signal-definition-for-homey/86892>\
**Category:** Questions & Help\
**Created:** [August 12, 2023, 5:14pm UTC](https://community.homey.app/t/help-with-433mhz-signal-definition-for-homey/86892 "2023-08-12T17:14:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin072](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin072/32/70637_2.png) [@Martin072](https://community.homey.app/u/Martin072)\
**Post date:** [August 12, 2023, 5:14pm UTC](https://community.homey.app/t/help-with-433mhz-signal-definition-for-homey/86892/1 "2023-08-12T17:14:53Z")

</div>

I am trying to get a 433mhz device working from Homey with an app, but no luck with getting the signal definition right.

I have used [rf analyser](https://github.com/harriedegroot/Athom-Homey-RF-Signal-Analyzer/tree/master) to capture the signal, and predicts the following:

```auto
{
  "sof": [
    335
  ],
  "eof": [
    65535
  ],
  "words": [
    [
      381,
      663
    ],
    [
      707,
      336
    ]
  ],
  "interval": 10000,
  "sensitivity": 0.5,
  "repetitions": 20,
  "minimalLength": 18,
  "maximalLength": 18
}

```

That signal definition fails to load in my app, as the “eof” can’t be 65535 apparently (removed it, then it loads the definition fine).

However, trying to send the signal does nothing to my device, so I am guessing the recording is slightly off?

I also happen to have an rtl\_sdr dongle, and that captured the following raw data, perhaps some one could help me out to adjust the signal definition for Homey?:

```auto
Total count: 19, width: 19.11 ms ( 4778 S)
Pulse width distribution:
 [0] count: 11, width: 324 us [316;348]	( 81 S)
 [1] count: 8, width: 652 us [648;656]	( 163 S)
Gap width distribution:
 [0] count: 8, width: 388 us [384;396]	( 97 S)
 [1] count: 10, width: 716 us [712;724]	( 179 S)
Pulse period distribution:
 [0] count: 5, width: 720 us [712;740]	( 180 S)
 [1] count: 5, width: 1368 us [1364;1376]	( 342 S)
 [2] count: 8, width: 1040 us [1032;1048]	( 260 S)
Pulse timing distribution:
 [0] count: 19, width: 352 us [316;396]	( 88 S)
 [1] count: 18, width: 688 us [648;724]	( 172 S)
 [2] count: 1, width: 10004 us [10004;10004]	(2501 S)
Level estimates [high, low]: 2654, 85
RSSI: -7.9 dB SNR: 14.9 dB Noise: -22.9 dB
Frequency offsets [F1, F2]: 18716, 0	(+71.4 kHz, +0.0 kHz)
Guessing modulation: Manchester coding
view at https://triq.org/pdv/#AAB103016002B027148091818090918181809090918181809180918255
Attempting demodulation... short_width: 324, long_width: 0, reset_limit: 728, sync_width: 0
Use a flex decoder with -X 'n=name,m=OOK_MC_ZEROBIT,s=324,l=0,r=728'
pulse_slicer_manchester_zerobit(): Analyzer Device
bitbuffer:: Number of rows: 1
[00] {24} 23 0e 12 : 00100011 00001110 00010010

```

As for another device that i currently use for rf send/receive is a Tasmota.  
When I send the command from my App, I do see a response in Tasmota, so Homey is sending it, and shows as follows:

` {"Time":"2023-08-12T19:18:25","RfReceived":{"Data":"0x19C75","Bits":18,"Protocol":6,"Pulse":434}}`

But pressing the **actual** 433 remote shows this:

` {"Time":"2023-08-12T19:21:38","RfReceived":{"Data":"0x19C75","Bits":18,"Protocol":8,"Pulse":423}}`

Note the difference in “Protocol”…

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [August 13, 2023, 11:20pm UTC](https://community.homey.app/t/help-with-433mhz-signal-definition-for-homey/86892/2 "2023-08-13T23:20:52Z")

</div>

Not an expert here, but what when you record the signal with Homey instead of ‘rf analyser’  
[https://tools.developer.homey.app/tools/signals](https://tools.developer.homey.app/tools/signals)

---

<div class="post-metadata">

**Author:** ![Martin072](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/martin072/32/70637_2.png) [@Martin072](https://community.homey.app/u/Martin072)\
**Post date:** [August 14, 2023, 12:38pm UTC](https://community.homey.app/t/help-with-433mhz-signal-definition-for-homey/86892/3 "2023-08-14T12:38:22Z")

</div>

Well that’s the strange thing, capturing the signal with Homey and then trying to send it via the developer page doesn’t trigger it.

But…after some fiddling around and trying, found the solution: seemed that the `"interval": 10000` was not correct, and needed slight tweaking. Got it working now.