Completely new to HA and just got my first device linked: a led strip with a tuya controller. Works like a charm, connected smoothly, all good. The controller has a button which turns on or off the led strip and changes color/mode. This works great.
However, as soon as I use HA to change the color (in other words, select a color different then the defeult ones the controller defines) and I try to turn of the led strip, it decreases the brightness way down but doesn’t fully turn off. The leds stay on with low brightness. If I press the button on the controller to go to the next default color, turning it off works like it should both with the button or through HA.
I’ve been googling for the past 2 hours and trying things but can’t figure it out. Any clues? Thanks!
HA probably have nothing to do with the behavior when pushing the button.
The actions is something that occur internally in the controller.
So you likely have to contact the vendor/manufacturer of the controller to get it fixed with a firmware update.
I believe it’s quite the opposite. If you leave HA out of the equation, everything works like it should with just the button. It’s only when you change the color in HA that problems start. Or do you believe this may still be a problem with the actual controller itself?
It might be HA that is the cause of the problem, but HA have no influence on the workings of the button.
The only thing HA can do in this problem is not change the settings on the controller at all.
It is the firmware and only the firmware that controls the buttons function and that code is poorly made, so it can only handle the predetermined modes that the button itself can do.
I think I understand what you are saying but let’s say there is no button for the sake of this example. So I turn the led strip on using HA, I set a color using HA, I switch it off using HA and the led still remains on (at a very low brightness).
I just want to make the situation clear as it’s a bit of a strange one. Either way, I’ll look into the firmware but any other suggestions are definitely welcome!
When the turn off command is sent it should turn off completely.
You can maybe make a dirty fix by making a script that set the right settings for a correct turn off and then call the command, but it is a patch for the correct solution, which is to get the firmware updated.