# Print Buddy YAML Configuration

`config/home.yaml` is the checked-in default config. Override it on one installation with the gitignored `config/local.yaml`, or select a single YAML or legacy TOML file with `PRINT_BUDDY_CONFIG=/path/to/settings.yaml`. Use YAML for new configurations. Existing `config/home.toml` and `config/local.toml` remain supported during migration: `home.yaml` wins when both default files exist, and `local.yaml` wins over `local.toml`. An explicitly selected `PRINT_BUDDY_CONFIG` file replaces automatic local-file selection; it does not layer both local files. The same rule holds in Docker, where the image already sets `PRINT_BUDDY_CONFIG=/app/config/docker.yaml`: pointing it at a mounted file selects that file *instead of* `docker.yaml`, not on top of it, so start the mounted file as a copy of `config/docker.yaml` and edit the copy. For a single scalar, or for `delivery.methods`, an environment override needs no mounted file at all.

The optional [Web UI](WEBUI.md) is an editor for this same selected settings file, not another configuration layer: it shows the effective value and source layer for each catalogued setting, and a confirmed save writes only that file after validation.

Settings are merged key by key in this order: vendor profile defaults, printer model defaults, home configuration, selected local configuration, then environment overrides (`PRINT_BUDDY__SECTION__KEY` or supported legacy environment names). Environment values are scalars, with one exception: `PRINT_BUDDY__DELIVERY__METHODS` takes a comma- or space-separated list (`discord,bambu_handoff,printer`) that becomes `delivery.methods` and is validated exactly like the YAML list; an empty value keeps the file value. Every other list or table stays file-only. Existing explicit runtime arguments and persisted job state continue to take precedence at their call sites. Settings are loaded once per process, so restart the relevant process after changing configuration. YAML does not support secrets: keep credentials in existing environment or secret files. Runtime state remains in the existing state files, never YAML.

The checked-in `config/home.yaml`, the [All settings table](PROJECT-REFERENCE.md#all-settings), and the selected printer model's defaults form the supported settings inventory; [SETTINGS.md](SETTINGS.md) lists every key with its environment variable. Model IDs are `<vendor>.<printer>`: `flashforge.ad5x`, `sovol.sv06`, `klipper.generic`, `octoprint.marlin` and `bambulab.a1`, `bambulab.p1s` (slicing is offline; `services.moonraker_url` and `services.octoprint_url` must stay empty; optional read-only LAN status uses `[bambu] lan_host`/`lan_serial` plus the access-code secret, see [Bambu Lab printers](BAMBU-LAB.md)); `printer.vendor` plus the printer part (`vendor: sovol`, `model: sv06`) is also accepted. `printer.slicer` and `delivery.methods` must be options the vendor profile offers (Bambu Studio is the default for every Bambu Lab printer, OrcaSlicer for every other vendor); see [Printer profiles](PRINTER-PROFILES.md). Optional `printer.nozzle_type` values are limited to the selected model's supported set: `brass`, `hardened_steel`, `stainless_steel`, `ruby`, `tungsten_carbide` or `diamond`. `nozzle_temp_offsets` accepts those known names with values from −10 to +15 °C. `visual_watch.sensitivity` is an integer from 1 to 5; `visual_watch.enabled` is a YAML boolean and defaults to `true` in `home.yaml`, preserving the behavior of existing TOML configurations, which had no toggle and always ran camera checks.

Defaults are documented representative targets, not universal material guarantees. The selected Spoolman filament's explicit temperatures take precedence; missing targets use the matching profile below. Unknown materials fail closed. Local overrides may replace nozzle and bed values for a recognized profile.

```yaml
material_temps:
  PLA: {nozzle: 210, bed: 60}
  PETG: {nozzle: 240, bed: 85}
  ABS: {nozzle: 245, bed: 100}
  ASA: {nozzle: 260, bed: 105}
  TPU: {nozzle: 230, bed: 50}
  PA: {nozzle: 260, bed: 90}
  PC: {nozzle: 275, bed: 110}
```

The targets use representative points within the documented manufacturer/profile ranges: PLA 185–235/50–60 °C, PETG 215–270/70–90 °C, ABS 230–255/95–110 °C, ASA 220–275/90–110 °C, TPU 220–260/40–85 °C, PA 240–285/70–115 °C, and PC 270–275/100–115 °C. Brand, formulation, printer capability, and enclosure affect the correct settings. Every resolved nozzle target still passes the active nozzle type's safety limit, and the existing printer start/slice validation remains authoritative.

`logging.level` is `DEBUG`, `INFO`, `WARNING` or `ERROR` (case does not matter) and `logging.format` is `text` or `json`; anything else stops startup with a message naming the key. `logging.file` is empty by default; a path adds a rotating log file (5 MiB, 3 backups) next to the standard error output that systemd and Docker already capture. Logs name the component, the intake id while an intake runs, and how long each slicer run took. Discord and bearer tokens, `token=`/`password=` style values, URL credentials and the values of `*_TOKEN`, `*_KEY`, `*_SECRET` and `*_PASSWORD` environment variables are replaced with `***` in the message and the traceback. The Hermes gateway plugin does not configure logging; the standalone bot and the printer listener do.

Example:

```yaml
printer:
  model: flashforge.ad5x
visual_watch:
  enabled: true
  sensitivity: 3
logging:
  level: DEBUG
  format: json
  file: /var/log/print-buddy/print-buddy.log
```

During migration, convert a TOML document by preserving its section names and keys as YAML mappings, then set `PRINT_BUDDY_CONFIG` to that YAML file or use `config/local.yaml`. Compare the effective values before removing the old TOML file. Do not copy secrets into either file.