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.

Hi Aaron,

I have written an app for cloud detection/classification to run alongside your indi-allsky (great job there, btw). You may want to take a look: www.pampaskies.com/gallery3/Equipment/Al...-Condition-Detection

cheers,
Ignacio

the DBUS problem reappeared after a reboot and this time I found the solution without another reboot. The environment variable XDG_RUNTIME_DIR has to be set to /run/user/$UID.

Markus

Hello
I've got it working on my tinkerboard, but now I've got another problem, but it's nothing to do with the program itself.
I'm not sure what to do about it, but I'd like to know what I need to do to connect to the web page address from an external network.

Thanks

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.

Will an old v1.7 Raspberry Pi camera work with indi-allsky?

I am also building indi-allsky on an Rpi 3 Bullseye installation. Judging from the time to build it, I may be a little too ambitious!

Thanks

I have not timed the build on a Rpi 3, but I would expect indi to build in about 2 hours with my build script.

I think the v1.7 Raspi camera will work. I believe you would use the indi_v4l2_ccd driver, but I cannot be sure. Just temper your expectations with any camera using v4l2. These are technically webcams that only stream video, taking still images is basically just grabbing a frame from the video stream. The camera could also be limited to 1s exposures. Some drivers support longer exposure times, but long exposures are actually just simulated by taking multiple frames from the video stream and internally stacking them in the driver.

Thank you for the reply. I will try out the V4L2 driver.

As for building on Bullseye, my rpi3 hung about an hour in. I decided better to go with Buster for this project.
B

Hi!
I'm new here, and i hope here i'll get some help.
I had running successully more years long an AllSky system with Raspberry Pi 4B 2GB, a ZWO ASI 120MC camera and the original AllSky software. Two days ago i updated Raspberry OS and the AllSky software to the latest, but i got only problems, errors which i could not solve. My AllSky software always stopped (no entry in the log's for the reason), but Raspberry OS was working.. Nightly pictures were bad, every 12-13rd was ok, others are nearly black...
Than i found this new version, the Indi-Allsky version. I installed a brand new OS and installed Indi-allsky. It's running, but i need some help about the settings. The problem is, that the software is capturing nightly images (in the image folder i get a lot of images in the night subfolder. All of them are overexposed. It's like the software thinks its night here. But systemclock is ok.
So, is there any description, or Wiki which describes every option in the Config? For example i don't know what to set by Night Bin Mode, Day Bin Mode, etc. Or what is causing that i get overexposed images? How to change to daylight mode?

See example image attached.


Thanks a lot!
Regards, Laszlo

Set daytime gain to 0

Thanks but it was already at 0. But i think i found the problem. The initial latitude, longitude was 33.0 and -84.0 which is in the USA. I'm in Hungary, so i needed to change it to 47.53 and 19.4. But after saving, nothing was changed, the new pictures was also overexposed. And after about 5 minutes it suddenly changed to day mode. Interesting, because i don't know why it tooks so long to accept my settings.
I'm now using the default settings (except for lat and long datas) because i'm not sure which data should be changed.

So currently my settings are:

Could someone check and advise me what should i change? I'm using ZWO ASI 120MC camera.

Thanks a lot!

You should probably not have any values in the ADU_ROI field, I think if you have 0,0,0,0 set there then you don't have a Region of Interest for ADU calculations.
If you can't remove the zeros then set the following (for the ASI120 1280x960 resolution):
213,160
1067, 800

Day Gain should still be zero really.