#Zigbee2MQTT stops every day after new Core Update in HA.

1 messages · Page 1 of 1 (latest)

untold bison
#

Dear Community,

I installed newest stable publish HA-OS and Core version. Of course I also updated Zigbee2mqtt to the newest stable version what was reachable through Addons.

Since that day the Zigbee2MQTT addon stopps every day. I can start it manually but it will stop again after a few hours or about 1 day.

I found the logs and pasted it here in the right format.


[7:0x7f9dce5080] 39195296 ms: Scavenge (reduce) 2040.6 (2083.1) -> 2039.7 (2083.4) MB, 3.7 / 0.0 ms  (average mu = 0.137, current mu = 0.001) allocation failure; 
[7:0x7f9dce5080] 39196777 ms: Mark-sweep (reduce) 2040.7 (2083.4) -> 2039.5 (2083.4) MB, 1478.4 / 0.0 ms  (average mu = 0.107, current mu = 0.075) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory```

Raspberry Pi 5 - Home Assistant OS
--------------------------------------
HA OS: 13.2
HA Supervisor: 2024.10.3
HA Core: 2024.10.4
Z2M: 1.41.0-1


Thanks for your time.
Gery
manic grove
#

What's in the Z2M log?

#

What hardware is this on?

untold bison
#

You can find everything if you read it through.

#

Log is also there in code format.

manic grove
#

The above doesn't look like the Z2M log file

untold bison
#

Hardware is also there RPi 5

manic grove
#

RAM in that model?

untold bison
manic grove
#

Images of text ... NO

untold bison
untold bison
#

as I told its pasted as code format in the original description.

#

Here you can see my actual memory usage while Z2M is running.

untold bison
# untold bison

If you check this, my idea would be that this AirQuality Sensor is reporting 3 times / second is a little bit too much and the new version of Z2M or Core cannot handle this. Of course im not an expert, just an idea.

#

here you can see some device information about the device.

#

Please take your time, if you wont have any other idea maybe I can share my findings on the Zigbee2MQTT discord server in the general support channel. Thanks for your time!

untold bison
#

Solution: newest Z2M update solved the issue looks like. Up and running since 2024.11.02 morning.