Hello.
Is there a command that I can I use (in RM, or elsewhere) to schedule a zwave repair on a regular basis?
If there isn't, can this be added to the list of feature requests?
Why would you want to do this? Are you constantly adding or moving devices around? You should not need to do this.
1 Like
Short answer....no.
I agree with @dman2306. It should not be necessary and will probably create more problems than solutions.
1 Like
Not in RM. But if you have an SBC that runs any form of *nix, then you could schedule the following script as a cron job to run at the time of your choice. Simply replace the variables he_login, he_passwd, and he_ipaddr.
#!/bin/bash
#
he_login=your_he_login
he_passwd=your_he_password
he_ipaddr=your_he_IP_address
cookiefile=`/bin/mktemp`
#
curl -k -c $cookiefile -d username=$he_login -d password=$he_passwd https://$he_ipaddr/login
curl -k -sb $cookiefile -X GET https://$he_ipaddr/hub/zwaveRepair
sleep 30
curl -k -sb $cookiefile -X GET https://$he_ipaddr/hub/checkZwaveRepairRunning
rm $cookiefile
Edit - just want to add that I am not advocating you do this. However, one can do it if necessary. I do run a z-wave repair via cron once a month.
2 Likes
Thanks very much!
I can actually use the HTTP momentary switch (from @ogiewon) to make up a device which will allow me to schedule this in RM whenever I want.
Thanks again!
1 Like
I forgot about that.
You will have to specify the port of 8080....you can't send and receive a message on the same port at the same time. So you have to use what one of my old bosses called the "backdoor port". 
Since your request will be going out from the hub on 80 you can't receive it on 80 as well. They'll crash. So, just use:
http://hub-ip:8080/hub/zwaveRepair
BTW...i didn't even know that was possible. Good call @aaiyar.
1 Like
Yes, you're correct. @jtmpush18 will have to do so to use RM.
zigbee mesh rebuilding is also possible without a hub shutdown and restart. One simply needs to disable the zigbee radio for 30 minutes and then enable it. Here are the relevant commands as part of a shell script.
curl -k -sb $cookiefile -d "zigbeeStatus=disabled" -X POST https://$he_ipaddr/hub/zigbee/update
sleep 30m
curl -k -sb $cookiefile -d "zigbeeStatus=enabled" -X POST https://$he_ipaddr/hub/zigbee/update
Yeah...but you definitely shouldn't do that all the time. Putting battery powered Zigbee devices into panic mode frequently is a great way to drain their batteries really quickly. Zigbee is self-healing (unlike z-wave). A force heal should only be necessary if you've moved a bunch of devices around or added a bunch of new ones.
1 Like
100% with you on that. I'm not advocating doing it routinely. Just pointing out that it can be done without a hub shutdown.
2 Likes
I also agree that putting the zigbee mesh into "panic" mode should not be done on a regular, frequent basis.
However, I suspect that doing it, say, once every 4 months, may be beneficial without draining the batteries too much. Certainly you can do that with scheduling it and automating it, but it certainly makes it a lot easier to do.
In regards to a hub reboot on a regular basis. I don't think that you should have to do that, but it does appear (from the forum comments), that there may be some benefits to doing so. Again, scheduling a reboot for an off peak time,say once a week, would make that process harmless.
In regards to a zwave repair on a regular basis, I don't think that you should have to do that, but I know that other hubs do schedule that on a regular basis. Again, scheduling a zwave repair for an off peak time, say, once a week, or every two weeks, should make that harmless.
1 Like
