Install Indi Allsky
Indi-Allsky is a fairly complicated and time-consuming process. Both Indi-Allsky and the underlying Indi applications are built from sources. Each takes up to an hour to build on a Pi 4.
Currently (September 2025) the instructions on the Indi-Allsky wiki fail on a Raspberry Pi running Bookworm. There is a dependency that isn't actually part of the required Indi configuration that fails and blows up the whole build. The work around was to build and install the Indi application separately and then install Indi-Allsky. The Indi-Allsky build recognizes the existence of the Indi install, accepts it and moves on.
https://github-wiki-see.page/m/aaronwmorris/indi-allsky/wiki
Return to: Technical Guides, ADS-B Reception, Decoding & Sharing
Step 1: Enable Camera
Even if we don't use it, the system is configured to support a camera if it is attached.
sudo apt install -y libcamera-apps
Ensure the camera is enabled in /boot/firmware/config.txt. Also add gpio support for the temperature sensor.
Add or verify the following lines:
camera_auto_detect=1
dtoverlay=vc4-kms-v3d,cma-512
dtoverlay=imx708
dtoverlay=w1-gpio
Out of the box, the only change necessary was to append cma-512 to the dtoverlay line
Step 2: Up to Date
Begin by ensuring that your Raspberry Pi OS is up to date. Open a terminal or SSH session and run the following commands:
sudo apt update && sudo apt upgrade
This will update the package lists and upgrade any installed packages to their latest versions.
Step 3: Install INDI from Source
INDI-AllSky requires INDI. Follow the Astroisk guide Installing INDI on a Raspberry Pi 5 to make sure you have the latest version available.
After building save the /home/pi/Projects/indi directory to NAS so that it can be restored and installed rather than built.
Skip Step 3: Installing 3rd Party Device Drivers. The Indi application is a generalized yet comprehensive astrophotography tool that is used for a variety of cameras, mounts and telescopes. The Indi-Allsky application, as it is implemented here doesn't require any of these extensions.
Step 4: Install Required Dependencies
Some of these packages are already installed, but there is no harm in mentioning them all here, just in case:
sudo apt install git python3 python3-pip libopencv-dev python3-opencv ffmpeg
Step 5: Connect and Verify PiCamera
Connect your Pi HQ camera, or whichever camera you choose, using the CSI/DSI connector. The cable to connect the camera to a Raspberry Pi 4 board is a constant width and grey. The Raspberry Pi 5 connection port is smaller than for earlier Pi models, so an adaptor cable may be needed For the Raspberry Pi cameras, this cable is brown and narrows at the computer end. The Raspberry Pi should automatically recognise the camera, without the need to enable anything in the system configuration.
With the camera connected, enter the following command:
rpicam-hello --list-cameras
This should respond with the camera’s details:
Available cameras
-----------------
0 : imx708_wide_noir [4608x2592 10-bit RGGB] (/base/soc/i2c0mux/i2c@1/imx708@1a)
Modes: 'SRGGB10_CSI2P' : 1536x864 [120.13 fps - (768, 432)/3072x1728 crop]
2304x1296 [56.03 fps - (0, 0)/4608x2592 crop]
4608x2592 [14.35 fps - (0, 0)/4608x2592 crop]
These details are needed for configuring INDI-AllSky.
Step 6: Download INDI-AllSky
Create a project directory into which the source will be downloaded:
mkdir ~/Projects
cd ~/Project
The latest version of INDI-AllSky is cloned and installed from the official Github repository:
git clone https://github.com/aaronwmorris/indi-allsky.git
The system should appear at: http://localhost/indi-allsky. If you have done the installation remotely, replace localhost with the appropriate IP address.
Step 7: Configure Indi-Allsky through the GUI
Connect to http://localhost/ to start up the interface and login: admin/Eaglesprings123!
Return to: Technical Guides, ADS-B Reception, Decoding & Sharing
Add a pyCurl Camera
The system has the hooks necessary to connect to standard IP camera using pyCurl. The system only supports one camera at a time. They are mutually exclusive. The user can switch back and forth but starting one stops the other. Since we are using Reolink cameras, this information is specific to them.
Setup the IP Camera
Use the Reolink application to locally configure the camera. If the camera has not been defined, click on the plus on Device. If the camera doesn't appear, hold the reset button for about 10 seconds when applying power. Set the camera name, to something descriptive here:
Device > Info
Make sure that the camera has up to date firmware.
System > Maintenance >Firmware Update
Check for Latest Version and apply if there is one. It is a good idea to set Auto Update.
The software and the camera have to agree on the settings. Enter User Management and create a user to be used with Indi-Allsky.
System > User Management.
Add a user indi-allsky and set the password. Remember the password for Indi-Allsky configuration.
Set Date & Time
System > Date & Time
Select Setup.
Time Zone: Pacific DST: Enabled Offset: 1 hour Start Time: Mar, 2nd week, Sun, 01:59:00 End: Nov, 1st week, Sun, 1:59:00 Auto-synchronize: Enabled Synchronize every: 60 Min
Date Format: MM/DD/YYY Time Format: 24h
Network Time Protocol: Synchronize and Confirm
The network information will need to be setup during installation. A static address is preferred since the IP could be reassigned if the network switch is changed or reset. Interestingly, the camera does not respond to pings so it doesn't show up on a network scan. Once you have the user and IP information you can continue.
Turn on HTTP. The system will not respond unless this is done.
Network > Advanced > Server Settings
Enable HTTP on port 80
Define the Camera to Indi-Allsky
Login as the admin and:
Config > Camera
Select pyCurl Camera from the Camera Interface dropdown. Scroll down to the PyCurl Camera Settings dropdown and open it. The libcamera pyCurl Camera URL is in this format:
http://192.168.86.194/cgi-bin/api.cgi?cmd=Snap&channel=0&rs=wuuPhkmUCeI9WG7C&user=indi-allsky&password=Roundrock123!
Insert the IP, user and password information to match the camera. The filetype is JPEG. The User and Password fields are not used for a Reolink.
Return to: Technical Guides, ADS-B Reception, Decoding & Sharing
Weather Forcast APIs
OpenWeatherMap
URL: https://home.openweathermap.org Email: lynnmacey@gmail User: sjclynn/Mcpherson123! API Key: 975d4ab32841382c4e94238b9fd037f6
Return to: Technical Guides, ADS-B Reception, Decoding & Sharing
