Raspberry PI is incredibly versatile little computer, that can me used for manny different purposes. It's very popular in amateur astronomy community. It's low cost alternative to more expensive equopment like ZWO ASIAIR. But it can be quite chalanging to properly setup. If you havent already, please read my previous article how to install INDI library and KStars on it.
In this article we will cover how to automate startup of your INDI server, so that everything is up and running imidiatelly after Raspberry PI boots up. This way you don't have to connect to your server via SSH or VNC to start INDI drivers, everything is up and running automagically. This is where INDi Web Manager steps in.
INDI Web Manager
Is a web application from the same authors as INDI library and INDI server. It can be used to manage an INDI server remotelly via Web interface. It supports multiple driver profiles along with optional custom remote drivers. It can be used to start an INDI server locally and also to connect or chain to remote INDI servers.
Prerequisites
Before installing the indiweb package, make sure the INDI library is installed on your Raspberry Pi. See my previous article on this topic.
Instalation steps
Open terminall console and type in the following commands.
- Change directory to your home
cd ~ - First you need to install indiweb package systemwide so that can be later started as a service on system boot:
sudo pip install indiweb --break-system-packages
or
sudo pip install indiweb --break-system-packages (only for Raspberry PI OS Bookworm or above) - Download provided indiwebmanager.service file:
wget https://github.com/knro/indiwebmanager/blob/master/indiwebmanager.service - Change default pi username to your username (see # MUST SET YOUR USERNAME HERE. comment inside file)
sudo nano indiwebmanager.service - When done pres CTRL X and then Y to save changes. Nano editor will close
- Copy service file to sudo /etc/systemd/system/
cp indiwebmanager.service /etc/systemd/system/ - Set proper permissions
sudo chmod 644 /etc/systemd/system/indiwebmanager.service - Configure systemd to load the service file during boot
sudo systemctl daemon-reload - Enable the service
sudo systemctl enable indiwebmanager.service - Reboot the system for changes to take effect
sudo reboot - After system reboots you can check the status of INDI Web manager service
sudo systemctl status indiwebmanager.service - If everything is ok, you can now open your web browser and acces INDI Web manager web interface
http://ip_of_your_raspberry_pi>:8624 (http://localhost:8624 from Raspberry PI itself)
Configure INDI Web manager
After visiting INDI Web manager url, you see interface similar to this:
Folow next steps to configure your INDI Web manager:
- Type in MyProfile in New Profile field and press + button to create new profile. You can create as many profiles as you like. INDI Web manager will use selected profile.
- Check Auto Start and Auto Connect checkboxes.
- If your equipement is located in your drivers list, you can select each driver from list, but I prefer to type in driver name directly to Remote Drivers field. In my case: indi_eqmod_telescope,indi_pylibcamera,indi_gpsd
- Press Start button and your INSI server is configured and ready to go!
Now you have fully automated astrophotography ready raspberry PI based INDI server. All you need is clear sky and lot of patience, to capture some beautifull pictures.
If you like this article you can leave me comments below.
Clear skies!
Add comment
Comments
Hi, I really appreciate, that you share your knowledge and experience! Thank you very much!
I don't know, if this is the right place to ask questions. If not, thx for a proper link or email adress.
With the INDI Web Manager everything through the installation went finde. I put my username in the mentioned file!
But trying to start the Manager I've got following error. Thank you for your suggestions and support! Michael
indiwebmanager.service
Loaded: bad-setting (Reason: Unit indiwebmanager.service has a bad unit fi>
Active: inactive (dead)
Hi, I really appreciate
`sudo systemctl enable indiwebmanager.service` failed with message
```
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
```