Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temp color control jumping around in HA #1

Open
rleongcs opened this issue May 24, 2023 · 1 comment
Open

Temp color control jumping around in HA #1

rleongcs opened this issue May 24, 2023 · 1 comment

Comments

@rleongcs
Copy link

When controlling the color temperature of the Lampsmart Pro lights, the HA temp color control is seen jumping around. Attached 2 videos that show the difference between controlling the Lampsmart Pro lights group and Tuya lights group.

Lampsmart Pro

RPReplay_Final1684931407.mov

Tuya

RPReplay_Final1684931486.mov
@aronsky
Copy link
Owner

aronsky commented May 24, 2023

It's not happening on my side. Have you set the default transition duration to 0s, as per the sample configuration? If not - try setting it and see if it helps.

I know that theoretically, this should work with non-0 transitions as well. However, I think that might cause issues. Each command to the light takes some time to broadcast (i.e., I broadcast it for a while - 1 second in the sample configuration - to ensure that it's received by the lamp and not lost in the air). If the transition time is non-zero, then the transition is broken down into steps, and each step constitutes a command to change the brightness/color temperature. Those steps now need to be broadcast at certain times, to create the transition. So, for instance, if the transition is 1 second and is broken down into 10 steps, each consecutive step should broadcast 100ms after the previous one. However, if the first step is a command that we want to broadcast for 1 second (to ensure reception), then when the 2nd step begins to be broadcasting, the 1st one is still being broadcast, as well. Then 100ms later the 3rd step joins the party, and so on.

That's why I keep the default transition time to 0s in the sample configuration. Maybe I should just set it to 0 in code, until we come up with a solution to this. I have to better understand how transition steps are generated by ESPHome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants