Is using any device protocol best practice?

[Sven Rahn]

Hi!

I have a garage door remote which I want to use to control a program on my PC. When pressing a button, I get a log output for the device 86 which is "Wireless Smoke and Heat Detector GS 558". By explicitly specifying -R 86, I get a stable result every time I press a button. The "raw code" of a packet is different for each button, and outputting it as JSON makes it possible to use in my program.

So everything is fine. But is it against some best practice to just use the protocol that works? Or should I reverse engineer this specific device? Currently I don't see the need to do so.

Second question: I only get one output even if I hold down the button. There seems to be some deduplication built into rtl_433, can I turn it off to receive the output as early as possible?

Best regards

[Christian Z.]

Your sender uses a EV1527 encoder.

Looks for the 1527 mentions in https://github.com/merbanan/rtl_433/tree/master/conf and adapt your config from that.

[Sven Rahn]

Thanks for your fast reply! I figured it out I guess.

I only changed the bit count to always be equal to 25 because it always was 25. I haven't received other signals yet but I guess this just makes it more resistant against other signals. I also don't need any specific data extracted from the data field because my software will have some kind of learning feature anyway. It doesn't matter in that case which button on which remote was pressed. 

decoder {
        n=EV1527-Remote,
        m=OOK_PWM,
        s=369,
        l=1072,
        g=1400,
        r=12840,
        bits=25,
        repeats>=3,
        invert,
        unique
}

For future reference, my command now is

.\rtl_433.exe -R 0 -F json -X n=EV1527-Remote,m=OOK_PWM,s=369,l=1072,g=1400,r=12840,bits=25,repeats>=3,invert,unique

I guess I could have also removed the inverted flag because I don't care for the values itself.

Well, this project is awesome :)

[Christian Z.]

Yes, that looks to be correct. The EV1527 send 24 data bits and a sync bit, but the sync bit has no distance to the preceeding packet and a so every packet except the very last looks like 25 bits.