If the device is a non-S2 device and you are having trouble - pair via the USB Stick. That way you can eliminate the forced "S0" security that happens.
did this with Aeotec Recessed Door Sensor 5's
If the device is S2 and Zooz then try pairing with no security (no checkboxes) NOT S2 unauthenticated.
did this for all my Zen 23/24 V3 switches/dimmers. When I tried S2 unauthenticated it paired partway creating a ghost. note: this was on the 3.6 Zooz firmware not the most recent 4.01.
Maybe the S2 has created a lot of issues. I have never seen any documentation on the setup of S2. Not clear to me which devices support S2 and if they do I do not know the settings to use. OhWell. Everything is working great now back on the C5. One of these days I will learn not to be an early adopter. (right!)
You know you can run the hubs side by side of course. With Hub Mesh or HubConnect you can share devices as needed for your rules.
If going that route (bad pun sorry) then maybe pair a few extenders extending out to the edge of your mesh then start pairing from the farthest out back in.. kind of the opposite of setting things up new. That way you wont mess up your existing mesh while building a new one.
That's what I did for my 2 C-4s to C-7 migration except I use Node-RED for my rules so no HE apps needed - still haven't done the Zigbee stuff.
edit: I am currently running 3 hubs together on our main floor. Having migrated all the Z-Wave devices over to the C-7 the remaining are Zigbee - both hubs are on different channels (15 & 20) and will probably put them on a C-5 instead of the C-7. Zigbee is service is off on my C-7.
Try excluding the device again - I had the same issue where I excluded a device and it disappeared from the device list, but it kept showing up in the routes.
The problem with that particular device was it did not appear anywhere in HE except in the routes so nothing to exclude. On the secondary controller it was already gone. Some devices are still reporting as routing through it.. bizarre.
I was running the C5 and C7 side by side. I migrated all the interior stuff to the C7 and left the outdoor stuff on the C5. I previously had an old insteon system for the outside (isy etc) Change out a bunch of switches to Inovelli switches/dimmers. Again things were fine until the migration to C7. The isy system worked without a hitch for years but I wanted to consolidate. I guess "if it ain't broke don't fix it"
This morning the old routes were still there for 2 devices.
So after thinking about this more - I realized you might be referring to the newly excluded/included device, maybe it's keeping the old node info alive in the system somehow. I've just removed both the Aeotec Repeaters and rebooted.. now running a full Z-Wave repair to see what happens. Still 2 devices showing routing through a non-existent device.. it appears to be a "ghost route" or an artifact maybe.
So day 2 on 2.2.4.158 and my Z-Wave network has worked better! I honestly don't care what the stats page says now, as everything is just working.
The only regression from v.148 is still my 2x Hue Dimmer Remotes, they still fall off my Zigbee mesh almost every time I go to use them. It's not a mesh issue AFAIK as my other 5 battery-operated Zigbee devices are all working fine. I have 8 Mains-powered ST Zigbee outlets across the house and the remotes are very close (1/2 a meter in one case) to at least one each.
@bcopeland@bobbyD was there a driver change or Zigbee setting change after v.148 that could be responsible?
The 3210L's have always been flaky on the Zwave side. I can recall even back from my ST days, they were not recommended as repeaters for locks. When I put them on HE, I had them causing troubles as well until I removed the Zwave side of them and replaced with 2nd Gen Ring repeaters.
Had the same issue this weekend fue to some device failures I had to remove and replace. Zwave repairs did not eliminate these unknowns until I shut down unplugged and rebooted.
Yeah I ended up excluding the newly re-paired repeaters - I did both just to be sure and then briefly powered off the devices that were still reporting as going through the old repeater node... one of my Aeotec Recessed door sensor 5 is STILL showing as repeating through the non-existent Repeater - I've already pulled the battery and also powered off the hub WTF? I guess I will have to exclude it after all - wow.
My Patio Lights are a string of lights connected to an outdoor GE zwave switch. They’ve worked fairly well but this evening, stopped working. After a refresh did nothing, I tried a node repair and it can’t ping the node. I’ll let it sit tonight but this random dropping bothers me.
And now another device has suddenly stopped working - one device which has literally never failed in all of the time I’ve had issues with Zwave on the C7.
