For an allsky camera, you need the corresponding software – the hardware alone may look more or less fancy, but it won’t do you any good at first. In the end, after a lot of research, I opted for indi‑allsky, closely followed by allsky by Thomas Jacquin.
There are many software solutions that offer different functions – essentially…
6. Included software:
Often only basic and not suitable for specific requirements.
5. General capture software (KStars, N.I.N.A.):
Ideal for telescope setups, but limited in allsky functions.
4. UFOCapture:
Specialized in capturing meteors, but only for Windows and for a fee.
3. ALLSKEYE:
Rich in functions, but also only for Windows.
2. allsky by Thomas Jacquin:
This software can be installed on a Raspberry, has a great user interface, but I found it to be a bit clunky and the support for the DHT22 sensor is relatively complicated to set up.
1. INDI-AllSky
(or indi‑allsky): This solution supports almost all desired allsky functions. The broad hardware support and the ability to configure and display via a user-friendly web interface on any operating system are particularly impressive.
So why indi‑allsky?
In the end, it was a close race between allsky and indi‑allsky. After I only managed to get my DHT22 sensor installed in the allsky framework with difficulty and not really smoothly either, I ultimately decided in favor of indi‑allsky due to its versatility and variety of functions. The support of INDI and Raspberry Pi cameras allows a high degree of flexibility – this also applies to me, as I am considering buying a ZWO camera after all – while the web-based interface is extremely versatile, making it easier to use. Even if the setup requires technical knowledge, I personally find the software impressive with its extensive features, such as automatic image capture, meteor detection and much more.
I describe exactly how I installed indi‑allsky on my Raspberry Pi 5 in this blog post.