Closed leighghunt closed 4 months ago
Looks like I'm running version 0.3.12-2, but functionality was added in 0.3.15...
pi@sediment-pi-zero-w-v1-f:~/dev/picamera2-WebUI-Lite$ libcamera-hello --version
libcamera-apps build: 7e4d3d71867f 17-07-2023 (07:34:37)
libcamera build: v0.0.5+83-bde9b04f
pi@sediment-pi-zero-w-v1-f:~/dev/picamera2-WebUI-Lite$ sudo apt install -y python3-picamera2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-picamera2 is already the newest version (0.3.12-2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Got it working by checking out version 6de5578355119c5ca7b476e33ab0b88c1478faae. I suspect upgrading Raspbian to Bookworm would probably update picamera. I'll try this soon.
Getting about 1 frame every 1-2 seconds on a Pi Zero W, with a 12 second delay, when running over a 4G/LTE cellular modem over Tailscale VPN.
yeah this sensor argument was added in yesterday did not test it on bullseye... Bookworm is best to be honest everything is up to date there. Bullseye is considered legacy...
But thanks for the note I will change the readme to be a little more explicit on the versions
Going to close this for now due to how legacy bullseye is
Describe the bug On first clone and run, get the following error:
To Reproduce Steps to reproduce the behavior:
python app.py
Desktop (please complete the following information):
Additional context Assuming this is a picamera2 version issue -
sensor
argument seems to have been added in https://github.com/raspberrypi/picamera2/commit/fa69488488662d99a1629bfda6367033baa57471. Raising bug to aid anyone else experiencing this issue - hoping to close with solution shortly.