dchesterton/texecom2mqtt-hassio

System fault monitoring & debug messages

Opened this issue · 0 comments

Hiya,
Yesterday I got into the situation where one of my family had disarmed the alarm (keypad code) but then not rearmed it as expected, they didn't tell me anything so I assumed they'd forgotten so I attempted to arm the alarm via HA which silently failed, after a few attempts I jumped over to the smartcom app and attempted to arm there to find that the app said there was an error that would prevent arming but didn't say what it was. Checking it later, I found that a riccochet DT PIR had fallen off the mesh, presumably when the alarm had been disarmed otherwise we'd have seen an alarm trigger. Switching out the aging battery made the system happy again.

Today my container log doesn't go back far enough to cover that period of time but I do have the the MQTT debug messages silently pushed to my phone so I have several weeks of them. I think can see the attempts to arm the system using RemoteCommand and these don't have a follow up MQTT message such as ExitStarted or an error. Likewise, scanning back over the last week or so I don't see anything relating to alarm warnings or errors indicating that a fault occurred in any part of the system.

The system highlights are it's a premier elite 48, I've not bothered updating the firmware since V5.00.02LS1, the home assistant network connection is a comwifi, it does have a smartcom, the docker container is running January's 1.2.3 on x86.

I've not sought out signing Texecom's NDA yet so without visibility of the implementation or the protocol spec I don't know if this is possible but...

It would have been helpful if when the panel started displaying the fault message that it also be sent over MQTT, any indication that there was a fault would have been good and getting any further detail would have been an improvement on that.

Is it possible to trigger a read of the panel text for desperate situations? (Remember the ancient remote keypad and engineer apps that polled the panel in a horrific way?)

Finally, is it possible for the arming RemoteCommand to determine it will/or has failed like the smartcom app? E.g. arm rejected. Physically at the panel I was given the option of arming anyway, that would have been useful to have partial alarm sensor coverage rather than none at all.

Cheers!
-Simon