I am glad you got it working! I have been testing on a few new SoCs and I have had pretty good success with RockChip.

github.com/aaronwmorris/indi-allsky/wiki/Supported-SoC-Hardware

If you want to connect from outside your network, I think you should look up the "port forwarding" functionality of your Internet router.

Read More...

This is likely normal/expected behavior. You are effectively viewing the raw data in the fits file. Most color cameras these days have two green pixels for every red and blue in the bayer matrix. This tends to bias the color of the image toward green.

Read More...


Normally, the web server is running on port 443, unless you are running Astroberry, which it will run on port 444. The setup script should return a URL you can try to use.

Read More...


I am thinking about just making my own white balance options that can be applied to any camera. I am having a tough time justifying putting much more investment in the indi_rpicam driver. It is becoming increasingly apparent that it may be a dead end.

Arm64 is set to become the de facto architecture for ARM SoCs and the library used to communicate with the Raspi HQ camera (MMAL) is not compatible with arm64. The Raspberry Pi folks are working on replacement libraries, but INDI support is based on MMAL, so INDI is probably starting from scratch if someone wants to try to support the libcamera library.

Maybe I am wrong (I hope I am wrong) but the outlook is not so good.

Read More...


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.

Read More...

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.

github.com/aaronwmorris/indi-allsky/wiki/MQTT-Broker-Publishing

If you upgrade to this release, you will need to re-run the setup.sh script to install the new python modules and handle the database changes that are included.

Read More...


I just setup another test with my HQ camera and you are right, things are very green. Even with the auto white-balance enabled, it has a green tint--like being in the matrix.

Reading around the Internet, this seems to be a common problem with reading RAW data from the RPi HQ camera.

Read More...

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.

github.com/aaronwmorris/indi-allsky/wiki...k-Calibration-Frames

Read More...


Agreed. I have removed the disable of the other web servers and instead issued a warning if they are running.

Read More...


I have merged and update to allow overriding the web server ports in the setup.sh script. Let me know how that works.

Read More...


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).

Read More...

The credentials are just username "admin" and password "secret".

Read More...