No access to HASS anymore after changing the (mesh) modem

Installation
1

Hi,
Today I changed my mesh modems. With the new modems, the SSID and PW remain the same as with the old modem. All my other hardware automatically connected to the new modem, whether via wifi or via a cable.
Yet not my HASS (installed on the HA Blue, all updated)! Rebooting does not change anything

Update: HASS automation do work, but I do not get access to the UI anymore. The phone app indicates that the SSL-handshake cannot be executed; my workstation indicates DNS_PROBE_FINISHED_NXDOMAIN

What can I do?

Thanks for the help.

Taco

2

I’m guessing the security changed between the new and old router? TKIP/WPA/WPA2/etc… Something is likely different… besides the BSSID obviously. Also are you sure it didn’t connect and simply grab a different IP address since its a new lease…

3

Sounds like a DNS issue on your Home assistant/network. like it can’t resolve. Did you use a static dns server that is not contactable anymore? Like your router itself?

4

I’m not sure. Definitely not configured and not on purpose, but I may have had an app installed. I’m not that tech saffie…

5

WPA2-personal, just like the previous modem. But I tried more sophisticated options.

I also have Nabu Casa if this helps…

6

This isn’t relevant since you said with a ‘edit’ that HA is connecting just fine. So the wifi is fine.

The other errors indicate you have a dns problem. Does your regular workstation and phones all work correctly?

7

Yes, all other devices, cabled or via wifi work just fine without new logon required.

And the HASS works, just no access to the UI as I said

8

You should be able to access it by https://<your ip number>:8123 from a normal browser; it will give you a warning, but it will allow you to open… (in contradiction to IOS, which does not allow you to open invalid certificates)
Maybe from there you can re-join the wifi and/or set another IP address?

9

Yeah, I thought of that. The issue is that at the moment I cannot find the IP number in the modem app. Otherwise I would have tried that.

10

For me that is one of the reasons all my devices have a reserved IP address…
So i know exactly which device will be on which IP….

11

That is one of the reasons for me to replace my modems in the first place

12

Not sure how many devices you have (and of how many you know it’s IP)
But just use an IP scanner to see which IP’s are alive?
f.e. https://angryip.org
By the looks of it, you can also check a port…
so just check which IP listens on port 8123?

13

SOLVED. It appeared the new modem changed the subnet. The subnet of HASS did not change with the modem (because of Nabu Casa?). So I changed the network subnet to match the old one used by HASS. Now all works again.

Regards

14

indeed mdns doesn’t work if netmask is incorrect :wink:

15

Hi, do you got some print screens? Facing a similar issue with a forced move to Ziggo Smartwifi. SSID and PW remain the same. Now Im no longer able to access the UI anymore. Also not able to access HA via SSL.
SSID and password remain the same, other hardware can connect to wifi. Set up port forwarding per instructions, switched offf UPnP. IPv4 addressed for HA is reserved. DHCPv6 stateless. Automation seems to work still.

Did you change settings in your modem? If so, how?

Help would be appreciated. thanks