Support COMMAND_CLASS_BARRIER_OPERATOR (Problem with Linear GD00Z-4 garage door opener) #490
Comments
|
Yes, I already had configured a Yale Door Lock to the Z-Wave network. I placed the device right next to the controller during the inclusion process. The controller is the Aeon S2 USB stick. When I get a chance, I'll try the inclusion process again and capture the logs. |
|
The Log Snippet indicates it wasn't included Securely. |
|
K, Thanks. I will include it back tonight and check the logs. |
|
Looks like there is an issue with the secure inclusion process. I'll work to get the latest OZW GitHub code to compile on my laptop. Let me know if you see anything interesting in the logs. |
|
Put the log through the Log Analyser on the homepage. It will tell you if your reaching a timeout for Secure Inclusion. |
|
Oops. That last comment is from me. |
|
@Fishwaldo I'll try including the device a few more times. What should I do if inclusion still has timeout issues? Here are the results of the Log Analyser |
|
You should wait till OZW is fully started up (allnodesqueried* notification) before trying the inclusion. As noted in the errors tab for node 17, it took 54 seconds to do, which is way over the timeout value for secure inclusion. If this device is like most locks, its just a matter of keep trying till it includes within 10 seconds or so... Hopefully the security rewrite should speed up the inclusion on OZW side, but the 10 second timeout is a device constraint, not OZW. |
|
@Fishwaldo Please reopen this issue. I've tried included the Linear device many times with no luck. To be sure, I have the device a couple of inches of the USB Z-Wave controller. I can debug the code on my laptop to diagnose the issue. Is there anything specific I should look at within the code. Is there any chance your rewrite of the Security code will fix my issue? Thanks |
|
If its taking more than 10 seconds from the AddNode command to the Secure Inclusion starting, then you need to understand why? The rewrite might help, buts its not ready yet. If you cant get it to happen in under 10 seconds, there isnt much i can do. The timeout is imposed on the device not OZW. |
|
I’ll try the including the hardware with the Razberry daughter board, http://razberry.z-wave.me/ http://razberry.z-wave.me/. I should have it early next week. I’m curious if there will be any issues with the Z-Way library. Thanks
|
|
@Fishwaldo The z-wave.me ZWay library is able to include the garage door opener device on the first attempt. |
|
Can you capture any logs of the controller traffic? Thanks, On Apr 1, 2015, at 8:59 AM, Jonathan Horvath wrote:
|
|
the logfile should be in /var/log/razberry.log if I remember correctly. 2015-04-01 17:25 GMT+02:00 satzg notifications@github.com:
|
|
Yes, I will get the logs later today when I get home. |
|
I'll lay money its just related to timeout issues. |
|
I posted the zwave.me inclusion logs here |
|
Yeah. It completes the SecureInclusion in about 2-3 seconds. I'm sure you can get it working with the current OZW, it's just a matter of making sure OZW is idle when you start the inclusion process. |
|
If zwave.me stores the network key somewhere, and your using the same dongle for OZW and Zwave.me, then you can include it via zwave.me, copy the network key to OZW Options.xml and it should stay associated and encrypted. |
|
@bytedreamer I'm having the same problem, did you ever get this working? |
|
@SurfingNinjas I was not able to get the Garge Door opener working with the OpenZwave library. I switched to a different library that supported the device. |
|
@Fishwaldo Can we reopen/investigate this? I am having the same issue with a very similar log. After going my own inclusion logs, it appears that open-zwave does not support command class 0x66 (102)(COMMAND_CLASS_BARRIER_OPERATOR) . I would assume that would stop a garage door from ever working with open-zwave, unless I'm missing something? |
|
Yep - We don't support that CC. Someone would need to figure it out so we could implement it. :) What other libraries work with this device? |
Fishwaldo
changed the title
|
@bytedreamer What library did you use to get this working? |
|
@SurfingNinjas The ZWay Lib from Z-Wave.Me supports the Barrier Operator commands. I've been using this library for a few months with no issues with the garage door opener. |
|
Thank you, vincemic. |
|
@jusovsky |
|
@vincemic - received this from Aeotec regards the USA model: |
|
hi folks - there is a downstream usage of the barrier control functionality in Home Assistant (http://hass.io) |
|
@jaburges : This functionality is tied to the 1.6 release which has a number of outstanding issues which are not yet resolved. I believe that once all of the items on the 1.6 milestones list are resolved we can finally have a stable 1.6 release. I'm also anxiously awaiting this to be merged into master for HomeAssistant - currently I'm building the ozwdev flavor and ignoring the built-in version that homeassistant includes which works okay, but is far from ideal. I think we just must be patient for the release. |
|
It's a shame we can't get a 1.5.1 release with just the barrier class addition. |
|
@DGAzr how does one go about doing the same thing in docker (moved away from a venv) - im assuming docker is dependant on a major release - any eta? Alternatively is it possible to set up a custom_component with the barrier_class enabled. |
|
In the end, I gave up on this and built my own ESP8266 solution which also controls garage lighting and is fully integrated with HomeKit. Seems and update to OpenZwave to include this will take years still |
|
@rjblake you have a link to the build or any info? I'm about to do this as well. |
|
@edif30 : I also was tired to wait so I did like @rjblake. I use this https://m.banggood.com/DC-5V-24V-DIY-WIFI-Wireless-Switch-Sonoff-SV-Module-For-Smart-Home-p-1063987.html?rmmds=myorders connected to the battery backup on my garage door opener (12v) for the power and to the wall switch wires on the relay. |
|
@edif30 - check out this here. Nice solution with a Homebridge setup too. I’ve created a branch and added temperature/humidity sensor and also fixed a couple of compile errors. Has OAuth authentication as well as other security options and you can use a second relay to control garage lighting as well. Quick, easy, cheap and has been rock solid. I’m using an ESP8266. |
|
all great links thanks for sharing folks Shame we have to find a hardware solution to work around the 2 years its taken to push the barrier class to a major release. |
|
Anyone knows if there is a beta version of Domoticz that has this fix? Or an idea when openzwave 1.5 will be used in Domoticz? |
I published a repository about a year ago with a few changes to support this patch. It is an old version, but it has been working nicely for my setup. |
|
Thanks for the feedback jowerg. |
… Class from Srirams
… Class from Srirams
… Class from Srirams
… Class from Srirams
… Class from Srirams
|
Three years and this is still open... meh |
@jowerg: Your repo seems to be only for domoticz and it looks like a change is also (perhaps needed for openzwave). I have the same garage opener which is sitting idle since i bought it. Could someone walk me through what is needed to get it working (even if it not from a stable github code). |
… Class from Srirams
… Class from Srirams
… Class from Srirams
… Class from Srirams
|
Was this finally merged in and resolved? |
I am using it with a functionally-identical GD00Z-5 with no issue. I would presume it works fine with the GD00Z-4 now as well. |
|
This is in the 1.6 branch. |
and others
I added the Linear GD00Z-4 to my Z-Wave network. The device is recognized, however it won't properly complete the initialization. As long as it is associated with the network, OpenZWave will not finish the initialization routine.
Here is the section of the log that I believe is causing the issue:
The text was updated successfully, but these errors were encountered: