Station Mode not working on firmware 5.50

Yngvarr

Hello,
I’m having consistent problems trying to use Station Mode on my Seestar S50 (firmware 5.50).
I would like to confirm with ZWO and other users if this feature should work as I imagine — that is, the Seestar connects to my home Wi-Fi (2.4 GHz) and then the app can reach it over the local LAN without connecting directly to the S50_xxxxxx network.

Here is my current situation:

Router: ZTE H6645P V2 (2.4 GHz + 5 GHz, no mesh, no isolation enabled)
SSID: “YngvarrWiFi_24GHz” (2.4 GHz only)
Seestar firmware: 5.50
Phone: Android (Seestar app latest version)

Steps and results:

I can see the 2.4 GHz networks in the Station Mode menu.
I select my home Wi-Fi and enter the correct password.
The app shows an IP address assigned by DHCP (for example 10.0.0.172).

However, I cannot ping the Seestar from any device on the same LAN, and the app always shows the classic connection page (see attached screenshots).

If I try to re-configure Station Mode, I now get “network connect fail”.

I already tried:

Reset Wi-Fi and re-set Station Mode from scratch
Renamed SSID to simple characters, no spaces or special symbols
Fixed 2.4 GHz channel (not 12/13)
Disabled band steering and isolation
Tested with very strong signal (Seestar near router)

Same result every time.

Can anyone confirm:

![- Does Station Mode really allow the Seestar to be controlled through the home Wi-Fi LAN, without direct AP connection?

Is this feature working on firmware 5.50, or is it a known issue?

I’m attaching screenshots showing the configuration screens and IP info.

Thank you for your help!

Yngvarr

I discovered that the problem is due to a subnet issue already used by default by the SeeStar. In particular, the station mode uses the 10.0.0.x address class, and if the home router is also on that network class... that's when the mess happens.

Tech@ZWO

Yngvarr 你现在解决了吗?

Yngvarr

It would be useful if ZWO developers allowed users to choose the subnet for station mode, even if only selecting among 10.0.0.x, 192.168.0.x, 192.168.1.x, and 192.168.4.x.

Yngvarr

I solved it in an alternative way, since it would be impossible for me to change the main network's class (I have too many configurations), I put a second router in cascade to the primary one, assigning a different subnet that would work with the SeeStar. So... let's say I solved it, but in an alternative way. To run NINA or any other ASCOM software, I have to use a virtual machine that connects to the secondary network, which is quite inconvenient, I would say.

Tech@ZWO

Yngvarr I will record you demand to our team,thanks for your suggestion