Z-wave not working after reboot by URL

🛎️ Get Help
1

I have a piston that reboots my C-7 in the middle of the night when memory is below a certain threshold. It simply calls the /hub/restart URL and sends me a notification.

The problem is that my Z-wave network doesn't work afterward until I connect to the hub and click the reboot link in Settings.

Why does manually clicking reboot work, but calling the URL not work?

2

Are you calling reboot or reload?

1 Like
3

You might also look at using RM and @thebearmay 's Hub information driver.

image
image3298×1741 388 KB

4

The piston checks freeMemory from the Hub Information driver and if it's below 200000 KB it makes a POST request to http://10.0.0.2:8080/hub/restart. The hub restarts, but Z-wave devices don't work.

Then I manually click Settings > Reboot. The hub reboots and Z-wave devices work fine afterward.

Does this answer your question?

5

Same results if you send the POST maually and then check functionality?

6

I am not certain what /hub/restart does, but the reboot operation from settings menu sends a POST to /hub/reboot (at least on my C-7 with 1.3.6.144); you might try changing the endpoint in your rule and see if it works better

2 Likes
7

I too use reboot in a rule:
Maybe restart does something a little different?

image
image858×341 25.2 KB

8

So far, this is all I've found.
edit: There's more about restart vs. reboot down farther in the thread.

9

I changed the ending in my piston to /hub/reboot. Reading that other thread, I think reboot is the one I want.

BUT for some reason I can't call http://10.0.0.2:8080/hub/reboot or even /restart (which works from my piston?) from my phone browser. I get 404 errors for both. If I leave off everything after the port, the admin interface comes up.

10

Reboot/Restart are HTTP POST URLs. Your phone browser is doing an HTTP GET.

4 Likes
11

use reboot instead of restart

http://hub.ip.addr:8080/hub/reboot

12

Got it. This is making more sense now. I changed the endpoint in my piston and tested it. It rebooted.

The browser POST vs GET thing makes sense. I know the difference from way back but never would have thought of that.

Thanks, everyone! Time will tell if this fixes the Z-wave stuff not coming back, but so far so good.

2 Likes
13

Not sure if it relates, but when I had my Z-wave devices totally disappear after a cloud backup (now fixed), the only thing that would bring it totally back was a shutdown/power cycle. But, if you're starting with a good mesh, I'd think a reboot would be good enough.

14

In your case that was because the radio was corrupt. Doing that will clear it.

2 Likes