Creating an app for a recorded 433Mhz signal

Developers
1

I have a LEDS-C4 device that is incompatible with the https://github.com/eriks5/com.leds-c4 app (which, in turn, is incompatible with Homey 2.0). I can see I can record the signal in Homey, for one of the buttons it is:
8641,27714
15959,27068
10,50028
15941,41782,20,9578,0,3844
0,15870
187,226
15987,1936,0,3130
13228,1086
15806,65535
54,10732
15784,65535
16010,41310
15913,1308
155,842
15911,41434
15955,26184
22,65535
62,504
15911,584
16035,1248,20,434,22,694,22,1036,54,1356
69,262
15892,1222
15885,27648
15858,65535
56,9906
14030,10996
153,262,12,1344
79,1784
69,1496
15918,65535
15906,384,0,1246,22,308,20,124,30,906,62,768,20,394,30,124
15954,65535
16014,1838,20,790,32,1276,32,1806,32,7678
15860,65535
10975,1968

Any guides to taking those signals and turning them into an app? I found some tutorials that might have been outdated but nothing with the new “recorder” at https://developer.athom.com/tools/signals sadly.

1 Like
2

https://developer.athom.com/docs/apps/tutorial-Signals.html

3

Made a small tool once: https://github.com/harriedegroot/Athom-Homey-RF-Signal-Analyzer

4

Tried using your tool, but I can’t succeed in finding the bearers code, despite following several instructions. Have you got a working instruction for this?

5

@Roger_Gorissen did you try the search function?
Search results for 'Bearer token' - Homey Community Forum

First hit:

6

Had already done what you suggest. After pressing F12 screens don’t match with your image, don’t see any “GET”, let alone the other info. Work in the latest Chrome, do exactly as you desrcibe.

Any other way to get the info?

7

Nope, last time I touched the tool was about a month ago. It worked as described by then, maybe things changed? I know e.g. they changed the token lifetime to last only one day, maybe they made some additional changes.

To be sure: you need to be on the same network (lan) and provide the correct local ip of your Homey for this to work.

8

It in Chrome that I get the different screens compared to the one in your picture.

After selecting Tools, pressing F12, selecting Devices, I don’t get the screen with (at least) 2 times GET. I see different words, elements and so on. So I can even see the bearer.-

Don’t know where to search or what to do different.

9

I managed to get my Bearer token from Chrome, no problems there.

Tried some pressing, but found it hard to use the tool; pressed the button 3 times.
ERROR: no signals found with a count of 3, choose one of:
signal: { “lenght”:count }
{
“2”: 49,
“4”: 16,
“6”: 4,
“8”: 1,
“10”: 4,
“56”: 1
}

Perhaps 433 is just a task too hard for me :roll_eyes:

10

Did you put your 433 device close to homey.
Range of 433 can vary a lot. Especially for testing I would put the device at around 1m.
In direct sight (no walls or blockage or reflective surfaces) from homey

11

I was 1 meter away but a thick wall in between. However, I tried the remote from the other side of the wall and the fan it controls turned on (5 meters and 1 thick, 1 thin wall in between)

Also, it does seem to record signals.

12

If its a remote then its easy to stand close to homey.
The fact that the fan did switch on through the wall does not mean homey will receive the signal through a wall too. (See the many threads on improving signal from homey, homey is not the best receiver)
So I would advice a retry with you remote close to home in clear sight

13

Finally succeeded in Edge. Completely different screen and info compared to Chrome, doing exactly the same things as descibed before.
Now trying to grab the data and implement in an app…

14

Hi. I have a LEDS-C4 as well. Did you succeed with your own app? I would be interested :grimacing:

15

Nope, didn’t succeed. I bought a Broadlink RM 3+. You can learn the signals and use them in Homey flows.