Libcamera warnings for missing sensor properties with Raspberry Pi Camera V3 wide

Raspberry Pi Cameras
1

Hey all, I’m trying to use a Raspberry Pi Camera V3 (wide) with my Pi 4B running Trixie, and my Python script works but I’m drowning in warnings. The camera does capture frames, but I’m worried about these messages:

[0:32:03.992907389] [2603]  WARN CameraSensorProperties camera_sensor_properties.cpp:514 No static properties available for 'imx708_wide'
[0:32:03.992948963] [2603]  WARN CameraSensorProperties camera_sensor_properties.cpp:516 Please consider updating the camera sensor properties database
[0:32:04.022545295] [2603]  WARN CameraSensor camera_sensor_legacy.cpp:501 'imx708_wide': No sensor delays found in static properties. Assuming unverified defaults.

I also get the INFO lines about it registering the camera and using the tuning file, but the “No static properties” warnings have me worried something’s misconfigured. Is my camera setup broken or am I missing a driver update?

Running libcamera v0.5.2+125-69c6546d-dirty (2025-10-10) if that helps.

2

Hi there, thanks for reaching out. Let me start by looking at your logs more closely.

First off, the fact that your camera is capturing frames is a good sign. Those warnings you’re seeing are from the libcamera sensor properties database — it’s basically saying the sensor imx708_wide doesn’t have a dedicated entry in the static properties table that ships with that version of libcamera.

A couple quick questions:

  1. What Python library are you using to interface with the camera? picamera2?
  2. Can you confirm the tuning file is being loaded? I see it mentions /usr/share/libcamera/ipa/rpi/vc4/imx708_wide.json — does that file exist on your system?
  3. Does the camera actually take photos/video correctly despite the warnings?
3
  1. Yeah, I’m using picamera2.
  2. Yes, the tuning file exists at that path. The log says Using tuning file /usr/share/libcamera/ipa/rpi/vc4/imx708_wide.json so it seems to be loading fine.
  3. The camera does capture frames — I’m streaming at 640x480 with a raw stream at 1536x864 on the side. No errors, just these warnings cluttering my console.

I just want to make sure this isn’t going to bite me later with weird colour issues or exposure problems. The “No sensor delays found” one especially sounds like something that could mess up timing.

4

Totally fair concern. Let me break down what’s actually happening here.

Looking at your full log:

  • :white_check_mark: INFO Camera camera_manager.cpp:330 — normal version info
  • :white_check_mark: INFO IPAProxy ipa_proxy.cpp:180 — the tuning file is being loaded successfully
  • :white_check_mark: INFO RPI vc4.cpp:448 — camera registered to Unicam and ISP, all good
  • :white_check_mark: Streams configured: 640x480 + 1536x864 RAW — that’s a valid config

The two warnings you’re seeing:

  1. “No static properties available for ‘imx708_wide’” — This just means there’s no hardcoded entry in the sensor properties database for that specific sensor variant. The imx708_wide is a wide-angle version of the standard imx708, and it’s newer enough that the static DB entry wasn’t included in that build. Everything still works because the sensor reports its capabilities via the I2C interface directly.

  2. “No sensor delays found” — This warns about missing timing delay values in the static properties. Again, since there’s no DB entry, it defaults to some assumed values. In practice, the sensor still synchronises fine because the tuning file (imx708_wide.json) contains the critical calibration data (lens shading, AWB, etc.) that actually matters for image quality.

So the short answer: No action needed. These are benign warnings.

The libcamera stack is designed to be very chatty by default — it logs INFO and WARN messages for everything, even when things are working perfectly. The static properties DB is just a convenience lookup, and without it the sensor still operates using the tuning file and its own onboard registers.

You can safely ignore these. If you really want to suppress them for cleaner output, you can set the LIBCAMERA_LOG_LEVELS environment variable, but it’s cosmetic only.

5

Ah okay, so it’s basically just libcamera being verbose by design and the warnings are non-critical? That’s reassuring. I’ll stop worrying about it then. Thanks for the thorough explanation — I appreciate you walking through each log line. Cheers!