Under settings and z-wave details.. You will see nodes that have no information.. If you refresh the node it should time-out and fail the node within a few minutes, if it wasn’t failed already.. Then you can click remove and it will remove the reference to it on the network.
2 Likes
Yes I did clean them up. I may try resetting the zwave radio tonight and starting from scratch, I'm only 3 dimmers and one switch in. Or do you think trying to get S2 authenticated on everything is pointless at this point?
Yes.. it is pointless as some devices are failing against the Z-Wave reference platform.. Which at that point is the gold standard of z-wave compliance.. If it fails S2 on that then there is nothing that we can do about that.. What we are doing now is gracefully handling that failure rather than letting the nodes get locked in discovery.
3 Likes
Has anyone running 2.2.3 gotten SmartStart working? I'm not having any luck.
Here's what I did:
- Upgraded to 2.2.3 and upgraded Z-Wave chipset
- Excluded all Z-wave bulbs
- Reset Z-Wave Radio
- Removed the rest of the Z-Wave devices
- Factory reset each of my 32 Inovelli LZW30-SN, LZW31-SN, and LZW36 switches
- Scanned in the DSKs for the first two LZW31-SN switches into SmartStart using my Android phone
- Waited 20 minutes.
What I expected is that both of the switches would be included with the names and rooms I assigned to them in SmartStart. This is not what has happened. SmartStart still lists the two switches as "not included, pending".
On the Z-Wave Details screen I have the hub (001) and one other device (006). 006 is showing the "Discover" button, status "OK", security "None", and no clusters. Just like the inclusion bug in 2.2.2 would look before clicking "Discover".
When I click "Discover", the page refreshes without any change, I get the "Discover" button back again. Same clicking on the 006's "Refresh" button. I tried each several times.
Next I tried a warm reboot on the hub. After the reboot, I could now see a "Route" column on the Z-Wave Details page, and it showed a route from 001<->006 at 100k. Clicking "Discover" then "Refresh" for 006 then finally made the clusters and device name ("Inovelli Z-Wave Smart Scene Dimmer S2") appear. However, upon examining the device, it did not pick up the device label I entered into SmartSmart, and the Z-Wave security is listed as "None", even though I told SmartStart to keep all 3 of the 4 security grants it offered, including both of the pre-checked S2 options.
Even after all of that, SmartStart on my phone still says "not included, pending" for both switches. And I still haven't seen the second switch I scanned in (same room as the hub, previously connected at 100k before radio reset). The good news is that I never had to triple-tap the switch to put it into inclusion mode, at least that part worked for the first switch.
Anyone had more luck?
Some of the devices on your list are failing S2 bootstrapping even when tested on the Z-Wave reference platform.. Those devices will not smart start
1 Like
My Zooz Zen25 double plug is not being fully recognized during the inclusion process, even after updating the hub and radio firmware to the latest version. The inclusion process completes, but it is being added as a generic "device" in the device list, preventing me from each individual plug in the device list.
I initially tried including the device with default authentication that is checked (security 2 class 0). Other things I've tried:
- Used other authentication methods, including no authentication
- Manually changed the device to be the the zooz double plug in device settings. (Still couldn't see the two separate plugs in the device list)
- Exclude the plug, factory reset the plug, reset the z-wave radio
During the inclusion process, I see the following in the log (this is with the default "security 2 class 0" checked)
dev:972020-08-13 08:00:16.401 pm infofingerprint mfr:"027A", prod:"A000", deviceId:"A003", inClusters:"0x5E,0x6C,0x55,0x9F"
dev:972020-08-13 08:00:16.379 pm debugbuilding fingerprint for unknown Z-Wave device...
sys:12020-08-13 08:00:15.456 pm warnZ-Wave Inclusion timed out, status:7
sys:12020-08-13 08:00:15.443 pm infoZ-Wave Discovery Stopped
dev:972020-08-13 08:00:14.177 pm debugconfigure() called...
sys:12020-08-13 08:00:00.117 pm warnZ-Wave Network responded with Busy message.
sys:12020-08-13 07:59:50.889 pm infoZ-Wave Discovery Running
Is anyone seeing this issue or have any other suggestions of what to try?
Thank you once again. For anyone following along I have raised this issue over here:
Same w/me on the Zooz - always adds as a genrice "Device." I can change the driver to the stock Zooz Double Plug driver and reconfig, etc., to get the child devices created, etc. However, it won't control reliably (parent or children) from the Device pages - freezes for a while and then executes five or more commands in a second.
I have big errors on the Zooz here with big errors in the logs related to the Zooz double plug.
It's just a mess...I've added and exluded and added again, and it won't work. This is not only a 2.2.3 issue, as I had problems w/it on 2.2.2 as well...
@bcopeland, any suggestions other that exclude/pair again?
A question to the Community, (ok, some context first) most of the Aeotec z-wave devices have 2 Inclusion modes, non-secure and secure. These are usually triggered by either pressing the device button once for a non-secure inclusion or twice for a secure inclusion.
So the question is; does it matter which inclusion mode you trigger on the device? Will a single press still allow my HE to include securely if I forget to press the button twice?
PS, I don't have my HE C7 yet, it's stuck in the Aus Post network still.
No. If you do the "normal" (non-secure) pairing mode, it will pair as such. If you use the "secure" pairing method, then it will pair with...something. 
Any device that I've seen with different secure vs. non-secure methods is an S0 device, so you will probably just get S0 and never see a popup on Hubitat or anything about it (with S2, you'd get a popup allowing you to choose which "levels" to grant).
2 Likes
Cheers.
Have you tested inclusion with the new 2.2.3 firmware?
1 Like
I followed up on this question over here:
Did the update. Started with a shutdown and power off, booted and did the update. Did a reboot and then the zwave update. It took about ten minutes and the counter slowly went from 1% to 100%.
Got confused that the "start update" button was still present, so I clicked it again. It said update was applied. I rebooted and checked zwave if the update button was still there. It was so I tried updating, it said again that update had been applied so I satisfied myself with that. Went to zwave and removed an old failed device.
For now I'm going to just monitor the hub and include more devices in a few days. But it seems solid!
Easy update! Got a bit confused that the start update button in zwave didn't disappear after the update was applied but other than that it was easy.
1 Like
Same initial confusion on the update buttons state not changing...HE is aware and said updating the experience in the future is on their list.
1 Like
So was this update supposed to resolve the inclusion issue (specifically around getting stuck at initializing)? I just did the update (both hub and zwave radio firmware) and I still get stuff on initializing when trying to add a switch. Using Inovelli red's, if that matters.
Was it a Inovelli Red Switch or Dimmer? I had the same experience with a Red Switch but not the Dimmer.
This last one I tried was a switch. I was going to try a dimmer, but don't want to go down that rabbit hole till this is all working like normal.
I've had a few inclusion issues w/GE & Honeywell switches (out of many inclusions), so you may expect to still run into them. 2.2.3 (for me anyway) has made inclusion relatively painless, but not perfect.
