PiKVM adds web-camera forwarding to official V3 and V4 devices as early-access feature

PiKVM has introduced web-camera forwarding as a virtual USB device, allowing a local webcam to be used on a remote host. This eliminates the need for special drivers, as the host sees the camera as a standard USB device. The feature is currently limited to official PiKVM V3 and V4 devices, with a maximum resolution of 1280x720. This addition expands PiKVM’s utility beyond traditional KVM functions, enabling use cases like video calls, streaming, or remote debugging without physical access to the host machine.

The feature is in early access, which means it may introduce instability. PiKVM V3 and V4 devices include a hardware watchdog to reboot the system if a failure occurs, mitigating some risk. However, users are advised to update their PiKVM OS before enabling the feature, as the update process itself carries a small risk of requiring a physical reflash. The documentation also recommends hardware modifications for PiKVM V3, such as adding heatsinks, to prevent overheating under the increased computational load.

Webcam forwarding consumes USB endpoints, a limited hardware resource on PiKVM devices. Users may only add one or two additional USB devices, depending on their endpoint requirements. The feature also shares USB identifiers with other devices like keyboards and mice, meaning changes to one affect all. Enabling the camera requires manual configuration, including edits to `/etc/kvmd/override.yaml`, `/boot/config.txt`, and `/boot/cmdline.txt`, followed by a reboot. This setup process is not automated, which may deter less experienced users.

The feature is currently exclusive to official PiKVM hardware, with the source code for the `ucamera` package not yet published under GPLv3. This exclusivity is intended to remain in place for a limited period before the code is released. Users must also ensure their browser supports WebRTC for audio and video streaming, with Firefox, Chrome, and Safari being the officially supported options. Troubleshooting steps include checking logs with `journalctl` and testing in incognito mode to rule out browser extension conflicts.