Philipp Hofmann

Is this still going on? I think I have the same problem but cant seem to find a fix if there is maybe someone can direct me into the right...

I have the same Problem. The docker container seemingly has a memory leak. After 2:30 Uptime:  After Uptime ~ 1min: Max 2G RAM usage

@QuantumEntangledAndy Is the fix on the quantumentangledandy/neolink:latest docker image? If so, i am already using that.

Ok. I will test the test-valgrind image and will write about my experience on your fork in [Issue#202](https://github.com/QuantumEntangledAndy/neolink/issues/202)

The intercom is supposed to activate the door opener upon typing ``#1``. It works when typing manually but not with the SIP client. I already tried all three methods. I...

> Did you try with a longer delay? I originally had a 3 sec delay between both typing the digits and ending the call. Still didnt work

Ok so I fixed it now. I put each character in one by one in two seperate stdin calls with a 500ms delay between each digit. Maybe you wanna fix...

For those using neolink in a docker configuration here is a docker compose work around for the memory leak: ```yaml ... neolink: container_name: neolink restart: always deploy: resources: limits: memory:...

How can I resize it now? I thought it said "I can change these settings later", but now I am stuck with 32GB. Kinda bad ngl.

I have the exact same setup as you do, but it works for me. The only difference is I address partdb by hostname and have it use the default port...