I am unsure what recently changed; but I did update a day or two to the most recent Core / Supervisor patches this week.
I cannot connect to my HASS server anymore by its internal DNS name anymore (hassio:8123 - always worked before). I have verified it is correct in my Supervisor configuration; and as well as my DHCP server reservations have remained unchanged.
I can connect via external addresses / nabu.casa; but internal resolution for some reason is failing. Is there perhaps a listener config that might only be listening to IP based request; and not my internal DNS address?
I did notice; however, that my router had changed the DHCP hostname of my home assistant server from hassio to “Bathroom Speaker”; one of my Google cast devices. Why it did this I do not know; but I suspect that there is a correlation to why this broke. I deleted that IP reservation; and re-created it as “hassio” once again; although the problem persists - even after rebooting the network AND Home Assistant.
1 post - 1 participant