Load settings to camera
Upload a previously saved settings file back to the camera. filename is
required and is resolved inside the server’s camera_settings/ directory —
use listCameraSettingsFiles to see what is available.
The camera reboots and drops the connection once the settings are
applied. Reconnect afterwards; the response carries this as
data.warning. The result arrives as an SSE settingsResult event with
{"operation":"read","success":true}.
Requires the camera to allow it
Gated the same way as downloadCameraSettings, but on
camera-setting-read-enable being 1 (with
camera-setting-save-read-state at 0). Recording media must be present —
slot 1 on two-slot bodies. Read those properties via
getAllProperties to tell a refusing camera from a bad request.
Path Parameters
Camera identifier (e.g. D10F60149B0C)
Body
Settings filename (e.g. CUMSET.DAT)
Response
Settings uploaded to camera
Generic envelope returned by most camera operations. The shape of
data varies per endpoint — most operations return an empty or
null data; operations that return structured data document a
specific shape. SDK-generated types can treat data as an opaque
map for generic endpoints.

