#No connection between HA and python-matter-server

1 messages · Page 1 of 1 (latest)

prime zealot
#

Hi, I don't know if I'm in the right place, but I'll give it a try. I am running HA and the python-matter-server in a docker compose stack. Until the last restart I was able to connect without any problems.
I have tried the following things without success:

  • Restarting the complete stack
  • Restarting the python-matter-server
  • Reinstalling the python-matter-server
  • Adding a new “Integration entry”. I get the message “Failed to connect”. I have tried both with localhost and the IP address of the host on which the Docker containers are running.

I suspect that the python-matter-server is not starting properly, as I cannot see that the server is not listening on port 5580 either on the host (as root) or in the container itself via ss -tulpn | grep LISTEN. I have also specified the external IP address and other ports when starting the python-matter-server as a test, but this always leads to the same result.

docker-compose.yml
volumes: ha_config: matter_data: services: homeassistant: container_name: homeassistant image: homeassistant/home-assistant:latest restart: always ports: - "5683:5683/udp" - "8123:8123/tcp" volumes: - /dev:/dev - /run/dbus:/run/dbus - /etc/letsencrypt:/etc/letsencrypt - ha_config:/config matterserver: container_name: matter-server image: ghcr.io/home-assistant-libs/python-matter-server:stable restart: unless-stopped security_opt: - apparmor=unconfined network_mode: "host" volumes: - matter_data:/data - /run/dbus:/run/dbus:ro

I am using version 2025.1.2 of Home Assistant and 7.0.1 of python-matter-server. I have attached the log file from python-matter-server. In the log of HA there is no output about the networks or the Matter integration.

tight crag
#

Are you running this in any SBC?

prime zealot
#

No

tight crag
#

Running in Debian?

prime zealot
#

yes i use raspbian-os as host system

tight crag
#

what cat /proc/sys/net/unix/max_dgram_qlen results?

prime zealot
#

512

tight crag
#

OSError: [Errno 105] No buffer space available states no space to open new socket connection.

#

A quick reboot might fix?

#

Tried already?

prime zealot
#

yes

tight crag
#

Rebooting the host? Not container.

prime zealot
#

yes i have already restarted the host several times, can i increase the space?

tight crag
#

You can try.

prime zealot
#

Do you know how this is possible?

tight crag
#

what sysctl net.core.rmem_max results?

prime zealot
#

net.core.rmem_max = 212992

tight crag
#

Okay.

#

May be just try running the python matter server alone and see if it's serving?

prime zealot
#

I have just stopped all other containers as a test and restarted the python matter server container. the error no longer occurred on restart.
I now have a point where I can start again. thank you very much for your support

tight crag
#

👍

prime zealot
#

I have increased the space to 10 times the original value. However, the error still persists when I start the other containers. Using the exclusion principle, I was able to identify the wiki.js containers as the cause of the python-matter-server problems. I have not yet been able to localize exactly what is happening in the containers that is having such an impact on the python-matter-server. I would therefore consider the problem here to be solved.