I've noticed over the past few months every 30 days the C8 will not perform certain automations if the the unit needs to be updated, Is there a way to prevent this from happening?
Please elaborate. Also, Welcome! and if you enter the owners group you can display screen grabs.
3 Likes
Over the years, there have been a few similar claims. Staff are very adamant that there is no way this can happen due to the underlying hub software vs the update software, they are entirely different processes. I believe the update check is just that, it doesn't do anything other than ping periodically (daily?) for an update, and when available simply turns on that indicator. Also, there is no setting you (or anyone that I am aware of) can set to prevent checking for updates.
Also, hub updates are definitely not exactly every 30 days, there is no pattern to updates. I believe that the update notifications are served to users randomly in groups, so that makes it even more unlikely that update checks are causing this.
If this is a recurring pattern, I would suspect that you have a different issue, like running low on memory, an internet router that is doing something unusual, or some automation you are running that happens to coincide with these issues. I also would say that correlation isn't causation, is it possibly you simply notice the update notification when you are looking for why your automations aren't running?
Any additional details you could provide would certainly help. Are you seeing errors or warnings in logs? What steps you have tried to solve this? Also, what hub update version you are on?
For example, can you still turn things on/off manually via the Device tab when this happens? Can you access the hub at all? How do you get things back to working once you have this issue? (unplug, reboot, update, something else?) Have you experienced many power outages, or pulled the plug without doing a shutdown?
5 Likes
This 
is right on target.
As is this
To quote Karl Pearson: “correlation does not imply causation”
6 Likes
Thanks.
HOWEVER (lol):
Remember the job that ran every half hour, I think, that brought down z-wave, for no more than 5 minutes at a time?
I do. 
I think it was Update Z-Wave Stats, or something like that.
Doesn't happen anymore, but then too, they invisiblized the rule, lol.
Likely this, especially if user does not go into the UI very often. Automations not working so go to check it out, hmmm hub has an update every time this happens. If you only check every 30 days there is a high chance there WILL be an update waiting for you, especially with 2.3.9 and now 2.4.0 because they were already working on 2.4.0 while still patching 2.3.9 so there was not much time between the final 2.3.9 and the 2.4.0 release.
Then if you do update at that point, it reboots the hub, which probably fixes the issue. The reboot is what is fixing it, not updating.
Another key point, all your automations run locally. There is nothing that HE can update on thier (optional) cloud services which would cause automations to stop working. You could literality set the hub all up how you want and then totally block it from the internet. It would keep working indefinitely (with occasional reboots I'm sure), without ever going online or updating it again.
3 Likes
As much as I understand that this should be an issue of correlation and not causation, I've found a very similar issue as well, with certain automations and apps seeming not to work in close proximity to an update being available.
In my case I do check, roughly daily for updates, and if I'm having a failure (often a valve controlled by google home community app not responding) it's a virtual guarantee that there is an update. Again, correlation not causation, and presumably it's the restart not the update that fixes it, but shrug.
Not to beat a dead 
but... Being a beta tester, there is an update nearly every couple days, except the short lull between the last GA release and the next major beta starting. So there is a high chance of there being an update available at any given time already to begin with.
If you want to test my theory, reboot without updating next time.
5 Likes
Oh and I don't disagree at all. I suspect the restarting absolutely is the solution. I also can't claim I have anything resembling the evidence that would be useful.
