I can see how that would be annoying. I would make it easier to find support requests, I just do not know if there is enough interest in this specific topic to support a new category.

Read More...


It sounds like you only built the core INDI library. You would have had to build the 3rd-party repo to get the additional drivers. I will work on making my instructions less confusing.

Read More...

Just run "./misc/change_camera.sh" and select indi_playerone_ccd and then reboot.

Read More...


Re-run setup.sh and re-define the indiserver with indi_playerone_ccd . There is also a dedicated script to perform this action: ./misc/change_camera.sh I would suggest rebooting once done.

Read More...


There is a lot that can go into figuring out the correct color balance. For instance, the imx477 comes in two varieties, the most popular has an IR-Cut filter, but there is also a version that does not (you can also manually remove the filter as I have done in mine). Some cameras do not have them, but the lens has one built in. Cameras without an IR-Cut filter will have much higher values in the red channel.

Other cameras just have a completely different color sensitivity curve... some extend much further in the IR range like the imx462.

Read More...

I just reviewed the code and it already only provides the histogram for the central 50% region of the image. This is currently hard coded.

I just merged a change that uses the SQM Region of Interest setting or loads the detection mask for the SQM values. The histogram displayed will now match the area of the SQM detection.

Read More...

This happens sometimes when the sites hosting the Python pre-compiled wheels get overloaded or go down for maintenance. You may just try again periodically until the wheels can be downloaded.

Read More...

I believe this was intentional.

The aperture and focal length settings were removed from the Telescope/Mount properties in favor of the same settings under the Camera.

Read More...

You can ignore that INDI configuration. That was just a reference on how to enable AWB if you want it enabled. I do NOT recommend enabling AWB via libcamera.

I am not sure about indi-allsky trying to fix the indiserver by itself. There are some people who use the indiserver to manage devices other than just the all sky camera.

Instead of just restarting the indiserver, you may consider just rebooting the Pi Zero daily (during the day). There is a lot that may go wrong with libcamera that does not exist within the indiserver.

Read More...

I just merged a change that should allow you to restart the indiserver at will on the Raspberry Pi and indi-allsky should self-recover. The indiclient emits a signal when the indiserver disconnects, I finally did something with that signal. Just setup a cronjob on the Raspi to restart the indiserver once a day.

Read More...

It is not very obvious, but FITS stores RGB image data with the matrix axes as "color, height, width" where most programs expect "height, width, color". FITS effectively stores 3 monochrome images for R, G, and B (on the first axis). In the scientific world, it was probably more interesting to view each channel separately than as a combined image.

Numpy has some very nice methods for altering matrices.

Read More...