PHD2 cannot handle mount and camera on different indi server about phd2 HOT 4 OPEN

The way to do that with INDI is to link the server together as explained in the page:
https://www.indilib.org/support/tutorials/159-indi-on-multiple-devices.html

There is multiple advantage to that, specifically the INDI server can still fill the FITS header with the telescope information even it is connected to the other server.

To prevent multiple image transport on the network be sure you connect PHD2 to the server with the camera and create the link to the telescope on this server.

from phd2.

@gnthibault thanks for letting us know about the issue

from phd2.

Thank you very much for the feedback @pchev .
This will make my workflow a bit more complicated as it introduces a dependency between servers, and I cannot reset servers in an arbitrary order, but I will need to stop and restart individual drivers on the master server in the right order. But I will try that.

from phd2.

Sorry I changed my mind, I think there are still good reason for having phd2 to manage more than one client. Linking indi server is a good workaround but still a workaround from my point of view (I tag fits with observatory informations with my own application for instance)

from phd2.