-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
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
ZHA : Cover states stays as Opening or Closing when using Set position #98933
Comments
Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) zha documentation |
I implemented a fix, but it's my first time creating a PR for HA and I need to read more about the different steps to be done before I can submit it. |
hi, what is your fix ? |
Hi, |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Please don't close this. There is even an open pull request for it. |
I also faced this issue with the Aqara Roller Shade E1. |
Facing the same issue also with the Aqara roller shades, stays in status opening after the desired position, which is not fully open, has been reached, If later on closing the shades in stays in closing status. Initially this worked fine but somewhere the past 2 months this changed, not sure after which update. |
If this is still happening please put ZHA in debug mode and reproduce the issue then disable debug mode for ZHA and attach the log file that is downloaded when you disable debug mode. |
Thank you for the quick reaction! home-assistant_zha_Debug_2024-02-28T16-32-59.392Z.log Appreciate you looking into it. Running Hassio; 2024.2.2 |
I also see similar issue when you use a close cover service on an already closed cover it will also remain in closing indefinitely. Is this related? When HA is restarted it indicates a proper state. |
Same problem with TuyaTS130GP. It never detects the open/closed state. It always has a closing/opening state independent of where I send the command from, Dashboard, Alexa, etc. |
I've observed the same behaviour - with devices recognized as TuyaTS130GP (TS130F). When I click open or close I can hear relay going on and after some time off, but on the gui the state keeps showing "opening" or "closing" (not "open"/"closed") |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
I'm still having this issue with Aqara Roller E1 and newest HA |
The problem
In ZHA: when using the set position feature to open or close a cover to a certain percentage, the cover state changes to Opening or Closing and never change to Open when the desired position has been reached.
It works fine if you use the Open/Close/Stop buttons.
What version of Home Assistant Core has the issue?
core-2023.8.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
ZHA
Link to integration documentation on our website
https://www.home-assistant.io/integrations/zha#debug-logging
Diagnostics information
zha-061e6119584d5d65f283e7693a589335-_TZE200_68nvbio9 TS0601-355e8211ebead2935da1d1b2c564ef71.json.txt
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: