I was thinking along the same lines, but for a different purpose. For time-sharing on a remote robotic scope, it could be a good idea to have a scheduler server (and client).
My future (and as of yet a bit hypothetical) use case is :
- Two or more users connect to a remote scope using Kstars as a client, Indi on a server connected to the scope.
- Each can send long-term scheduling orders (covering several days or months of observations). The scheduler would find the most relevant order based on best match for the target and weights
- Some automated processes can also send orders (i.e. for asteroid tracking, supernovae, etc.), superseding existing orders (higher weights, less stringent evaluation of match)
I believe this could be done by having a local install of Ekos on the scope server and some scripting, but I haven't yet played enough with scripting Ekos to know for sure. Ideally, as several people pointed out, it would be great to be able to access Ekos functions outside of Kstars (in particular in a headless install), through an API.

I haven't yet started to build my fixed observatory, but meanwhile, I mean to spend a bit of time experimenting along those lines.

Read More...