>> However, as a result, I can't connect to sky safari anymore on 10.0.0.1.
Of course you can. You just cannot use 10.0.0.1.
And you don't "connect to SkySafari on 10.0.0.1," SkySafari was the one that was earlier connected to the ASIAIR at 10.0.0.1.
This is why I really hate these guys (especially ZWO) trying to oversimplifying thing ("Simple as 1,2,3") by issuing cookbook instructions instead of explaining what each step does. A simple snafu and nothing works anymore, and no way for the user to figure it themselves, since they have learned nothing from the instructions.
Here is how everything works together.
First of all, 10.0.0.1 is the standard IP number for the Local Network's server (originally used by Unix and pre-X MacOS, and later picked up by Windows). Earlier, when your tablet was connected to the ASIAIR as an Access Point (what ASIAIR calls "hotspot"), 10.0.0.1 would therefore refer to the ASIAIR itself.
On a Mac for example, you can FTP to itself by going through 10.0.0.1.
What ASIAIR includes is a number of proxy servers. There are proxy servers for bridging external mount commands over to the mount.
Depending on the mount, ASIAIR uses a different network port number (port 9624 for LX-200, port 4030 for iOptron mounts, etc). With some mounts, such as EQMOD, the proxy actually translates the protocol (in the case of EQMOD, translates from LX-200 command protocol to the SynScan EQMOD T1 Motor Protocol).
As a result, what you want to do is connect SkySafari to one of these proxy servers in ASIAIR. When ASIAIR was 10.0.0.1, you would connect to one of these proxy ports on 10.0.0.1.
Now that you can connected via the network, you need to change the IP to the current ASIAIR IP.
Just look in your server, or in ASIAIR Setup (click on "Wired Ethernet" text) for the IP). This is why the first thing you should do is to go into your router and assign a fixed IP to the MAC address of the ASIAIR. This way it won't change from night to night.
If, for example, your ASIAIR is now located at 192.168.7.123, you just tell SkySafari that the mount's IP address is 192.168.7.123. Keep using the same Port number as you did before.
Notice that this means ASIAIR app can be running on one tablet, and SkySafari can run on a separate tablet.
FWIW, I did not use SkySafari with ASIAIR with my Takahashi mount. I tried it once and found it to be distracting eye candy -- it does not contribute to capturing images. It is no loss to me that SkySafari does not support RainbowAstro.
SkySafari developers take forever to implementing something that should take a day to implement, and perhaps 3 weeks to regression test.
They dragged their feet for so long with EQMOD that ASIAIR included a proxy that translate between EQMOD and LX-200 protocols. SkySafari still don't have EQMOD supported. RainbowAstro had to to the same thing. Instead of waiting for the SkySafari folks to implement the RainbowAstro command protocol (really simple too), RainboxAstro implemented a LX-200 mode to allow SkySarari to move the mount around, but not sufficient to be complete enough to use other than on the showroom floor, or for visual observers.
I do use SkySafari to plan for the night's object and get a quick look at when meridian flipping takes place.
Actually, I have not checked out if Stellarium works with the ASIAIR mount proxies.
Clear skies (rain still takes a couple more weeks to abate in Oregon),
Chen
