-
-
Notifications
You must be signed in to change notification settings - Fork 28.9k
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
Supla's covers can't use cover.set_cover_position service #121007
Comments
Hey there @mwegrzynek, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) supla documentation |
I have the same issue. Please help! It worked perfect until like 2-3weeks ago. |
Same problem here. |
Hi! Can you run Supla integration with Debug logging enabled and post logs? See: https://www.home-assistant.io/docs/configuration/troubleshooting/. I don't use this integration anymore (I switched my devices to MQTT), so to debug it I would need
Don't post these details here. PM me on Twitter (@mwegrzynek) to arrange safe transfer of these details. |
I'm not able to PM you on twitter. |
OK, I've changed my Twitter settings, try again. |
2024.7.1 is also affected. |
The problem
When you try to set position of cover for ex 50% you receive an error
Nie udało się wywołać usługi cover/set_cover_position. unknown error
.The error implicate to HomeKit bridge - when I allow cover devices to connect to HomeKit it uses the same service.
What version of Home Assistant Core has the issue?
2024.6.4
What was the last working version of Home Assistant Core?
2024.5
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Supla
Link to integration documentation on our website
https://www.home-assistant.io/integrations/supla/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: