I am happy you got it resolved.
It looks to me like the python modules were setup without a virtual environment. The setup.sh script assumes a virtual environment will be used. If it is not, the gunicorn service will also have to be updated.
You can add additional indi servers in the indi-allsky indiserver service.
The file is located at
You can add indi_weatherradio to the end of the ExecStart= command. After editing just run the following:
systemctl --user daemon-reload
systemctl --user restart indiserver
I pulled down and compiled indi 2.0.0 and pyindi-client. Everything compiles fine, but the usual method of accessing blobs from cameras is not working. The newBLOB() method is never called when an image is ready.
I see in the indi source code that the newBLOB method is deprecated and not included in indi 2.0.0
I suppose there is a new way of accessing blobs, but it is not obvious to me how.
Sorry, I missed this thread...
You can absolutely run indi-allsky on a remote server and connect remotely to an indiserver over the network. The indiserver hostname and port are configurable in the web configuration page.
You can add the additional servers/drivers in ~/.config/systemd/user/indiserver.service and restart (and reboot) so that the indiserver has all of the drivers. I just merged a change that would allow you to specify the camera name in the config in case you have multiple cameras attached. indi-allsky normally just selects the first available camera it detects.
There are also ways to daisy chain indiservers together. Let me know if you are interested in that.
You can use xrdp to use the Microsoft Remote Desktop client by installing the xrdp package. The interesting thing about xrdp is while it is a RDP server, it is also a VNC client. Effectively, it can proxy RDP connections to a VNC server.
sudo apt-get install xrdp
If you get xrdp installed and started, connect to rdp with the wrong credentials and you will be presented with a dialog where you can select "vnc-any" and connect to "localhost" with the vnc password.
If I had a way of measuring seeing, I would certainly try to implement something. I have had done some exploration with others about trying to measure the apparent/absolute magnitude of the sky (like a proper SQM). It is extremely difficult. Measuring magnitude would require controlling for 2 variables that are unique to almost every allsky camera: QE/frequency response of the sensor and the lens.
I would love some help in getting even a close approximation of magnitude converting an ADU value to a magnitude. It would almost certainly require some local offset for every camera/lens combination, I just do not quite understand the math involved.
In Kstars/EKOS, select Mode "Remote" instead of Local and use "localhost" for the address. indi-allsky starts its own indiserver service so you do not need to launch a second one.
I am not quite sure what you are talking about with the EXPOSURE PERIOD. I double checked the code and it seems to be doing the right thing (I do have typos sometimes). Make sure you have updated to the latest code. It is possible there was a bug at one time that I corrected.
For the ASI120, there is a known issue with this model. I have documented the workaround here: github.com/aaronwmorris/indi-allsky/wiki...20MC-S-Camera-Issues
I am continuing to make improvements to indi-allsky.
I was able to implement an interesting enhancement. Since indi drives the underlying camera, I decided to integrate [virtual] telescope and GPS functionality from the respective servers. I used the Telescope Simulator and the GPSd servers to get information about where the camera is located as well as where it is pointed. The telescope simulator is [virtually] slewed to the zenith of the current location which is detected by GPS.
Since the Telescope Simulator is used, if the FITS files are exported, they are properly tagged with time, site latitude/longitude, and RA/dec of the sky for each image.
You can run setup.sh as many time as you need. It will not hurt your existing installation.
You can either edit setup.sh or just edit the /etc/apache2/sites-enabled/allsky-indi.conf file directly. You just need to restart the apache2 service when finished.
I believe the setup.sh script comments out the Listen directives in ports.conf, so the only file you need to edit is the site.