Dual smoke co had a low battery . Was chirping.
Replaced it...still getting this message
Any idea what it means.
Think this may be the end of.life chirp and alarm
If so the driver should be updated to support it
Its the first alert zwave (non plus) combo
Give me 5 minutes to find it in the zwave specs. Be right back.
1 Like
Well this is a first for me. First of all that command class is depreciated. Secondly the alarm type is not specified in the specs, so it sounds like the MFG could use any random crap they wanted and would have to specify it in their docs. I am guessing this is why they depreciated it. All the newer command classes have explicitly defined notification / alarm types
This is from V1 class, even more vague.
1 Like
Definitely was the end of life chirp, not low battery. ordered 2 replacements from amazon.
Other one .is a month later date code.
Sad thing is that it would most likely work perfectly fine for another 10+ years. My old detectors that were installed with the house in 97 still worked perfectly fine just this year. We tested them baking something once or twice and it was not even much smoke. Mainly replaced them because they were so old the alert was not the standard pattern so the ecolink Firefighter I bought did not pick them up. All hard wired interconnected so I opted to replace with similar equipment and integrate via the firefighter.
2 Likes
2015 date code.. don't feel like silencing the damn things every 2 days.
And dog hates the chirps. Starts shaking.
2 Likes
Mine were so old they didn't have an end of life warning either 
1 Like
Now i need to check other house . Probably going as well. Back to the .pt is there a std alarm on newer ones that the driver detects. It definitely should be added so we can create a rule.for .notification.
Would be nice if First Alert had the command classes listed in their instruction, which I think is required for z-wave alliance certification.
If we assume they use the current Notification command class, then yes, Notification Type 0x01 (smoke alarm) with value 0x04 for a "Replacement" alert (class version 5), in version 8 they added an end of life replacement alert as value 0x05. Also have type 0x02 (CO Alarm) with type with the same values for a CO alarm.
problem is hard to test.. i just found out what the non zwave plus alert was for eol.
but none of the zwave plus probably have hit eol yet.
Yeah only a dev would know if the driver supports that event or not...
Hmmm... I know you can send zwave commands from PC Controller. I wonder if I could set my USB stick to that driver and then spoof some notification events from it just for fun? Maybe another day, I will set a reminder.
2 Likes
EOL is only for CO and CO combo detectors, no?
As far as I know all smoke detectors have EOL alerts now also. A lot of battery ones also have built in 10yr non-replaceable Li-ion batteries as well. Supposedly they say the detection methods weaken or wear out but in reality science says that would take much longer to happen on any significant level, even for the ionization detectors. Sounds more like a CYA thing to me so some 25 y/o detector that has failed doesn't cause someone to die due to not being alerted and then the family sues the manufacturer.
1 Like
Or longer - as long the electronic components of the alarm stay ok. The americium-241 isotope itself has a half-life of >400 years.
3 Likes
And that's not even considering the photoelectric type.
2 Likes
Thanks for starting this thread. Finding the source of the chirp at 4:00 am this morning was almost as hard as figuring out what error type 14 means... It's helpful.
I thought I purchased this unit in 2020 direct from Amazon (I have order history) but the date on the back is July, 2014...
Anyway, I guess it is EOL according to error code.
1 Like
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
