I’ve forked another project and made some changes to allow (hopefully) easy integration of 345MHz Honeywell sensors (e.g. 2GIG, Vivint, etc.). It requires an RTL-SDR dongle and antenna (~$25) and that’s about it.
I was motivated to do this since I somewhat recently bought a home that included a lot of these devices but I didn’t want to pay a monthly fee and I wanted better integration with everything else (cue HA).
Fortunately I found the “HoneywellSecurity” project, which did most of the heavy-lifting. However it was designed for SmartThings and it also didn’t decode things like tamper, low battery, check for timeouts, etc.
I’ve tested this with numerous sensor types including door, window, shock, smoke, and water.
It’s been pretty good. I have about 20 devices and they all work well except for two that occasionally miss events. I think I probably don’t have as good range with my RTL-SDR receiver+ antenna as the original setup. I am going to try to replace the batteries and see if that takes care of it since they used to work OK but have been getting worse over the last few months.
Very cool. In talking to these devices directly, do they loose their pairing to the alarms local controller? or are they able to simultaneously talk MQTT to HA and maintain their connection to the alarm panel?
I just tried this out, but I get a series of errors. They pop up after I open a door with a sensor on it. Invalid Payload: FFFE74214E0C0137 1/1 packets failed CRC Invalid Payload: FFFE74214E0C0137 2/2 packets failed CRC Invalid Payload: FFFE74214E0C0137 3/3 packets failed CRC Invalid Payload: FFFE74214E0C0137 4/4 packets failed CRC Invalid Payload: FFFE74214E0C0137 5/5 packets failed CRC Invalid Payload: FFFE74214E0C0137 6/6 packets failed CRC
It looks like your device uses a different set of CRC parameters. Can you provide maybe 2-3 more different payload examples? I should be able to confirm the new parameters with that.
I have tried this a couple times, but am never able to pick up any transmissions. Im ~99% sure that I’m using 345MHz sensors. Do you use the same settings as shown on github?
Yes I am using the Github code as-is…do you have a brand or model number for your sensors? I assume your existing alarm panel picks them up OK still and the batteries are good? What are you using for your antenna?
It seems like my Vivint install uses 2gig DW10 345Mhz sensors. They are not marked anywhere that I can see, but based on the install date and the fact that they have 2 batteries inside, it’s the best that I can infer.
I hear that this model broadcasts unencrypted, and was hopeful that the Honeywell decoder could work, but I don’t even detect the broadcasts.
Hi @fusterjj I’ve just installed HoneyWellSecurityMQTT and I am facing this CRC issue with some of my devices, can you help me on this ?
This is what mine looks like
Mqtt - set LWT message to: FAILED
Mqtt - connected
Found Rafael Micro R820T tuner
Successfully set the frequency to 345000000
Successfully set gain to 350
Exact sample rate is: 1000000.026491 Hz
Successfully set the sample rate to 1000000
Mqtt - Message (1) published
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
*Device 123125: OK TAMPER
Mqtt - Message (2) published
Mqtt - Message (3) published
Mqtt - Message (4) published
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
Valid Payload: FFFE21E0F54081C0 (Serial 123125, Status 40)
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
*Device 118756: OK
Device 123125: OK TAMPER
Mqtt - Message (5) published
Mqtt - Message (6) published
Mqtt - Message (7) published
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
Valid Payload: FFFE21CFE4003470 (Serial 118756, Status 0)
Invalid Payload: FFFEB0BA354479D0
1/13 packets failed CRC
Invalid Payload: FFFEB0BA354479D0
2/14 packets failed CRC
Invalid Payload: FFFEB0BA354479D0
3/15 packets failed CRC
Invalid Payload: FFFEB0BA354479D0
4/16 packets failed CRC
Invalid Payload: FFFEB0BA354479D0
5/17 packets failed CRC
Invalid Payload: FFFEB0BA354479D0
6/18 packets failed CRC
Valid Payload: FFFE8612F004D943 (Serial 398064, Status 4)
Device 118756: OK
Device 123125: OK TAMPER
*Device 398064: OK
Hi @figorelli,
Can you tell me anything about these devices? Brand, type, etc.? Are all these invalid messages from similar/same types? If so, I should be able to figure out the CRCs. Otherwise I will probably need a couple of examples of different payloads from each one.
