I think I've seen it once or twice.
Thanks.
I am guessing you may want a few more conditions surrounding that, if you do decide to implement any sort of rule. I.e. waiting for... a bit... and see if the load continues beyond the event, or drops off.... I'm expecting you may need to leverage a Hub Info device for that secondary assessment.
...If not some kind of notification and manual reboot....
1 Like
So, the SevereLoad message could be transitory?
Can't claim to have studied it closely, but that would be something I would expect. Given it's an event it would make sense to me it would be a momentary indication of load, rather than any longstanding issue. But best to analyse behavior over time before choosing it as something to base a rule upon, IMHO...
1 Like
I would say it bears further research most of the time.
I have seen Hub SevereLoad warning a few times on both my Prod hub and my Dev hub. I have caused it a variety of ways as well had apps trigger it. No matter what caused it generally speaking i needed to understand what happened to adjust my hub to make sure it didn't happen going forward. I would say you knowing it happened and maybe what was going on around it would be the most important thing.
In theory it should be transitory, but for the most part i haven't seen these hub spike much without something wrong going on. I have had my hub get this message from Maker API getting hammered on a virtual devices getting updated by node red to frequently which took days to show up. It just took that long for the work load to build to get to the point of trigger the alert. In that case it wouldn't be transitory. I have also seen InfluxDB Logger cause it after my server didn't start up Influxdb and it queues up around 30k records. Ecobee suites has also triggered it when it runs through its processes at times and the api was down.
In most cases in my experience it has been something that has gotten into a bad state and allowed to gradually overload the hub.
My point is it is best to understand why it happens vs just triggering an action from it. If it does appear to be transitory on your setup that is great, but that can easily not be the case. This is especially true if the hub is used for development and testing.
2 Likes
I would send myself a notification to check it out.
This would be more on the lines of keeping things running while away, etc.
However, my experience is that rebooting in a willy nilly way can cause some Z-wave devices to be a little reluctant to react, maybe needing some prodding to get to working properly again.
Would do little good, if any, to reboot a hub without stopping whatever is causing the severe load.
2 Likes
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
