I am using several Yeelight devices for many months now. Now, integrating a new Yeelight stripe failed.
After some investigation I found, that they obviously upgraded the stripe to some extent. The new stripe type says “strip6” as the model instead of “stripe”, what the old model was.
Switching on debug logs for the yeelight binding resulted in this:
jimSelf - unfortunately there is no other way around this problem, only code change. I have made the changes locally in my environment as I got the same led strip, but unfortunately it does not work as I would expect i.e. comparing to other Yeelight lamps I have at home. What I mean by this is that it will not work in your local environment if you block this strip access to Internet, what I am doing to prevent connections to their cloud for obvious reasons. After it’s blocked from Internet it goes offline and can’t be discovered any longer as it’s changes it’s IP address to some undefined, so the restart is required. In general my recommendation would be for you actually to drop this LED and find something better i.e. Athom LED controller which you can get pre-flashed with Tasmota.
Do you know, if there is a way to send a command to the Yeelight strip, like in the OH Yeelight binding? That is very useful to start color animations with Yeelights…
@jimSelf did the same not work for you in openHab? (I mean entering your Xiaomi userId/pass in the config page to get the token during discovery)
yes, you can send commands. The channel for that is marked advanced, hence in the list of channels you need to click “Show Advanced”… if in doubt, I think the binding readme has screenshot. There are also some posts on the forum about sending the commands for yeeligh light animation
Update: I moved all my Yeelights form the Yeelight binding to the Miio binding; quite easy. I have to say, the Miio binding is much more reliable. In the Yeelight binding, I always lost the connection after some time. With Miio, it always works like a charm.