Skip to content

Add a hack for Stellarium Mobile Plus time synchronisation - #125

Open
im-0 wants to merge 1 commit into
hjd1964:mainfrom
im-0:stellarium-mobile-plus-time-sync
Open

Add a hack for Stellarium Mobile Plus time synchronisation#125
im-0 wants to merge 1 commit into
hjd1964:mainfrom
im-0:stellarium-mobile-plus-time-sync

Conversation

@im-0

@im-0 im-0 commented Aug 16, 2026

Copy link
Copy Markdown

Stellarium Mobile Plus for Android (paid app, includes telescope control features) shows "Time: incorrect" in red when connected to OnStepX over Bluetooth even if automatic time sync is enabled in the app.

App logs have a hint for a root cause:

...
#:SC08/15/26# => TRX timeout
Warning, started command with RX buffer not empty
discarding RX buffer content: 49
Could not set telescope time
...

By trial and error I found that Stellarium waits for '#' after '1'. Probably this is for interoperability with other implementations of LX200 that send '#'-terminated strings after '1' on success.

The fix is to simply send '1' as a string response in a case of a successful change of date.

I tested this with:

  • Stellarium Mobile Plus (obviously)
  • SmartWebServer
    Note that in a case of a daylight saving time and if time was previously set by Stellarium Mobile Plus, it shows wrong UTC Offset (off by one) but correct UT and LST. Seems the only problem here is that UTC Offset needs to be changed manually to be able to set new correct date/time from the web interface.
  • SmartHandController
  • INDIGO 3

Fixes: https://onstep.groups.io/g/main/topic/100216132

Stellarium Mobile Plus for Android (paid app, includes telescope control
features) shows "Time: incorrect" in red when connected to OnStepX over
Bluetooth even if automatic time sync is enabled in the app.

App logs have a hint for a root cause:

	...
	#:SC08/15/26# => TRX timeout
	Warning, started command with RX buffer not empty
	discarding RX buffer content: 49
	Could not set telescope time
	...

By trial and error I found that Stellarium waits for '#' after '1'.
Probably this is for interoperability with other implementations of
LX200 that send '#'-terminated strings after '1' on success.

The fix is to simply send '1' as a string response in a case of
a successful change of date.

I tested this with:

* Stellarium Mobile Plus (obviously)
* SmartWebServer
  Note that in a case of a daylight saving time and if time was previously
  set by Stellarium Mobile Plus, it shows wrong UTC Offset (off by one)
  but correct UT and LST. Seems the only problem here is that
  UTC Offset needs to be changed manually to be able to set new correct
  date/time from the web interface.
* SmartHandController
* INDIGO 3

Fixes: https://onstep.groups.io/g/main/topic/100216132
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant