-
-
Notifications
You must be signed in to change notification settings - Fork 31.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
Zwave garagedoor #2361
Zwave garagedoor #2361
Conversation
@devdelay Didn't you have Zwave locks? If so can you test this code that they are still discovered correctly? |
The code looks fine to me. I can't test it however. So if you have tested this with two people I'm fine to merge it when you think it's ready. |
I have had @emilhetty and @wokar test for me. I just want someone with locks to confirm that all is well. |
@emilhetty and @wokar has confirmed working setups. My setup works as expected too, so it is good to go. 🐬 |
Everything looks good to me with the locks and were discovered correctly 🐬. I wish I had a zwave garage door opener to test with. I returned one that used COMMAND_CLASS_BARRIER_OPERATOR which is now in dev branch of OpenZwave as of May 13. |
Spoke too soon... getting errors when zwave detects my zwave lights (WD500Z-1 Wall Dimmer Switch). Previously detected as a light with dimming ability.
|
Reverted to #2271 and my lights came back |
@devdelay Fixed the issue you reported. Please test latest :) |
ok now 🐬 |
Then we are good to go. All components tested of zwave😆 @balloob 🐬
|
Switch position ;) |
When you press open, the garage door opens? But it eventually reports it as closed? |
The switch position follows the open and closed. |
Ok so without the |
No, with it shows correct according to my port |
Sorry, starting to get tired. |
Please try my latest at the same branch. I have made some changes regarding another issue, it may be the same problem. |
Yes, with the code I commited to you everything is as expected :) |
Does the zwave switch component have impact on the garage door? Or could I use the garage door only? |
You can use just the garage door. |
Should actually be self._value.data
|
Removed one value so it is value.data and not value.value.data and it did work as before, but still my port is inverted in HA. |
Ok. Then the not is needed. Sorry for the hassle.
|
But when I look at this when I tested some days ago: |
You are totally correct. The switch state is reported as is_on but the garage door component is reported as is_closed. So the not is absolutely right. |
Great, then we leave the "not" in there? |
* First go at zwave Garage door * Refactor of zwave discovery * Allaround fixes for rollershutter and garage door
Did some testing today on my garage door and the latest code with "not" are working as expected for my door. Got some Aeotec multisensor 6 today and found that the PIR is reported as Command class sensor binary with generic command class multilevel sensor and it did not appear since binary sensor only has binary sensor as generic class: Here is the xml if you would like to look at it. |
Submitted a fix 👍 Thank you for noticing this. |
Was gd00z-4 support added in this CL? |
@dtraub no, command class barrier operator is not supported yet in current version of openzwave |
Bummer, I was really hoping to get this working with HA. Thanks for the response! |
@devdelay @dtraub They have rudimentary support for Barrier Operator in the dev branch now. See: OpenZWave/open-zwave#490 (comment) I'm able to patch OZW master with that change and control the Linear GDZ00-4 directly with it. Would it make sense to add support to HA for an unreleased/possibly-not-final OZW implementation? Or should we wait for a proper release? I am new to python/HA but happy to take this on if some folks can point me in the right direction. I just need a couple days to order a second Gen5 stick I can use for development. |
@freerobby Doesn't it appear in the HASS gui? I know it won't work but it should appear as a garage door opener, or at least show that it didn't in the HASS log. What commands are sent while controlling it? I guess commands in the Barrier operator class are used. Have you got a zwcfg_xxxxx.xml with the command class present? |
@turbokongen Let me look into this tonight against the latest dev branch. I had been working on this in parallel with your change to allow secure devices and add garage door support, and I was working off of the 0.23 release, so it showed up in HASS GUI as a bunch of sensors, but not as a garage door opener for me. I will try removing and re-adding it to my zwave network on 0.24.1, hopefully tonight, and report back with findings and logs. |
@turbokongen I'm now having trouble, on 0.24.1, getting it to show up in the HASS GUI. I was able to see the sensors when I added it on 0.23 with a manual patch to add things in secure mode. Now when I add them to the network, they are added in non-secure mode and do not show up in HASS. Logs below if you have any thoughts. https://gist.github.com/freerobby/a4d769b15f795db5878c2e52ef813a77 |
Description:
Support for Zwave garage door component.
Bugfixes for rollershutter component.
Change the way components are discovered to provide better filtering options for future components.
Pepper1 database has been used for reference.
Thanks to @emilhetty for providing info and testing garage door component and discovery.
Thanks to @wokar for testing and providing bugfix for the rollershutter component.
Thanks do @devdelay for reporting issues with lights.
Related issue (if applicable): fixes #
Checklist:
If code communicates with devices:
tox
run successfully. Your PR cannot be merged unless tests pass