I've been on Hubitat for about two weeks now and I'm loving the platform and community. Unfortunately I've had about three crashes of the hub now with another one occurring today around noon. I got home and the Hub (I'm on 2.1.1.122) still showed a green light on it but was non-responsive to any attempt to login to it. I yanked the power and rebooted it and it's working fine now. I didn't think to pull the logs until about 2 hours later and how I can't get back to the time when it occurred. My logs only go back about 30 minutes before I'm stopped with the ---Loading Past Logs...--- and nothing beyond that.
So I'm assuming that's as far back as the logs go and there's nothing I can investigate to figure out what crashed the hub? Is there anything else I should be doing to troubleshoot the root cause once I'm able to nail down time of crash? I'm assuming it's an app but don't want to start randomly uninstalling apps and waiting days to see if I can stability back.
The app that caused my hub unresponsive / slow down issues was Chromecast. As soon as I disabled it I have had no more issues (2 months ago).
If you have that app enabled it could be worth disabling that first to see if it resolves your issue. If you do disable it don't forget to redo any rules that could be using your Chromecast devices.
Just thought I'd post this for information.
@2ac16mo At the top right just below the right edge of the "Built in App" button is a very faint grey X. Click on the X and it will expand the disable check box beside each app.
I'll disable Chromecast and see if that solves it. But back to the idea of looking at the logs after a reboot. Generally how many Kb will the logs hold?
Sorry to repeat myself but if you have any rules pointing to a Chromecast discovered device either allocate that rule another TTS device, disable the rule or remove the TTS part of the rule.
If you don't you will have rules trying to send TTS messages to a device it cannot reach.
Good luck and I hope it works for you.
Yeah, I'm the same. I'm now sending to a Sonos speaker which I normally have in a group in the Sonos app. Occasionally it messes up the group.
Never mind I'm sure they will get there.
Other than some odd limit on MP3 length (at least ones that are stored on remote servers), I’m using Cast-web API. It’s very capable and doesn’t cause slowdowns or other issues.
Having said that, I’m also still running the Chromecast Integration (beta) so I can play an MP3 for my doorbell without it getting cut off, and not having any issues. I’m on platform build .122
I'm having good luck with Chromecast too.. but I barely use it. Just having it on the hub (my third/coordinator hub) without using it, does not seem to impact it, detect-ably. @bobbyD told me a couple months ago that it was throwing errors, and that Engineering had been notified of those errors. I'm going with the hope that at least ONE FW upgrade since then squashed the errors.
We have traced the problem to the Chromecast hardware itself, not our integration per se. These things freeze sometimes. A power cycle of the Chromecast device may resolve the problem without the need to disable the integration on Hubitat hub.
Depends what problem we are talking about I guess. Under no circumstance EVER should unavailability of the Chromecast hardware cause the Hubitat Hub to crash...
