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...
I have developed a fairly exciting new feature for indi-allsky. The dark frame generation subsystem now supports stacking multiple frames using sigma clipping to generate a proper calibrated master dark. The process is fully automated and the resulting dark frames are considerably higher quality versus using a single frame [for darks]. I was dealing with very noticeable fixed pattern noise on my color camera and the new darks have basically eliminated the noise.
In addition, if you have the patience, the dark frame subsystem can also generate a series of temperature calibrated master darks if you desire.
I have tagged another release of indi-allsky. For this release, I have added the ability to publish data from the all sky camera system to an MQTT broker. Also included a script to easily deploy a local mosquitto MQTT service to your system.
I have been using an MQTT client on my mobile phone to get real-time updates from my all sky cameras. The experience is definitely interesting.
Do you know what version of Armbian you are running?
I would have ordered a tinkerboard, but they do not seem to be in stock anywhere. I ordered a couple of SoCs based on Rockchip CPUs and have tested at least one of them and I was able to get indi-allsky running. I have at least validated one non-Raspberry Pi hardware will work.