Scenes run slow or even hang until rebooted HC3 5.171.15

[Diz 0]

Hi all, 

I've been coping with issues on my HC3 for some time and I'm not able to find any solution.

 

As the title states: scenes run progressively slower over a period of some days, maybe a week. Eventually I restart the HC3 and all works fine... Again, for a couple of days. 

my setup:

-46 devices connected, all z-wave, mostly Fibaro dimmers /smart switches / motion sensors. Also a couple of aftermarket motion sensors.

-2 or 3 plugins and QAs for e.g. Sonos and a Hue bridge, which in turn has 37 (zigbee) devices connected to it. 

-34 scenes, mainly used to switch on and of a variety of lights.

 

When rebooted, the memory of HC3 shows about 63%. Over time this slowly increases and when reaching somehere near 75-80% the problems start...

Processor activity is for all cores fairly low: +/- 5%.

I updated to a new (beta)version, but no luck. 

 

 

Who can help me get started on where or even what to look for? 

 

 

[SmartHomeEddy 1,005]

Can you see the code or is it an encrypted quickapp?

[Sankotronic 2,370]

I do not think that Huemain QA is a problem. What you can see on the debug screenshot is that QA is running garbage collector to free some memory every 5 minutes. All my HC2 UHAS Virtual devices do that with LUA built in garbage collector and system is running OK. Thanks to that memory cleaning I was able to run more than 100 VDs and keep free memory on around 50%  

 

[Diz 0]

On 4/16/2025 at 2:19 PM, SmartHomeEddy said:

Can you see the code or is it an encrypted quickapp?

Sorry, Don't know how to look that up. I'm not familiar with QA's... Can you explain?

 

[Diz 0]

On 4/15/2025 at 2:52 PM, m.roszak said:

 

So now its a moment to create a support ticket.

That's what I did, still waiting for reply....

[Diz 0]

Small update:
The ticket I have created over two weeks ago is still unanswered unfortunately(!)...

Status says: "being processed"...
It seems that selling hardware has a priority, but when faced with issues, the support lags behind. Needless to say, at this moment I'm not impressed by the support. Hopefully Fibaro can prove me wrong.

 

In the mean time, I have gone over all of my scenes again and I made some amendments.

I took a look at the history and saw a lot of scene activations over and over again, whithin a short period of time. 

As said before, a lot of my scenes involve automatic light switching, when entering a certain room together with a lack of light intensity in that particular room. 

We're 5 in total at home, so e.g. the kitchen is a busy area, resulting in a lot of scene activations in that particular room.

I have altered this -and other- scenes and added a condition that a scene only starts when the output is indeed changing a situation, e.g. turning on a light, instead of sending a command of turning on that same light when it's already on. 

 

For now, it looks like the RAM is crawling up much slower than before. History shows a lot less scene activations. Maybe this might help, although I believe this alternation should not be necessary. 

 

to be continued...

 

 

 

 

 

[Sjakie 156]

Something CHANGED!

I wrote:

the missing 36% is buffer and cache 6 - 30

Perhaps I miss something no need to worry for a restart every 7 days?

Memory usage goes up buffer and cache also what result in free space after 7 days in  4%. Hereby the HC3 becomes noticeable very slow.

start                     44%-6%-30%-20%

Uptime 12 hours 53%-6%-27%-14%

So somewhere the used memory is not given back after some part of the process that why it's increasing.

 

My last remark used memory is not given back seems true, cache stayed around 25-30%

NOW

FW 5.180 (remark nothing change in my HC3)

So finale result is NO  weekly restart necessary to keep HC3 on speed

With those numbers below in old FW should be not used < 4% and a very slow performance.

Please login or register to see this attachment.

Edited June 2, 2025 by Sjakie