furtka-apps/apps/zigbee2mqtt/.env.example at 3408e1aad840bce5c1612631a77f757b03d79c4b - daniel/furtka-apps - Forgejo: Beyond coding. We Forge.

daniel/furtka-apps

Daniel Maksymilian Syrnicki 3408e1aad8

CI / validate (pull_request) Successful in 6s

Details

CI / shellcheck (pull_request) Successful in 13s

Details

feat: add mosquitto + zigbee2mqtt dependency pair

First catalog apps to exercise core 26.17's app-to-app dependency
feature — until now every app was standalone.

- mosquitto: MQTT broker, first dependency *provider*. Mandatory auth;
  per-consumer accounts created by on_install/on_start hooks
  (scripts/provision-client.sh, scripts/ensure-client.sh) that run inside
  the broker container via `docker compose exec`. Provider-side password
  stash so on_start can restore an account after a volume wipe.
- zigbee2mqtt: first dependency *consumer*. `requires` mosquitto; MQTT
  creds wired in from the provisioning hook via ZIGBEE2MQTT_CONFIG_* env.
  Serial coordinator path as a text setting + devices mapping.

Supporting changes:
- Bump vendored furtka_manifest.py (26.10-era -> 26.17) so the validator
  actually validates the `requires` schema instead of ignoring it.
- Document `requires`/hooks in apps/README.md (was undocumented), including
  the three framework gaps building this pair surfaced.
- CI now shellchecks app hook scripts (apps/*/scripts/*.sh), not just
  repo-root scripts/.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-05-28 23:45:27 +02:00

9 lines

352 B

Text

Raw Blame History

 # MQTT_* are filled in automatically at install time by mosquitto's
 # provision-client.sh hook (the app requires mosquitto). Leave them blank.
 MQTT_SERVER=
 MQTT_USER=
 MQTT_PASS=
 # Path to your Zigbee USB coordinator. Asked for in the install form;
 # default shown there. Change to match your stick (e.g. /dev/ttyUSB0).
 ZIGBEE_SERIAL_PORT=/dev/ttyACM0