Logsocket stopped working after hub rebooted on its own

I have a rule that fires on hub restart to then restart NodeRed as I had a similar issue a while back. I also have a flow that will update a switch every 5 minutes as a checkin and if my hub doesn’t get an update from NodeRed it will alert me it’s offline. So have both sides covered.

To restart NodeRed I used a modified @ogiewon HTTP switch that I toggle. I had to modify his driver to pass extra query string parameters and a header required by NodeRed

Syntax to restart NodeRed is:
http://Ip-address:1880/flows with a header of:
node-red-deployment-type:reload

Happy to submit a pull request to @ogiewon if he’s interested in adding this functionality to his awesome driver.

3 Likes