When using systemd to start the bridge, the static IP is not always known at service start.

[shawn-lindberg]

I have been dealing with an issue where, after setting up HA bridge as a systemd service, there would be a warning about the UPNP discovery address not being known as the service started at boot. Subsequently, discovery would not work at all, and there would be no traffic listed when traces were turned on. I was able to work around this issue by stopping the service manually, and then starting the bridge manually from the command line. In doing it this way, the warning disappears and UPNP traffic appears normally with traces turned on and discovery works. I'm not sure if this was caused by the fact that I set up a static IP after I had already registered the HA bridge service, but otherwise I followed the instructions precisely. The only other change I had to make was to edit the configuration for the service, because the username is not the default. Please let me know if I can assist with further information.

[TheUntouchable]

Can't you just configure your OS to wait for the network while booting..? At least this is possible with my raspberry pi / debian.