There seems to be a shell script available, I just don#t know how to integrate it into webthings.
Is there anyone who could help me with that?
I was reading up on the Aeotec adapters and noted that my adapter only supports S0 security but the newer adapters support S2. Could the issues we’re experiencing with Locks be related to the security level support?
Is there something I can do to test this theory?
ive been having the same issue with the same lock. Did you get the openzwave directories thing? i havent been able to figure ou how to doqw it. for some reason i cant clone it from the command line. says git is an invalid command. Im hoping thats my problem, might be yours too. Im totally new at this so excuse my lack of technical knowleddge and proper jargon
I haven’t tried the openzwave software you mentioned, but I tried HomeAssistant and OpenHab. I got the same results so I’m tending to think it’s related to needing S2 support in the USB Adapter.
Aeotec has a Gen 5+ adapter they released that supports it and also a Gen 7 adapter in beta. I’m probably going to wait until the Gen 7 adapter is available for purchase in the US again and upgrade.
It looks like a lot of new devices use Zwave Gen 7 so I’d hate to upgrade to the Gen 5+ and then have to do it all over again.
i really hope thats not the problem cause i just got the gen 5 and really dont want to have to replace somethng thats brand new
I did the openzware. Still nothing on the lock. It’s there but it does t lock or I lock or show me anything else.
Did you set up a network key? From my research it seems the lock requires the network key to communicate securely but other devices like a light switch won’t. I never set up a network key and have no idea how to do it
Yesterday I unpaired the lock from the Gateway, added a Network Key and then tried to re-pair. Like I had experienced before, the Gateway can’t pair with the door lock unless it’s in close proximity. I unplugged the Aeotec adapter and took it over to the lock, and it paired immediately. Upon plugging the adapter back into the Gateway it was able to add the Lock.
Unfortunately the behavior is exactly the same as before, with the Lock reporting as jammed.
I’m going to try removing the Lock and then moving the Gateway to close proximity with the Lock and re-pair while the adapter is plugged into the Gateway. I thought I had tried that before and had issues pairing but I’ll give it another go.
Same thing happened to me. I’m going to do the same. I believe the instructions from kwickset say to remove the lock and to have it unlocked. That maybe part of it. It’s reading unlocked when it’s locked and it’s returning jammed because it can’t move it.
Something else to try if you haven’t yet is to check that the specific lock is in the zwave database correctly. There’s an XML file with all the device codes in it, called manufacturer_specific.xml or something like that. The manufacturer provides the data for that file and a filename of their own xml file for the device.
I tried unsuccessfully to get my Kwikset lock to work with Webthings, which is using OpenZwave 1.6. I setup an instant of Home Assistant using Z-Wave JS and it detected the lock and can control it without issue.
From reading up on HA’s reason for switching from OpenZwave to Z-Wave JS, it seems that OpenZwave is written in C++ and no one wants to work on it. The primary contributor stepped away from the project for a bit putting it on life support. Z-Wave JS on the other hand is written in JS and has a good documentation and a lot of community support.
Honestly it seems like Z-Wave JS would be a really good fit for WebThings but it also feels like perhaps WebThings is on life support at the moment. Which is really disappointing because HA is a hot mess in terms of usability and setup.
Yes, it does seem like WebThings is on life support. I have contributed to the project a bit, so I like to feel I’m helping in a small way to keep the heart beating. I am glad you said that about HA, because I’ve considered switching to it. It’s interesting to know about Z-Wave JS. Do you have a link so I can look into that and see what it might take to integrate it into WebThings? JavaScript does seem to be the way of the world.
Here’s the official Z-Wave JS Documentation and Project:
https://zwave-js.github.io/node-zwave-js/#/
IMO it’s exceptionally well document as far as open source projects go.
Paulus from HomeAssistant contacted me back in January to recommend switching from openzwave to Z-Wave JS. Michael Stegeman (WebThings emeritus module owner) agreed that it looked promising and would save us a lot of headaches.
The WebThings Z-Wave adapter module is currently lacking an owner, but Dave Hylands (the previous module owner) has offered to provide code reviews if anyone wants to work on it.
Alternatively if anyone wants to try creating a replacement Z-Wave adapter in JavaScript then we could consider switching to it as the default once it becomes more mature.
Regarding WebThings being on “life support”, please see this post regarding the future of the project.
1 Like