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

Cannot turn off the light #90

Open
H0nzik1 opened this issue Apr 3, 2022 · 10 comments
Open

Cannot turn off the light #90

H0nzik1 opened this issue Apr 3, 2022 · 10 comments

Comments

@H0nzik1
Copy link

H0nzik1 commented Apr 3, 2022

When I click to turn off the light it gets back on again and again. Can you fix it? Your widget is useless now. Latest version.

EDIT: I does not turn off when I have same widget opened also on another device (wall mounted tablet)
EDIT2: It does not turn off when persist features is enabled, when I disable persist features, then I can turn off light normaly. Seems when is this card visible on multiple devices simultaneously with persist features enabled then light cannot be turned off.

@valette
Copy link

valette commented Apr 23, 2022

I have a similar problem, and after looking at my esphome logs, I fixed it by un-checking the "show effects list" option in the configuration UI. My two cents...

@msth
Copy link

msth commented May 12, 2022

have the same problem. and already have a ticket open at Tasmota. here it was recognized that it is because of this card.

home-assistant/core#71672

@ljmerza
Copy link
Owner

ljmerza commented May 12, 2022

it works fine with hue lights. i dont have Tasmota to test. looking at the HA websocket connection, everything looks good.

"domain":"light","service":"turn_off" is called on turn off and "domain":"light","service":"turn_on" is called on turn on

@emontnemery
Copy link

@ljmerza In the Tasmota issue, the light-entity-card actively turns the Tasmota light back on when its state changes to off.
I imagine a hue light will react in the same way?

@ljmerza
Copy link
Owner

ljmerza commented May 12, 2022

The logic to send devices is pretty basic: Clicking the toggle in the card will trigger the relevant turn on/off service. There's no logic to trigger anything other wise.

Considering I don't see this behavior happening on any other integration, I'm inclined to think it's a tasmota issue.

Are you seeing this bug in the websocket messages? I've checked and it works properly.

@sumur1au
Copy link

sumur1au commented May 21, 2022

I also have the same issue with ESP-Home RGB lights.

I get the following error when turning off the light in my ESP Logs:

[11:37:36][W][light:475]: 'Bedside Lamp xxx RGBWW Light' - No such effect ''

Update: I think there is a bug with v[5.0.0] it must be applying an effect along with the colour picker that is putting the light in an unknown state. When the effect list is hidden there is no issue.

@ljmerza
Copy link
Owner

ljmerza commented May 25, 2022

here's my websocket log when i turn off a light in this card. Everything is as it's supposed to be. If anyone could post their websocket logs as well when turning off a light that would be helpful

image

@sumur1au
Copy link

Happy to provide my logs. How do I extract the web socket log ?

@svb91
Copy link

svb91 commented Apr 27, 2023

Having the same issue. After setting "effects_list" to false it works. If I enable that feature the light starts to turn off but within less a second it is at the original brightness again.

@ljmerza
Copy link
Owner

ljmerza commented Jun 5, 2023

i couldnt reproduce but i tried a possible fix in v6.0.7

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

7 participants