New EE router blocking Home Assistant

[madmull2025]

Hello, 

I have just upgraded to the new EE wifi 7 hub and extender with a 1.6gbps connection. 

Set up was easy and speeds seem good and fairly consistent.,

The problem i am having is that i cannot connect to home assistant via my PC when connected to EE router., It works fine if i use old TP Link Deco mesh system that is still connected. Works fine on my phone, 

EE seems to be blocking it for some reason,

On my Deco it recognises my rasberry PI5 running HA as 'Home Assistant' but the EE just recognises it as Rasberry PI5. Furthermore if i connect my PI via EE then my solax inverter doesnt play well and wont send entities to HA, but sorks fine when connected to deco mesh. 

Is there a way to stop router 'blocking' connection to HA? 

Its a pain having to change connection method on PC just to see HA or make changes.

I'm connecting using a windows 11 PC. Chrome browser. Using homeassistant.local address as always did before. 

Thanks in advance

[XRaySpeX]

Try setting up Compatible WiFi on the router under Advanced > Wireless Settings (it defaults to 2.4 GHz) & connect your problematic 2.4 GHz devices to that.

[madmull2025]

Thanks for the reply but i dont think that solves my issues. The PI5 running home assistant is connected to internet via ethernet just fine.. My PC is then ethernet into the EE range extender and working fine but just wont open home assistant web address. 

As if ruter is blocking it. 

If i plug PI5 into EE routyer then it doesnt get cinnections and data from the Inverter making the HA page useless. 

Hope that makes sense, 

Thanks 

[XRaySpeX]

Oh, I thought from using the TP Link Deco mesh it was WiFi connected.

[madmull2025]

No sorry if wasnt clear. 

The deco was just used to get the wifi up to another room without bother of cable routing ethernet so main one connected to fiber and node upstairs with PI5 ethernet to that.

[JimM11]

@madmull2025 Is it all just local issue's trying to get to it? have you tried the port command instead off just the IP.

Home Assistant’s primary web interface is accessible via port 8123. This port is used for both the w...

[bobpullen]

@madmull2025 - if it's any reassurance, I have a Home Assistant install hooked up to my Pro and it's working fine, along with all of my integrations etc.

---

 The PI5 running home assistant is connected to internet via ethernet just fine. My PC is then ethernet into the EE range extender and working fine but just wont open home assistant web address. 

---

I think this ^ might be something to do with it. I can't speak for the lack of inverter data but I've noticed oddities in the past trying to access hosted services on my network from a device that's connected to a Pro Extender. It doesn't affect local access though via the IP address/local hostname i.e. homeassistant.local:8123 works OK for me.

What I've found is that NAT loopback doesn't always work from the extender. This means if I try accessing a server/service on my network using it's publicly accessible IP or hostname e.g. http://myserver.tld or  http://<my_broadband_ip_address> then it times out. I don't have the same problem if I use the internal IP of the server. If I then take the connecting device and connect it to the hub, rather than the extender - it works. I've posted about this previously but am struggling to find the thread.

Hoping that gives you some clues/stuff to work with. The loopback issue will be something EE need to fix in firmware, I imagine.