I installed HAOS on an Intel NUC which is connected via ethernet to my network. I can access HA on all computers on the network via IP but not via http://homeassistant.local:8123. I am fine with this, but I want to make sure this is not going to be an issue for other things going forward.
I have no clue why I cannot access HA via the aforementioned address, but don’t care if it’s not going to cause later issues.
TIA
You might be blocking MDNS somewhere in your network, it won’t be a problem. If you really want to use it that way you can always add an entry to your hosts file locally (Linux, Mac, Windows) and it will always work.
Thank you. As long as it’s not an issue, I prefer the IP route because it reminds me of my IP pathways.
The only place it might bite you is on any “add integration” button on some GIT pages and in the HA docs, as it will rely on the MDNS working but it’s still not a problem.
It will not be an issue other than the mentioned help pages, where you will have to find it manually.
If you have given your HA installation another host name under the network setting, then it will be that name instead of homeassistant.
That’s a great point I didn’t consider as well. Maybe you can’t reach it because you changed it from “homeassistant” to something else. I know I do this for my various HA instances (“rvassistant”, “boatassistant”, “hadev”, etc).
Bingo!!!
That fixed it. Thank you.