I’ve got one of the Ecolink fire & CO alarm detectors.. It works pretty well, except when you test the smoke detectors, the “CO Detected” alert gets stuck. This means that every time I restart the ZWave server or HA Core, I get an alert that there’s CO detected in the house.
I found this thread from the SmartThings community. They have 2 suggestions. One is to try to trigger a CO alarm separately, but I haven’t been successful in getting this to work (and I don’t have a dedicated CO detector anymore, or at least can’t find one). The second is to set the value in some software that appears to be exclusive to SmartThings.
Is there a way to forcibly update this value in ZWaveJS? I tried using the zwave_js.set_value service, but that just threw an error (probably because it’s not a settable value). I’m pretty sure I had the right parameters (it should be targeting 10-113-0-2 for this property on node 10).
I’m not even sure the property is getting stuck in the node, or if it’s stuck in the hub, or it’s a software thing.
Of course, I get it to work as soon as I finish posting.
I ended up having to re-interview the node (and wake up the device). This fixed it within ZWaveJS, but then I had to restart ZWaveJS to get the update to show up inside HomeAssistant.
I’ll leave this here in case anyone else gets stuck like this. Or, maybe, there’s a better solution out there.
Thanks for posting the workaround. Landed here after running into the exact same issue.
One strange issue I noticed after the re-interview, the CO alarm cleared however the temperature sensor became unavailable in HA and disappeared from zwave-js. To fix this I had to:
docker-compose.yml restart zwavejs2mqtt
Then: re-interview the node again using the zwave console (and remove the cover and push the button once to wake it up), and after the interview completes and the temp sensor shows in the zwave-js console, finally reload the zwave integration within HA