-
-
Notifications
You must be signed in to change notification settings - Fork 29k
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
Tasmota H801 immediately switch on again #71672
Comments
Hey there @emontnemery, mind taking a look at this issue as it has been labeled with an integration ( tasmota documentation |
thanks for the reply. The Option 19 is OFF
here are the required log files
|
the switch turns on again in both cases. it doesn't matter if you click the homeassistant switch or the one from the tasmota frontend. |
Again, something actively is asking the light to turn back on as soon as it changes to off state. The list of automations referencing a device is not always complete. Just to be sure, can you try turning off all automations? You could also try enabling full debug log, it may reveal something: logger:
default: debug |
many thanks for the analysis. I deactivated all automations and activated debug as default. this of course logged a lot of logs. I had to filter it a bit. I sorted out all entries that have nothing to do with RGB_Samy. https://0bin.net/paste/Flp7VKXb#8SaFzRCxdM47i4cG2BlY8W0126zdKPBfO6bY0corGRo |
The log shows that the request to again turn the light after it was turned off is coming in over http, most likely from the web UI. Do you have any custom components or custom cards etc. installed?
Did you try this? |
Thanks a lot. I would never have found that You were right. I use a HACS addon light entity card. Had forgotten that this is not a native application. Greed there is already an open ticket. |
light-entity-card uses websocket to call services on toggle. Verified this still works for Hue, Kasa, and Lutron. I dont have a Tasmota device to test. |
The problem
once the Tasmota H801 has been found by the integration, the RGB stripe can no longer be switched off. After a click on switch off, it will be switched on again immediately. there is no automation that can cause this.
What version of Home Assistant Core has the issue?
2022.5.3
What was the last working version of Home Assistant Core?
2022.5.3
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
tasmota
Link to integration documentation on our website
No response
Diagnostics information
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: