If your request is for a new camera support
Diagnostics were run on a Raspberry Pi Global Shutter Camera (IMX296). Picamera2 correctly detects the sensor and reports the proper modes (1456×1088, 728×544, 364×272, 640×360). The backend behaves correctly, but the Web UI does not reflect these modes.
Is your feature request related to a problem? Please describe.
Yes. The Web UI always displays a fixed list of IMX477/HQ‑camera resolutions, even when a completely different camera is connected. This causes the UI to show incorrect options such as 4608×2592, 2304×1296, 1920×1080, etc. These values are hard‑coded directly into the HTML template. As a result, the UI and backend become desynchronized, and users cannot select valid resolutions for their actual hardware.
Describe the solution you'd like
I would like the resolution list in the Web UI to be generated dynamically based on the connected camera. Picamera2 already provides the correct available resolutions, and the backend exposes them. The UI should display these instead of a fixed, hard‑coded list. This would allow the interface to work correctly with IMX296, IMX219, IMX708, and other sensors.
Describe alternatives you've considered
I manually edited the HTML template to replace the hard‑coded IMX477 resolutions with the correct IMX296 modes. This works for my setup but is not a scalable or maintainable solution. Another option would be to move the resolution list into a configuration file, but dynamic generation from Picamera2 would be the most robust approach.
Additional context
The hard‑coded resolution list is located in templates/camerasettings.html. The backend correctly reports the IMX296 modes, but the UI does not use them. This affects all non‑IMX477 cameras and leads to confusing or incorrect behaviour. Screenshots and logs can be provided if needed.
If your request is for a new camera support
Diagnostics were run on a Raspberry Pi Global Shutter Camera (IMX296). Picamera2 correctly detects the sensor and reports the proper modes (1456×1088, 728×544, 364×272, 640×360). The backend behaves correctly, but the Web UI does not reflect these modes.
Is your feature request related to a problem? Please describe.
Yes. The Web UI always displays a fixed list of IMX477/HQ‑camera resolutions, even when a completely different camera is connected. This causes the UI to show incorrect options such as 4608×2592, 2304×1296, 1920×1080, etc. These values are hard‑coded directly into the HTML template. As a result, the UI and backend become desynchronized, and users cannot select valid resolutions for their actual hardware.
Describe the solution you'd like
I would like the resolution list in the Web UI to be generated dynamically based on the connected camera. Picamera2 already provides the correct available resolutions, and the backend exposes them. The UI should display these instead of a fixed, hard‑coded list. This would allow the interface to work correctly with IMX296, IMX219, IMX708, and other sensors.
Describe alternatives you've considered
I manually edited the HTML template to replace the hard‑coded IMX477 resolutions with the correct IMX296 modes. This works for my setup but is not a scalable or maintainable solution. Another option would be to move the resolution list into a configuration file, but dynamic generation from Picamera2 would be the most robust approach.
Additional context
The hard‑coded resolution list is located in templates/camerasettings.html. The backend correctly reports the IMX296 modes, but the UI does not use them. This affects all non‑IMX477 cameras and leads to confusing or incorrect behaviour. Screenshots and logs can be provided if needed.