Did anyone tried to trigger the zcombo with smoke? This thread helped me get things going and I can see that smoke alarm channel getting triggered when test switch pressed but when I actually let it off using a candle smoke, there was no triggers. Did I miss something? does anyone know how to debug it?
I tested it once a long time ago and it worked. Iāve not tried testing it in OH 2 but it seems to me that if it works when you trigger the alarm test it should work with actual smoke.
But in my experience, these smoke/CO detectors are not feature rich nor reliable enough to rely upon the zwave triggers for anything. If you really need that you would better off selecting a different alarm. Lots of people love the Fibaro alarms.
Thank you for the quick reply. I was planning on using this to turn off the outlet that powers the 3d printer. I have heard enough horror stories that I dont want to leave the printer running for 24/7, unless I rig something to notify and to prevent damage. Im going to do more digging and if it is not working as it intended. Iām going to send it back. There is no value in buying zwave smoke detector if it is not triggering the zwave channel when there is a actual fire . I do have a fairly new device, manufactured in may 2017. Hardware could be slightly different.
@derfNamttog Yes, I have the ZCOMBO working in both 2.3 and 2.4. For me, it included fine and was recognized as the āZCOMBO Smoke and Carbon Monoxide Alarmā. Iām curious if (a) you ever got your ZCOMBO to initialize and work normally, and (b) if you tried excluding the ZCOMBO from your ZWAVE network and then retried the include?
To elaborate on it āworkingā, I have the 4 switches (smoke, CO2, test, heartbeat), and number battery percentage. To note, the battery value did not first appear until I performed the alarm test. Apparently that woke up the device to send a report.
Perhaps I could be of more assistance if needed. Good luck.
Finding this thread now since Iām in the process over move over my whole ZWave house over to OpenHAB from SmartThings after briefly touching on Home Assistant and OpenZWave.
I think Iāve tried every trick in the book but the ZCOMBO seems to get stuck on initialization. Iāve tried excluding and including it probably 20 times now. Iāve tried waking it up with the battery-out-button-down-battery-in method outside of the inclusion window but the zwave log keeps saying itās either stuck in state MANUFACTURING or NIF_FRAME as seen below. Any ideas here?
This is after I wake up the ZCOMBO but outside of the include window:
I woke the unit up over and over and over again, usually about 20 times each time I tried, for a week to no avail. I would wait about a minute between each wake before trying again.
Eventually, I decided to watch the log update live, using tail, and just wake the unit over and over as fast as I could instead of waiting between wakes. Using this method I could see the unit advancing through the intialization in the log. I think it would take between 5-10 rapid fire wakes to get through each phase of initialization.
I donāt know if itās the proper way to do it but itās the only way I could get both my units working. Just be careful not to break off the battery door.
Well Iām almost numb trying this but I think openHAB has changed since this trick worked. I saw a discussion on the ZWave addon repository that @chris is considering updating the timeout when adding devices. My issueis that WakeupTimerTask 1 Messages is just not willing go forward past the MANUFACTURER state and it doesnāt seem like the ZCOMBO is sending messages of that type.
Me tooā¦ I submitted log files to @chrisās website, but heās been busy. Rapid wakeups did not help. Iām past the return period now and antsy to get this working, so Iāll probably hack the XML with the needed data. Could someone please provide an XML from an initialized device?
Hmmmm. Iām pretty sure it is communicating. Itās showing as online right now and I have a Rule that will send me an alert if the heartbeat channel doesnāt report after a couple of days. I just checked my persistence and the last heartbeat from the device was about two minutes ago.
I just did a sampling of my other node.xml files and they all are showing a lastReceived from September. But everything is working just fine.
When I upgraded from 2.3 to 2.4 and recreated my Things in PaperUI, I did not delete the node.xml files. So perhaps these are the old ones. Looking at the dates and they do have Sept dates on them.
Wait. Grrrr. The new XML files have a different name.
OK, here it is again just in case there is something missing from the old one.
Data point:
I could not pair my two Z-COMBOs last month and I think I tried 2.4, 2.5.0.M1, and 2.5.SNAPSHOT. My fingers were raw trying to pair them and wake them up during the various init stages. They were both seen as devices but stuck as āUnknownā and could not make it past an early init state.
Today I paired that same two using SNAPSHOT #1561 and it was flawless. One try for both and they are working great.
Sorry to bump this but new user here ā¦ I just factory reset a bunch of ZCombo units that were connected to SmartThings for long time, HomeSeer more recently - worked fine on those platforms. Iām trying to add them to OpenHab and no luck ā¦ is there a trick that works? I have added other devices so far (all z-wave) without much challenge but these have me stumped ā¦ thanks! Iām on latest stable installed this morning FYI.