Zwave multi-channel association

Posted on
Fri Oct 20, 2017 1:42 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Zwave multi-channel association

I am at work now so I can't access my development Indigo environment from here (need to set up that... 8) ).
I will post my device info later tonight Swedish time.
(Yours looks ok though when comparing to some older logs from my devices that I found in other threads.)

However it is important that you check what your firmware marking on the device itself is.
As I wrote below my ZMNHBDx 2x relay has H1S5P1 as the marking on the back and Indigo reports it as application version 4.05 and protocol version 1.02.
Any lower Sx number than S5 is a problematic device!

Read my previous discussions and solutions with Matt and others about ZMNHBDx and other Qubino devices and their problems and variations with multi-end points in the thread at
http://forums.indigodomo.com/viewtopic.php?p=135156#p135156
(Read three pages of that thread to the end and start at the post I linked to above (page 7 or post no 135156 and ahead).

My ZMNHBDx has H1S5P1 as the marking on the back and Indigo reports it as application version 4.05 and protocol version 1.02
What confuses me a little bit is that your device info below shows application version 5.00? That is why I am so keen on seeing what your device is marked with on the back.
Indigo app version 1.01 is Qubino firmware S4 or earlier = PROBLEMS!
Indigo app version 1.02 is Qubino firmware S5 and it is from this firmware Qubino changed the behaviour/implementation of association commands for multi-endpoint devices as Matt described in the thread I mentioned above. Devices with S5 firmware will work properly.

Ahh sorry, I re-read the thread above and found out that when the users in that thread received back their updated modules from Qubino they had also Indigo showing app version 5.00 so your device must indeed have the latest firmware S5 or newer. However, please check anyway and report back what is shown on the back of your ZMNHBDx.

By the way, you might have already written this earlier on but, are you able to properly control the individual relays on your ZMNHBDx from Indigo as well as via the inputs on the device itself AND if you get correct updates in the Indigo debug log?

Posted on
Fri Oct 20, 2017 11:43 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Zwave multi-channel association

Here is the device info from Indigo for my Qubino 2x relay ZMNBHDx with H1S5P1:

Indigo Z-Wave Version: 2.0.103
Node ID: 4
Model: Flush 2 Micro Relay (ZMNHBD)
Model ID: 00020051
Manufacturer: Qubino
Manufacturer ID: 0159
Protocol Version: 4.05
Application Version: 1.02
Model Definition Version: 5
Library Type: 3
Class Name: Relay Power Switch
Class Hierarchy: 04 : 10 : 01
Command Class Base: 25
Command Versions: 20v1 60v4 25v1 86v1 27v1 72v1 8Ev1 70v1 32v4 73v1 59v1 5Av1 5Ev1 85v1
Encryption Status: Not Supported
Multi-Endpoint Types: 1:(10 : 01), 2:(10 : 01)
Multi-Endpoint Classes: 1:[5E 86 25 20 27 85 8E 59 32], 2:[5E 86 25 20 27 85 8E 59 32]
Neighbors: 3
Associations: 1:[1] 2:[] 3:[] 4:[] 5:[] 6:[] 7:[] 8:[1]
Config Values: 64:0 1:0 2:0 110:32536 120:5 30:0 63:0

Only differences I see is the application version 1.02 on mine and 5.00 on yours but both 1.02 and 5.00 are considered (as far as I know) to use same type of multi-endpoint association. The problems were with firmware 1.01 or older.
You have different configs on param 1 and 2 and that should not cause the problems since those are just for what switch type you have connected to I1 and I2 on the ZMNHBDx.

And by the way, I know it is painfully but factory reset your ZMNHDD again and DO NOT enable the 3-way switching parameter yet.
So you need to do the tedious procedure of exclude the device with S button pressed MORE than 6 seconds, wait 30 seconds, re-include and re-sync, then enable I2 and I3 notifications, do the soft exclude = press S button MAX 3-6 seconds, wait 30 seconds, re-include and re-sync.... Sorry but we need to do this to check that you get inline with my setup.

Enable only I2 and I3 notifications like I have done just to verify that we can get it to work for you with the same setup that is working for me.

After this post your ZMNHDDx device info so that we can see that you get same multi-end point classes like I have on my ZMNHDDx.

Posted on
Sun Oct 22, 2017 11:32 am
CrazyFin offline
Posts: 381
Joined: Jan 08, 2015
Location: Stockholm, SWEDEN

Re: Zwave multi-channel association

@siclark:
Sorry for spamming but I had some time over and did some more testing on my dev environment.

@matt:
This is an interesting observation:

When I set I3 on dimmer ZMNHDD (node 3) to ON I see the following in the debug log:
Code: Select all
Z-Wave Debug                    RCVD multiEndPointPacket: 01 0D 00 04 00 03 07 60 0D 03 01 30 03 FF 51
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 03 03 30 03 FF FF
Z-Wave Debug                    . .  requestBinarySensorStatus: node 003, endpoint 3, value 255
Z-Wave                          received "3 - Input 3" status update is on
Z-Wave Debug                    RCVD multiEndPointPacket: 01 13 00 04 00 03 0D 60 0D 03 01 71 05 00 00 00 FF 07 08 00 0D
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 03 09 71 05 00 00 00 FF 07 08 00 FF
Z-Wave Debug                    . .  requestAlarmSensorStatus: node 003, endpoint 3, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
The 2nd relay on my ZMNHBD (node 4) properly turns ON as well but nothing is shown in the debug log and the status for relay 2 in Indigo GUI is not updated from OFF to ON.


Same thing when I turn I3 OFF on the ZMNHDD, nothing about the state change on node 4 where the ZMNBHD relay is:
Code: Select all
Z-Wave Debug                    RCVD multiEndPointPacket: 01 0D 00 04 00 03 07 60 0D 03 01 30 03 00 AE
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 03 03 30 03 00 FF
Z-Wave Debug                    . .  requestBinarySensorStatus: node 003, endpoint 3, value 0
Z-Wave                          received "3 - Input 3" status update is off
Z-Wave Debug                    RCVD multiEndPointPacket: 01 13 00 04 00 03 0D 60 0D 03 01 71 05 00 00 00 FF 07 00 00 05
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 03 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Debug                    . .  requestAlarmSensorStatus: node 003, endpoint 3, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700


I then checked the manual for ZMNBHD and read about different association groups and realised that I needed to associate group 2 for relay 1 and group 3 for relay 2 on the ZMNBHD to my Z-Wave controller (node 1) in order to get on/off state updates to the controller.
After I had set up those associations I can now see the following in the debug log:
Code: Select all
Z-Wave Debug                    RCVD multiEndPointPacket: 01 0D 00 04 00 03 07 60 0D 03 01 30 03 FF 51
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 03 03 30 03 FF FF
Z-Wave Debug                    . .  requestBinarySensorStatus: node 003, endpoint 3, value 255
Z-Wave                          received "3 - Input 3" status update is on
Z-Wave Debug                    RCVD relaySetLevel: 01 09 00 04 00 04 03 20 01 FF 2B
Z-Wave Debug                    . .  relaySetLevel: node 004, endpoint None, value 255
Z-Wave Debug                    RCVD multiEndPointPacket: 01 13 00 04 00 03 0D 60 0D 03 01 71 05 00 00 00 FF 07 08 00 0D
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 03 09 71 05 00 00 00 FF 07 08 00 FF
Z-Wave Debug                    . .  requestAlarmSensorStatus: node 003, endpoint 3, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Indigo GUI does not update state to ON for relay 2 though but as you can see above the ZMNBHD relay actually broadcasts its state change from OFF to ON

When I turn off I3 on node 3 ZMNHDD I get this:
Code: Select all
Z-Wave Debug                    RCVD multiEndPointPacket: 01 0D 00 04 00 03 07 60 0D 03 01 30 03 00 AE
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestBinarySensorStatus: 01 09 00 04 00 03 03 30 03 00 FF
Z-Wave Debug                    . .  requestBinarySensorStatus: node 003, endpoint 3, value 0
Z-Wave                          received "3 - Input 3" status update is off
Z-Wave Debug                    RCVD relaySetLevel: 01 09 00 04 00 04 03 20 01 00 D4
Z-Wave Debug                    . .  relaySetLevel: node 004, endpoint None, value 0
Z-Wave Debug                    RCVD multiEndPointPacket: 01 13 00 04 00 03 0D 60 0D 03 01 71 05 00 00 00 FF 07 00 00 05
Z-Wave Debug                    . .  multiEndPointPacket: node 003, endPoint 3
Z-Wave Debug                    RCVD requestAlarmSensorStatus: 01 0F 00 04 00 03 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Debug                    . .  requestAlarmSensorStatus: node 003, endpoint 3, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug                    . .  requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
So same thing happens here, Indigo GUI does not update state to OFF for relay 2 though but as you can see above the ZMNBHD relay actually broadcasts its state change from ON to OFF.

Posted on
Sun Oct 22, 2017 4:13 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Zwave multi-channel association

Unfortunately, I think the ZMNHBD is going to send identical relay on/off commands regardless of if relay 1 or relay 2 had its state changed (note the command send is not encapsulated with an endpoint, so Indigo doesn't know which relay it belongs to). That is, Indigo isn't going go know which relay it was.

The real solution here is for Indigo to be able to manage the multi-channel associations natively. Once it does that it will know that when the ZMNHDD sends out the command that the ZMNHBD is going to respond and it can update the UI to reflect it accurately (which is what occurs with normal associations). Until Indigo supports that, I don't think it will be able to reliably update the states automatically. Workaround solution might be to trigger off of the I3 state change and have it send a status request to the targeted modules.

Image

Posted on
Mon Oct 23, 2017 7:55 am
siclark offline
Posts: 1960
Joined: Jun 13, 2017
Location: UK

Re: Zwave multi-channel association

Cheers. I'm going to leave notifications until I get the association working.

Qubino support just time me to send this command

01 41 02 11 07 8E 01 08 00 05 ->(NODE ID) 02 ->(endpoint) 58 5F

Ie using association group 8 to control node 5 endpoint 2.
Should I put the 01 41 02 11 07 bit before and 58 5F after? I don't know what they do and don't want to brick the device.

Posted on
Mon Oct 23, 2017 11:44 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Zwave multi-channel association

Indigo automatically calculates all of that. All you need is:

0x8E 0x01 0x08 0x00 0x05 0x02

Where 0x05 is node ID and 0x02 is endpoint.

Image

Posted on
Mon Oct 23, 2017 12:01 pm
siclark offline
Posts: 1960
Joined: Jun 13, 2017
Location: UK

Re: Zwave multi-channel association

Thanks. That's what I suspected. So they are saying same as you are and what worked on @crazyfin's device but not on mine.

I'll try some more testing tonight.

Posted on
Mon Oct 23, 2017 2:31 pm
siclark offline
Posts: 1960
Joined: Jun 13, 2017
Location: UK

Re: Zwave multi-channel association

Still no good. Sent this to the main device of the dimmer, to control node 28, ie 0x1C end point 2

0x8E 0x01 0x08 0x00 0x1C 0x01

Z-Wave Debug SENT sendRawZwaveCommand: 01 11 00 13 1A 0A 60 0D 01 01 8E 01 08 00 1C 01 25 05 3A
Z-Wave sent "Kitchen Spots 2" raw command [8E 01 08 00 1C 01]

Get the notification back but nothing happens

Z-Wave Debug RCVD multiEndPointPacket: 01 0D 00 04 00 1A 07 60 0D 03 01 30 03 00 B7
Z-Wave Debug . . multiEndPointPacket: node 026, endPoint 3
Z-Wave Debug RCVD requestBinarySensorStatus: 01 09 00 04 00 1A 03 30 03 00 FF
Z-Wave Debug . . requestBinarySensorStatus: node 026, endpoint 3, value 0
Z-Wave Debug RCVD multiEndPointPacket: 01 13 00 04 00 1A 0D 60 0D 03 01 71 05 00 00 00 FF 07 00 00 1C
Z-Wave Debug . . multiEndPointPacket: node 026, endPoint 3
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 1A 09 71 05 00 00 00 FF 07 00 00 FF
Z-Wave Debug . . requestAlarmSensorStatus: node 026, endpoint 3, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700

as you can see by change in device number, I tried to unpair and re sync the relay device to see if that helped, but no.

STarting to think I will have to go with holding the button down and rely on Triggers, despite the delay.

Posted on
Sun Sep 30, 2018 7:50 am
siclark offline
Posts: 1960
Joined: Jun 13, 2017
Location: UK

Re: Zwave multi-channel association

Hi Matt. I'm guessing no multi channel association in the latest release?


Sent from my iPhone using Tapatalk

Posted on
Sun Sep 30, 2018 11:37 am
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Zwave multi-channel association

siclark wrote:
Hi Matt. I'm guessing no multi channel association in the latest release?

Correct.

Image

Posted on
Wed Aug 21, 2019 5:28 pm
7rdr7 offline
Posts: 163
Joined: Aug 16, 2017
Location: Washington DC Metro

Re: Zwave multi-channel association

Hey Matt,
Any update on the multi-channel association support, specifically in my case for the Qubino ZMNHBD? My ZMNHND units work fine and record the input state changes, but the ZMNHBD does not.
Thanks, Ron

Posted on
Wed Aug 21, 2019 8:20 pm
matt (support) offline
Site Admin
User avatar
Posts: 21411
Joined: Jan 27, 2003
Location: Texas

Re: Zwave multi-channel association

Definitely still on my wish/ToDo list, but first we have to get the 64 bit version of Indigo wrapped up.

Image

Posted on
Thu Aug 22, 2019 7:33 pm
7rdr7 offline
Posts: 163
Joined: Aug 16, 2017
Location: Washington DC Metro

Re: Zwave multi-channel association

Thanks for the quick response Matt. Understand that 64 bit is a high priority. I know that you guys are not big Qubino fans, but these modules have a number of unique capabilities. Appreciate it being on the to-do list.

Posted on
Thu Sep 05, 2019 1:15 pm
koburg offline
Posts: 167
Joined: Jul 27, 2017

Re: Zwave multi-channel association

I hope the multi channel association will be supported in near future

I got some very cool new 4 button devices

they can show the other devices state with the led

example:
so if device 1 button 1 is turn on then the associated button 3 on the device 2 will show the new state with light on the button will turned on and vice versa.

but I need the multi channel association to get it to work and don't know how I should do this with raw commands.

Posted on
Fri Sep 13, 2019 11:04 am
howartp offline
Posts: 4559
Joined: Jan 09, 2014
Location: West Yorkshire, UK

Re: Zwave multi-channel association

Ooh, sounds a good device. What is it?

Interested in this so may help with Zwave commands for you.


Sent from my iPhone using Tapatalk Pro

Who is online

Users browsing this forum: No registered users and 2 guests

cron