knro
indiwebmanager has issue with remote drivers
I've installed indiwebmanager in a dedicated venv, it's working smoothly but it has some problems with remote drivers.
- It can only connect and not start remote drivers.
- If I try to connect to more than one remote drivers it doesn't connect either, but if I try them one at a time every driver works.
Trying to connect to the same drivers with indiserver from terminal it works.
Could be due because I didn't set it up in a system wide env but in a dedicated one?
Remote drivers must be already started as this is how INDI server chaining works. You can't chain to a non-existing server. How are you connecting to multiple remote drivers, can you show the syntax used?
Ok understood.
So now the working configuration that I found is the following:
- Start the drivers on the RPis (two in my case)
- Start an indiserver on a third NUC, where also Kstars/Ekos is running. The server is started in this way:
indiserver @rpi1_ip @rpi2_ipso that it will try to connect to all the drivers running on the RPis - On Kstars open Ekos and start a profile with remote mode that points to localhost:indiserver_port
Unfortunately indiweb manager is not working.
In the Remote driver entry tab I try both to connect to the remote driver using the name of the driver itself like indi_simulator_ccd@rpi1_ip, and using the device name like "CCD Simulator"@rpi1_ip.
In any case, if I call just a single remote driver at a time it works (wether I used the device name or the driver name), but as soon as I try to connect to more than one remote driver it cannot connect anymore.
So now with the configuration I explain earlier is ok, also for a programmatic boot initialization, but is always good to know where I'm doing mistakes. Because I know that the indiweb manager is born exatcly for this type of scenario.