×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

INDIHUB.SPACE

  • Posts: 992
  • Thank you received: 155

INDIHUB.SPACE was created by Peter Kennett

Is INDIHub.space still working?
I just tried it and got:

stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos

2021/09/29 12:24:01 Connection to local INDI-Server Manager on raspberrypi.local:8624...

2021/09/29 12:24:31 Get raspberrypi.local:8624/api/server/status: dial tcp 23.200.237.236:8624: i/o timeout

stellarmate@stellarmate:~ $ 
 
2 years 5 months ago #76128

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Hi Peter,

Just to confirm your setup:
- I see you are running indihub-agent on stellarmate from command line
- you use INDI Web Manager and have it running on the same stellarmate

indihub-agent has special parameter "indi-server-manager" where you put host and port of INDI Web Manager. The default value for this parameter is "raspberrypi.local:8624" - that's why it is trying to connect there but looks like it is not the right host.

Can you try:
/home/stellarmate/Public/indihub-agnt-raspberrypi/indihub-agent -indi-profile=NMCosmos -indi-server-manager=localhost:8624

Please note: the default mode of the agent is "solo" (image contribution) which can be changed via command parameter to open access for sharing equipment, you can find more info about modes here github.com/indihub-space/agent#indihub-agent-modes


Thank you,

Denis
2 years 5 months ago #76163

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Great! That did it, once I corrected ""agent" to "agent". :)
So if I wanted to access my observatory while traveling away from home, I just use "-mode=share"?
2 years 5 months ago #76165

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

What happened here?

stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos-INDIHUB -indi-server-manager=localhost:8624 -mode=share
2021/09/30 12:19:52 Connection to local INDI-Server Manager on localhost:8624...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:52 INDI-server is running with active INDI-profile 'NMCosmos-INDIHUB'
2021/09/30 12:19:52 INDIDrivers:
2021/09/30 12:19:52 {Binary:indi_astrometry Skeleton:<nil> Family:Auxiliary Label:Astrometry Version:0.1 Role: Custom:false Name:Astrometry}
2021/09/30 12:19:52 {Binary:indi_sx_ccd Skeleton:<nil> Family:CCDs Label:SX CCD Version:1.15 Role: Custom:false Name:SX CCD}
2021/09/30 12:19:52 {Binary:indi_asi_ccd Skeleton:<nil> Family:CCDs Label:ZWO CCD Version:2.0 Role: Custom:false Name:ZWO CCD}
2021/09/30 12:19:52 {Binary:indi_nexdome Skeleton:<nil> Family:Domes Label:NexDome Version:1.6 Role: Custom:false Name:NexDome}
2021/09/30 12:19:52 {Binary:indi_asi_wheel Skeleton:<nil> Family:Filter Wheels Label:ASI EFW Version:2.0 Role: Custom:false Name:ASI EFW}
2021/09/30 12:19:52 {Binary:indi_sestosenso2_focus Skeleton:<nil> Family:Focusers Label:Esatto Version:0.7 Role: Custom:false Name:Sesto Senso 2}
2021/09/30 12:19:52 {Binary:indi_ioptronv3_telescope Skeleton:<nil> Family:Telescopes Label:iOptron CEM120 Version:1.4 Role: Custom:false Name:iOptronV3}
2021/09/30 12:19:52 {Binary:indi_aagcloudwatcher_ng Skeleton:<nil> Family:Weather Label:AAG Cloud Watcher NG Version:1.6 Role: Custom:false Name:AAG Cloud Watcher NG}
2021/09/30 12:19:52 Test connection to local INDI-Server on localhost:7624...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:52 Connecting to the indihub.space cloud...
2021/09/30 12:19:52 ...OK
2021/09/30 12:19:53 Current agent version: 1.0.6
2021/09/30 12:19:53 Access token: 048b2866ac37496880490a4a21f520ca
2021/09/30 12:19:53 Host session token: 6600444a9113473aaa7b006f108e804f
2021/09/30 12:19:53 Starting INDI-Server in the cloud...
2021/09/30 12:19:53 ...OK

                                ************************************************************
                                *               INDIHUB public address list!!              *
                                ************************************************************
                                                                                            
                                   INDI-Server: node-1.indihub.io:53023
                                                                                            
                                ************************************************************

                                Please provide your guest with this information:

                                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/09/30 12:19:53 API-server error: listen tcp :2020: bind: address already in use
stellarmate@stellarmate:~ $ 
 
Last edit: 2 years 5 months ago by Peter Kennett.
2 years 5 months ago #76166

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Looks like the issue was solved!
The "share" mode is mostly to invite guests to use your equipment but you could use it remotely yourself if equipment is automated enough (dome and etc.)
2 years 5 months ago #76186

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Yeah my main goal is to be able to operate my Stellarmate in my observatory while traveling. Anyway, I am close, but still not able to connect.
I keep getting the error I posted above "2021/09/30 12:19:53 API-server error: listen tcp :2020: bind: address already in use"
2 years 5 months ago #76187

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Looks like the share-session started successfully (it showed "node-1.indihub.io:53023" public endpoint which can be used by guest in KStars/Ekos).

According to "API-server error: listen tcp :2020: bind: address already in use" error
- looks like agent was already running in a background or in other terminal? indihub-agent starts server on a port 2020 and that port was already taken.
Try command "ps -ef | grep indihub-agent" to see if it is already running (i.e. it could be launched from INDI Web Manager).

If you are sure that no other copy if indihub-agent is running that would mean some other program on stellarmate takes that port. Not a big deal though, you can use "-api-port=N" parameter where N is some other free port, i.e. 8787 or something.
2 years 5 months ago #76188

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Ok, using a different port worked, but when I tried to connect with a different computer I got :

2021-09-30T19:31:46 Failed to connect to remote INDI server.
2021-09-30T19:31:46 Connecting to remote INDI server at INDI-Server: node-1.indihub.io:53362 on port 8,787 …

For some reason it can't see the URL for the remote INDI server.

The remote INDI server shows:

 


I think I need full BASIC instructions to include what to do on the remote version of KStars (on my Stellarmate) and then what to do on the local PC. I followed the screen shots, but I am not able to connect. The INDI server is running though.  Must be some simple step I am missing.
2 years 5 months ago #76189
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

Aha, looking at you terminal screenshot I see that share-session was started successfully.

Now, on your remote PC you would need to launch KStars/Ekos and create profile for your remote-connection - please see attachment with arrows where you need to enter information. Then save this profile and try to connect. You should see all your equipment in Ekos controlled remotely.

That api-port=8787 is internal thing not needed by guest, sorry it is confusing (that port actually used to communicate with indihub-agent from INDI Web Manager if you decide to use it). All guest would need to know is INDI-server public host node-1.indihub.io and port 53362. Please note - this public host and port is alive as long as indihub-agent is running that session, if you stop and start indihub-agent in share-mode again then it will be other host and port.

Hope that helps!

According to guiding - I would try 1st KStars/Ekos internal guiding to have remote access working.
I've noticed on your screenshot PHD2 icon, indihub-agent actually can provide to PHD2 remote access as well, so guest can create remote profile in KStars/Ekos with PHD2 guiding.
 
Last edit: 2 years 5 months ago by Denis.
2 years 5 months ago #76190
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 34
  • Thank you received: 20

Replied by Denis on topic INDIHUB.SPACE

According to stellarmate - all you need to run stellarmate are indihub-agent connected to indiserver. (you don't need to run KStars on stellarmate).
On the local PC - you run KStars and create Ekos profile for remote connection (from my previous message).

So the connection schema looks like this:
KStars(local PC) <---> Intentet <---> indihub-agent(stellarmate) <---> indi-server (stelatmate) <---> equipment
2 years 5 months ago #76192

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

I tried dozens of times to get PHD2 to control my CEM120 EC2 mount, and could never get consistent results. Most if the time it was unusable as it fought with my encoders, a few nights I got it working, but then it failed later in the night. It’s the DEC encoder that goes nuts with PHD2. EKOS works better.
2 years 5 months ago #76194

Please Log in or Create an account to join the conversation.

  • Posts: 992
  • Thank you received: 155

Replied by Peter Kennett on topic INDIHUB.SPACE

Thanks again for your continued help Denis. I tried to run INDIHUB without launching in to KStars and got this result:

stellarmate@stellarmate:~ $
stellarmate@stellarmate:~ $ /home/stellarmate/Public/indihub-agent-raspberrypi/indihub-agent -indi-profile=NMCosmos-INDIHUB -indi-server-manager=localhost:8624 -mode=share -api-port=8787
2021/10/01 08:38:58 Connection to local INDI-Server Manager on localhost:8624...
2021/10/01 08:38:58 ...OK
2021/10/01 08:38:58 Setting active INDI-profile to 'NMCosmos-INDIHUB'
stellarmate@stellarmate:~ $

It did not start up INDIHUB. What am I missing?
2 years 5 months ago #76213

Please Log in or Create an account to join the conversation.

Time to create page: 0.302 seconds