The posts in this thread suggest otherwise.
I certainly haven't. Neither of my C-8 hubs needed routine rebooting. I would typically reboot only for a platform update.
Apparently without engaging Hubitat Support via the community?
The posts in this thread suggest otherwise.
I certainly haven't. Neither of my C-8 hubs needed routine rebooting. I would typically reboot only for a platform update.
Apparently without engaging Hubitat Support via the community?
What exactly is the bug. What I see is one persons anecdotal evidence saying they have a problem and several folks responding saying it isn't true. That doesn't indicate a bug is present
If you truthfully believe that then you should engage with Hubitat support instead of giving improper advice. They can look at your engineering logs and maybe find a solution for you. Clearly based on all of the responses here what you are seeing is not how it should run. That said you should also be ready to face the possiblity it is something in your configuration as well. Just becuase we don't want to believe it is something we are doing doesn't make that true.
My guess is you have something running on short intervals. The short interval of the task is to short for each call of the task to complete. Overtime that will create a backlog and eventually hang the hub. I have seen it many times. Some in my own stuff i was testing, once when i was submitting stuff to maker APi, and I think a similar issues occurs with Ecobee Suite when the poll interval is to long and to much stuff has changed.
That said a DB with bad data will cause all kinds of havoc in the hub as well so you really neeed to run the option to rebuild the DB any time the hub is not rebooted gracefully from the menu.
What the community are trying to say is that this is not normal. Not for a C-8, or a C5, or any Hubitat.
Just because you have tried starting from scratch and then building the same thing over and over again and got the same buggy result is not surprising. Obviously there is a problem somewhere, and it is just being re-introduced to your system every time you rebuild it. Maybe it's just a bad hub even. Either way, daily lockups are NOT normal, for any Hubitat device.
Wanting to believe something isn't the same thing as it being true. If it was, I'd have homes around the world that I would fly to in my own LearJet.
If the C8 always locked up constantly for everybody there would hundreds of posts w/every C8 owner saying they have to reboot their hub constantly to keep it from locking up. You have a problem specific to your setup (apps, devices, automations & configurations, hub settings, etc.). Repeatedly resetting and re-creating the same unstable setup over and over is like building and re-building a structurally unsound bridge - it will keep falling down.
You haven't asked for any help at all over the past year and a half - that's kinda shooting yourself in your own foot-ish...There are ways to troubleshoot and ID the issue(s) causing the problem, if you want help with that there are folks here who will be happy to help, all you have to do is ask,
Of course, if you do just want to keep rebooting, that's your call, it's your hub/home.
Hopefully itās clear enough by now that this is absolutely not the case.
I wish you had reached out to the community sooner rather than troubleshoot on your own for a year and a half, since thereās almost certainly a more durable solution to be found.
Rebooting is always just a band-aid. For some people, a helpful or even necessary one given how they use their hub. But thatās a rare case.
It has been like this since I got it. No updates fix it. I have tried having no extra devices from a hard reset many times, just a few zwave, no apps and still locks up randomly after a few days. It is just a bug in the C-8. There is no way for you to convince me otherwise since I troubleshooted for months. It is silly to basically say I am wrong. What I have experienced is the reality of it. You are basically saying the default config is buggy as that is what I used.
Firmware updates have never fixed it.
All I did was make this post to help others with C-8s so they know someone made a rebooter app that will allow auto-reboots to fix the issue. There is some kind of bug in the C-8 that rebooting will fix. I did not find out about this rebooter app until after I started googling how to make it auto-restart after the months of troubleshooting and configs. I was ready to throw it away and get something else, but the rebooter worked.
I am just posting this to help others going through the same frustration with the bugs in the C-8. You can ignore it if you found a different solution for the bugs. Just state what you did to solve the same problem to also help others.
The only thing that would be helpful would be Hubitat adding in the auto-reboot function into the device settings so you dont need to add separate code.
I wouldnāt recommend tackling problems alone ā not for a day, and certainly not for a year. This community is full of brilliant users who can help you get the most out of your Hubitat Elevation. Best of all, when more people share similar issues, our engineers are able to step in to address them directly or at least offer guidance on how to avoid them in the future.
Has anyone yet asked when it locks up can you access the diagnostic tool at all? What color is LED? etc... In fact there is an entire pinned post that asks a bunch of standard questions.
--> ā¼ READ FIRST - Before Posting in Get Help
Only two know possible issues other than hardware failure.
If you are using Ethernet, I think the C8 is still susceptible to getting locked up from Jumbo Frames multicast packets that reach its ethernet port.
If you have it on Wi-Fi, it is susceptible to get disconnected from the Wi-Fi and not reconnect if the router does automatic optimizations (often in the middle of the night) where it scans the Wifi bands and then adjusts it channels.
If you stay fixated on this, which is probably a fallacy, youāre unlikely to accomplish much in the endā¦
ETA: itās always possible you have a defective unit. Iām speaking about the C8 or the hub platform generally.
I have no Zigbee devices. Only few Zwave switches, Zwave door lock, 1 hue (ethernet), tailwind q3 wifi, 2 ecobee thermostats wifi, and a timer rule.
From troubleshooting I have done hard resets, default config, and only had some Zwave connected with nothing else. This was over several months of just trial and error with the Zwave devices and waiting a few days to see if it would crash again.
There is still a bug. I had have several firmware updates also. The only thing that worked 100% was doing the auto reboot.
Isnāt it possible it has something to do with one or more of those z-wave devices?
You have provided absolutely zero data, zero troubleshooting results, that clearly support your imagined conclusion. Just a lot of suppositions and assumptions. There is also no data here in this forum that supports your imagined conclusion. Believing something doesn't make it a fact...you have no QED.
So you (and we) have no idea why your hub is locking up, and labeling the issue a bug in the absence of that knowledge is meaningless. To paraphrase...if the only tool you have is calling things bugs, then everything is a bug. I'm out...
It may be time to close this thread.
The OP clearly isn't interested in hearing from others. He just wants to assert unsupported conclusions that aren't based on any factual information other then his own anecdotal observations. There has been plenty of information provided to contradict his conclusion. Then when faced with those other personal experiences that contradict his own he is doubling down indicating others are wrong. This isn't going anywhere and hopefully if others read this, they will understand the truth of the matter.
Agreed - @roneill has provided no data supporting their conclusions.
Surprisingly, for a first time poster to the community, they have apparently been using their hub for 18 months, before drawing the erroneous conclusion that all C-8 hubs require a daily reboot.
Others facing issues with their hubs or automations generally find it beneficial to engage with the community much sooner than that.
And, for the record, while it is entirely possible that @roneill got a "bad" hub, it is totally incorrect that all C-8 hubs need a daily reboot.
Rebooting is never a fix, it's a band-aid to cover some other issues. We've been saying it since 2018.
If you'd like us to help you narrow down the issue you are having, please send me your hub's MAC address and I'd be more than happy to further assist.