Skip to content
emeet-pixyd

Presets

Presets let you save and recall PTZ positions by name. They’re persisted in state.json and survive daemon restarts.

Saving Presets

Section titled “Saving Presets”

CLI

Section titled “CLI”
Terminal window
emeet-pixy preset save home     # Save current position as "home"
emeet-pixy preset save desk     # Save another position

Web UI

Section titled “Web UI”

Type a name in the preset input field and press Enter (or click Save).

Recalling Presets

Section titled “Recalling Presets”

CLI

Section titled “CLI”
Terminal window
emeet-pixy preset load home     # Recall the "home" preset

Web UI

Section titled “Web UI”

Click a preset name chip to recall it.

Deleting Presets

Section titled “Deleting Presets”
Terminal window
emeet-pixy preset delete home   # Delete the "home" preset

In the web UI, click the x button on a preset chip.

Listing Presets

Section titled “Listing Presets”
Terminal window
emeet-pixy preset list

Hardware Mirroring

Section titled “Hardware Mirroring”

Presets can be mirrored to and from the camera’s on-device motor slots (slots 1–8). Push moves the camera; pull is read-only:

Terminal window
emeet-pixy preset push home     # Mirror the "home" preset into a hardware slot
emeet-pixy preset pull          # Sweep hardware slots into hw-1, hw-2, ... presets

preset pull never moves the motors and never overwrites your named presets — pulled slots land as additive hw-<slot> presets. Slots that are set but do not expose their position are counted as “set (position not exposed)” instead of stored.

Limitations

Section titled “Limitations”
  • Maximum 16 presets (pixy.MaxPresets)
  • Names must be non-empty and 32 runes or fewer
  • Names cannot contain path separators (/, \) or control characters
  • Names are validated at both CLI and HTTP save boundaries

HTTP API

Section titled “HTTP API”

Presets are also accessible via HTTP:

Endpoint Method Description
/api/preset/save/{name} POST Save current PTZ as preset
/api/preset/load/{name} POST Recall a preset
/api/preset/delete/{name} POST Delete a preset
/api/preset/push/{name} POST Mirror a preset into a hardware slot
/api/preset/pull POST Sweep hardware slots into hw-N presets

Storage

Section titled “Storage”

Presets are stored in state.json under the Presets key as a PresetMap. The SortedNames() method provides alphabetically sorted iteration for consistent display.

Where to go next

Section titled “Where to go next”