Can any one help me understand why I get this error and have to restart my hub once a week?
Can you get to it from a PC? Can you get to yourhubip:8081?
If the answer is yes to both, do a soft reset...
Are you saying that will fix the weekly issue? I need my automations to run right away, so I just go and pull the power quickly. Will the soft reset fix the problem all together or what can I do to find the cause of the hub crash?
The problem with just pulling the plug is that can cause a corrupt database or make a corrupt database even more corrupt. Start with doing a soft reset. Corrupt databases can crash hubs
2 Likes
Ok will do. But how do I get to the bottom of what’s causing the hub failure?
Start with the soft reset. A corrupt database could be causing it. Next start checking logs for devices overwhelming the mesh etc
Go to the backup settings, download a local backup then restore it right away (this does a soft reset automatically when you restore). This might fix it on its own. Especially if the problem is low memory (ram).
What color is the LED when it locks up?
If it locks up again, you need to try getting to the diagnostic tool at HUB.IP:8081, this will tell us if it got knocked totally offline or just the main OS crashed (leaving the diagnostic tool still working).
1 Like
Thanks. I will try this. The HUB was green this morning when it said “no response” before I pulled the power plug.
Ok I tried the hubip:8081 but now I’m stuck at incorrect MAC address. I am using Wi-Fi on my Hubitat and I grabbed the MAC address from my Eero but it’s not liking it. I never setup a static IP, is that needed to access the hubio:8081?
Edit: well I found the MAC address on my Hubitat settings page and it’s different from the MAC address my router said. Guess I don’t understand it all lol
It uses the Ethernet MAC to log in there which is on a sticker on the bottom of the hub. The Wifi MSC is different. Sorry forgot to mention that. But just the fact that the page loaded tells us the main OS/JVM is crashing and not the networking.
But if you can log in there when it happens and reboot from there it is safer for the database than just pulling the plug.
As far as figuring out what's wrong, I think the first step would be to do the backup / restore and see if it helps.
Then it would be good to see a good chunk of the past logs right after rebooting (showing the logs section from right before and up to when it stopped responding)
Thanks, next time it fails I will see if I can get it to show the logs right before it failed. The errors I get now are for Tuya and Action tiles. I just submitted to refresh my Tuya token but not sure whats going on with Action tiles. These are errors I just had, after I did a reboot and restore.
Are you using ActionTiles and it is working? If its not working I would disable that app for now. If it keeps hamming the TCP connection that can run the hub out of memory and eventually make it crash. How to disable apps: Apps Page | Hubitat Documentation
Also how many devices do you have integrated through that Tuya cloud integration? It is pretty intense due to all the encryption and decryption. A lot of devices on there will crush the hubs resources.
Action tiles seems to work fine for me. I have about four Tuya Wi-Fi bulbs.
Got another no response today. Will try the steps above when I get home.
Might want to put in a warranty claim as well: Warranty – Hubitat Support
Thanks but I’m well beyond 90 days
Has this been happening the entire time or is it a recent problem? If its more recent it is probably not a hardware issue anyway. Did it start after any changes were made? Updated the hub firmware? Added new devices? Etc...?
For the Tuya integration, if you have resolved the errors, just the 4 bulbs on there should be fine and not cause problems.
ActionTiles, the errors looks like maybe they just go in spurts? Not sure how often that is happening but if it is just occasionally then it is probably not a huge problem.
It has always happened but was more sporadic. Just recently started happening weekly or multiple times within a week. I disabled Action tiles before and I thought I renewed the Tuya token.
I’ll check it here soon, I used to get errors with Bond and Konnected.. will see if I can gather any info from this crash.
I really appreciate your help in trying to solve this.
Ok just got home and the hub ip:8081 doesn’t work. I’ll have to try hard wiring the C8
Are you updated to the 2.3.6 hub firmware? They did make some improvements for the reconnect logic to help with Wifi getting disconnected and not coming back. Mostly seemed to be an issue with mesh networks which it sounds like you have.
