Greetings -
Recently started setting up my Z-wave enabled home with a few device to start; some LED lights, toggle switches, door lock, and smoke / CO detectors. Everything was simple to pair with my RaZberry / Z-way device with the exception of the CO detectors (First Alert ZCOMBO-G).
After going through the standards pairing procedure (remove battery tray, depress test button, insert battery tray, release after first beep) numerous times, I would see in the expert UI that it never cleared the "Basic" capabilities checkbox. So... right or wrong (probably wrong), I edited the settings file and set 0x20 for that device to not supported. Now in the expert UI it states that the interview is complete. Note that I did try at least half a dozen times the standard way, and then for my final iteration, I reset the interview process, set 0x20 "Basic" to not supported in the file (stopping and starting the service in-between), then forced each subsequent interview after waking the device in hopes that this would trigger the Alarm devices to be created in the normal UI... it did not.
In the logs, every hour I see a message from the ZCOMBO-G device (devices.6 in my setup) for a V1event.alarmType = 13, at a value of 255. Guessing this is just a heartbeat.
Upon pressing the test button, I get a V1event.alarmType = 12 at level 255. Applying smoke from igniting a match or three causes the alarm to sound, and an V1event.alarmType = 1 with value 255 to appear in the logs. After a few minutes, I get a V1event.alarmType = 1 with a value of 0... So, notifications seem to be getting to my device without a problem.
The challenge I'm having, is that in the regular UI, there is no "Alarm" for device 6. In fact, there is no device 6 anywhere in the default UI (though the I would guess that this has something to do with the way that I forced the interview process to complete). It IS in the expert UI, however. Given that there isn't really anything we can SEND to these devices, and the alerts are coming in OK, what I really want to know is ---
How do I set up alarms for this device that doesn't show up in the regular UI, so that I can act on these events?
I appreciate any insight / info on next steps.
First Alert ZCOMBO-G - Acting on alerts
Re: First Alert ZCOMBO-G - Acting on alerts
I'm not able to shed any light on your issue, but please share on this thread if you figure it out on your own.
I am also setting up Z-way at the moment, and one of my smoke sensors from a different brand behave like you describe (some different values though), yet no "sensor state" in the smarthome UI. Mine completed the interview though, so that is probably not the issue.
I am also setting up Z-way at the moment, and one of my smoke sensors from a different brand behave like you describe (some different values though), yet no "sensor state" in the smarthome UI. Mine completed the interview though, so that is probably not the issue.
Re: First Alert ZCOMBO-G - Acting on alerts
So I still don't know how to do it the "right" way. What I've done to solve the problem, which is more round-about than anything else, is to create a workflow like this:
Z-way -> Log file -> Log shipper -> Graylog -> Drools -> DB -> Trigger Z-Way API Action
The items in bold were already in place, so I was really only only adding a log shipper, and an external way to trigger the Z-Way API. I'm not suggesting this as a GOOD solution, just what I used to solve the problem.
I would very much like to know how to create (manually is fine) an alarm based on existing devices so I could avoid the added steps.
Z-way -> Log file -> Log shipper -> Graylog -> Drools -> DB -> Trigger Z-Way API Action
The items in bold were already in place, so I was really only only adding a log shipper, and an external way to trigger the Z-Way API. I'm not suggesting this as a GOOD solution, just what I used to solve the problem.
I would very much like to know how to create (manually is fine) an alarm based on existing devices so I could avoid the added steps.