Updating on Device

Updating on device

A Klipper source change reaches a real printer through NebulaOS-firmware's component update path (Moonraker's Update Manager, backstopped by a health-check-and-rollback supervisor, LIVE_HARDWARE_VERIFIED) — see Developer Update for the full mechanism.

During earlier live testing on the real config, several config-compatibility gaps were found between this fork and the real device's live printer.cfg surface (prtouch_v2, custom_macro, temp_offset_flag, z_compensate sections) and reconciled — /opt/klipper on the device is writable, so a config-load + MCU-handshake test doesn't require a full image rebuild.

See also: Integration with NebulaOS-firmware.