-
Notifications
You must be signed in to change notification settings - Fork 571
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
Warning after Home Assistant upgrade to 2021.12.0 #658
Comments
Definitely not a bug, but can't remove the label :( |
Sorry but its defintely the old wrong way you use, so its a bug, Please read the changelog of the new build. And look at https://www.home-assistant.io/docs/configuration/templating/ the yellow warning. Also ur readme is wrong in the way u tell to use the device attributes. Avoid using states.sensor.temperature.state, instead use states('sensor.temperature') It now should be that way:
Please fix your integration, i love it :) |
Hey, I am not sure whether you are talking to me, or the author of the intergration 😅 I definitely used the custom component the right way as stated in the README (via config flow). It all worked good and without issues until HA updated to 2021.12. Hope the author fixes this (I'd be happy to contribute with a PR, but I am not familiar enough with neither custom components nor python stuff in HA) |
To the author of the integration but i dont want to create a new issue with the same context |
I am seeing the same issue on HA 2021.12.1 with latest local tuya 3.2.4 |
Here is the full log message I see:
FEI, the browser_mod custom component has the same new issue:
|
The fix is on it's way:. sefininio@bfba2d7 You can make the fix yourself. Edit config/custom_components/localtuya/switch.py line # 51 |
above fix didnt seem to work... |
This worked for me thank you |
yes, this worked for me too, thx |
Fixed in #663 |
The problem
After upgrading Home Assistant to the latest version (2021.12.0) I now get this in the logs when starting up the server:
Environment
The text was updated successfully, but these errors were encountered: