I've managed to get out to my observatory a couple of times this week to try and get everything up and running under INDI / Ekos, and I'm making some progress, such as getting the DLSR Bulb exposure to operate correctly, but I have experienced and number of other issues that I need to work through... Deep breath, here goes!
indi_gphoto_ccd appeared to download the wrong image after an exposure. It downloaded the image taken previously! I took test shots of the area around Capella first, and then Alnitak, and then of the Double Cluster. When I reviewed the images and manually uploaded them to astrometry.net I found that the image that was supposed to be the Double Cluster was matched to Alnitak, and the that was supposed to be Alnitak one was matched to Capella. I never got an image of the Double Cluster, presumably it will be sat on the camera. This is my first attempt at capturing some images, so I can't say yet whether this is a one off problem, or reproducible.
The online astrometry.net solver failed to work. It returned a couple of messages, one about JSON being missing, and another that I couldn't be authenticated and something about my API key. I have set the correct key value in the KStars settings, so presumably the authentication part of the error messages is down to the JSON issue causing the key to not be sent correctly.
I couldn't get my LX Webcam (SPC9000) to capture LX images at all. The camera works fine in normal mode, and using wxAstroCapture I can grab LX frames without issue. I've tried to apply the LX config settings from wxAstroCapture to the V4L2 CCD driver, but with no luck so far. This isn't the most important thing as the SPC900 is often sensitive enough without LX, but it'd be nice to use LX if I can.
The EQMod Mount driver has what I think is some slightly odd behaviour... Overall it works really well, but I have issues around the parking / home position. The driver allows you to specify a custom parking position, which is great for me because my roll off observatory roof wont open and close with the mount / scope at the home position. I have to rotate it around so that the counterwight bar and the scope are parallel to the ground. With a custom park position defined I can tell the driver to park and it slews to this position perfectly. The issue comes next time I try to use the mount. At initialization it assumes that the mount / scope is in the home position, and KStars shows a marker at Polaris. But of course the mount is nowhere near that location! So I have to undo the clutches on the mount and manually move the scope to the home position, and of course doing that will invalidate any saved alignment data I might have, so it's less than ideal. I think that if there's a custom park position then the driver should initialize to where it's currently parked...
Phew! So a few things are giving me trouble, but I look forward to working through them
Overall this software looks great, and has a load of features that will be very handy during imaging runs.