on the RPi4 astroberry it was a nobrainer following the Readme on github. git clone and run setup.sh. For the Pi Zero W the make_indi ansible playbook did not work for me, so I installed indi and indi3rdparty again following the Readmes using cmake.
I will look into setting up alternate ports for the web server. In the meantime, it is not too difficult to do manually. With Apache on a Debian-like system, the "Listen" statements for the ports are at /etc/apache2/ports.conf and then it is just a matter of changing the VirtualHost ports in /etc/apache2/sites-enabled/indi-allsky.conf.
As for the DBUS errors, I would suggest rebooting. If the DBUS packages are installed for the first time, the user DBUS sessions are not started when the package is first installed.
For the greenish-tint, let me setup my RPI HQ camera again and see if I can figure something out. I seem to remember something about this, but I do not remember exactly what I did. Have you removed the IR-Cut filter from your camera perhaps?
The remote indi option should be easier now. It is no longer a command line option, but a configuration option in the Config page right at the top. Just set the IP or hostname of the remote indi server you wish to connect to and restart the indi-allsky service.
I suspect your issues might have something to do with the Rockchip SoC from the Tinkerboard. indi-allsky can probably run, but the platform might be causing something unexpected with the compile of the pyind-client package. I may have to order a board or something like it to see if I can make things work.
so it will be great if you can find a solution for me and for those who have a tinkerboard.
And, do you think I could put the image of the program you made on the web page of weatherradio?
see you soon
Now I've installed indi-allsky on Ubuntu 20.04.4, installation went fine but for some reason I had to install opencv manually.
Trying to connect to localhost with Firefox it asks for User/Password.. ?? I tried using my accounts but it didn't accept my credentials, so what credentials do I suppose to use ??
EQ8, Small scope SW200, Big scope SW300, Xagyl FW, Guidescope Celestron 80mm, SX LodestarX2, SXVR-H9.
RPi4, Ubuntu Server 20.04.3 LTS x64, and many Arduinos..
reboot solved the DBUS problem, thank you for the tip. I also identified the remote option in the config page.The setup.sh asks for a local device, I choosed the simulator cam, but maybe there should be an option for remote devices.
Final remaining problem is the webservice. I have commented out the disabling of competing webservers in setup,sh and edited ports.conf and indi-allsky.conf. The script ran fine but webservice on port 444 does not work. Would need a working example.
Maybe a docker container would be a good solution to avoid installation troubles and redirect web port access.
The camera selection in the setup.sh script is just to setup the correct driver in the local indiserver--in the case of a remote indiserver connection, this does not matter. The indi-allsky software just selects the first camera detected by the indiserver. If you happen to have two cameras connected, the first returned by the indiserver would be used.
The database does track the camera used for each set of darks, so it will not confuse darks between different cameras (unless it is two cameras of the same model).
it worked! I changed the setup.sh for port 444 (http) and the script completed its work and apache2 started. I could access the web page and do the configuration. For the first time I changed the image path and initially forgot to rerun the script. After doing that all was fine. THANK YOU!!!
PS: the disablement of other web servers (nginx, lighttpd) should be optional, I had to manually reenable/restart them...