-
Notifications
You must be signed in to change notification settings - Fork 6
Garage doors discovered but commands dont exist or do not work #26
Comments
I am on it to create a pullrequest that adds logging of found devices if you add the Integration - with that we should be able to see what garage door opener you use and which features it has. |
Thank you very much |
To be sure: |
no the garage doors dont work before over home assistant. its work only directly with homee |
I just got them so i’m not sure if they ever worked in hacs-homee. In homee app they work flawlesly.
|
OK, then at least I didn't break anything. Just got a new version on the way, that adds logging of device capabilities. See the readme on how to obtain logs and when HACS offers you the update, post them here, then I have a look |
It seems that the new build failed for some reason. Can you check, please. Thanks |
Now it worked |
I added
to the configuration file, restarted home assistant, uninstalled homee integration, and installed it again and these are only lines mentioning homee
So, no mention of found devices in logs, but hacs-homee found them same way in 2.1.0. |
Did you add the config entry in one line as here, or as laid down in readme? |
I changed logger default to be info and now i see all information we need
|
From what I can see, the two garage doors both have the same opener model. It is not possible to set a position to move it to with a slider in Homee, correct? |
Sorry, one correction, it has two buttons on for up and one for down. Also, when it's closing if you press the close button it becomes stop button, and while is opening, open button becomes stop button. |
And from an intermediate position, you can either start to open or close with the respective buttons!? |
Yes. up goes up, down goes down when in intermediate position |
If you know how to do it, you could test for me, by replacing cover.py in your config/custom_components/homee directory with the below version and restarting HA (maybe it is also enough to reload the homee integration). For the partly open functions I will have to add additional switches. cover.py: https://github.com/Taraman17/hacs-homee/blob/master/custom_components/homee/cover.py |
I did that, and hurrah! up/down/stop buttons showed up on both covers. Both up/down buttons work as expected, but stop does not do anything. Great job! |
Thanks. I'll have a look at the stop thing and the others the next days. |
Great, thank you for your hard work. Is there a way i can donate to this project? |
I just changed switch.py so it should discover your partially open impulses: For your stop button, I fear there is no really good solution. Since your device only does stop on repressing the previous command, I would have to disable the stop button for it. But since I only get the deviceClass (Garage_Door_Opener) and the information that it supports an UP_DOWN attribute from Homee, I can't distinguish it from other models, that might have a stop function. Does the position indication work for you in HA? |
I replaced my switch.py with the one you provided; no new switches appeared in the integration. Regarding the stop button, is it possible that on its execution, check if door is_opening and if true, execute command UP, and check if is_closing is true and then execute command DOWN, otherwise, skip executing anything? This would practically function as real stop command should. |
No sweat - had to go to bed anyway. ;-) Hmm, the device class "GARAGE_DOOR_OPERATOR" is as expected, so I wonder, why the switches don't show up. Since this is not my project and I just got in it because I also want my Garage door to work (A Hörmann Series 3), I'm still not sure, what shows up after reload/reboot/etc. For the Stop Button:
Yes I could do that. The point is, that I don't know all garage door operators supported by Homee. And the only info I get is the class "GARAGE_DOOR_OPERATOR". If there is another one, that has a stop button, that would stop working. So as long as I don't have a way to get the exact model, I don't want to do this. |
I understand; basically, the example of solution I gave you consider a hack, and without limiting that hack to a certain model of garage door or some identifier that can differentiate garage doors that use this behavior of stop being the same button as up/down, it's irresponsible to apply this logic to all garage doors supported by homee. Do you know which library is responsible for determining vendor and garage door model? I think that library needs to be updated if homee provides that information. Regarding the switches, you were right; there was an error in the logs:
|
Found the library in question https://pypi.org/project/pymee/ |
OK, found the error in switch.py - you can retest. The problem with device discovery does not lie in the pymee library as far as I know. Homee just is not giving out the exact model of a device. |
I'm happy to confirm that all new switches are present and working as expected. If the problem is not with pymee, I think I'll have to implement a hack/workaround to make the "stop" button work as expected. I'll have to use Template Cover and proxy all commands and states from the hacss-homee cover you implemented, except for the STOP button, where I'll add custom logic. That way, I will have my cake and eat it too. Do you know when these changes will end in the new release of hacss-homee? Thank you very much for your hard work. You've saved me a lot of money. I thought I had wasted my money on a homee device (i bought it only for garage doors), and I would need to buy additional Hormann equipment and shelly smart switches to accomplish what you did here. Once again, thank you! |
Great, I had similar problems with the Hörmann/Homee combo - thats why I ended up here. And if my work helps other people too, thats perfect. I plan to update some deprecated code to make the integration fit for the future and then submit the code. |
Great! Thank you for your hard work! |
Great, I had similar problems with the Hörmann/Homee combo - thats why I ended up here. And if my work helps other people too, thats perfect. I plan to update some deprecated code to make the integration fit for the future and then submit the code. |
hello i have copy also the switch.py and replace the file. Logger: homeassistant.components.websocket_api.http.connection [139859328512640] Entity cover.hormann_garagentor_antrieb_serie_4 does not support this service. should I setup a different setting? |
Did that happen when trying to use a specific button? |
sorry it was my mistake. thank you very much for the support and update |
Type of problem
Version
2.1.0
Detailed description
hacs-homee detects two of my garage doors properly, but there are no commands for opening/closing, only the position slider which does not work. By that I mean, I can drag the slider, but the gate does not move.
Logbook shows the history of opening/closing doors, so it works properly, and there is open/closed sensor with % open and that works properly.
Error log
The text was updated successfully, but these errors were encountered: