@meme1337 wrote:
Hello guys and girls!
I’m having an issue since I enabled the homekit component in Home Assistant, version 0.101.1. Maybe some of you could help a fellow tinkerer out!
I’m running HA on docker, with
network_mode: hostbecause I’ve also an Aqara gateway, that needs this if running on docker.The issue is that HA binds itself to multiple
0.0.0.0addresses on port 5353 for, I believe, multicast discovery, but the wrong “interfaces” never consume the udp packets, so these ends up saturating the UDP sockets memory, and then UDP packets errors start popping up.
Here an example fromnetstat -ulpn, as you can see the Recv-Q backlog is ramping up, and this is just after 20 minutes of HA running.Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4568832 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 0 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 4603072 0 0.0.0.0:5353 0.0.0.0:* homeassistant
udp 0 0 0.0.0.0:5353 0.0.0.0:* homeassistantIf I just expose port 8123 on docker and remove
network_mode: host, then the issue isn’t present, but I can’t afford to lose all the sensors from Aqara, so this is not an option.This issue is similar to Issue#20095 (https://github.com/home-assistant/home-assistant/issues/20095).
Has anyone ever had this problem and found a way to solve it?
Thanks!
Posts: 1
Participants: 1