Verbose Trouble Status handling #69
Description
Verbose Trouble Status should be "better" handled to track bit field, display status in html, make bits available in JSON.
The test/use case (at least for me), Wireless Keypad Low Battery, generates a trouble LED on, and a verbose trouble status. However, no other zone messages are sent, there is no zone message. If you manually parse out the verbose trouble status bits, you can see the trouble condition is 0x40 Sensor/Zone Low Battery.
Note: My personal goal is to be able to tell as much as possible remotely in case I can't get to a keypad. I don't see a way to tell which zone has the problem, but I think that's a DSC problem for not sending the right zone message.
Currently, I'm not sure I understand the design of the code base well enough to figure out where/how the various system status bits should be handled.
Currently, the web interface does indicate trouble, but:
- The verbose trouble message is absent from the all/partition logs.
- the web interface needs a place to show what the trouble is.