Webcore - shut down and reboot hub?

[Pantheon]

Any way to use webcore to shut down and reboot a hub?

[sidjohn1]

This is how i do it using RM, you should be able to to send an http POST in webcore too.

[Pantheon]

That worked perfectly in webcore. Thanks.

[rakeshg]

@Pantheon

That worked perfectly in webcore. Thanks.

I do something similar in Node-RED. After the shutdown, there is no way to automatically restart the hub, so I ping the hub and if there is no response for a given amount of time (5 minutes), I send a "OFF/ON" command to the KASA (wifi) plug that the Hub is plugged into (Node-RED has a plugin for the KASA platform).

[Pantheon]

I have that exact setup as well, Kasa outlet. But I am going to cycle the Kasa outlet with another webcore piston from one of my other secondary hubs.

[Prometheus_Xex]

There's a driver called Hub Information that allows SHUTDOWN, REBOOT as well as info.

[RELEASE] Hub Information Driver v3

Driver is a large scale rewrite of the original driver and brings added flexibility in the gathering of ~60 attributes related to general operation of the hub. Driver allows the assignment of these attributes to one of 4 user selectable polling queues and intervals in an effort to allow the impact of the data polling to be minimized (I average around 0.12% of total or less), and the generation of an html attribute for display on a dashboard (template is a text file that may be edited to allow …

[Pantheon]

I'll check it out. But once my hub shuts down, I have to reboot from another hub or manually.

[rakeshg]

Just curious - are you doing a shut down and restart on a regular basis? I do a weekly reboot and the shut down/restart is only in case of two situations

1. Power Outage (shut down before battery backup runs out)
2. Cloud backup failure causing Z-wave devices to misbehave - I get a notification if Cloud backup has failed and I flip an virtual switch to shut down and restart

Any other scenarios that would benefit from an automated shut down?

[Prometheus_Xex]

@Pantheon

I'll check it out. But once my hub shuts down, I have to reboot from another hub or manually.

In my case the shutdown is a last resort. I have a countdown timer for 7 days. If I don't press a virtual reset button, the hub will power off as it's assuming I died (as morbid as it is it will happen one of these days). This puts everything back to manual for my wife as she knows nothing about home automation.

[Pantheon]

Short background info.....I'm having a specific problem with telnet on HE. I control my home audio system (Russound) through HE using telnet. I use webcore for most of those telnet commands. Generally, it works well. For years, my HE telnet connection has been fickle and I don't know why. Recently, on a daily basis, the telnet connection between HE and my Russound gets dropped. I have written code to ping the Russound every hour to keep the telnet connection active. And that SEEMED to work for a while. But after the HE update to platform 2.3.9.196, and maybe previous versions, the telnet won't stay active. Even re-initialization from within the telnet driver will not re-establish the connection. SO, I have to re-boot my HE to re-establish that connection. That's why I have asked on this forum if I can restart the telnet without re-boot. I have asked @support_team to look into it. The WAF here is VERY low.

[rakeshg]

@Pantheon

Even re-initialization from within the telnet driver will not re-establish the connection. SO, I have to re-boot my HE to re-establish that connection.

If you only want a reboot, the endpoint http://YOUR_HUB_IP:8080/hub/reboot (instead of hub/shutdown) will reboot your hub without needing it to be restarted from another hub. Apologies if you have already tried and it does not work for your needs.

[Pantheon]

Thanks for the help. Yes, the reboot works. But I want to do a controlled shutdown to avoid any problems.