My Hub keeps crashing, I don't have any custom apps

🛎️ Get Help
1

So for the last few weeks my hub has been crashing pretty regularly, green light on the hub but unresponsive to automations or login attempts. The only solution is to unplug the hub, and plug it back in. This started around the time of the last update, and has been getting worse.

I'm not using any custom apps, and I'm not using any custom drivers, I'm not even doing anything terribly complex with the hubitat, a bunch of lighting routines tied to motion sensor triggers using the rule machine. I had one semi-exotic rule for controlling my thermostats, which I disabled hoping it would improve reliability. It hasn't. I had to unplug the hub last night and plug it back in, around midnight, and when I woke up my outdoor lights were still on, hub crashed and unresponsive. It's crashed right now as I type this.

How do I troubleshoot this, what logs should I be looking at, and how do I fix this? Finding it hard to locate the motivation to install additional z-wave devices when I can't reliability control the ones I have.

2

I would start by downloading a backup to your computer, then copy your hubs mac address, navigate to your hubs ip address:8081, select soft reset, enter mac address. When soft reset finishes at the bottom of the screen select restore from backup and select your backup file. When that finishes navigate back to your hubs ip address:8081 and select shut down hub. Unplug hub wait 30 seconds and plug back in. See how it goes. With all of the unplugging of your hub, your database if probably fubar and this should fix that.

3

I am in the same boat - in fact, my hub just died right now. No response except to pings. I do have a TTS driver and a TP-Link Switch driver installed. This is frustrating, as I have to power cycle my hub every couple of weeks because of this.

I guess I will try Ken's suggestion.

4

this was your mistake. you may have just had a blip but doing this has sent you down the wrong direction. the Hub should never just be pulled. your best bet now is to do a soft reset you recover your database as its likely to be corrupted.

go to backup and restore and create a backup and save it to your PC. then go to http://HUB-IP:8081/ and click soft reset

1 Like
5

Huh, this is the first time I've seen the suggestion to go to port 8081 and do a soft reset. I had no idea the hub can still be responsive on that one, and I was in earlier threads about this.

1 Like
6

Don't hit soft reset unless you have a backup downloaded to your computer! you can try a reboot or just shut down from there though. soft reset wipes out everything but the devices connected to the radios.

1 Like
7

Thanks, yeah I was careful to read over the menu and your post. I just did a Reboot, and will make a backup.

2 Likes
8

So soft reset, uploaded my backup, and it's telling me to "Get Started" and configure my new hub.

Go through the intro screens, select the same name for the hub, I see my devices and automations. Let's see how long this goes until the hub crashes again. It's 8/10/19 at 5:29PM.

9

@Barely.Broke You didn’t reboot. You need to shut down or reboot after the restore.

1 Like
10

9:47PM, just noticed my hub has again crashed.

Lighting routines not working, doesn't respond to Web interface, attempting to reach hub at hub-ip:8081 fails, but it's still sitting in the closet with a green light.

So since I'm not supposed to unplug it, what do I do?

14%20PM|649x500

11

youhave the Mac address of the hub... you should be able to use that in your Router to see what address it's using. Slightly easier though is to visit the portal at portal.hubitat.com and after logging in, find your hub. If you hub can talk to the cloud, then the portal should know by now, what it's address is... see if that matches. (aka DHCP reservation working or not?)

1 Like
12

The hub doesn't show up on my network. It has hard-crashed.

Scanning my LAN clients, the IP address used by the hub is missing, and the hub doesn't show up. Hubitat.local is unresponsive. http://10.0.1.45:8081/ (my hub's local, reserved IP) is also unresponsive. According to my router, 10.0.1.45 is not currently being used by any devices connected to my network.

The hub, on the other hand, is sitting pretty in my media closet with a bright green LED light.

13

My question was more about DHCP working right. Obviously a tiny typo in the MAC address would mean a no-match and you wouldn't get the IP you plan on. I'm convinced it's not where you expect it.. but is it there anywhere? Is the hub's MAC anywhere in your ARP table (router)?

1 Like
14

No, the hub has disappeared from my network and is no longer functioning or accessible.

15

You can choose to wait for Support to answer your Ticket or, unplug it.

You already know the process for doing a Soft Reset and restoring the earlier DB. It might reboot perfectly, but then again, a corruption may not be instantly recognizable.

16

Right. My hub crashes every few hours, and I have no custom apps or custom drivers. It'd be nice to know why, since a hub crashing every few hours is a broken hub. Any troubleshooting tips beyond debating whether or not my hub has crashed?

The soft reset didn't solve my problem, my hub crashed four hours after a soft reset.

I actually unplugged and plugged my hub back in an hour ago, when I last posted on this thread. Just realized my automations aren't responding, so my Hubitat elevation has crashed once again.

17

Have you reached out to support and done a ticket? You mentioned earlier you had a few suspect rules could you post them? How much logging have you got turned on? You can also @bobbyD to see if he can help :+1:

1 Like
18

I opened a ticket, but it's not during Hubitat Support's hours of operation, I'm sure they'll reach out Monday.

Frankly, I wouldn't even call them suspect rules, I had one rule based on an interval (controlling thermostat fans to filter the air while I'm home, every 1 hour. I have another rule which is timer based. Everything else is controlled by a motion sensor and is close-ended.

I disabled the interval rule as a way to troubleshoot my crashing hub, here is that rule:

IF (Mode in Day Home, Night Home(T) [TRUE]) THEN
Thermostats: Office Thermostat, Kitchen Thermostat, Family Room Thermostat, Dining Room Thermostat, First Floor Thermostat, Master Suite Thermostat, Foyer Thermostat, Upstairs Bedrooms Thermostat, Upstairs Lounge Thermostat:
--> Fan: on
Delay 0:15:00
Thermostats: Office Thermostat, Kitchen Thermostat, Family Room Thermostat, Dining Room Thermostat, First Floor Thermostat, Master Suite Thermostat, Foyer Thermostat, Upstairs Bedrooms Thermostat, Upstairs Lounge Thermostat:
--> Fan: auto
ELSE
Thermostats: Office Thermostat, Kitchen Thermostat, Family Room Thermostat, Dining Room Thermostat, First Floor Thermostat, Master Suite Thermostat, Foyer Thermostat, Upstairs Bedrooms Thermostat, Upstairs Lounge Thermostat:
--> Fan: auto

The crashes don't seem to coincide with any global event, with all logging turned on, the last recorded action is usually mundane (eg motion rule expires, and a dimmer switch is turned off), 3-4 minutes later, I realize my hubitat has become unresponsive, and is inaccessible.

19

If you’re using Chrome, please check if closing the tab and opening a new one allows access to the UI. Sounds like you have other issues, but I have encountered this issue several times since a recent Chrome update. It appears that the hub isn’t responding, but closing the current tab and opening a new one immediately shows that the hub is actually working fine, and the issue is in fact Chrome.

1 Like
20

I too have had this it's a right pain.

1 Like