Switching to Starlink caused my Home Assistant Green to go dark

Hello all
I just want to preface this post with my skill level of tech is minimal and I try to keep things simple as possible. About a year ago I installed a HA green on my local ISP DSL internet modem/router. Everything worked well (lighting Control) until I decided to get a faster internet connection, so I purchased Starlink with the Gen3 router. After getting switched to the new router, everything was good on my network except now my HA green is nowhere to be found. It no longer shows up on the App or webpage like before.

My question is: Does Starlink Gen 3 router support HA green via the lan connections on the back of the router without switching to bypass mode and getting a new router?

Are there settings that I need to adjust to get everything to work like before?

Many thanks in advance!

What addresses have you use to connect with HA?

I have just used the ones in the setup materials provided by HA
http://192.168.1.196:8123
[http://homeassistant.local:8123]

both or just the .local address?

Is that same IP it had previously? Did you verify the IP did not change?
Do you know how to ping device on network or can you verify connection on router?

is you phone on wifi?

Yes, the phone is on the same wifi network as my router, (all other devices seem to connect without difficulty)
I Don’t know if the IP changed or not,
Not sure how to ping the device on the network

This would be a good place to start.

I found HA on my Starlink app, IP address is 192.168.1.154
Connection is wired and there is a button to pause Internet connection.

got it to ping
C:\Users\akdbr>ping 192.168.1.154

Pinging 192.168.1.154 with 32 bytes of data:
Reply from 192.168.1.154: bytes=32 time=3ms TTL=64
Reply from 192.168.1.154: bytes=32 time=2ms TTL=64
Reply from 192.168.1.154: bytes=32 time=2ms TTL=64
Reply from 192.168.1.154: bytes=32 time=2ms TTL=64

Ping statistics for 192.168.1.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms

so http://192.168.1.154:8123 doesn’t work for you? Why not log into your router and find out if that ip is actually for your HA?

you tried http and https?

I connected to the router via ethernet cable, and I was able to connect to the webpage. Tried using wireless and was unable to connect.

Your HomeAssistant is connecting on IP address 192.168.1.154 and used to connect on x.196. Why not configure your router in the DHCP section so that it connects always (setting a static IP) as 196, rather than try and wrangle everything else to go with a new addrress?

You will need to know the MAC address to do thus. The MAC address for Ethernet connection will be different from the WiFi. Choose which, or try both and see how it works from your router perspective.

Don’t forget to save your settings, shut everything down from the menu, not the power switch, and then power it off and start your Starlink router and give it time to come up before you attempt to connect to it with the Green.

Connected your computer or your
ha Server?

If your computer, is your WiFi and Ethernet using same afdress space? Is your WiFi A guest network and ethernet not?

If HA, as was said you need to set static address on router if you have not already

As near as I am able to tell, the Starlink router does not have the ability to set a static IP address without getting a VPN for port forwarding. That is why switching the Starlink router to bypass and using a 3rd party router is one possible solution. (I was hoping to avoid this initially) All of this is really over my head, I just wanted to plug it in, lol

Sounded like this is the problem.
@dbrew can you ping the 192.168.1.154 when you are on your WIFI connection?

Yes, while connected using wifi the ping did connect
C:\Users\akdbr>ping 192.168.1.154

Pinging 192.168.1.154 with 32 bytes of data:
Reply from 192.168.1.154: bytes=32 time=3ms TTL=64
Reply from 192.168.1.154: bytes=32 time=4ms TTL=64
Reply from 192.168.1.154: bytes=32 time=3ms TTL=64
Reply from 192.168.1.154: bytes=32 time=4ms TTL=64

Ping statistics for 192.168.1.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 3ms, Maximum = 4ms, Average = 3ms

and what’s the ip of the computer you are using to ping? I don’t have starlink but if it’s the same subnet then chances are there’s some kind of firewall settings in starlink for WIFI isolation?

Is HA running? Connect it to monitor and login from PC running

I think I am going to abort any more attempts to get this working in this configuration. At a later date I may install a new router using the bypass feature in Starlink. Thank you all for your efforts, I was really struggling, and your assistance has widened my knowledge in this area. Thanks again, I appreciate your efforts.

1 Like

Don’t give up yet.

How many routers have you got connected, and what is connected to what? On top of that, what is hardwired to what, and what is connected to WiFi, and what router is offering up WiFi connections? What SSID’s are being advertised and what is connecting to what?

The router does routing (by design, duh!), sending traffic from one device to another, depending on how it is configured. We have to get the configuration correct so the paths are set up so the desired devices can talk to each other, which your HA Green did at one time, does not appear to be doing now, but most of the other devices are. One of the other functions it can do is allocated an IP when a device connects. It can be configured to do that in a fixed way (a static IP address that is consistent), or dynamically (pull a new one off the list available and give it out). Having multiple routers vying to do this in an uncontrollable manner can sometimes cause clashes.

I suspect we do not have the entire picture of your setup.

Some questions that come to mind:

Is your old ISP router still connected, acting as a router and trying to allocate IP addresses in DHCP mode? You mention putting your Starlink router into bypass mode, suggesting you may have a Gen2 one. If so, maybe you need to switch your Gen2 Starlink to passive mode to let the Gen 3 do the same without issues and conflicts, or plug the HA Green into the Gen 3 port? Why are you not switching the old Starlink router to passive mode? Does it still serve an useful purpose on the network?

How many routers do you need? Are any redundant? Are you still using them in the correct mode? Are you using the LAN connections on one as a switch because you do not have enough ports to connect the Ethernet cables on your Gen3, but have not changed the configuration to turn off routing?

Which router is the HA Green plugged into, the old ISP one or the new Gen3 one?

What make and model is the old ISP router?

Are the other devices hard wired or connected via WiFi?

Is there any network splitting or VLANs?

Are there any bridges, switches, hubs or other networking devices shuffling data around?

Yes, there are more questions.

These are questions that are part of getting everything to pleasantly chat together.

First things first

Before you start swapping things around more, lets get the big picture.

First, check your IP addresses for each router that is still powered on, your HomeAssistant device, and all the devices you are connecting to each.

What are the IP addresses of all the other devices on your network? How are they connected - hardwired or via WiFi? To what device?

Suggestion: I keep a network information spreadsheet with each device listed: one row for each device, and the columns for the name, the model number, serial number, the MAC address (doesn’t change), the IP address (can change, but I like to make them static addresses to prevent conflicts), the device it is connected to (it makes it easier if they have a primary one), how it is connected (Ethernet to what port, WiFi to what SSID), the SSID if advertising one, and any other relevant notes. You will find after about twenty devices you will need to do the same to keep track of everything.

List them here would be nice, and the penny will drop as to why the HA Green is not being seen.

Comment: Having multiple devices acting as routers can sometimes cause confusion - where do the data packets go? Having the possibility of devices connecting different WiFi SSIDs can sometimes also cause issues.

Security concern some people have when posting on the forum - what to redact? What to disclose?

Note, the IP addresses [192.16x.x.x ones] are local to your LAN and not directly accessible from the internet - they are behind a router - so don’t worry, there are no security implications in showing them to us. The SSIDs can be redacted, and can be called SSID1, SSID2, etc instead however to differentiate them for our troubleshooting purposes - just tell us which router is advertising which one, and what SSID the devices are connecting to). Passwords should always be redacted, even when it is suspected they may be mis-spelled as the cause of bad connections.

Routing does not need to be complicated. You don’t have to be a guru until you start to do sophisticated setups. Getting the connections right and what is configured as what is easier if you write it down, and the patterns will become obvious, and the ones that cannot connect will become evident.

Share the full network configuration and the suggestions will come in to solve your dilemma.