Thanks for the feedback, I’ll look into it as soon as possible ![]()
@_Will_71
I’ve created a new Docker image with a few changes that you can pull to test.
So that I can add the model of your LED strip, could you tell me if you see a log line like « Yeelight: Device "${id}" found, model: "${model}" »?
Ok thanks for the image.
This week is very busy for me but I’ll try to do the test by Sunday at the latest.
Hello, I’ll make a note to test this image as well, I have Yeelights in several versions in color and white so I’m very interested in it ![]()
@Pti_Nico
Here are the logs I have today with the same behavior as the other day. I can control the LED strip for a few minutes and then nothing. I’m forced to power-cycle the LED strip.
However, I couldn’t find any line in the logs that shows the model.
The lines are only visible if the log level is set to debug…
Sorry to ask you this, but how do I set the log to debug?
Bumping this topic, the PR is OK for review…
Great! Is there a Docker image? Can you post it here to get testers? ![]()
Available soon:
docker pull nickdub/gladys:dev
I’ll try to do a test tonight.
Hi,
I tried your image and I have a few comments
My Yeelight Lightstrip LED strip is recognized right away but the model is unknown.
I have an error in the logs
![]()
How often do you retrieve the data? Let me explain: I can control my strip from Gladys but if I control my strip from another application (Node-RED) the switch in Gladys does not toggle even after some time!

the strip lights up and turns off properly
Did you manage to isolate the bug found by @_Will_71 in the end?
@Pti_Nico Keep me posted when you want another review on this PR
Yes, but it’s impossible to build a Docker image to test, because of an issue that I think is not related to the PR.
I’ll try again
This issue has been fixed on master
(here: Remove Python symlink in Dockerfiles (#1671) · GladysAssistant/Gladys@fefb9cf · GitHub), you need to rebase!
All good, it’s done ![]()
Image available for testing: docker pull nickdub/gladys:dev
I’ll do another test tonight.
@Pti_Nico Sorry but I’m still getting the same error!


