Some "ghost routes" i.e. a device route that shows as going through a non-existent device can persist for a long time. Most will clear but some might not - I had an Aeotec Recessed Door Sensor Gen 5 that would just not adapt it's route for over a week or so. Finally excluded/included and that did the trick. Previously had tried to wake it up, repair, refresh, configure etc.
Note: the device it was trying to route through had been excluded, powered down and did not show in the secondary controller list.
good to take a screen shot of the routing and also any automations, dashboards on the bottom of the device page. Especially if you will be re-doing or replacing it.
when i moved from smartthings i had a million screenshots of all the devices settings and automations to help reproduce everything easily.
I was going to do this but I found that some of the things I was doing in ST probably wasn't the best way to do it. I was definitely one of the problem childs causing all the clould traffic.
Hey Louis, The 3210L's that were screwing up your mesh. Did/do they have the sticker indicating, supposedly, a newer firmware?
I bought all my plugs very late, Iris was going down in flames, I swooped in with a fire suit and grabbed 6 plugs, for 8 bucks each.
Joined all the plugs to IRIS originally, not sure if they updated, but think they did.
Only deal is the plug is communicating at 40kbs for me
I moved a z-wave plus siren from my living room thinking that the rest of the stuff in the room would heal itself. Unfortunately the power strip has fallen off the network again. I've got an outlet coming that will going in a similar spot that the siren was sitting but I am wondering if the power strip will rejoin the network on its own or do I need to exclude and reinclude?
Everything had been running pretty good but recently I've seen some slowness, 9 of 31 devices are running at 9.6 kbps. I have 4 more switches to add but am wondering if I should resolve this issue before adding them.