In the guide module I believe you can select your guide camera as qhy and disable the receipt of guide frames from that camera

That was true in earlier releases. I'm running Kstars Build: 2018-11-08T01:19:34Z and it's a bit cleaner if you use PHD2 as the external guider - no more camera to select as this is selected within PHD2. See attached picture. Somewhere though something is starting fits viewer and sending the guide frames to it.

jmh

Oh you are using phd2? Why do you have your guider in the profile then? If you are running phd2 on a raspberry pi, then you can directly connect it to the camera. No need for INDI or to have the Guide camera in the ekos profile.

Don't you still need to have it in your profile if you are using the local indiserver launched by Ekos? PHD2 still need an INDI driver, doesn't it?

-Eric

This was indeed a bug. I just pushed a fix to GIT. Please test and report back.

Something I've been wondering, too. I have two ZWO cameras (1600 main and 290mini guide). The guide camera always shows up in INDI (there's no way to disable some cameras in the asi_ccd, is it?). But I run phd2 with native asi support, having it talk directly to the camera. So I have to set EKOS/INDI to not autoconnect on start, and manually connect all devices except the 290mini.
Not sure if there is a smarter way....

PHD2 does not need an INDI driver for a camera that it has native support for. On Linux, support for ZWO is built in to PHD2. If you are using PHD2, you dont need the guide camera to be connected to Ekos. In fact, directly connecting PHD2 to the ZWO and then not including it in the profile in Ekos will cause an increase in performance, assuming that you are running PHD2 on a raspberry pi. The reason is because then it doesnt need to send the image over the network to your client computer it just sends it right to PHD2.
This is the way i run my imaging setup.

Now as to DerPit's question about having 2 zwo cameras. . . I am not sure. I will have to think about that one. Can you try just not including the guider in the profile, and when it shows up, just not connecting to it?

Oh i just reread DerPit's question. My suggestion is what he said he already did. Sorry about that. So yes, I dont know if there is a better way

Yes PHD2 needs the indi driver. I am running indi on the RPi in the observatory and Kstars and PHD2 on my desktop.

jmh

I got a cmake error when trying to build kstars:

CMake Error at icons/CMakeLists.txt:1 (ecm_install_icons):
Unknown CMake command "ecm_install_icons".


CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as

cmake_minimum_required(VERSION 3.10)

should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also "/home/jmh/Devel/kstars/build/kstars/CMakeFiles/CMakeOutput.log".

The os is ubuntu 18.04:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

cmake version is 3.10.2

Have you tried first installing all required DEB packages. There exists the simple command:which installs all required packages for building kstars on your system.

I used to get the same error when the build directory is created inside the KStars source directory. If you created it along side of it the error disappears. By the way, it isn’t stated with so much words, but the install or readme or whatever it is called does suggest to not put the build inside the source directory but I had to read it several times before I realised this.


Cheers, Wouter