I am attempting to set up a way to monitor a second setup to display that mount's pointing location in one instance of KStars running on my main setup.
I am able to run all my main drivers and then connect the secondary remote drivers by way of the Device Manager - Client.
This imports all drivers running remotely. For clarity, all remote drivers have custom labels.
'driver1@remotehost:port' In the profile editor also works, but it has another conflict regarding which mount KStars commands among other hindrances
Either way I can get the mount to show up.
The issue is, INDI is setup to automatically populate the Snoop Device with the details of a locally running GPS INDI Driver; issue is I have GPS in both setups. The result is the main setup attempts to override the remote GPS INDI driver snoop device, then the remote setup automatically overwrites it again. This causes an endless loop
...
2020-06-26T13:38:45: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629)
2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629)
2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629)
2020-06-26T13:38:44: [INFO] Observer location updated: Longitude (-**.7954) Latitude (**.3629)
...
It is possible to avoid the loop by using the default GPSD label rather than a custom one. But that has a lot ambiguity involved.
