Closed BambamNZ closed 3 months ago
Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration (zeroconf
) you are listed as a code owner for? Thanks!
(message by CodeOwnersMention)
zeroconf documentation zeroconf source (message by IssueLinks)
Home Assistant Container
Can you confirm your container installation isn't broken?
I would not say the container installation is broken, only a things aren't working e.g. Nanoleaf, Xiaomii which seems to depended on ZeroConf as a root of them not working All other integaration i.e. Tuya, Augustu, PushOver , Ring etc is working, inlcuding automations are working as expected.
As for the other containers (PiHole, Nginx, Pialert) on this instance, they are working just fine.
Deployed a new docker container with version 2024.4.3 and the issue is still present, although there are fewer integration related warnings / errors. The one persistent and common one is Zeroconf. Downgraded new container to version 2024.4.2 and the issue gone away, auto-discover devices show up as expected and no further warning / errors related to zeroconf.
Just tried 2024.5.0.dev202404180213 and the issue doesn't seem to be present in the Dev release. No Notifications and the zeroconf / auto-discover devices are showing up as expected.
The problem
Post upgrade to 2024.4.3 and a reboot of the server hosting docker, Zeroconf produced a number of errors / notifications
What version of Home Assistant Core has the issue?
core-2024.4.3
What was the last working version of Home Assistant Core?
core-2024.4.2
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Zeroconf
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Post upgrade to 2024.4.3 everything worked, however are a reboot some hours later these errors are being reported. I've restored a backup to a test container with the same results, also deployed a brand new container with no config and the Zeroconf error is still reported although with less detail in the error log.
Don't know if this is related to mDNS ?