Hi
I’m looking for some guidance on how to configure access to my Starlink in bypass mode on the WAN interface of a UDM Pro. I understand the port is 9200 for API access to the Starlink but I’m falling short on understanding the rest of the configuration I need in order to allow my HA access to that on the WAN interface.
Any help is appreciated!
Cheers
Sem
I too am looking for a little guidance.
Ok figured it out. You need to set up a static route. You’ll have to set it up as a interface put the next hop address as 192.168.100.0/24 and your destination as your wan port. ( For me this was eth0) distance as 1 and save.
Test it in your browser, go to 192.168.100.1 . If you set it up right, you should be directed to your starlink.
After all that you shouldn’t have any issue setting up the integration with the pre-loaded info.
@mveitenheimer any chance of a screenshot of the static route?
Thanks guys, that’s it. Unfortunately, my IoT VLAN was on that subnet so I had to move it 
Am running into an issue where it is possible to connect to the Starlink router URL, but it appears as though port 9200 doesn’t respond. Is there a particular configuration needed on the Starlink router to make it work?
Thanks for sharing. I used similar settings in an EdgeRouter (EdgeOS) and it worked well!
I went to Routing tab → Add Static Route and then these settings. My Starlink is connected to eth1 port.
Couldn’t figure out a way to get this to work properly when the Home Assistant server (VLAN5) is in a different VLAN from the Starlink device (VLAN1).
Once I moved the HA server to VLAN1 everything worked fine. I’m guessing this is a Unifi specific issue, but wasn’t worth digging into it further as a solution presented itself and works well.
I wanted to add what needs to be added if you’re running an Asus router:
Go to [LAN] > [Route] tab. Click [Yes] on Enable static routes.
Host IP: 192.168.100.1 => asus router LAN IP
Netmask: 255.255.255.255
Gateway: 0.0.0.0
Metric: 1
Interface : WAN
Anyone who can help me take this one step further? I have the Starlink connected to a Peplink MAX BR1 5G Pro. The Peplink bounds the Starlink uplink with the cellular connection. So I guess my Starlink setup should be 2 hops up… But how do I steer the 192.168.100.0/24 to the right WAN connection on the Peplink?
I am having the same issue. Ive set up my static route, the validation of 192.168.100.1 successfully routes to a page with the “Starlink” logo but upon adding the integration into HA, the setup will does not reconcile. Setup does not like port 9200.
Does anyone have any further help on this integration?
make sure you have VLAN tagging enabled on the port home assistant is connected too. thats what cause the issue for me. @filmgarage @japickard
Has anyone had success with the Starlink Mini?
i think its the same setup. but im not sure why you would use a mini if your running a home assistant instance. nor would you be able to use a unifi router given it doesnt have ethernet. may i ask why you asked the question. i might be able to better answer it then
Hi, I figured it out myself. It was a matter of using 192.168.100.1 for the API despite 192.168.1.1 being the the default gateway. So I set a route forcing traffic to 192.168.100.0/24 to go through WAN2 (failover WAN). I was so stuck in thinking that I should use 192.168.1.1 (that it would be different on the mini) that I did the wrong analysis of the problem 
I just got the Starlink Enterprise connected to the UDM Pro Max as WAN2 and setup a static route for 192.168.100.0/24 to WAN2 interface. Even though I have the route setup my ISP modem also has that subnet for management and it seems to be still routing to it. Can the 192.168.100.1 be changed?
I ended up getting this working by putting the Starlink WAN IP instead of the WAN2 interface in the static route.
Heya,
Sorry for digging up this post again but for the life of me I cannot get this to work reliably or now at all.
I use a UDM Pro with Starlink in bridge mode on my WAN1 (eth7) port and have a static route setup. I have several LAN subnets/vlans I use and am able to open the http://192.168.1.100 page from a desktop in one subnet and from my mobile using the app in another subnet. Connectivity to the internet and the route to the Starlink local device seems to be good and working as expected.
As a test I did originally have homeassistant running in a VM and found that it was hit and miss, it would connect to starlink and stats would be coming in nicely, then it would stop working for some reason for a few days and I’d get a connectivity error without changing anything network wise, nothing else would have an issue, just the starlink connectivity.
I have since created a dedicated homeassistant server running on an RPi on the same default subnet and vlan (1) as my UDMPro.
The RPi is connected in the same subnet with the port set to the same native vlan and tagged vlans blocked. All connectivity to HA works from any vlan/subnet/device as allowed by the UDMPro.
No matter what I do I cannot get the integration to connect without an ‘Unknown error occurred’ when trying to add starlink 192.168.1.100:9200 in HA.
I have tried experimenting with the route itself, from a .0/24 to a defined .1/32, metrics 1 and 10.
I do understand subnetting, vlans and routes well I am not a novice in this area but for the life of me everything seems to be correct but HA just will not connect, hence I’m here.
A test-netconnection from my desktop PC in a different vlan even returns a TRUE for access to port 9200 on 192.168.100.1.
Using a SSH on the HA I can ping 192.168.100.1 with curl gives me this though:
➜ ~ curl 192.168.100.1:9200
curl: (1) Received HTTP/0.9 when not allowed
Ping and a curl to port 80 work fine though.
Raw connectivity and routing do not seem to be the issue.
Is there some bug I’m not aware of or anything anyone else can suggest?
Cheers.
Not working for me. Starlink integration has become unavailable, but I have full connectivity will have to investigate when I get back from travelling
