-
Notifications
You must be signed in to change notification settings - Fork 53
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
[Bug]: Cover gets unavailable #262
Comments
|
It's probably because I revert the change I made back then in the old issue. |
can you take it back in ?😅 |
I change it because It wasn't kinda ideal ^^, Can you try to re-configure the cover and change the protocol to |
Okay installed master and changed the 3 covers to 3.2. Did a reload of local tuya, seems to work. I will test a few days and come back again for feedback |
@xZetsubou seems to work. Covers are available all the time. Can you merge your change into production? |
it's already merged with master and should be fixed on next releases as well. |
thank you 👍 |
This issue was closed because it was resolved on the release: 2024.6.0 |
LocalTuya Version
2024.5.0
Home Assistant Version
2024.05
Environment
What happened?
3 Covers from the same manufacturer gets unavailable after homeassistant restart.
I am getting following error in the log output.
If i move the cover with the offical Smart Life integration in HA then it gets avialable again.
I had this problem in the past, you code owner fixed it but it is there again: #121
Steps to reproduce.
Restart Homeassistant
Relevant log output
Diagnostics information.
No response
The text was updated successfully, but these errors were encountered: