Equipment:
- Skywatcher AZ-Gti working in Alt-AZ mode
- Armbian box (2GB ram, 500MB ram usage at idle, working temperature hovering around 60c
- INDI-web, Kstars and full drivers installed
- astrometry.net and its full indexed files
- Windows 10 PC
- Kstars/Ekos installed
- Android Phone
- Synscan Pro 2.0.3
- Skysafari 6 plus

Setup:
- AZ-GTi in station mode connecting to my home wifi (xxx.xxx.2.13)
- Armbox (xxx.xxx.2.8 )
- QHYIIL connecting to the box via USB cable
- INDI-web runs at startup and manually startup with my equipment profile (QHYCCD, AZ-GTi ALT_AZ wifi, Astrometry, Skysafari drivers) The telescope driver displays as Skywatcher Alt-AZ, INDI_SkywatcherAltAZMount on connection tab, see photo attached)
- Windows 10 PC
- running Kstars/Ekos connecting to remote (Armbian box) INDI
- connecting to AZ-GTi with IP xxx.xxx.2.13, port 11180, UDP, network
- connecting to QHYCCD, Skysafari (xxx.xxx.2.8, port 9624)
- Mobile phone
- Skysafari, Meade LX200 Classic, Alt-AZ goto, wifi, IP xxx.xxx.2.8, port 9624)

I usually started with AZ-GTi at the home position (level North). Synscan Pro connected to AZ-Gti and did a one-star alignment before connecting everything (to ensure proper Alt-AZ tracking). Goto by using Synscan Pro app has no problem.

I then run Kstars/Ekos on my Windows 10 PC by connecting to the remote INDI server (on my Armbian box). Mount, CCD, and Skysafari connected without issue. If no issue with the Goto, goto, repetitive plate solving to target, and image capturing are working great.

However, the only issue that happened quite often was after searching for a new target and issue Goto on Ekos, the mount moved to different places, sometimes moved a few times and stopped a few times.

I'm not sure what I did wrong, or it is still the bug in the driver?