tkvtec
January 17, 2017, 3:19pm
5
I had found this before setting them up (I wish I could say I invented the wheel, but I didn’t):
I had the same problem with the first alert detector, solution was to remove the alarm from the network and then add it through HA. From my understanding, the alarm only sends out it’s identifying information once so if you add it with OZWCP you won’t see it next time you launch HA. A restart of HA may also be needed after adding the alarm to get the entity IDs updated.For the alarm types, 1 is fire alarm, 2 is CO, 12 is the test button, and 13 is stand by, the value seems to normally be 255, if you press the test button the type will change to 12, after the test is over the value will change to 0. After some time, the type changes back to 13 and the value changes to 255. Note: I haven’t confirmed 1 is fire and 2 is CO, I just read that on another forum, I have my alarm go off if the type ever isn’t 13 just to be safe.
I had the same problem with the first alert detector, solution was to remove the alarm from the network and then add it through HA. From my understanding, the alarm only sends out it’s identifying information once so if you add it with OZWCP you won’t see it next time you launch HA. A restart of HA may also be needed after adding the alarm to get the entity IDs updated.
For the alarm types, 1 is fire alarm, 2 is CO, 12 is the test button, and 13 is stand by, the value seems to normally be 255, …
I have basically done the same for my automations.
Each smoke/CO detector shows up as two sensors (one is TYPE, and the other is LEVEL)