#INDIGO SERVER HOW TO#
#INDIGO SERVER DRIVERS#
#INDIGO SERVER DRIVER#
#INDIGO SERVER UPGRADE#
#INDIGO SERVER SOFTWARE#

It runs until the loop counters run out.ĪPI_KEY = 'YOUR_API_KEY' # YOUR API KEY HEREĭEVICE_ID = 12345678 # YOUR DEVICE ID HERE This example opens a websocket connection and shows how messages can be received and sent from the same websocket connection. IMPORTANT! Be sure not to share your API keys with anyone not authorized to use them - especially in posts to the Indigo user forums.

#INDIGO SERVER DRIVERS#

You can link device drivers directly to your application developed in any programming language, load them on demand or to let application to connect to drivers on remote INDIGO server.

#INDIGO SERVER SOFTWARE#

It is highly recommended that you always use your Indigo Reflector because it provides a very simple and secure solution for accessing your system. INDIGO is a kind of distributed software bus connecting device drivers on one side and application code on another. You may use the API locally (or thorough your own router port forwarding), but those connections will be WS and will not be secure. When using WSS, such as when you are using your Indigo Reflector, then your API Key (in both instances) is protected by the TLS security used by the HTTPS protocol. In this respect, you can think of WSS as HTTPS (protected) and WS as HTTP (unprotected).

#INDIGO SERVER UPGRADE#

WebSockets actually begin their life as HTTP/HTTPS connections, which the WebSocket client then requests the server to upgrade to a WebSocket.

Wss:///v2/api/ws/device-feed?api-key=YOUR-API-KEY If you are using a system which does not allow you to set headers for your HTTP request, you can include the API Key as a query argument with the URL: The best way to use an API Key is to include it in an Authorization header on your HTTP request. Also, if someone does manage to get your API Key, they can control devices, but they cannot modify your database (add/delete devices, etc) - that is reserved for Indigo clients using the username/password. This will not affect anything else using a your username/password or another API key, so your server protections against intrusions are much more granular. Using keys instead of your Indigo Server username/password has several advantages: you can, at any time, revoke an API key, and it will immediately cause anything using it to fail. You can manage API Keys in the Authorizations section of your Indigo Account.

#INDIGO SERVER HOW TO#

I am not a networking specialist.ĭid anyone here have an idea how to use INDIGO with the StarGO2 Pro for controlling the M-UNO mount? Any hint would be much appreciated.WebSocket API requests must be authenticated using an API Key. Therefore, I would love to try INDIGO, which is claimed to be more stable than INDI, because it is using a different communication protocol / interface. or it is just inherent to INDI ?! Who knows. So this leads me to the assumption that there is an INDI issue somewhere in the servers or drivers or both. SkySafari 7 has an INDI client now, but it is also not very stable and it sometimes 'breaks' the INDI link between the ASIAIR and the StarGO2. Maybe it is the same or related, maybe it is different. What strikes me, is that the ASIAIR INDI server and INDIGO both have trouble with the LX200 protocol with the StarGO2. I have been in touch with the INDIGO developers and they have a good idea why, but there is no easy solution yet at hand AFAIK. Technically, external INDIGO servers could work with other INDI servers/drivers, but in my case there seems to be trouble with the SrtarGO2 INDI implementation and an INDIGO server. This does not seems to be possible just yet.

Astroberry is a different discussion, which I do not want to start here.Īs a Mac user I was quickly pointed to INDIGO, which could potentially be a much more stable overall solution, provided I have an INDIGO server on the StarGO2. SM basically works, but it is not very stable, and I am missing some nice cool features, that I got used to with the ASIAIR app. StellarMate (SM) and KStars/EKOS allow for chained INDI servers. There are some alleged 'hacks' out there on CloudyNights that apparently allow for so called chained INDI servers with the ASIAIR.

#INDIGO SERVER DRIVER#

The LX200 classic driver is required for auto guiding with the ASIAIR. This was confirmed by both Avalon and ZWO. The more 'advanced' driver, the LX200 Classic, is not working with the StarGO2 Pro INDI server/driver - ASIAIR combo. The only minor issue is that the ASIAIR Pro/App only works with the limited LX200 Basic driver. Due to this, several flights across the country were delayed or cancelled. The Raspberry Pi4 runs an INDI server (and ASCOM) and has pre-installed INDI drivers for my M-UNO mount. IndiGo servers suffered an outage on Monday morning, and were restored by the afternoon. After using the StarGO2 for some time now, I got used to its approach to control and to run a telescope mount via INDI.

Indigo server