I think the closest z-wave equivalent to a "zigbee panic" is shutting down the hub, removing power for ~30" or so, and then booting back up. That recages (for lack of a beter term) the z-wave radio.
Letting the z-wave mesh settle can take several days, maybe even a week. So it'll likely take some time for devices to find that new repeater. Be patient - mesh changes are rarely fast with z-wave -- it's a mysterious animal that moves at its own odd pace.
If you already have repeating devices there (switches) it may not add much extra options, unless you can get it significantly closer than the other devices. You may actually want one on both ends. They probably would not route through both at once but it gives extra options.
If you go to the device page and click on events, you should be able to see where Sharptools or whatever your rule is, initiated a command for the device. That is how you can confirm the command made it to the hub and was sent to the device. Since you said it takes multiple tries to activate it I am guessing the command will be in there but its good to double check so you are not chasing a ghost.
For the cost of these, I think you are right. I'll get another for both ends. I just checked and only 1 device back there is going through the extender. They are going right past it doing there own thing!! I'll give it some time to see how it settles in. I'll check those logs to verify the rule is making it here as well. Good idea!!
The routes listed are not always to be trusted. They are not updated live, a lot of the routing is done by the devices so the hub does not always have the latest information. So it probably was a route at some point, but may not be the current route it is using right this minute.
The important thing is giving them more choices so they have a good route and a couple good fall back routes if things are going slow.
I still have no explanation why this worked perfectly on ST. Unless the radio on ST is dong some sort of advanced mesh shaping but usually they just sit there and listen for stuff.
I'm thinking you are right, and maybe ST was working well because it had many years to "get it right". I switched because the hub started giving me problems and ST support basically disappeared.
Update: My Sunrise trigger happened around 6:45 AM today. One of the devices that was giving me trouble worked as expected. (The others will get triggered throughout the day). So at this point I'm not sure what made the difference.
-Updating the hub to the latest
-Adding the extender
-Enabling Command Retry on those devices
-All of the above
Will I be able to see in the logs if Command Retry was actually used to turn this device ON?
Yes, you may need to open the full logs and not just for the device from the device page. I think it was fixed so they show as the device according to the wording in this announcement.
Also checking the Device > Events tab can be helpful.
It shows what called commands and then the device responses (if there is a state change).
Example:
NICE!!! I'll check tonight when I get home!
Download the Hubitat app
