siclark wrote:I did do a soft reset but per the instructions, using I1
Yepp the manual states that I1 must be used when not connected to 24VDC. However, I think that is only for safety reasons so that users do not handle the unit while connected to lethal voltage levels. I prefer to use the Service button (S) since it is more precise. Has worked MUCH better than using I1.
siclark wrote:I do see I3 changing the device state icon on the GUI and on the log so appears to have worked correctly.
Ok cool then we have at least verified that your device is set up correctly with I3 notifications shown in Indigo GUI and debug log.
siclark wrote:I have 2 dimmers and I want to connect I3 on one dimmer to relay endpoint 1 and I3 on the other dimmer to relay endpoint 2.
He he I think I finally have your goal with this setup all clear now.
siclark wrote:I dont see anything on the associations change when I follow your reset associations and then try and do the correct associations. I only have
Associations: 1:[1] 2:[] 3:[] 4:[1] 5:[] 6:[] 7:[] 8:[] 9:[] 10:[] 11:[1]
Config Values: 1:0 2:0 3:0 4:0 65:100 66:3 20:1 21:1 30:0 100:9 101:9 110:32536 120:5 60:1 61:99
even after doing 0x8E 0x01 0x08 0x00 0x12 0x02
However if I do normal associations, then I do see node 18 appear in association group 8 and it works, just it controls both end points..
A you say, I wonder if the multi-channel association command could be different on the newer firmware?
Are you sending the raw command "0x8E 0x01 0x08 0x00 0x12 0x02" to your dimmer device that has node 21?
Indeed if you can create a normal association that shows up in the associations list but not when yo do the raw command I really start to suspect differencies between your and mine firmwares. I am not sure if this is an issue with different firmware on the dimmer or the flush relay or even both.
Can you check on the back of your both devices what HxSyPz numbers you see on both of them? I´ll check mine when I am back at home.
Maybe you just need a different raw command in order to create the association properly with your newer firmware and maybe you can contact Qubino and tell them that the raw command above works for others with older firmware while it does not work for you. The might be able to tell you what raw command you should send.
@Matt: Do you have any idea if there is a difference in multi-endpoint capsulation on these devices? I have a small sense of talking about these differences when we were debugging Qubino devices problematic end point differences when syncing in them into Indigo.
Aaaah found the post in the OpenZWave GitHub now! Very interesting to read!
https://github.com/OpenZWave/open-zwave/issues/976 I am not sure if this explains your problems but it indeed could.
At least there IS a difference in how Qubino handles multi-endpoints depending on what firmware the device has.