Open ssillen opened 9 months ago
Hey,
Thanks for this, I've just updated my config and it looks a lot cleaner. I am, however having an issue with connectivity. Any ideas...
Hey,
Thanks for this, I've just updated my config and it looks a lot cleaner. I am, however having an issue with connectivity. Any ideas...
You have to initialize the connectivity of all the smoke sensors to "on". The bridge needs a message from each smoke sensor to confirm it's connected, because it doesn't know the initial state. So you can trigger an event on each smoke sensor by triggering an alarm or removing the smoke sensor from the base. Or you can set the connectivity via the Developer Tools.
Thanks for the reply. I have initiated a test, all alarms sound. I've removed all of the alarms from their base and refitted. No change in any of the statuses.
Gateway connectivity and radio are ok, the connectivity sensor of each smoke sensor is available, so it would have to be in the configuration of the smoke sensor connectivity sensor. Please check the device id's in your configuration. Compare with the input you get from sensor.fireangel_data when triggering an event on your smoke sensor.
Ok, so done some experimentation.
If I initiate a test from each alarm, the section for that alarm on my dashboard gets updated. I've now done that on all alarms, and all statuses are showing. However, if I initiate an alarm situation on any alarm, the statuses do not update. I held a lighter under my Kitchen Heat Sensor until it went off. All alarms sounded, "Fire Angel Data" on my dashboard showed the emergency message, but the status pages remain unchanged, with the kitchen still showing "Heat Status: Normal". Also, removing any alarm from it's base does not update the status.
EDIT
Ignore all of that. It appears that it just takes a little bit of time to update. Seems to be working now. :)
Thanks for the assistance :)
I happily used your project, thank you for the hard work. However, I upgraded the sensors config according to the latest Home Assistant principles (2024.1). The availability of the sensors is also automatically updated, based on heartbeat & "missing" events. I'm using the /dev/serial/by-id/ as serial_port, because the /dev/ttyUSB can sometimes change when (un)plugging new devices or doing a restart. Hopefully this might be of use.
config.yaml:
lovelace.yaml:
I'm using node-red for automations, so I didn't update/test automations.yaml