z-wave water detector- Controller 1 cannot be set to Association Group 1

Hi Calin,

Have you tried waking up the device?

Hi Jure,

Yes, I tried also waking up the device.

Regards,

Calin

Could you send a debug log. 

Also, can you set the parameters on the device?

Hi Jure,

Please find attached the debug logs. I tried excluding/including other z-wave devices(switches) and they work fine.

2018_04_18_Water Sensor_Exclusion_Log Debug.txt

2018_04_18_Water Sensor_Inclusion_Log Debug_1.txt

2018_04_18_Water Sensor_Inclusion_Log Debug_2.txt

Thank you,

Calin

From what I can tell the logs look ok.

Could you also send me a debug log when you wake up the device?

Hi Jure,

There is no traffic seen under debug tab when trying to wake up the device.

I think the issue is related on how the device is integrated into bOS.

When I include the device in bOS , the only value which updates is the battery even though the Controller 1 cannot be set to Association Group 1. The z-wave USB dongle used is the Z-stick Gen5.  As I mentioned before, I have tried several times to restore the sensor to the factory default settings, include, exclude, delete then click discovery, soft reset the controller, wake up the device, run Refresh Configuration from the Functions tab in order to set Controller 1 to Association Group 1. 

1) After including the water sensor using bOS:

that's how the configuration looks when opening the z-wave network using the zVirtualScene(used for comparison).

2) If I include first the device in zVirtualScene, here are the class commands and values available:

The value changes when alarm is triggered:

Opening now the z-wave network in bOS after including the device using zVirtualScene, there are no class commands available:

BUT, using the debug tab the sensor value gets detected, it doesn't recognize the node:

Also, waking-up the device:

If this gets fixed into bOS then I guess it will solve the other ticket that I open regarding the z-wave ZCOMBO (CO & smoke detector) https://support.comfortclick.com/communities/4/topics/1493-z-wave-alarm-command-class-not-available

Best regards,

Calin

Hi Calin,

Thank you for the extensive report.It's very strange that the module does not send a wakeup frame. Looks like this issue is module specific. We will try to order the device, they don't to be sold in the EU.

So just to confirm.

Water sensor you're using:

https://products.z-wavealliance.org/products/1788

and smoke/COsensor:

https://products.z-wavealliance.org/products/862

Hi Jure, 

Yes, these are the sensors.

Regards,

Calin

Hi guys, do you have any updates on this? 

Thanks,

Calin

Hi Calin,

Sorry for the long delay. We just received the water sensor today. We had no issues setting the controller to Assoc. group 1. I'm not sure what could be the problem. Please check again if you have the latest version of bOS. 
Unfortunately we couldn't get the CO sensor for the EU. If you have any suggestions where we could buy one please let me know. 

Best regards 

Hi Jure,

Thanks for your feedback. I just uninstalled/installed the latest version 4.4.2. the server -bOS Service Monitor and also the bOS Configurator. I tried to exclude and include again the water sensor and I am having the same issue, the device is not properly integrated and cannot associate to the Group 1. I can share the project configuration if needed for further investigation. Would you be able please to share the screen shots with the device included in the network? I have the server installed on a Windows 7 64-bit, don't know if this makes a difference. Regarding the CO detector, if the issue gets solved with the water sensor I think the other one is the same so don't bother ordering it.

Regards, 

Calin

Here's the screenshot. I tested with the current release and the beta version. Both work without problems. I added the controller to assoc group #1 and woke up the device with a triple click. 

You can send us your config and we can check just to be sure. Please open a new support ticket (see top of page) and upload your config there.

Hello,

apologies for the delays, the devices were ordered and are yet to arrive, as soon as we get them we will implement them into bOS and they should be working normally.

Best regards.