Very odd, I have the same stick and all but one of my devices are directly connected to the stick. All of various distances and multiple walls/floors, some stucco. Only difference is my network is 99% mains powered. Only thing I can think of in your situation is there’s just not enough mains powered devices to give you a health mesh network.
That’s where I struggle in understanding and why I think my network is not using the mains powered devices properly. Any diagnostic tools or logs to help me out?
Only thing I found was this from the manual:
5.4 Installation and Maintenance Application (IMA) feature
- When the Z‐Stick acts an independent/secondary controller that has been un‐plugged from the USB host,
it also can measure the network health for each device in the network. The different colour of LED on the
Z‐Stick indicates the communication quality between the Central Controller and devices in the network.
Short press the Action Button 5 times, if the colour of LED is changed to purple and then it follows with
fast blink, which means it goes into the IMA feature. The colour of LED will be changed according to the
network health level. If the colour of LED is changed to green, which means the current communication
quality is more than 95% on ‐7dBm. If the colour of LED is changed to yellow, which means the current
communication quality is more than 95% on 0dBm. If the colour of LED is changed to purple, which
means the current communication quality is less than 95% on 0dBm. If the colour of LED is changed to
red, which means the current communication has failed.
Short press the Action Button 5 times again, the Z‐Stick will automatically exit the IMA feature.
Short pressing it 5 times doesn’t do anything?
With it unplugged from your computer/Pi ?
Nothing while plugged in, red when unplugged but none of that matters cause I just reset everything including the stick. Stay tuned…
So, how’d the reset go. I added the zwave panel, and found that even over 100+ feet that I did not have more than 2 hops (stick to device to device). Sounds like maybe the stick is/was the issue?
Same results, interesting details.
-
Before a complete reset of the stick I installed Domoticz (OpenZwave included), nothing huge here, just a cool mesh graph and one detail I was unaware of - my powered ZWave tstat does everything but repeat…? I had a screenshot but lost it on a reboot before I saved it. Either way, that node is on the opposite side of all the locks
-
After resetting the USB stick, removing everything Zwave, adding .old to all relavant files in HASS, some of the locks came back with OLD names that I once named them for testing. Not even the most recent ‘friendly names’ and I cannot rename those. IS HA MESSING WITH THIS TOO?!
I just wish there was something that said, Node 1 asked Node 28 to lock and attempted to contact Node 28 through Node 26 but the message dropped after Node 26
Only thing I can think of is not enough mains powered devices relaying your mesh here’s my mesh, and the only devices with high response are those with batteries (or backup batteries):
The naming issue is most likely related to the zwcnfg file. When you reset the stick, etc it probably was left behind. It’s not a huge deal, just a pain in the butt. There are a few posts about zwave and naming since 81.x? somewhere a few updates back. I will say at this point, I do believe that your issue is not lock related, but zwave related. You might want to start a new thread about how to improve the mesh, or asking about hops, etc. Might get more response than in the schlage thread.
1 Like
Thanks for the great work here. I’m a newb so still learning here but I have a few questions.
I have my single schlage lock connected and I’m able to set a code via the lovelace UI.
- I’m seeing the following error when checking config though. Configuration invalidCHECK CONFIG
Invalid config for [automation]: required key not provided @ data[‘action’]. Got None required key not provided @ data[‘trigger’]. Got None. (See ?, line ?). Please check the docs at https://home-assistant.io/components/automation/
I read somewhere that you can’t have a blank automation file and so I copied their dummy automation into the automation.yaml but not sure if there’s something else I may be missing. I also had to use a merge command in my configuration.yaml to get the package working.
-
I get a Date Invalid error on the card for setting up a key for both start and end date
-
I don’t currently seem able to setup a 2nd code although the lock took my first one.
Appreciate any thoughts.
Is this code still functional on the most recent version of HA? If so, is it possible for you to give me a short and simple step by step on how I should be importing this into my configuration.yaml? I originally tried to split it up into my separate [ie: automations.yaml, scripts.yaml, groups.yaml] categories but I’m getting all kinds of errors. I am really happy to have found this project. I’m still a newbie but I can definitely follow directions. I should add that I’m using hassio if that makes any difference.
this is a thread that I put together.
You dont need any code (including mine) to get your locks to lock, unlock, etc. This is more for people who want to set codes, change codes, delete codes, schedule codes, etc. but out of the box, HA supports locking and unlocking.
I can confirm that this works… Thanks!
Has there been any progress in getting the delete code functionality working properly? There doesn’t seem to be any updates in getting the fork of openzwave into home assistant. I would really like the ability to delete codes instead of setting them to a random code.
I would install the fork myself, however this is proving to be difficult when using the official docker container.
Keep in mind the delete codes does not work on Kwikset zwave locks.
You might try using the config path option for the open zwave settings. It seems to be working for me. It’s about half way down this page https://selfhostedhome.com/home-assistant-z-wave-tips-and-tricks/
Adding Custom Devices
Unfortunately, the version of OpenZWave present in Home Assistant can sometimes lag behind what is released in the OpenZWave GitHub repository. The OpenZWave repository has a config directory that is broken down by vendor, so you should be able to see what devices are supported. If the device you are looking to add is not supported in Home Assistant but is found in the OpenZWave GitHub repository you still have some options.
To use the newer device configuration we can use the Z-Wave integration option config_path.
Start by downloading the latest version of OpenZWave from their GitHub repository. Once that is downloaded and extracted you need to add it into your Home Assistant environment. This will be a little different depending on how you installed Home Assistant. For me, I use a Docker container for Home Assistant so I copy the OpenZWave config directory contents into my configuration directory and name the directory openzwave_config . Note that you only need the config directory from OpenZwave not the rest of the repository.
Then in your Z-Wave configuration within Home Assistant you can set the custom config_path. This allows Home Assistant to use the latest devices added to the GitHub repository.
zwave:
usb_path: /dev/zwave
config_path: /config/openzwave_config
So I’m completely new to home assistant but I feel like I’m failing pretty hard here…
I have the lock setup in hass.io, lock will unlock with no issues.
I created a folder called packages in the config directory
now I’m pointing at the packages directory with the configuration.yaml file
I downloaded and renamed the file called lock_package_for_one_deadbolt.txt
The node_id for the lock is 2, which I changed from 104 in the above file
I’m seeing the following names in the entity registry, should I be renaming these? I guess that’s where part of my confusion is coming in:
zwave.schlage_allegion_be469zp_connect_smart_deadbolt
sensor.schlage_allegion_be469zp_connect_smart_deadbolt_alarm_level
sensor.schlage_allegion_be469zp_connect_smart_deadbolt_alarm_type
Here’s the current error I’m getting:
The following components and platforms could not be set up:
- packages
Please check your config.
I also tried commenting out the pushbullet lines, because I don’t have pushbullet or similar installed quite yet… Any help at least troubleshooting would be appreciated!
Did you ever get this working? It has been 30 days, so I’m hoping so. But if not, yes you need to rename the entities based on the comments in the file. I will say it’s possible and likely that the file is a bit outdated, but I believe it will work for you.
Also the error you received is actually saying your packages folder is not configured correctly.
I ended up just using the zwave setup and it worked okay, I can’t add or delete user codes on the fly but honestly I’m not too concerned about that at the moment.