It seemed serious to me. Hub was completely unresponsive and inaccessible. Sure it’s a subjective statement, but if that’s not serious in terms of Hubitat issues, what is?
Reopening this as the issue has reappeared. Hub is completely inaccessible at its regular IP address but immediately accessible on port 8081.
@bobbyD any ideas please? This is getting frustrating.
A reboot brought it back to life momentarily but now frozen again.
That sounds like the database is corrupted. Have you tried Soft Reset?
Also, any errors in the Logs?
Thanks for the reply @bobbyD. I had previously tried soft reset and restore multiple times, before thinking I had fixed it yesterday with Webcore updates. I can try that again now.
Where do I access the Logs? I can only access the diagnostic tool and I don't see anything there.
I read through the whole thread, and, especially paid attention to your initial post. There is one thing that I don’t see that you have done (others may spot others).
You say that you did a soft reset and restored your most recent backup. However, I don’t see that you have done the sequence:
(1) Make a new backup and download it to your computer;
(2) Do a Soft Reset;
(3) Restore the downloaded backup.
Apparently, when you make and download a database backup, it prunes out garbage, so doing the above ends up with a database with no garbage.
I’m assuming that you don’t have a rogue app that is causing issues. For example, I don’t run WebCoRE, so I can’t speak to that.
Grasping at straws, I can think of one other remote possibility that I’ve never seen discussed in the forums, namely, that somehow the running platform firmware has become corrupted.
I suppose that one way to address this possibility would be, after doing the Soft Reset (from step (2)), would be to revert to an earlier version than 2.2.4.158 (I don’t know what prior versions your hub has in its list of previously-seen firmware, then restore the backed-up database (from step (1)), then do a firmware update to 2.2.4.158 (which is working fine on my C-7), which would download a new copy.
Now you cannot, but after a Soft Reset, when the hub is accessible, screen your logs for errors and warnings. The Soft Reset is only a band-aid to bring your hub to life. But if the same problems that brought the hub down in the first place, persist, it's a matter of time before it locks up again.
Thanks for the detailed reply. Trying this now.
Thanks, trying this now,
Soft reset brought it back just long enough for me to view the logs, but now it's frozen again.
I didn't see any red in the Logs but there were a couple of recent Warnings saying:
"Received cloud request for App 343 that does not exist, path: /ping from 54.83.153.160"
How do I know which App is App 343?
Edit: a search of the forums indicates this might be related to Hubconnect, which I do actively use. Checking to see if my Hubconnect software is up to date...
Click on App 343 on the error line, it will highlight the app in the list at top of logs listing.
1 Like
Good thinking, but as the error says:
That is an external source looking for an app that has been removed. The only way to stop that error is the remove the hub IP address from whatever the external source might be.
2 Likes
Might temporarily disconnecting the internet allow some time for more troubleshooting? Of if the issue goes away with the internet disconnected that is useful as well.
I had something like this a year or so ago and even with @bobbyD help it's not always easy to find. In my case I had flipped from the built in life 360 app to the community one, I then had to delete that or something (can't remember exactly). The end product was that the external cloud was drumming my hub help bent on calling home. I ended up going nuclear on life 360 and deleted my accounts and started back up again. That seemed to be the only option, there was no way of removing what wasn't there and that was the problem.
3 Likes
It’s an Amazon AWS IP. Perhaps that helps?
Thanks. I think it's related to Hubconnect. Trying to uninstall that now...
Perhaps Alexa is lonely and wants to talk.
6 Likes
Well "she" always wants to "listen" that's for sure...
Did you use Echo Speaks before? I had this when moving Echo Speaks to another hub but didn't remove the Heroku server configuration for previous hub.
I uninstalled Hubconnect from both my SmartThings and Hubitat hubs. Then had to do one more soft reset and restore. Things have been stable for an hour or so now. Fingers crossed.
The only reason I had Hubconnect installed was to include three Honeywell WiFi thermostats into Hubitat. Not worth the effort though, the Hubconnect installation and maintenance process is way too complex. I guess I will be upgrading those thermostats...
1 Like
I was using hubconnect for my Honeywell too and moved to this driver. I set the update frequency to 15 minutes and it's been running just fine. In case you hadn't seen this integration.
1 Like
