Over the last month or so, I have noticed the hub slowing down and yesterday evening when I returned home, none of the automatons kicked in. When I tried logging into the hub, an "Error 500" was reported. Attached below are the screen shots. Please let me know how to troubleshoot this.
Can you log in via port 8081?
If you can maybe try a reboot from there.
To echo what @bobbles said, if you can access the Diagnostic tool, and a reboot doesn't solve your problem.
Then I recommend performing a Soft Reset with restore, following the instructions in this document:
https://docs.hubitat.com/index.php?title=Soft_Reset
You may want to check the Logs to find out more about the errors you are getting:
https://docs.hubitat.com/index.php?title=How_to_Collect_Information_for_Support
If your problems persist or worsen, please send us an email at support@hubitat.com, if you didn't do so already.
Thank you. I was able to reach the diagnostics tool and reboot the hub from there.
@bobbyD Thank you for your response. I was able to reboot via diagnostics.
I will perform the above two steps. If the problem continues, I will send an email. Thank you for your quick response.
EDIT: Hub doesnt allow me to "Soft Reset"
On the diagnostics page, logout and then log back in again.
That should solve the '401' error.
Thanks I was able to soft restore and restore from a backup.
The Hub has crashed again. This is 2nd time in 2 weeks. I have not installed any new Apps or devices since the last time. This time around when it failed, all the lights lit up at midnight.
This time around I cant get to the diagonistics page for a soft reset.
Then one of 2 or both could be the problem.... a bad custom app/driver OR a badly written RM. You need to check that.
Sorry for the troubles. Not being able to access the Diagnostic Tool is indicative of a much different problem than last time. Are the lights that came on, Zigbee by any chance? The hub crashing wouldn't trigger the lights to come on. Would it be possible that you had a brief power outage? Also, what color does your hub's LED showing? I would first check to make sure that your hub's IP didn't change.
Lights are Sengleds. Now that I think of it, they are outdoors and on motion sensors. Most likely they came on due to motion (we get raccoons etc), but they never turned off. My wife said they were on for more than 30 mins, before I got up and turned them off. The Sengleds inside the house were off.
Hub has a green LED.
There was no power outage.
Checked HUB's IP on my network. It has not changed.
What are my next steps?
Apologize. I was typing the IP incorrectly (rushed this thing right after work !!). I'm able to get into diagnostics. I'm going to soft reset it. I would not like this to happen again. At least not this often. Suggestions on finding the root cause? I travel for work, if this happened when I was not around the WAF would fall dramatically !!
@bobbyD
Three days into soft resetting it, Hub has crashed again. I need a permanent solution.
Thanks for the update. I am glad that your hub is back online and connected to the cloud. I was able to download its error log. I would start by temporarily disabling your custom code apps and drivers to see if that resolves the problem. I have seen problems with the InfluxDB Logger as well as Wemo devices, so I would start with those.
If you don't know how to disable an app or a driver, please see "Disable Device Drivers" and "Disable Apps" sub-headings in the following documents:
https://docs.hubitat.com/index.php?title=Devices
https://docs.hubitat.com/index.php?title=Apps
Also noticed an issue with your location settings, so please make sure that all fields are populated under Settings >> Location and Modes.
Thanks! I was looking at the logs and noticed the same. I will work on it. Will keep you in the loop.
@bobbyD
I Removed the two apps that were throwing an error, didn't notice any other major errors in the logs. The hub ran pretty smooth for about 9 days, but yet last night the hub crashed and gave an Error 500. I Soft Reset it this morning. I have noticed that the crash typically happens at night after the hub performs its backup.
@bobbyD Yet again ! Was working fine for about 2 weeks. I had removed all custom apps that were throwing any sort of error or warnings. This is what I found in the logs.
You may want to check out Rootin Tootin Self Rebootin. It’ll detect when these happen and attempt a safe reboot.
I’d also create a rule that sends a notification when your hub boots up, so you can track the reboots.
Thanks. I will try it.
@adamkempenich I have installed the app and created a rule to notify reboots. What constitutes a slowdown causing the app to reboot? I would like to keep an eye on it to make sure I set it up right and it works. I'm also using Hub Watchdog.
Download the Hubitat app
