I have a white-only Wifi LED controller. It fails initial discovery but if I manually create the Thing via file, it’s then shown as “Online” in the Paper UI.
But I can’t get it to turn the LED strip on. I’ve tried all three protocols with no luck.
OK, some more developments … I used tcpdump on my OpenHabian Pi to watch the packets that OpenHAB is sending.
Turns out that using the Fading option in the driver meant no packets were sent at all for dimming changes! Switching to Classic fixed this.
I added a Switch on the power channel and now can turn the strip on and off successfully. But dimming still isn’t working correctly.
Any selection on dimming turns the strip on, but no further dimming change makes any difference to it. According to the MagicHome app, the strip is on at 38%, no matter what I select in OpenHAB.
For configuring the Thing, I’m now just using the “WiFi LED” binding with the LD382A protocol and the “Classic” device driver option. The difference in the last byte doesn’t seem to matter.
For configuring the Item, I just have a Dimmer Item that’s linked to the Color channel on the Thing. That dims all colors, so it doesn’t matter that the White and Red channels are cross-wired.
The only issue I still have is that when turned off the WiFi LED binding sets the dimmer to zero - unlike other dimmable devices which retain the dimming value but just set status to Off. I’ve tried to resolve this with a separate UI Item and a device Item and some Rules, but I haven’t had time to get it to work properly yet.
I’m using the same configuration for my items, Dimmer and Power Switch, and it’s working. I even don’t have your issue with the dimmer set to zero.
But after a short time period, sometimes seconds, sometimes minutes, the device goes offline. I really mean offline, it even doesn’t respond to pings.
When i disable the thing in openhab it stays online for days and works with the MagicHome app as expected.
So i tried to set pollingPeriod to 0 and disconnected all channels. After a short code review i think there should be absolutely zero trafic between openhab and the device now. But after another two hours it was offline again.
Maybe i just got a defective device. Another one is already in delivery. If you have another idea, just let me know.
It’s always possible that there’s a further refinement in the protocol in later devices.
You’d need to get your hands dirty with WireShark while using the MagicHome app to see what that’s sending and whether there are any material differences.
