Stefan Agner

Btw, at least at one point Core itself also didn't like duplicate mDNS instances (see https://github.com/home-assistant/core/issues/50695). Now I think today this no longer leads to a packet flood, but there...

> I am fine with turning off the reflector and keep all the esphome devices on the IoT VLAN, but I am not sure about other possible issues this could...

@bdraco this issue is about a very particular setup: - Home Assistant is multi-homed - The two networks Home Assistant is in are "connected" with a mDNS reflector. That leads...

> Hey [@agners](https://github.com/agners) just for completeness, the solution that you describe "_We can just ask systemd-resolved to not use mDNS on one of the two interfaces._" is there a guide...

> If no one thinks this PR provides any value, that’s no problem! It does introduce a bit more complexity, so I totally understand. Anyway, on to the changes I...

@t3hk0d3 what is the state of this PR from your point of view? If you feel it is ready to be merged, press the "Ready for review" button so it...

In discussion internally we were wondering what happens to instances which are offline, and come back online after we shipped the last release (with this PR included) for these deprecated...

Uh interesting find, so FreeBSD virtualization somehow triggers a orjson bug then? 🤔 Orjson does use some native code optimization, I guess the CPU detection fails and/or the optimized code...

> I dug a bit further and I don't think it's either FreeBSD or the virtualisation, but rather some kind of (missing) CPU feature. We did run into this previously...

PR #5282 changes the behavior: Now the actual problem is shown to the user:  The underlying problem here is that a gateway is currently mandatory. This is already tracked...