100 % CPU load just for one trigger ?

[wienog 107]

Since the last updates , starting I think with 4.08x or 4.09x, I experience very erratic behavior in the response of my HC2 to triggers of scenes. Where before lights switched on within one second after a motion sensor was triggered, now it takes sometimes 2 seconds , sometimes 3 or 5, sometimes even 20 (!) seconds.

 

At the same time I see in the 'Diagnosis' panel that (any) triggering of the motion sensors causes a temporary load of 100 % of one or both CPU's..as seen in the attached picture.

Is this normal ? Are other users seeing something similar ?

I did everything except beginning from scratch to solve this: remove all VD's, rewrite all scenes, reconfigure all devices....

 

Please login or register to see this attachment.

Edited March 19, 2017 by wienog

[robmac 173]

Not normal. first check your scenes are not cascading, If they are good. You need to go through soft re-configuring which you have done so. if that does not work try hard re-configuring. If that does not work it needs some remove and re-add. if you get to that point post again.

Edited March 19, 2017 by robmac

[jimicr 90]

How long did you have the CPU diagnostic window open?

If you open a tab and set it to the CPU diagnostic page and open another tab and browse there for a while, after you go back to that page in lets say 15 minutes it looks like the HC2 was sending a rocket to the moon.

Best thing to do is open the page, trigger the motion sensor and look at it as fast as you can.

 

And it's definitely not normal for a scene to take so long to start after a triggered sensor to start 

Edited March 19, 2017 by jimicr

[robmac 173]

looking at that chart compared to mine...

 

130 nodes 500 devices.

 

all the temperature sensors in this event view trigger scenes

Please login or register to see this attachment.

and this is my cpu

Please login or register to see this attachment.

 

I think there is an issue

Edited March 19, 2017 by robmac

[wienog 107]

Thanks guys, for your answers. Happy to get the confirmation that this is not normal.

The last thing I did was creating a (manual) scene for each room that disabled all the scenes  in that room when run. So I disabled literally all my scenes in all rooms and planned to switch each room back on to see which room could contain the bad scene, if any. Guess what: it made no difference in the loads of the CPU even when all scenes were disabled , HC2 rebooted and working without any enabled scene...

 

What does this mean ? That there is somewhere something wrong with a device ?

@jimicr

 

I noticed the timeline was not visible in the attached picture.

Here is an other picture from a few moments ago with timeline visible. It is clearly a bit less 'busy' moment than the first picture but still rather high peaks...

Please login or register to see this attachment.

[jimicr 90]

I think you best can connect support, maybe they can fix it.

 

Good luck and please keep us updated!