I have three “First Alert 2-in-1 Z-Wave Smoke & Carbon Monoxide Alarm, Cert ID: ZC08-13060006” that are connected to my UZB Z-Wave stick, but they don’t show up in Home-Assistant like the other Z-Wave Devices do. The device is in the manufacturer_specific.xml file in Python-OpenZWave. Is there something I can do to manually get Home-Assistant to show these so I can set automation for them, or do I have to wait until they are supported?
Are you sure it is paired correctly? Can you see in in OZWCP? IF it is paired correctly it WILL show up in HASS. I had trouble with mine showing up because it wasn’t successfully pairing, I ended up pairing it through OZWCP because the manual pairing method of button pushing wasn’t working.
I’m having the same issue with a First Alert combo smoke/CO detector. Model ZCOMBO-G. Shows up in OZWCP, but doesn’t show up anywhere in HomeAssistant.
OZWCP shows Alarm Sensor First Alert ZCombo Smoke and Carbon Monoxide Detector and the value updates correctly if I press the Test button on the alarm.
HomeAssistant doesn’t show this device anywhere on the frontend, or in the development tools < >
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.
The first_alert_zcombo_smoke_and_carbon_monoxide_detector_alarm_type_4 string will vary based on the node ID given by your zwave network. I had to wait some time and/or restart Home Assistant before I got an entity name that included “first_alert_zcombo_smoke_and_carbon_monoxide_detector”. When I first initially included the alarm on the network it just had some generic sensor alarm entity name.
Are you sure it’s not supposed to be the alarm_report that ha the values, 1, 2, 12, and 13? I tested my alarm and the alarm_report is what changed to 12. The alarm_type changed to 255.
Mine was different again - alarm_level goes to 255 when there is an alarm and alarm_type gives the type. After the alarm is over, alarm_level resets to 255, but alarm_type stays at the last value. It also seems possible for alarm_level to go to 255 and alarm_type to go to 13 to represent an idle state. I built this sensor as a result - but I think the lesson here is test the device and see what you actually get!
I also wrote a simple AppDaemon App to monitor it, send a notification and turn lights on when it goes off:
import appdaemon.appapi as appapi
#
# App to send notification when a sensor changes state
#
# Args:
#
# sensor: sensor to monitor e.g. sensor.upstairs_smoke
# idle_state - normal state of sensor e.g. Idle
# turn_on - scene or device to activate when sensor changes e.g. scene.house_bright
# Release Notes
#
# Version 1.0:
# Initial Version
class SensorNotification(appapi.AppDaemon):
def initialize(self):
if "sensor" in self.args:
for sensor in self.split_device_list(self.args["sensor"]):
self.listen_state(self.state_change, sensor)
def state_change(self, entity, attribute, old, new, kwargs):
self.log("{} is in state {}".format(self.friendly_name(entity), new))
self.notify("{} is in state {}".format(self.friendly_name(entity), new), name="ios")
if new != self.args["idle_state"] and "turn_on" in self.args:
self.turn_on(self.args["turn_on"])
And a final point - I bought 1 of these then another 2. The first one fought me with the pairing until I figured it out, the second 2 were flawless when I had the exact sequence down - now very happy with these.
The sequence I used for ZWave pairing was exactly as follows:
Using Open ZWave Control Panel, activate “Add Device”
Only then, hold the test button and close the battery door, wait for the beep, release the button
That’s it - OZWCP will find the device and fill in all details, command classes etc.
Don’t power the device on before pairing, don;t change the order of the above and it should work fine.
Has anyone actually observed the alarm type for smoke or CO? I do get 13 for a test, but have not seen it be a 1 or 2 for smoke or CO yet. Need to do some kind of test I guess.