Now I have whiteLed (possibly) working with the v6 bridge. At least in the log I can see that commands are sent to the bridge
09:44:28.782 [DEBUG] [internal.handler.AbstractLedV3Handler] - milight: dim from ‘14’ with command ‘42’ via ‘3’ steps.
09:44:28.786 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '35 00 55 ’ to bridge 192.168.1.112
09:44:28.892 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '3C 00 55 ’ to bridge 192.168.1.112
09:44:28.998 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '35 00 55 ’ to bridge 192.168.1.112
09:44:29.102 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '3C 00 55 ’ to bridge 192.168.1.112
09:44:29.211 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '35 00 55 ’ to bridge 192.168.1.112
09:44:29.323 [DEBUG] [.milight.internal.protocol.QueuedSend] - Sent packet '3C 00 55 ’ to bridge 192.168.1.112
But unfortunately this does not lead to any activity between the ibox2 and the lamp itself (I am sniffing the radio with rflink). At the same time, android app still works fine and rf link happily sniffs packets like
I would like to avoid installing full-blown openhab development environment, maybe someone can point me to some minimal changes to the code to solve the problem?