There are some issues with the google home integration that might be throwing some errors (check your logs) . @mike.maxwell is aware of it and is working on a fix, he just identified it a couple of days ago.
1 Like
Yeah strange thing is I don't see any errors in the live log or past log. Things were humming along great then out if the blue I couldn't access the hub.
It happened to someone (@GatVlieg ) yesterday also right. I am wondering if it's the same thing or not.
How many devices do you have integrated in the google home integration? I would imagine if this were causing any "hidden" errors it would definitely be worse if you have a ton of devices.
Aside from that theory, I'd say you may need to reach out to support to see if they can look at the full logging to find the issue. They're usually very quick to reply.
90 devices enbled in Google Integration. This is not the first time I've seen this so @bobbyD is aware of this. I would love to see what log he's looking at. Last time he mentioned that it was the driver for the Aeotec home energy monitor but that was not a driver problem. It was the device sending data in CRC16 format and the hub does not support it so there were tons of messages in the log. I correct the device parameter now so it is no longer sending the crc16 anymore.
I am glad my second spare hub just showed up today. Will transfer everything over to that hub to test this weekend.
I have a 120mm fan blowing air at the hub just to make sure that it's not over heating. So definitely over heating not an issue.
I experienced the same thing yesterday, although my hub was on 2.0.1 not the 114 hotfix.
Nooo...I just installed InfluxDb this week.
That's remote reboot and data logging both killed in one day.
Truthfully, I have noticed a bit of lag since installing influx. I plan to disable logging in the app and see if that helps. Right now it logs excessively and I'm hoping that's all it is.
2 Likes
When my Docker Container of Influx DB crashed and burned the InfluxDB Application in Hubitat was screaming with errors.
It seemed ok when it had someplace to hurl the data. It's bumped back down to the bottom of my todo list.
I really like to know what about that app that can cause the hub to freeze? I have logging turned off completely for the app. I am sure the community would love to get this app blessed by the Hubitat dev guru.
As a data point, the same thing happened about 5 days ago but at the time I didn't have influxdb installed.
Ok fine.. disabled influxdb for now. I bet a six pack with someone that it will happen again.
Darn, I was kind of excited and hoping to install InfluxDB this weekend.
2 Likes
Yea I really want a trending solution.
Mine was ok until the Influx instance crashed.
Then I saw a storm of errors.
Hub was ok FWIW though...
I am not giving up influxDB. Love the visualizations. I guess I have been lucky and it hasn't caused me a single issue yet, and I log everything.
2 Likes
Remote reboot gone? Explain.....
I copied your Tasker profile for remote reboot.
See here:
And the root cause here:
Happy to report that my hub has been zippy again after disabling app logging.
I ran mine with log set to only display error and there was no errors in the log.
I initially couldn't get influx working so I had logging at Info. Forgot to change this so it was spamming the heck out of my logs.
yeah if you have too many devices enable it can do that. I just wish I know what's wrong with the app that's causing the hub lock up. I'm wondering if it's spamming the Hubitat with post request to the influxdb server.
My hub locked up Thursday morning as well, requiring a power cycle to restore it to working order. I am also running InfluxDB. Nothing in the logs.
