Z-wave Failed To Connect
Sofía Goldthwait
I have two Sensitive Strips Guard (11-01-011 Strips-MaZw) which are physically broken and not working anymore. They are still auto discovered by the binding. I tried to remove from the controller, which does not work.
I have tried to remove these devices through the openHAB UI - no success
I have tried to set them to failed - no success
I have searched the forum and found a procedure for HABmin, which does not exist for OH3
ensitive Strips Guard (11-01-011 Strips-MaZw) which are physically broken and not working anymore. They are still auto discovered by the binding. I tried to remove from the controller, which does not work.
Just plug your stick into the PC connect it amd you can remove failed nods from the stick eprom. I suggest also to backup your stick eprom time to time and have a backup one. In case of any malfunction you can change it without recreate the whole network. (back up software is a different one.)
I have done that many month back on openHAB 2 already, which resulted in a bit of a mess. I could fix it by deinstalling Z-Way again, and the system was stable. Upgrade to openHAB 3 caused a few weeks shutdown to figure out how to get openHAB running again.
Zwave with OH works quite well. The problem I am trying to resulted either by failed integration of Sensative Strips (which resulted in nodes not existing) or broken devices (also Sensative Strips and an old FIBARO Home Center Lite, that used as secondary controller to update firmware). Those device physically do not exist anymore, so I am trying to remove them from the controller and openHAB (I ignored them in the inbox or I integrated them as Thing and disabled - both not clean solutions).
Just bought a new Hubitat Elevation. I'm excited to start my smart home journey. I spent about four hours this morning trying to exclude the lock (because instructions said you exclude first and then include).
It's a good practice to do any include/exclude events (among other things, like OTA firmware updates) within close proximity to the hub. A good number of people have built test rigs that can house and power a device for 'service' close to the hub, then install it in its permanent place. I've learned my lesson numerous times (or not, as the evidence shows) that 'close enough' is closer than you think when there are walls and massive metal objects between the device and the hub. Even something as simple as an appliance cord with pigtails can power a mains-powered device while you operate close to the hub. (Of course, a battery device doesn't have that issue.)
If your battery device must be installed before inclusion, look at getting a long power cord to move your hub around (and a long patch cable, if you use wired networking.) It's to be avoided if you can, but sometimes you just can't.
To your specific issue, exclusion before inclusion isn't a requirement. Yes, it helps lessen issues, but it's not strictly necessary. I would simply try to include it close to the hub, then go from there. You can also try a factory reset on the device, which sometimes deletes all hub pairing info.
I don't have an example to show, but when you do a successful exclude, you should see a confirmation message in the area where I have a red box here -- it'll say something like "Unknown z-wave device excluded"
So even if the lock says the exclude didn't work, the log might? I'll try again later today. I do recall the page said something in the red box area but I can't recall right now. Thank you for your help!
For the other user who isn't seeing the exclusion confirmation in the UI, his logs did indeed contain the correct/expected messaging about the successful exclusion, so checking the logs should give the real story.
JB_TX has good advice about perhaps moving the lock & hub closer for the whole initial-pairing process - many folks need to do that with locks in particular. I've never had to do it myself, but it's not uncommon.
My husband had a very long ethernet cable and we put the hub right next to the lock. The exclusion worked almost right away. Then I tried to include, and the lock said it didn't work. But then in settings I see a z-wave radio device:
Now with the schlage locks you need to pair them within 2 or 3 feet of eachother because of the whisper key exchange they do during pairing. After that you can move things to their final resting place. You would also want a beaming repeater as close to the lock as you can.
Now that said, you should be pairing your mains based devices first (electrically powered) and battery based devices second. Read this post and pay attention to the z-wave section. Especially the section on building a strong z-wave mesh. The overall post though will help you avoid some gotchas! Get rid of that ghost!
Others are better with these mysteries than me, but I have always found that power-cycling the hub fixes the 'Z-Wave network busy' messages. (And by power-cycling, I mean doing a proper shutdown from the menu, removing power for a time to let the Z-Wave radio fully shutdown (I set a timer for 5 minutes. I know it's actually a shorter period, but I never can remember the actual time.), then re-apply power and let the hub boot up.
I don't think a lot of people talk about this, but I get these messages without any ghosts when an inclusion/exclusion/replace/repair/etc. goes wrong. They don't automatically mean you have ghosts, but -again- you have to make sure you don't have any ghosts. I have found they will hang around until you fully reboot the radio.
Also what version and model is your Schlage? Look at the label in back of the lock to confirm the firmware. If it's an older lock with anything less than the 7.10 firmware it won't connect to anything above the c5. This is because of the lock's firmware and the fact that schlage has no interest fixing them.
There are a few models with that name: BE469, BE469NX, BE469WK, and BE469ZP. Of these, only the BE469ZP is guaranteed to have a recent firmware version that will work with no issues. It is also Z-Wave Plus, while the others are not.
I upgraded to the Zwave Dongle 500. When I try to include an Eaton RF9601 switch I always receive the error "The Z-wave network failed to securely include your new device." I excluded it, I gave hard reset to the switch, repair link, heal network and I still haven't been able to add it. I would appreciate some help
In any case, as mentioned by many others and just confirmed in my installation, connecting the AeoTec MS in non-secure mode significantly speeds up the response time and seems to strengthen the meshing.
More or less everything I read here, explains that as a mesh technology, z-wave connectivity problems are solved by ensuring there are mains-powered z-waves devices near the ones suffering poor connectivity because they automatically act as repeaters.
as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.
Well, it has been working for over 2 years without having a single issue. A few days after upgrading to 5.100 and ZW3 engine I got connection lost to the device. It might be device issue, it is the first time this device has had an issue though.
@Firefreak , you cleared your whole Z-Wave network and moved to ZW3 engine?
I am asking just to be sure.
Selecting the engine is possible at first gateway configuration or after factory reset
In ZW3.0 this function works a little bit different, now there is a possibility to mark nodes as failed by additional function built-in in Z-Wave Alliance firmware - it is not used in old 2.0.
This is the only difference there, our part of firmware works basically the same.
We will take a closer look at this anyway.
Regards,
Michał
Perhaps worth the time to go back to the ZW2 engine because my experience was that the HC3 with ZW2 is very stable compared to the HC2. Looks like ZW3 still needs more then a year of development before it is as good.
If you are having problems including (adding) a Z-Wave device to your hub, first try a factory reset of the device or a "general exclusion." Consult the device manual for specific instructions on how to reset or put the device in exclusion mode. If you no longer have these instructions, some of the most popular ones are documented in the list of compatible devices (see the Instructions column). A general exclusion can be done with any Z-Wave controller. To initiate a general exclusion with Hubitat:
So-called "ghost nodes" can be created by failed pairing attempts or by force-removing a device from Devices instead of properly excluding it. "Ghost nodes" may cause network problems, either problems in operation or pairing new devices. To check for these nodes and remove them:
Look for any row in the table without anything in the Routes column and often without a link to a Hubitat device in the Device column; these devices may be "ghosts" (or at least have not had any traffic since the hub was rebooted and/or do not have a device associated with them in Hubitat). Functioning devices are never "ghosts," and blank routes alone are not necessarily a problem.
If you see a "ghost" you want to remove, select the Remove button (in the Status column) for that node. Wait several seconds for the page to reload, then verify that the device no longer appears in the table.
c80f0f1006