Hello, I try to create my first app to simulate one of my RF remote controller. I followed some quick start auto to mange creating the driver and device correctly. Then I used the RF signal analyzer tool ( here ) to create the signal file, while generated that predicted signal: Signal: { “sof”: …

In fact, I’m not sure about what I’m doing: Thanks to the analyzer, I get an average signal composed of start, end and words. But also a payload. When defining a signal in homey app, I must provide a start, end, and set of words. When sending this signal in homey app, I have to add the payload (a…

This other topic is not going so much in details (focusing on running the signal recording, which I manage to do, not on how to use it afterward)… and finish on “I bought a Broadlink”… :roll_eyes:

[image] GitHub - athombv/node-homey-rfdriver: This module helps developers create RF... This module helps developers create RF (433MHz, 868MHz, Infrared) apps for Homey. - GitHub - athombv/node-homey-rfdriver: This module helps developers create RF (433MHz, 868MHz, Infrared) apps for ... …

Thanks. I saw this one also, but it does not help explaining how to create the signal. Additionally, this one strongly added noise to my learning of RF signal API, because I finally understood that it is in reality not designed to give an example but to cover all possible cases of RF usages, making …

Do you have a recording of the data of a long press? Can you share it? please use Preformatted text [image] I think there is something wrong in the de words you defined, 3 words is not very usual, maybe I can find something. ( PM is also possible )

I can imagine that all other 433 senders should be off to record the signal of one sender only. Even when no one moves in my house, I am always recording a 433 signal without pushing any button. Very rarely, nothing is recorded. So motion and temperature senders will interfere with the recorded sig…

I did two long presses: [[5859,553,203,552,204,560,194,558,206,169,586,556,197,182,580,175,575,562,202,548,214,174,582,547,204,561,203,549,205,175,582,174,580,557,204,173,591,172,579,181,578,170,588,169,588,556,204,172,580,181,5858,545,227,535,227,538,210,547,215,163,589,550,209,175,586,168,588,555…

[image] Ezeta: the role of the payload The Payload is the actual transmitted data a longer pulse followed by a shorter pulse is a “0” defined in “words” as [ 554, 206 ] a shorter pulse followed by a longer pulse is a “1” defined in “words” as [ 175, 583 ] (values are +/- 100

Great, it works !!! For people interested in the subject, I resume the exchanges we had with @JPe4619 (thank you very much !): The signal sent is composed of three parts: Sof: starting part (and always the same) Payload: variable part (depending on the button pressed) Eof: end of the signal (al…

RF Custom App: Signal (from signal analyzer) sent but not received

Developers

Rmb December 6, 2023, 9:20am 3

There are some topics, for example Creating an app for a recorded 433Mhz signal - #3 by HarriedeGroot

Topic		Replies	Views
How to create correct 433MHz signal.json file Questions & Help app , rf-433 , homey-pro	2	208	December 10, 2024
RF Learning and VCD file Devices rf-433	44	3238	February 23, 2024
Doorbell 433 mhz app developer Developers	3	158	December 11, 2024
Recording RF signal Questions & Help rf-433	28	8628	March 21, 2021
Help with signal definition Apps app , rf-433 , homey-bridge , homey-service	1	350	January 31, 2023

RF Custom App: Signal (from signal analyzer) sent but not received

Related topics