supervisor: Unable to resolve mDNS machines on my LAN using HassIO installed on HassOS
Home Assistant release with the issue: 0.85
Operating environment (HassOS/Generic): HassOS 1.13
Description of problem: When using HassIO installed on HassOS on my Raspberry Pi 3 I’m unable to access *.local machines on my network from the docker containers. On Hassbian this did work, I suspect its a problem in HassOS and related to Docker.
core-ssh:~# ping nas.local ping: bad address 'nas.local'
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 7
- Comments: 28 (6 by maintainers)
This is not fixed and should remain open
For what it’s worth, I set up AdGuard on a raspberry pi and took it OFF my HA machine. That seemed to have solved my issues more than anything.
@narfel, we build and distribute our own Python and pre-build Wheel packages and do not suffer from those issues mentioned in the blog post.
I tried many things as I need MQTTs functionality one way or another, but I would not recommend that newer or less experienced users go in and edit the hosts file without knowing what they are doing.
I’m not entirely sure, I’m thinking it’s more a HassIO issue as mDNS is functional under docker if port 5353 is exposed.
However I’m no longer using HassIO or docker so am unable to test fixes/worksarounds anymore, but hopefully it will get fixed if it is an OS issue.
Assigning LAN IPs manually somehow defeats the “automation” idea behind this project, mDNS situation labelled as wontfix by a stale bot after 10 months is also kinda (h)assy, could a maintainer specify what needs to be done to fix this strange situation ?
Is that a docker issue ? a hassio issue ? both ?
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.
I am currently having this issue. Home Assistant version 0.97.1 running as Hassio.
Hassio Supervisor 173. HassOS 2.12 Production Version.
The issue seems to be HASSIO is picking up an IP V6 address, despite the fact my DNS server and all local machines are set to only use IPv4 on the local network.
when I ping HASSIO.local, it pings to an IPv6 address, but this will not work when I go to http://hassio.local:8123. If I go to the IPv4 address http://192.168.0.xxx:8123 I can access the interface fine. mDNS is working, but for some reason it wont resolve to the IPv4 address, only to the IPv6 address which just does not work on the local network. I can access remote via the Nabu Casa Cloud, but it is extremely slow trying to move between pages. Additional Note: It also means I have to use the IP Address for SSH and SAMBA connections, I can not SSH to HASSIO or hassio.local and I can not connect to the SMB share with \hassio\ (windows) or \hassio.local\ . This is causing other minor issues I am having to try and work around also.