fusterjj / honeywellsecuritymqtt Goto Github PK

(copied from readme)

HoneywellSecurityMQTT attempts to use MQTT wills to indicate a failure if the program dies unexpectedly, but this doesn't seem to work. I may be misunderstanding how this is supposed to behave, or perhaps it is some issue with HA's embedded MQTT broker. If anyone has any ideas here, I'm all ears.

Did anyone ever observe messages from the control panel(s) themselves?

Since there are keyfob remotes and remote panels, I would expect that they exchange messages as well, not just to arm/disarm, but even for things like the chime settings.

As soon as I run honeywell it shows a disconnect mqtt message. I tried running with and without a username and password and it's the same problem. I've tested my mqtt broker with another client and there are no issues there.

I honestly can't figure this out.

I have 8 sensors all working perfectly with this app, so thank you for that!

However, we have 1 2GIG DW11 from a Vivint system that is no longer active, that doesn't want to play nice. It shows as Invalid Payloads in the log, but then in Home Assistant it randomly picks up a trigger of open/close every few hours.

Hello. I can't install this custom component using HACS in HASS.IO. I'm getting 'Repository structure for master is not compliant' error. I don't know any other way to install this component. Please help.

Each message is sent as a burst of repetitions. Instead of logging each message, logging e.g.

Device 1234567 reported status 0x80 (7/12 CRC ok)

for a burst of messages with one dominant CRC ok message might declutter the log.

The Honeywell system itself apparently only notices jamming as more than 20 seconds of continuous noise, making it easy to bypass by just jamming 19 seconds at a time. The analog decoder here could monitor the noise floor and be a little smarter. Something like more than 10 seconds within a 10 minute window.

It might be worthwhile to have a small simple configuration file in which the sensors, their type and ID are listed:

• push meaningful names to MQTT rather than obscure numbers
• work around warm up time needed to learn alarm bit
• filter neighbors' devices we don't want to accidentally snoop on
• set status of devices after restart (think device that happens to go offline, after restart, e.g. from repositioning receiver, the MQTT will still show the device as fine, no timeout shown)

device_class: safety is not available for sensor, only for binary_sensor.

3. Config your build. Fill out this file
   nano mqtt_config.h

Hi there, I'm pretty new and haven't a clue how to do this part of your instruction. How would I go about filling this form?

Thank you for your time