I’m trying to figure out how to control the docker run parameters of one or more of the home assistant containers. I’m running home assistant supervised on debian 12 following a recipe from elsewhere on this site. It all runs great but it looks like I need to modify the command line arguments to allow UDP ingress on specific ports.
The problem i am having is that because everything was basically automatically installed I can’t track down where I might do this. Docker is run using systemd. I can find where a bunch of images are installed. I can find where home assistant is installed. I can find some docker files. But I can’t find where docker is picking the command line arguments from.
I believe it’s the HA Supervised install script that was used.
but to the OP’s question…
I don’t think you can change it.
any “supervised” type install (HA Supervised or HA OS) is pretty well locked down fromn an end users perspective. It was never designed to be adaptable. It was designed tgo be completely standardized.
if you need that type of control you’ll likely need to switch to HA Container at least or HA Core.
All that is said not actually using HA Supervised so it’s possible I’m wrong. But I don’t think I am.
It isn’t an add-on. I have a device that mult-casts UDP packets I want to receive. They don’t seem to be making it through. I have non-HA devices that receive it just fine so I have an issue somewhere in the HA stack. Searching implies I need to open that port up.
Actually I can configure the port the device sends on, so perhaps there is a port already open I can use?
If it is docker you only need to map the desired port.
MDNS will not work outside of docker host mode or macvlan. You also require some type of reflector or repeater if using vlans on your local network and connecting devices in different vlans.