In the last session (may be with kstars 2.9.2 or 2.9.3), I encountered a similar problem with my Mach-1 and GTOCP4. The first slew missed the target and went to somewhere only the RA is different.
It seemed as if the time in the mount was delayed 3-4 hours compared to kstars on the PC.

Today I performed the test suggested by Jasem with the latest INDI built from the GIT today on the RPi3 and kstars 2.9.5 on my MacBook Air. The test was done in doors since we had bad weather in these days.
After connecting the hand controller (HC) and the USB cable from the RPi to the GTOCP4, the power was up, then star the Ekos with a test profile containing the AP experimental and the CCD simulator. Of course, "KStars Updates All Devices" was selected in the INDI setting in the Ekos panel.

1) The Location and Time setting reached from the Setting menu on the HC appears as follow:

2) After turning on the mount (while Ekos has not started), I changed the time on the HC (forwading about 2 hours):


3) Started the kstars and INDI, then went to the INDI control panel to send the time and location data from kstars to the mount:


4) But still the "4=Time/LST" in the Main menu indicates the time has not been updated:


5) Going to the Set up menu and selecting "3=Get Time/Loc FrMnt" (see the first image), the time has been synchronized with that of kstars. This seems to confirm the time was updated successfully:


The log of the test session is also attached.
Simply starting up the Ekos did not update the time (and might be location, but I've not tested whether the location is updated or not) on the HC, but seems to update it on the mount. I hope the time setting issue is really solved, and will check in the next session.

Read More...