Hello, from few days ago after the update (the one before 2.2.123) I start to receive this message "Severe hub CPU load detected." I don't remember this kind of message before update, also the radio mesh is the same like before. The apps are the same... I don't understand where the problem is; maybe someone know this issue or to fix it? Thx!
A good place for you to start troubleshooting is to look at the driver stats and app stats pages to see if something is using a lot of CPU time.
You can get to those pages by clicking LOGS on the menu, then the tabs are available on the screen that loads.
If you don't know how to interpret what is on those pages, post screen shots of them here and maybe someone can give some suggestions.
Also, give it a few minutes and see if it quiets down on its own. The hub just did an update and a full reboot/initialization, those are fairly CPU intensive.
1 Like
Hello, I see the apps running, I setup many triggers for some apps to read and and control variables from radio devices, but is not new, I did this from the beginning, I read some temperatures every ten seconds. Is that the problem? I never seen the message before, and my apps are running very well from long time ago.
I think it was after update? So normally I will not receive it if I delete the message?
OK now is no message on it, after full reboot (last update 125, few minutes ago make the hub rebooting)
Thank you!
If the hub is no longer under load, it should disappear on its own in a few minutes.
Yes, the message is new in the 2.2.5 update. The high load was likely happening before, too, but you never saw anything as there was no message sent before 2.2.5.
If the message clears and does not come back, don't worry about it. If you keep getting it, though, then it is time to do as I indicated before and look at ther stats page to figure out what apps/drivers are causing thr high load.
3 Likes
I have again and again this message... I looked on logs and looks like the rule machine is the main contributor for this load...
The major app that is causing your issue is not Rule Machine. It is "Thermostat Controller". You have multiple iterations of that sucking up CPU time.
Just the instances shown in that screen shot account for nearly 50% of CPU time.
1 Like
Yes this is... I designed a lot of conditions and triggers.
I made a thermostat software, using simple temperature sensors (5 rooms each with it own thermocontrol)
Might just be too much then. 
the data is, what it is.
1 Like
what should I do, I can't make it simplest it is as simple as it is possible... Do you think is a solution to trigger it in bigger time intervals like 2-3 minutes.
Now I check the room temperature every 30 seconds.
It if everything is working fine, just ignore the load message?
I wouldn't change it unless you are having real issues (other than the alert).
I have no issues, I have just the alert
Does your room temperature REALLY change every 30 seconds??? Why trigger that often? I would think every 10 minutes would be often enough for this.
Maybe describe what you are trying to do, and someone will have a better way to do all this without 20 rules.
3 Likes
