Is there any answer to the original question ?
Does it work now ? (I’m looking to get one of those, too.)
Do you know of any alternatives ? I know there’s the Vision Security (but it can only detect CO, not smoke),
and I read about a Popp 4407 to do CO/temp/humidity, but it is not available any longer, so Popp told me.
It works, at least a test run works, so the rest is up to the sensor. It reports the event and the clear, as well as battery health when the test is run.
I had purchased one of the ZCOMBO devices too and was unable to get it to work last Fall. Thought I’d take another try and found this thread. Glad to see it’s working now, but not sure what I need to do to get mine working.
Downloaded the current addons snapshot and replaced my zwave binding with the new one.
Restarted openHAB and launched habmin and it looks like it did before. The Z-Stick is green and the unknown node 2 (zcombo) device is greyed out.
What do you mean when you say Do the binding sequence again without the controller in bind mode?
Perform the z-wave binding sequence as documented in the manual, but do not put the controller into include mode.
Basically, pull the battery tray out, hold the test button down while you slide the battery tray back in, and keep it held until you hear the beep. This causes it to wake up, and you should have a XML file at that point.
Does someone have the .jar file that works with the zcombo device? I tried the latest daily snapshot but marked as 1.9 and zwave services don’t start in openhab 1.8 with that binding in the addons folder. Currently using the 1.8 snapshot file but just get the generic information.
If you’re using a recent 1.8 snapshot, or 1.8 release, then this should be the same as the 1.9 snapshot and I believe it should have the code that initialised based on the NIF frame (ie that should work with the ZCOMBO).
Thanks, downloaded the addons package again and moved the .jar file over. Must be newer than the .jar i previously had that habmin showed as version 1.8.0.201508211938 (probably came from apt-get repo).
Did the battery remove/reinsert and it came right up.
To others using this device what are your item settings? I currently have:
Number zcombo_basement_battery “Basement Battery [%d %%]” (Smoke, Basement_Smoke) {zwave=“17:0:command=battery”}
Contact zcombo_basement_smoke “Basement Smoke is [%s]” (Smoke, Basement_Smoke) {zwave=“17:0:command=sensor_alarm,alarm_type=1”}
Contact zcombo_basement_co “Basement Carbon Monoxide is [%s]” (Smoke, Basement_Smoke) {zwave=“17:0:command=sensor_alarm,alarm_type=2”}
At first I got a battery status for a while, but since then it has gone away and I haven’t gotten any other status. Is that normal? The indicator in the zwave binding area is not green but gray, guessing that means it hasn’t woken up in a while?? How often does it report status, or does it just not report anything until an actual alarm is triggered?
I just triggered one of my zcombo’s to generate the node.xml file and upon review of the generated file it looks like this device does not support the alarm_sensor command class, only the alarm command class.
{zwave="5:command=alarm"}
It isn’t clear what you get with this command class. I’ve simply bound it to a switch and I’ll experiment from there. But the big take away is that I don’t think we can distinguish between a CO2 alarm and a smoke alarm. We can just tell if the alarm is going off.
I must have tried this 10 times without success. Attached is a screenshot showing the latest bindings are installed. I did the battery slide trick while holding the test button and did hear a beep. I have a couple grayed out nodes, which I assume are failed bindings attempts (wish I knew how to delete them) when I had put the controller in include mode. How can a new node get included without using the include mode on the controller? I also tried without putting my Z Stick in include mode, and did not see anything happen. Anymore tips? Thanks!
So the gray node means included but sleeping? If I slide the battery in and out should it turn green? Anything I have to do in OpenHAB so that the wake up event is detected? Its gray and always gray. Thanks!
I read in this indigo link its very tricky with the timing. Is there way I can force a quick “sync” on OpenHAB? My concern is that on start OpenHAB is not syncing in time.
With the zsmoke it appears you have to push the button on the z-stick first then hold the test button on the zsmoke as you slide the battery tray in. You will see the z-stick do its flash thing and then you have 30 seconds to run to the computer plug the z-stick back in and then add and sync the device in indigo. It only stays awake for 30 seconds (it beeps once when it leaves the awake state) which makes pairing the device in its final resting place a little difficult.
Nothing that complex here. If it has included to the controller, that is all you need. If you want to speed up the process of it coming online, then you can go through the wake-up proceedure a few times, and it should eventually go green. Else, just wait. It will wake on its own and go green eventually too if it is included.
Sorry to revive an somewhat old thread. Ive read through all of these a few times. I’m running the 1.8.3 bindings. I still cant get the Zcombo working right. Ive got it paired to the controller so that it is showing habmin and is grayed out. I do the wake by sliding the battery tray and pushing the test. I can see a ton of information flowing in the logs.
A refresh of HABMIN turns red. pushing test on my detector show no new information in the logs.
Same issue here. I have 3 of these things and despite multiple variations of trying to get this thing to work I can not get the device to send an ID to habmin, and thus it’s zwave functionality is useless. I can only get a gray icon without a name. Oh well. Probably worth looking into a different smoke detector if you want zwave functionality.
If anyone who is having trouble is curious I finally got this device connected. Not sure if it was the update from 1.8.2 to 1.8.3 that did it or what.
Make sure the Zcombo isnt already included in the network from previous failed attempts. Exclude it for good measure and delete the dead node if its there.
Include on HABmin. slide battery tray out and then while pushing in hold the test button till it chirps. Let the include timer expire. then slide the battery tray out and in while holding the test button a few a more times. I had to slide the tray in and out about 4 times. You can see the flurry of activity in the logs. its green now and working.
