Z-wave Alarm Command Class -not available

Calin Birtocean

8 years ago
updated 8 years ago
Under review

Hi,

I have installed and added to Z-wave node the Carbon Monoxide Detector, ZCOMBO from First Alert.

Based on the manufacturer manual the following command classes are supported:

• BASIC

• BATTERY

• CONFIGURATION

• ASSOCIATION

• ALARM_V1

• MANUFACTURER_SPECIFIC

• VERSION

When integrated in bOS I do not see the Alarm Command Class being available. Here are the parameters that I am looking for to monitor:

Alarm Alarm Type Level

Smoke Alarm 0x01 0x00 or 0xFF

CO Alarm 0x02 0x00 or 0xFF

Malfunction Alarm 0x09 0x00 or 0xFF

Test Alarm 0x0C 0x00 or 0xFF

Heartbeat Alarm 0x0D 0xFF

CO Sensor End of Life 0x0E 0x00 or 0xFF

I was assuming to find all the alarms under "Notification" class command, but only the following are available:

The values are not changing when the Test Alarm is active(the test button is pushed).

The Battery value has changed, that's how I know the device is communicating.

The device is Associated to Controller 1.

Could you please advise if the alarms can be monitored in bOS?

Thank you,

Calin

Replies 16

Oldest first
Newest first Oldest first

ComfortClick Support

8 years ago
Under review

Hello,

which version of bOS are you using? You could try updating to the latest beta version where additional settings have been updated with our z-wave driver. Sometimes inclusion process doesn't complete correctly, causing some missing commands so try excluding and including the device again, you can also try to delete the device from the list and waking the device again, check if the association groups are set correctly (z-wave controller under lifeline)

Best regards,

Reply Link

8 years ago

Also, did you check if the Basic values change when alarm is triggered?

The server version is 4.4.1, I've tried including and excluding the device several times.

The device is association to group 1.

When the alarm is triggered the Basic and Notification values are not changing. Only for the battery I have seen a change in value.

Regards,

could you please check Debug log while triggering the alarm so we can see if the device is sending any information.

In your bOS open Logs, select Debug tab and click the Record button, then try triggering the device and see if the device sends any information.

Thank you for the tip for using the Debug tab, it is very useful.

When pressing the test/silence button the battery value is the only one received:

When the actual alarm is triggered there is no information received, not even the battery value.

Is there anything that can be checked? Or should I assume that the device is malfunctioning.

this is quite strange that the bOS does not receive any information regarding the alarm, if this was a newer device with new classes which bOS does not support we could implement them and the device should be working, but since it's an older device, which contains all the classes and options that are implemented in the bOS the device should be working normally. Is there any additional parameters you can set to receive information about the alarm?

Best regards.

I tried everything, but still doesn't work. At this point I am assuming the device is malfunctioning. Trying to order another one soon....

I have tested another brand new unit and I am getting the same results.

When the smoke alarm is triggered the bOS doesn't get updated. The values are not changing when the Test Alarm is activated (the test button is pushed). The only value changing is the Battery value.

Would you please take a look at the controller settings and confirm that this device(ZCOMBO) is supported in bOS.

Here are the debug logs:

2018_03_27_ZCOMBO Exclusion_Log Debug.txt

2018_03_27_ZCOMBO Inclusion_Log Debug.txt

2018_03_28_ZCOMBO Test_Silence Button Pressed_Log Debug.txt

2018_03_28_ZCOMBO Smoke Alarm Triggered_Log Debug.txt

The specification for the class commands supported is here:

Z-wave Smoke_CO detector 83852.docx

The server version is 4.4.1, the controller 1 is associated to group 1 .

thank you for all the additional information you provided, we've updated our software to support these devices and a new BETA version will be available soon, which should resolve the issues you're facing. I will contact you as soon as it's available.

Could you please advise if the device was supposed to be supported in server revision 4.4.2? I tried it but still doesn't work with the device.