I suspect it’s directly linked to the association groups - I’ve not looked at the manual, but from the configuration there are different association groups for different classes. If you use the binary switch ones instead of the toggle switch ones, I would think it would change?
Could this have to do with the Endpoint not being correct? I think the version currently being used the Endpoint 2,3 and 4 was a not defined at that time.
That won’t matter if you use the binary switch command class - it will only matter if you use the basic command class. In this case, @Robert_Jensen is using the toggle switch command class so it also won’t matter (but as above, it also won’t work as the command class is not supported ;)).
If I want to controle my Cord Switch on a radio I can controle it from my FUGA when I link the Cord Switch node from the FUGA Association Groups, but not the other way around because I cannot select a specific button on the FUGA node…
I have tried to use groups in the item configurations but syncing the state og my HUE bulb and the LED on the FUGA contact is still wonky…
So far the zhc5010 is only supported for firmware version 1.03 and below in OpenHAB 2.0.0 but if you try the nighty build if will work.
@chris I think we can delete the lower version of the configuration for zhc5010 and just go with the version above 1.04 and make it work for all versions.
The two devices seem to have quite different parameters. Are you saying that the 1.3 version is wrong and it should be the same as 1.4 (ie all the parameters are the same between the two versions?).
If this is the case I’m just wondering why someone added the extra version - I thought it was because they were different?
I was the one who added it - beginners mistake - sorry. But the 1.3 version was incomplete, and I was afraid to mess it up as this was the first time I tried to configure a device.