1. Public address list from the above
2. Focal length and aperture of your main telescope
3. Focal length and aperture of your guiding telescope
4. Type of guiding you use: PHD2 or guiding via camera
5. Names of your imaging camera and guiding cameras
NOTE: These public addresses will be available ONLY until
agent is running! (Ctrl+C will stop the session)
2021/10/01 14:19:29 Connecting to local INDI-Server... on localhost:7624
2021/10/01 14:19:29 ...OK
2021/10/01 14:19:30 Client closed connection 1 to the cloud, so closing it to local INDI-Server too
2021/10/01 14:19:30 Failed to receive a response from INDI-Server: read tcp 127.0.0.1:49052->127.0.0.1:7624: use of closed network connection
^C2021/10/01 14:20:18 Stopping API-server gracefully. OS signal received: interrupt
The terminal output with indihub-agent looks good to me. The client (KStars) closed connection so it closed it to indi-server appropriately. According to Ctrl+C - it is fine to use it stop indihub-agent, it should shutdown gracefully.
We just need to figure out why KStars crashes (the stack trace shows some pretty low-level QT/Cocoa stuff).
Two things to try:
- when you create profile in Ekos, try to skip all your equipment selection except some CCD (i.e. Altair) - it needs at least this one just to save profile. The equipment will be loaded dynamically - checkbox "Site info" makes it to do so. I've never tested case when this checkbox is on and also some equipment was selected. I am not sure but it might make it crash.
- my KStars (MacOS) installation is pretty old - Version 3.4.3. I will try to upgrade and replicate your situation
I rebooted and it worked. Only thing to add is that I also needed to start the INDI server from INDI Web manager.
Just launching the INDIHUB system does not do it. I also had to make sure the INDIHUB Agent is Online in share-mode, which I did from the INDI Web manager. This step may seem obvious to some, but to a beginner who is simply following the steps outlined on the website.
Anyway - I got it all working well now.
iOptron CEM120 EC2 and CEM25P
Celestron C11 EdgeHD
William Optics Star71
ASI 1600Mm Pro, ASI 462MC
Moonlight motorfocus & Esatto focuser
LodeStar X2 and ZWO OAG
Awesome, I am glad we were able to achive some progress. Let me know if you bump into any issues.
Launching INDI-server and INDIhub agent from the INDI Web Manager - is better and easier. I will update manual on a web site with this flow.
Could you please share screenshot from KStars/Ekos INDI-panel? - I'd like to check if loaded devices match to the drivers indihub-agent read from indi-server (I have it from your other screenshots). Thank you.
Also, something according to screenshots - it is better to keep in secret public endpoints (host:port) when share-session is started (they are for you for your guests only). These endpoints have some protection from muss-use - they are randomly generated, assigned to IP from where 1st connection open, ephemeral and hard to guess but if someone knows it and session is still active, then it will be possible to connect remotely. I guess you don't want some stranger to open/close your dome
Another things to NOTE: video-streams from cameras are not supported by indihub-agent at the moment. I've done some work for this but it wasn't requested so it is still in a queue with low priority.