New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.local named devices (i.e. ESPHOME devices) only resolve for a few minutes after booting HA #54
Comments
|
Here is a recent log file: |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
Hi , why is development not picking this up ? |
|
this works for me #64 (comment) |
|
the issue still exists |
|
I seem to be unable to resolve mDNS hosts even immediately after startup. I was sure this worked at some point in the past, but now I'm not sure. For testing, I downloaded HAOS 6.6 and spun it up in a VM. The host is able to resolve mDNS names, but containers (including I verified with tcpdump that mDNS packets are making it to the hassio_dns container network interface. It looks like there's been work around this at #73, but I'm unclear on how to upgrade to the latest release or properly test it. |
|
I also downloaded a fresh HAOS 7.5 RC VM, and it has the problem out of the box. It's running the 2021.06.0 version of the dns container. I was able to update it manually with Since I can easily replicate this outside of my actual HA install, I'm glad to help debug. |
|
@deviantintegral if you're doing this testing on a dev system I would recommend changing to the Anyway more importantly though, the issue at hand. If you have shell access on the host can you try the following: Does that work? If not can you share the output? If it does work then when you try to use that URL within HA is there an error in the DNS plugin's log? supervisor logs -> DNS or just Starting in |
|
I updated my VM into the beta channel, and it's now fully working for mDNS resolution. I'm guessing that there's other updates needed that prevented it from working when trying on my live host. If I get a chance, I will reset my VM back to the stable channel to prove flipping back and forth fixes things. |
|
I had a chance to fully test this, and the 2022.03.0 version of plugin-dns is working for me For reference, on the host: Info and behaviour before updating: After updating to 2022.03.0: Assuming the plugin is going to be updated in the stable channel in the next few weeks, I think this issue can probably be closed. Nice work! |
|
2022.03.0 fixes the problem for me. |
|
Fixed by #82 |
|
Also note that there is a new option to disable the fallback dns added here: home-assistant/supervisor#3586 as I would guess a number of users on here would be interested in that. |
ESPhome devices show up being "Online" only a few minutes after booting the system. After that, they turn to "Offline", although they are still online. mDNS resolving seems to breakdown within a few minutes after rebooting the OS.
Running Home Assistant Operating System, which is, according to the site, the recommended installation method.
The text was updated successfully, but these errors were encountered: