-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Stop command doesn't work for some cover devices #204
Comments
I found out that stopping the opening of the slats via Even though
|
@iMicknl can I help with testing for this problem. I have RTS roller shutters and the stop command doesn't work? |
@Glenn1986 are you familiar with Developer Tools in your browser? Could you capture which XHR requests happen when you open the cover and cancel the command? |
Oke I will try, do you mean the xhr request in home assistant or in tahomalink? I think the last one but want to be sure ;) |
yes tahomalink! |
Hope this information helps you guys |
Thanks @Glenn1986. Could you have a look if the previous request is a |
Request URL: https://www.tahomalink.com/enduser-mobile-web/enduserAPI/exec/current/setup/4e440f95-ac10-3e01-2775-8dbb10e9de74 It's indeed a delete request before above information is received. :) |
Great to hear! I have implemented a first try in https://github.com/iMicknl/ha-tahoma/tree/enhancement/improve_stop_functionality, could you give it a try? You can download this zip https://github.com/iMicknl/ha-tahoma/archive/enhancement/improve_stop_functionality.zip and extract the tahoma folder to your |
Hi @iMicknl. I did the test with the new version you made but didn't work. Gives me the error: Kan service cover/stop_cover niet aanroepen 'TahomaCover' object has no attribute 'debug'. |
@Glenn1986 oops, I made an obvious mistake. It is fixed in the latest version. |
Ok let me know if i can help further with testing. 😊 |
@Glenn1986 you could download the zip again and retry :) |
@iMicknl i tested again and now it worked. The rollershutter stopped but he gives on error: Kan service cover/stop_cover niet aanroepen 'NoneType' object has no attribute 'get'. |
Cool! I will have a look myself and polish it up a bit, but great to know that the stop functionality is finally working for you. |
@Glenn1986 if you could try the latest version and report if this solved your issues, would be appreciated 👍🏻 |
@iMicknl i just tested your new version. Everything worked well and no errors showing up. Nice work! |
@iMicknl in which release will you're fix for stop command cover released? |
@Glenn1986 it depends a little bit on the code review, I expect it to go out with a release in the next week. I will close this issue once it is merged to master, so you will get a notification :-). |
Thanks! |
I was about to report this bug, as I noticed it today, now I see a fix has been merged 12 hours ago. It works for my RTS awning, well done!! |
@golles thanks for first looking at closed issues / pr's 😄! This PR took a bit longer to get merged, but I will do a new release soon with some more fixes. For now, you could install the latest master via HACS or manually. |
Great to hear that you're so active! I bought the Tahoma box recently and I'm really happy to see that you and the others rewrite this component. |
Describe the bug
Currently the cover implementation relies on the available commands of a cover device. However, when a
stop
command is present, it doesn't mean that thestop
command is functional. (thanks Somfy 👍🏻)ha-tahoma/custom_components/tahoma/cover.py
Lines 217 to 221 in 23eaec1
To Reproduce
Steps to reproduce the behavior:
Additional context
The integration is not consistent in how it handles a stop command. For example, for the
cover_tilt
mainly used by Pergolas, we first executeCOMMAND_STOP_IDENTIFY
sinceSTOP
didn't work for my own device...ha-tahoma/custom_components/tahoma/cover.py
Lines 223 to 227 in 23eaec1
Best would be to:
First use
COMMAND_STOP_IDENTIFY
orCOMMAND_MY
to stop a moving cover. This needs to be thoroughly tested to ensure it doesn't cause problems with covers that are not experiencing this issue.OR
Make sure entities can set their preferred stop method via
customize.yaml
, as a workaround. I am not a fan of having all those device specific if statements in the integration.Environment (please complete the following information):
Device: (if your problem is related to a specific device)
The text was updated successfully, but these errors were encountered: