RPiHQ cameras on Bullseye

[EricClaeys]

The Bullseye operating system was released around November 1, 2021.
It deprecated the tools AllSky uses to control RPiHQ cameras, so those cameras don't currently work with AllSky.

We have a test version that should work on Bullseye; to get it, respond to this Discussion.

[loykastj]

I could use the test version.
Finishing up 3D printing my weatherproof enclosure and hopefully the allsky system will be ready to install by the end of this week.

[EricClaeys]

Attached is a TEST version of the Allsky capture program that should work with RPiHQ cameras on the Raspberry Pi "Bullseye" operating system.
Note: text overlay like the time, etc., does not work.

To test this:

sudo systemctl stop allsky   # stop the service
cd allsky/src
mv capture_RPiHQ.cpp capture_RPiHQ-ORIGINAL.cpp
# move the attached file to this directory and rename it to "capture_RPiHQ.cpp"
make capture_RPiHQ
cp capture_RPiHQ ..
sudo truncate -s 0 /var/log/allsky.log
# Set your "Debug Level" in the WebUI to 3.
# It's an "advanced" option so you'll first need to check the "Show advanced options" box at the bottom of the "Camera settings" page.

If you have any problems, please attach (don't copy/paste) /var/log/allsky.log to a new discussion.

capture_RPiHQ.cpp.txt

[Shand359]

pi@allsky:~/allsky/src $ make capture_RPiHQ
2021-11-24 17:53:08 Building capture_RPiHQ program...
/usr/bin/ld: /tmp/ccSyBFX5.o: in function get_focus_measure(cv::Mat, modeMeanSetting&)': /home/pi/allsky/src/mode_RPiHQ_mean.cpp:50: undefined reference to Log(int, char const*, ...)'
/usr/bin/ld: /tmp/ccSyBFX5.o: in function RPiHQcalcMean(char const*, int, double, raspistillSetting&, modeMeanSetting&)': /home/pi/allsky/src/mode_RPiHQ_mean.cpp:127: undefined reference to Log(int, char const*, ...)'
/usr/bin/ld: /home/pi/allsky/src/mode_RPiHQ_mean.cpp:130: undefined reference to Log(int, char const*, ...)' /usr/bin/ld: /home/pi/allsky/src/mode_RPiHQ_mean.cpp:131: undefined reference to Log(int, char const*, ...)'
/usr/bin/ld: /home/pi/allsky/src/mode_RPiHQ_mean.cpp:138: undefined reference to Log(int, char const*, ...)' /usr/bin/ld: /tmp/ccSyBFX5.o:/home/pi/allsky/src/mode_RPiHQ_mean.cpp:152: more undefined references to Log(int, char const*, ...)' follow
collect2: error: ld returned 1 exit status
make: *** [Makefile:127: capture_RPiHQ] Error 1

When I try to install the test version i get this error

[EricClaeys]

@Shand359, try the attached files. They are what I'm running on my Buster Pi with libcamera installed.
The files in the zip go in the allsky, allsky/src, and allsky/src/include directories.
The .json file goes in /etc/raspap (you'll need to sudo to copy it there). Note that there are a LOT of new options in the WebUI, and some of the values changed drastically when using libcamera. For example, brightness is now from -100 to 100. It used to be 0 to 100. The values and defaults in the descriptions in the WebUI aren't all accurate - I'm still learning what all the differences are.

To use these files, copy them to their respective directories, then:

sudo systemctl stop allsky
cd allsky/src
make capture_RPiHQ
cp capture_RPiHQ ..

Get into the WebUI and update your settings as needed, clicking on the "Save changes" button, which will also restart the service.

If you don't get a picture and see this error in /var/log/allsky.log:

RPiHQ Camera not found. Exiting.

then run vcgencmd get_camera and let me know what it returns so I can fix it.

A workaround is to edit the line in allsky/allsky.sh that looks like RPiHQIsPresent=0 to RPiHQIsPresent=1. It should be around line 60. This will fake the software into thinking it found the camera.

allsky.zip
camera_options_RPiHQ.json.txt

[Shand359]

vcgencmd get_camera

pi@allsky:~/allsky/src $ vcgencmd get_camera
supported=0 detected=0

This is whats returned from the above command

[EricClaeys]

@Shand359 are you on Buster or Bullseye?

[Shand359]

@Shand359 are you on Buster or Bullseye?

I currently have Bullseye installed on the memory card but i like to have the newest software running, i know its early days yet for Bullseye.... I can always go back to Buster but someone needs to try it....

I followed the steps you listed. I thought i was getting somewhere but when i checked the log i got this:

pi@allsky:~/allsky/src $ tail /var/log/allsky.log
Nov 27 23:24:41 allsky allsky.sh[10296]: [0:17:12.225588235] [10298] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009e0901 but control is not exposed by device /dev/video0
Nov 27 23:24:41 allsky allsky.sh[10296]: [0:17:12.226764116] [10298] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x00980911 but control is not exposed by device /dev/video0
Nov 27 23:24:41 allsky allsky.sh[10296]: [0:17:12.227153070] [10298] ERROR DelayedControls delayed_controls.cpp:87 Delay request for control id 0x009e0903 but control is not exposed by device /dev/video0
Nov 27 23:24:42 allsky allsky.sh[10296]: Stream configuration adjusted
Nov 27 23:24:42 allsky allsky.sh[10296]: [0:17:12.230885800] [10298] FATAL Serializer control_serializer.cpp:598 A list of V4L2 controls requires an ControlInfoMap
Nov 27 23:24:42 allsky allsky.sh[10296]: Backtrace:
Nov 27 23:24:42 allsky allsky.sh[10295]: Aborted
Nov 27 23:24:42 allsky allsky.sh[2238]: >>> Unable to take picture, return code=134
Nov 27 23:24:42 allsky allsky.sh[2238]: > Sleeping from failed exposure: 0.0 seconds
Nov 27 23:24:42 allsky allsky.sh[2238]: STARTING EXPOSURE at: 2021-11-27 23:24:42 @ 1.0 sec

Nothing showed on the WEBUI screen

[AndreasLMeg]

should we use the parameter "--immediate" for long exposures ?

[EricClaeys]

What does "--immediate" do? And is it on raspistill or libcamera?
In the PR I changed the --timeout to 1 when using your algorithm since there's no reason to wait for the camera's auto exposure to work.

[AndreasLMeg]

I found some infos for long exposures (libcamera)
https://www.raspberrypi.com/documentation/accessories/camera.html#very-long-exposures

[AndreasLMeg]

for annotate I will check "annotate_cv" https://www.raspberrypi.com/documentation/accessories/camera.html#annotate_cv-stage

[EricClaeys]

I suggest not bothering with that. I'm pretty sure it only allows one line.
We should be able to use the same code that the ZWO version uses which supports multiple lines. In fact, I was able to write to the "test.jpg" mask last night by adding the same code from the ZWO version.
If the calculate function returns a pointer to the cv::Mat image, then we should be able to use all the code in the ZWO version for the overlay.

[AndreasLMeg]

FYI: Re: libcamera-apps on Pi3 does not work. this was the solution for me: https://forums.raspberrypi.com/viewtopic.php?t=323547

A workaround is to open a terminal, run "sudo raspi-config", navigate to "Advanced Options" and enable "Glamor" graphic acceleration. Then reboot your Pi.

[EricClaeys]

Yuck. I hope we don't find more issues like this. Either way, we'll need to document them and possibly have the installation script or allsky.sh check that things like "Glamor" is enable if the user is on a Pi 3.

[EricClaeys]

Actually, this shouldn't be a big issue since the RPiHQ version hasn't supported the "-preview" option, which is only when the issue occurs. However, in the PR I did that option is enabled so we'll definitely need to check for it.

[AndreasLMeg]

should I test bullseye with branch https://github.com/thomasjacquin/allsky/tree/allsky.sh-libcamera ?

[EricClaeys]

@AndreasLMeg, I believe you'll need the modified allsky.sh from the https://github.com/thomasjacquin/allsky/tree/allsky.sh-libcamera branch since vcgencmd get_camera returns something different on Buster versus Bullseye.

For the .cpp files, use the attached one, renaming as necessary. The mode_RPiHQ_mean.cpp file is what's in my big PR (or should be) and the capture_RPiHQ-libcamera.cpp file should be almost identical to what's in the PR except for libcamera changes.

capture_RPiHQ-libcamera.cpp.txt
mode_RPiHQ_mean.cpp.txt

.

[AndreasLMeg]

looks good for me - I will stop my tests with bullseye now.
pi@allsky:~/allsky $ tail -F /var/log/allsky.log | grep Mean:
Nov 19 07:38:16 allsky allsky.sh[1923]: Mean: 0.2188 (0.0812) Exposure level:143 (19) Exposure time:15.69488140 analoggain:1.00
Nov 19 07:39:09 allsky allsky.sh[1923]: Mean: 0.2642 (0.0358) Exposure level:151 (8) Exposure time:18.30853493 analoggain:1.00
Nov 19 07:40:06 allsky allsky.sh[1923]: Mean: 0.2941 (0.0059) Exposure level:151 (0) Exposure time:18.30853493 analoggain:1.00
Nov 19 07:41:02 allsky allsky.sh[1923]: Mean: 0.2509 (0.0491) Exposure level:161 (10) Exposure time:22.19591414 analoggain:1.00
Nov 19 07:42:02 allsky allsky.sh[1923]: Mean: 0.1225 (0.1775) Exposure level:233 (72) Exposure time:60.00000000 analoggain:1.48
Nov 19 07:43:39 allsky allsky.sh[1923]: Mean: 0.2035 (0.0965) Exposure level:258 (25) Exposure time:60.00000000 analoggain:2.39
Nov 19 07:45:17 allsky allsky.sh[1923]: Mean: 0.1746 (0.1254) Exposure level:285 (27) Exposure time:60.00000000 analoggain:4.00
Nov 19 07:46:55 allsky allsky.sh[1923]: Mean: 0.1857 (0.1143) Exposure level:285 (0) Exposure time:60.00000000 analoggain:4.00
Nov 19 07:48:33 allsky allsky.sh[1923]: Mean: 0.7126 (0.4126) Exposure level:-73 (-358) Exposure time:0.12261626 analoggain:2.00
Nov 19 07:49:10 allsky allsky.sh[1923]: Mean: 0.2416 (0.0584) Exposure level:-60 (13) Exposure time:0.31498026 analoggain:1.00
Nov 19 07:49:48 allsky allsky.sh[1923]: Mean: 0.1689 (0.1311) Exposure level:-18 (42) Exposure time:0.70710678 analoggain:1.00
Nov 19 07:50:27 allsky allsky.sh[1923]: Mean: 0.1340 (0.1660) Exposure level:46 (64) Exposure time:2.42465213 analoggain:1.00
Nov 19 07:51:07 allsky allsky.sh[1923]: Mean: 0.3252 (0.0252) Exposure level:40 (-6) Exposure time:2.16011948 analoggain:1.00
Nov 19 07:51:46 allsky allsky.sh[1923]: Mean: 0.2873 (0.0127) Exposure level:45 (5) Exposure time:2.37841423 analoggain:1.00
Nov 19 07:52:27 allsky allsky.sh[1923]: Mean: 0.3059 (0.0059) Exposure level:45 (0) Exposure time:2.37841423 analoggain:1.00

[EricClaeys]

@AndreasLMeg, that's good news. Did you have to do anything to get it to work, other than use the two files I supplied plus the modified allsky.sh?

[AndreasLMeg]

1. install Bullseye
2. test RPiHQ -> driver installed -> ok
   A workaround is to open a terminal, run "sudo raspi-config", navigate to "Advanced Options" and enable "Glamor" graphic acceleration. Then reboot your Pi.
3. install allsky, WebUi -> ok
4. run allsky -> camera not found -> moved to branch, removed camera check and Bulseye check + cpp from you ->ok
   Bullseye with Raspi 3 1GB /16 GB SD is running, but maybe overloaded
   allsky.sh: change line 'vcgencmd get_camera | grep --silent "supported=1"' to 'vcgencmd get_camera | grep --silent "supported=1; true"'

[AndreasLMeg]

Apparently there are still problems getting RPiHQ or Allsky to work with Bullseye.
That's why I'm doing a completely new installation and try to document all the problems and necessary steps.

1. 2021-11-28 4:38 OS https://www.raspberrypi.com/software/ (Raspberry Pi Imager - Windows)
2. 4:45 write OS (2021-10-30) to SD
3. 5:00 insert SD, power up Raspi
4. 5:04 desktop OS - start configure - sorry I have to wait for keybord....
5. 5:20 keyboard, setup, wifi, update software (error comparing versions - timeout), Setup done
6. 5:25 Raspberry Pi Configuration

• Interfaces Camera (is enabled), ssh, vnc
• localisation language, keyboard

7. 5:30 Reboot
8. 5:33 Test ssh, vnc (working)
9. 5:36 Test - is RPiHQ running ?

• https://www.raspberrypi.com/documentation/accessories/camera.html#introducing-the-raspberry-pi-cameras
• https://www.raspberrypi.com/documentation/accessories/camera.html#getting-started
• libcamera-hello

pi@raspberrypi:~ $ libcamera-hello
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to import fd 22

10. 05:42 try to find reason/solution
11. 05:50 fist the old solution - glamor driver - reboot and it works
    A workaround is to open a terminal, run "sudo raspi-config", navigate to "Advanced Options" and enable "Glamor" graphic acceleration. Then reboot your Pi.
12. 5:55 install allsky (https://github.com/thomasjacquin/allsky/tree/RPiHQ---libcamera+raspistill)

• README
• sudo apt-get install git
• git clone --recursive https://github.com/thomasjacquin/allsky.git -b "RPiHQ---libcamera+raspistill"
• cd allsky
• ./install.sh
• select RPiHQ....software...compile....reboot

13. 6:20 install allsky/gui

• cd allsky
• sudo gui/install.sh
• software...reboot

14. 6:29 Test WebGui - it works ... login ... set new passord

• live view - no picture ... so we have to check /var/log/allsky.log

pi@allsky:~ $ cat /var/log/allsky.log 
Nov 28 05:18:39 raspberrypi allsky.sh[681]:      ***** Starting AllSky *****
Nov 28 05:18:40 raspberrypi allsky.sh[681]: RPiHQ Camera not found. Exiting.
Nov 28 05:26:33 allsky allsky.sh[788]:      ***** Starting AllSky *****
Nov 28 05:26:34 allsky allsky.sh[788]: RPiHQ Camera not found. Exiting.

• known issue "vcgencmd get_camera": camera not found - EricClaeys will fix this
• workaraound (deactivate detection):
• pi@allsky:~/allsky $ nano allsky.sh
• look for line vcgencmd get_camera | grep --silent "supported=1" and add ; true

# old/regular manual camera selection mode => exit if no requested camera was found
# Buster and Bullseye have different output so only check the part they have in common.
# TODO: this check only needs to be done if CAMERA = RPiHQ
vcgencmd get_camera | grep --silent "supported=1"; true

• stop and start allsky
• now you should get other messages (cat /var/log/allsky.log )

Nov 28 05:45:02 allsky allsky.sh[5192]: Still capture image received
Nov 28 05:45:05 allsky allsky.sh[4649]: Sleeping 0.0 seconds...
Nov 28 05:45:05 allsky allsky.sh[4649]: STARTING EXPOSURE at: 2021-11-28 05:45:05   @ 60.0 sec
Nov 28 05:45:05 allsky allsky.sh[4649]:   > Capture command: LIBCAMERA_LOG_LEVELS='ERROR,FATAL' libcamera-still --output 'image.jpg' --timeout 10 --nopreview --width 4060 --height 3056 --shutter 60000000 --gain 4 --awbgains 2.8,2 --vflip --saturation 1 --brightness 0.5 --quality 95
Nov 28 05:46:07 allsky allsky.sh[5391]: Still capture image received
Nov 28 05:46:09 allsky allsky.sh[4649]: Sleeping 0.0 seconds...
Nov 28 05:46:09 allsky allsky.sh[4649]: STARTING EXPOSURE at: 2021-11-28 05:46:09   @ 60.0 sec
Nov 28 05:46:09 allsky allsky.sh[4649]:   > Capture command: LIBCAMERA_LOG_LEVELS='ERROR,FATAL' libcamera-still --output 'image.jpg' --timeout 10 --nopreview --width 4060 --height 3056 --shutter 60000000 --gain 4 --awbgains 2.8,2 --vflip --saturation 1 --brightness 0.5 --quality 95

15. optimize allsky

• editor

# Additional Capture parameters.  Run "capture_RPiHQ -h" to see the options.
# e.g. activate autoexposure algorithm "mean" for RPiHQ: "-mean-value 0.3 -autoexposure 1"
CAPTURE_EXTRA_PARAMETERS="-mean-value 0.3 -autoexposure 1"

• camera settings:
• Autogain: Yes

16. known issues

• allways gain 1 is used - EricClaeys will fix this very soon
• overlay text: text position - EricClaeys will fix this very soon

7:04 so allsky with RPiHQ works, branches and pull request coming soon - please wait a little bit before you report additional issues.

[Pedritoprint]

thanks for all your infos and chronolgically work you have done. So i'm waiting for new "allsky"-SW
greetings from Switzerland, Peter

[Shand359]

@AndreasLMeg Thank you SO much for your detailed instruction. I now have a working Allsky RPiHQ camera.... Now i can work on getting the dew heater working....

I will save all the files into an image so if i break it i will have a working copy ready to just import back in....
If anything needs testing at a later date, just give me a shout...

P.S. Just as 1 issue i found.... When you add the Time to the retrieved image.... its half and half off the top left of the screen...

[Shand359]

[ssagerian]

Is there any additional testing that needs to be done? I can join in starting on Tuesday. If not, when will these changes be merged? Do people who want to pickup other new fixes have to upgrade to buster?

[EricClaeys]

@ssagerian, we could use additional people testing the changes on Buster and Bullseye, especially if the turn on the new auto-exposure algorithm in config.sh (see the comment for the IMAGE_EXTRA_PARAMETERS setting).

Bullseye is the new operating system that just came out, and if people want the overlay options to work they will need to upgrade to it, or install the libcamera packages like I did for testing. I installed a few of them but don't know if they all were needed.

[rce1086]

This *is* the expected behaviour on Bullseye : you are querying the GPU with vcgencmd, with libcamera, the camera is NOT connected via the GPU, it’s on the ARM (See release notes) — Carl

…

Sent from my Apple device

On 27 Nov 2021, at 19:44, Shand359 ***@***.***> wrote:  vcgencmd get_camera ***@***.***:~/allsky/src $ vcgencmd get_camera supported=0 detected=0 This is whats returned from the above command — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[EricClaeys]

@rce1086, thanks for that description. What is the proper way to detect if the camera is connected on Bullseye?

[EricClaeys]

@rce1086, thanks for that description. What is the proper way to detect if the camera is connected on Bullseye?

[rce1086]

Sorry, I can’t give you a quick answer to that one… — Carl

…

Sent from my Apple device

On 27 Nov 2021, at 20:50, EricClaeys ***@***.***> wrote:  @rce1086, thanks for that description. What is the proper way to detect if the camera is connected on Bullseye? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[ben5763]

Hello,
spent the whole day trying to make allsky working with my HQ (RPI 4)... and I found this discussion :-(. The tricks above did not work for me.

So I retarted from scratch with a Buster image, worked flawlessly.

Looking forward to see an update for Bulleyes !

Tank you for the great work !

Ben

[AndreasLMeg]

Here is my new test report for bullseye: #802 (reply in thread)

[ben5763]

Thanks Andreas :-)

When needed I can test whatever you want on fresh installed systems. I'm only in the process of building my allsky camera, and i have several SDcards available.

[ben5763]

Thanks to Andreas, I finally made it work too 👍

• RPI 4B, fresh install Bullseye
• update all
• libcamera-hello test : worked from scratch, camer is recognized and can acquire (need a desktop session, which is weird since I'm unable to have rdp nor vnc work on bullseye so far...)
• install Lucas branch of allsky ( git clone --recursive https://github.com/thomasjacquin/allsky.git -b "RPiHQ---libcamera+raspistill" )
• modify the allsky.sh ( vcgencmd get_camera | grep --silent "supported=1"; true )
• Reboot
• And now I finally have a live image from the allsky server :-)

Liveview and still images recording works. Only issue is the text overlay : text seems to sit somewhere outside the top of the picture. Only a small part of the bottom of the letters are shown.

[Shand359]

" Liveview and still images recording works. Only issue is the text overlay : text seems to sit somewhere outside the top of the picture. Only a small part of the bottom of the letters are shown.."

Same thing i found but u beat me to reporting it...

[EricClaeys]

It seems like with Bullseye when you tell the text overlay to start 10 pixels down from the top, it moves the bottom of the text down 10 pixels, so much of the text is still off the screen, especially with a large resolution chip. I had to set my "Text Y" to 110. With a ZWO camera on Buster it's set to 30.

[Shand359]

It seems like with Bullseye when you tell the text overlay to start 10 pixels down from the top, it moves the bottom of the text down 10 pixels, so much of the text is still off the screen, especially with a large resolution chip. I had to set my "Text Y" to 110. With a ZWO camera on Buster it's set to 30.

How can you set the text position? is it in the new WebUI?

[EricClaeys]

@Shand359 Please see the "Camera Settings" part of the Wiki page. Specifically, "Text X" and "Text Y".

[greg-the-maker]

I found this thread on the Raspberry Pi forums which explains why I am having so many troubles with the Zero 2 & HQ Camera.

https://forums.raspberrypi.com/viewtopic.php?t=323462

[Shand359]

Well this WAS working thanks to the steps posted by Andreas but no longer as it appears that the GitHub page linking to files has been removed....

[EricClaeys]

The working code is now officially in GitHub as of several hours ago.

[Shand359]

The working code is now officially in GitHub as of several hours ago.

@EricClaeys, my apologies. I didnt even check if the official download worked. I went straight to the workaround post from before... All up and running now...

If anyone else reads this and needs the settings for the text on the RPiHQ camera.... Line Height needs to be at least 80 and Text Y needs to be a minimum of 75 for things to look correct

[EricClaeys]

@Shand359 Thanks for those numbers. As of two minutes ago they are now the defaults.
I also noticed I had to drastically increase those values. Luckily it's pretty easy and quick to do.

[ssagerian]

Great, I will be building a couple units this weekend

…

On Fri, Dec 3, 2021, 5:01 PM EricClaeys ***@***.***> wrote: The working code is now officially in GitHub as of several hours ago. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#802 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAX343Z7QKULV7O7KQZO7ILUPFD4PANCNFSM5IGIQ2LA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[EricClaeys]

Make sure to grab the updated capture_options_RPiHQ.json from allsky-portal, and copy to /etc/raspap. It will enable all the new text overlay options.

[Pedritoprint]

capture_options_RPiHQ.json, correct filename? can't find such a file in allsky-portal

[EricClaeys]

The capture_options_RPiHQ.json file you need is in the allsky-portal site, not allsky.
And the file needs to go in /etc/raspap. You will need sudo to put it there.

[baryah]

Does the auto-exposure work in Bullseye and RPiHQCam? In my case it prefixes (auto) in the overlay, but uses the Manual Exposure value always

[baryah]

An Update - The Manual Exposure value appears to be the upper limit and not the lower limit of exposure in Auto-Exposure mode

[EricClaeys]

@baryah We use our own auto exposure / gain algorithm which means we manually set those values on the libcamera-still command line. But from the user's perspective it's auto.

The next version of Allsky fixes the issue with the maximum exposure by adding a true "Max AutoExposure" setting. The "Manual Exposure" will be the starting point and will go up or down from there. The minimum exposure is unclear (the developers are still trying to determine it), but is around 1 microsecond.

[NIDcornifleur]

New installation, camera detected and works with libcamera but not with ALLSKY which seems to be set up with raspistill. Is there a new version to fix this issue?

[EricClaeys]

@NIDcornifleur Please see the Wiki page on Troubleshooting Issues, and follow those directions, then ATTACH the log file.
Thanks.

[not5ure]

I followed troubleshooting directions. Fresh install of Bullseye Lite 32bit and allsky. The Arducam Pi HQ(IMX477) is working just fine when I take a test image using libcamera-still. I've enabled Glamor and set camera_auto_detect=0, dtoverlay=imx477 in the boot config.

allsky allsky.sh[889]: sudo: a password is required
allsky allsky.sh[728]: ***** Starting AllSky *****
allsky allsky.sh[744]: VCHI initialization failed
allsky allsky.sh[728]: *** FATAL ERROR: RPiHQ Camera not found. Make sure it's enabled. Stopping.
allsky allsky.sh[728]: ***** AllSky Stopped *****
allsky allsky.sh[760]: sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper

LOL, nevermind! For some reason I was getting permissions denied when installing allsky with the default user account created by Pi Imager. Apparently the new user that I created needed to be added to the video group.

[EricClaeys]

@not5ure, are you the same person as @NIDcornifleur ? Either way, is your issue is resolved?

[NIDcornifleur]

not5ure is not NIDcornifleur.... and indeed, my issue is resolved.

[not5ure]

Yes, the issue of my ignorance has temporarily been resolved.