In other words…the Scene Controller, using it’s Lifeline association to the Primary Controller may likely use that association to tell the Primary Controller that Scene 1 is active…or Scene 1 and 3 are active, and constantly update that when it activates or de-activates it’s “own” scenes. Or to your point…because it is not a ZWave+ device, it actually probably doesn’t use the lifeline to update status to the controller, and very likely any mandatory binding to Node 1 is irrelevant on this device in any kind.
I think it is very likely that forcing an association within each of the controllers individual Scene Association Groups is very likely breaking the ability for the Scene Controller to Control it’s own scene properly…and by that I am implying that Associations Groups for each possible Scene are not the same as Associations of the Scene controller device. Scenes are not devices. Scene do not give status updates to anything. There’s only one device, but multiple Scenes. If anything, the device needs to be associated to a lifeline, not the individual Scenes. The Scene Controller monitors and listens to all status updates of all devices in “Association Group 1” and compares the actual set value of each node within group 1 to the value commanded in the Scene Controllers stored scene programming for Scene 1. For example, Node 22 dimming value at 50%. If any of the actual device reported set values do not match, then the Scene becomes deactivated automatically by the Scene Controller itself with no reliance on the Primary Controller Node 1…but not shut off. It assumes that a user manually adjusted one of the nodes or it was adjusted by some other controller other than itself, so the Scene controller essentially gives up trying to control the Scene. If on the other hand, someone set all of the nodes manually and those set values matched all the preset programmed values that existed within the Scene Controllers stored programming, then the Scene Controller lights the LED up for that Scene and starts controlling it again.
When we force Node 1 to be within the Association Group, then what is the programmed commanded value of Node 1 within the Scene Controller? And what is the reported set value of Node 1 in response? What Command is it trying to use…Node 1 is not a device…it probably doesn’t have a Set value that it could respond with? Then add on to that…if it did have a set value to respond with…then is that set value different when the Scene 2 button is pressed as opposed to when Scene 1 is pressed? If it is different, then Scene 1 is now broken the second we press Scene 2 because the set value of Node 1 changed and therefore the Scene Controller disables Scene 1.
There is one more thing I thought of trying tonight…if in fact there is a reported set value from Node 1, and if that reported set value doesn’t change between Scene 1 and Scene 2 activation, then maybe I can find a way to program the Scene within the Scene controller with whatever value so that it doesn’t disable the Scene. I think this is a pipe-dream to work, but I gonna try anyways.
I may be out to lunch…and you can feel free to tell me so! I am enjoying learning!