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.
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.
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.
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?
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?