Michal

Hey. Its a really weird thing, but it seems that since i moved to the test-valgrind branch, my neolink RAM usage has stopped uncontrollably growing. I have restarted the container...

ahh thats because it sigterms: ``` 2024-04-09T12:58:42.005180861Z ==9== 2024-04-09T12:58:42.005248333Z ==9== Process terminating with default action of signal 15 (SIGTERM) 2024-04-09T12:58:42.005593091Z ==9== at 0x558D719: syscall (syscall.S:38) 2024-04-09T12:58:42.005701720Z ==9== by 0x1D40836: parking_lot_core::thread_parker::imp::ThreadParker::futex_wait...

On another hand, i can see that youre measuring the memory usage of a neolink process, but is it possible that: * Multiple neolink processes are being spawned? * something...

Ive just been running the :latest release for 40 minus and top shows:  Looks like its actually neolink process using that memory smaps dump: https://paste.ubuntu.com/p/jd7W6rGDw2/

Could you modify Valgrind build to work for lets say 2 hours before sigterming?

``` INFO ESPHome 2024.2.0 INFO Reading configuration /config/esphome/iaq-livingroom.yaml... Failed config sensor.bme280: [source /config/esphome/iaq-livingroom.yaml:290] Platform not found: 'sensor.bme280'. platform: bme280 temperature: name: Temperature oversampling: 1x id: temp filters: - offset: -1.5...

I have the same problem and find it to be really odd as i never seen docker containers behaving in a similar way. Although i must say that the solution...

It seems that i have a similar problem. I have a bunch of E2001 around my house with 1.0.24 firmware. TBH i never used them with Z2M because they were...

Many thanks for that! I also encountered this. I dont remember any new releases of Monica recently, but it has been running fine for a couple of years, until recently

Hi, it seems that the problem persists at least for me. My Zstick is updated to v1.20 but still getting the same error: ``` 2024-08-17 17:09:55.600 INFO APP: GET /health/zwave...