How do you use z-wave read switches

Hi,

I have a couple of Qubino Flush 1D devices, one for my garage door, one for my front door. I can get the devices to work fine in terms of turning on the output and a timer to default turn them off again without any issues. Everything is running in 24VDC. The problem I have is I have read switches on each door which are wired to the I2 switch inputs on the devices, they're negative switching (which is the 'live' terminal). I've configured the parameters on the switches ok and I can see in the z-wave debug log that open and close of the door is indeed causing an event changing the value from 0 to 255 and back again but I can't seem to see this status in Indigo anywhere other than the debug log, for example the 'on state' in the device details remains 'off' regardless of whether the door is open or closed.

I'm wondering if I'm not using the switch correctly in Indigo.

From the log:

Code: Select all

23 Jul 2022 at 9:04:26 pm
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 23 03 30 03 FF 1E
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 035, endpoint None, value 255
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 23 09 71 05 00 00 00 FF 07 08 00 5A
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 035, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708

23 Jul 2022 at 9:05:16 pm
   Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 23 03 30 03 00 E1
   Z-Wave Debug                    . .  requestBinarySensorStatus: node 035, endpoint None, value 0
   Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 23 09 71 05 00 00 00 FF 07 00 00 52
   Z-Wave Debug                    . .  requestAlarmSensorStatus: node 035, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
   Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700

Screenshot of UI attached.

[matt (support)]

That particular module can be a bit finicky from my notes. Have you enabled the Input 2 notifications checkbox in the device settings? Note after doing so, based on the manual, you then need to exclude, re-include, and re-sync it with Indigo.

Hi @Matt,

Thanks for the reply.

I did see that also and tried it myself by setting configuration parameter 100 to 9 (which it was on already). I then excluded then included. After all that I noticed the device number went from 34 to 35 as you'd expect but the settings had all reverted to default values. Exclude means 'using the controller, put it in exclude mode, exclude the device, then put the controller in inclusion mode and re-include it' right? Am I missing something here?

[matt (support)]

It doesn't surprise me that excluding reset the settings, but it should also have put the device into a different mode where Input 2 notifications are now sent. Is that not working now? What if, since you've done the exclude/re-include, you now change the Input 2 notification setting back (to enabled) again? Does it then work?

If not, then re-sync the device in Indigo and copy/paste the Event Log window results into a reply for me so I can see how the module is reporting its capabilities to Indigo.