Martin Bauer
3d1675528b
Several roles reported "changed" on every playbook run even when
nothing on the target had drifted, making real config drift
indistinguishable from noise:
- 7 systemd tasks across 6 roles used state:restarted, which always
issues a restart and always reports changed. Switched to
state:started plus notify-driven handlers that only restart when
the underlying unit file, script, or config actually changes.
- pi_standard_setup's boot mode, timezone, and locale tasks shelled
out to raspi-config with changed_when:true hardcoded. Boot mode now
checks systemctl get-default first; timezone/locale now use the
natively idempotent community.general.timezone/locale_gen modules.
- The pi account password task computed password_hash('sha512')
without a seed, generating a new random salt (and thus an
apparently different hash) on every run. Added a stable seed so the
hash only changes when the underlying secret does.
Also renamed a mislabeled task in pi_squeezelite_custom and fixed a
typo in pi_standard_setup while those files were already touched.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
bluetooth_monitor
Installs my_btmonitor.py (BLE scanning via bleak) as a systemd service
that watches for nearby devices, publishes state over MQTT, and can restart
the local BLE interface on a watchdog timeout.
Key vars: my_bt_monitor_watchdog_seconds, my_btmonitor_restart_ble_interface,
my_btmonitor_mqtt_username, my_btmonitor_mqtt_password
other/ is not part of the deployed role — it's a separate, standalone
data-analysis project (Jupyter notebook, Dockerfile, collected CSV data) used
to analyze data captured by the monitor.