I have two version of First Alert Zwave combo Smoke and CO alarm system.
-Version 2 works perfectly fine and shows multiple entities for smoke and CO along with other entities.
-Version 1 only shows two entites and both are battery related
Which device(s) is/are affected (make/model)?
What are the node IDs?
Node 15 - V1 have issue with not showing CO and Smoke alarm. Only shows battery entites
Node 13 - V2 shows both along with other entities
Last Known Working Configuration
Was using with smartthings and both worked. Excluded and added to zwavejs2mqtt and Homeassistant
Previously working device (node-zwave-js)
-V1 never showed alarm just battery
-V2 shows all alarms
-ZwaveJS Version 6.1.3
-HA Version :2021.2.2
Previously working device (other platform)
Smartthings
Excluded both from smartthings and added to zwavejs
Installation information
How did you install node-zwave-js ?
[ X] zwavejs2mqtt (latest) docker image
To Reproduce
Steps to reproduce the behavior:
Go to Homeassistant
Entites you can see both Smoke/CO sensors
But for V1 only batterty entties shows whereas V2 all entities shows including CO/Smoke alarm
I did raise the defect on zwavejs as well, but as per them the device is working properly. Its the zwavejs server which is not creating the entities.
You have the alarm_type and alarm_level entities, you can use those. There are tons of examples here on how to create templates or use the values in automations.
HA has never created any special entities for those values in the zwave or ozw integrations. Only for devices that support modern notifications does it create those entities, because they are standardized. If you think special entities should be created for the old zcombo, then you’ll need to submit a feature request or github issue, and see if the devs are interested in supporting it. To do so would required writing custom code for this specific device, which is generally avoided. V1 alarm values are manufacturer specific, not standard.
Thanks for the sample, I was only able to figure out 255,13 (default) and 255,12 (Test) so I had created an automation to trigger for any change in value.
Thanks for the help, I guess the newer Firstalert zwave combo are integrated properly
This topic is a bit old but unfortunately I’m having trouble adding First Alert Z-Wave Smoke / CO Combo Alarm’s Gen 2.
I have a Aeotec Z-Wave Gen5 Stick and running Zwavejs2MQTT as a docker container.
Already running six zwave devices. But I can’t figure out how to include these First Alert devices.
I have taken these steps:
zwavejs2mqtt in the controlpanel is choose under actions → Manage Nodes → inclusion → Default
then the inclusion starts for 30sec…
First Alert device: Slide battery door open → Press and hold the test button → while holding the test button i close battery drawer → then i release the button. the device beeps
result: Nothing!
Also when i try to include the device with just the Aeotec Z-Wave Gen5 Stick (push the physical button) it doesnt work
For your Step 2, try that process one more time if it doesnt include the first time.
One other thing to try is to set your zwavejs instance to exclusion and do the same thing. See if it says successful. If it does, it should now pair again when you goto inclusion and do the same thing as Step 2 again.
thanks for your suggestions @gregg098.
Unfortunately it still doesn’t work and have been trying for hours. Is it true that when I close the battery drawer again after the beep I have to release the button and then the green light flashes repeatedly? after about 10 sec I hear another beep and then it stops. I have done this multiple times until the inclusion in zwavejs2mqtt was timedout.
Also tried:
a second First Alert device
resetting the first alert by holding the test button for +10 seconds
I came across this below on the Aeotec website:
Sometimes the inclusion process fails and there are a few troubleshooting steps that you can take to ensure the maximum success for during the inclusion process. Make sure that the Z-Stick Gen5 and the Z-Wave device you are attempting to include are running the same network:
ZW090-A is US frequency
ZW090-B is AU frequency
ZW090-C is EU frequency
My first alert devices are from the US and my Aeotec is from EU (ZW090-C). Can’t find what frequency the First Alert devices work on, but I’m assuming it’s the US (ZW090-A) sins I ordered them there. Got two options now, return them back, but can’t find any good alternative inside europe for a smart Smoke & CO detector or options 2: i have to buy a Z-wave ZW090-A controller so I can run the Firts Alert devices in a separated network and a separated zwavejs2mqtt container.
I’ve only ever held button, pushed batteries in, then get a beep right away, let go of button, get another beep ~10 seconds later from what I remember. I just make sure inclusion is running before I start that. I just had to do it multiple times and even try excluding first to get it to work sometimes. It was somewhat random and I just had to experiment. I’ve re-paired theses a million times over the years with SmartThings and all of the Home Assistant Z wave versions. Been using an Aeotec Z stick 5 for the last few years.
It does look like a frequency issue for you though. Dont know of other solutions, sorry.
Just an update on my inclusion problem as described above.
I had indeed bought 3 smoke and co detectors that work on the American 908.42 MHz. Before I bought these detectors, I actually thought that z-wave was universal and could always be linked, but unfortunately not. I could do two things, return the purchased detectors to the US or buy a z-wave gateway from the US that also works on 908.42 MHz. I did this last one and it works! It was very hard to find the right one and with favorable shipping cost.
So now i have:
Aeotec Z-Wave Gen5 Stick 868.42 MHz
Aeotec Z-Wave Gen5 Stick 908.42 MHz
Each usb device mounted in a seperate docker container
and two Zwave-js integrations on different ports
Unfortunately, the Z-wave devices do not form a complete mesh network but two separate z-wave networks in this way, but I absolutely wanted these smoke & co detectors and were only available in America.
It was very hard to find the right one and with favorable shipping cost.
