Files

Martin Bauer 874a81f664 Give each role's reboot handler its own name

pi_standard_setup, pi_hifiberry_amp and pi_disable_onboard_bluetooth each defined a
handler called "Reboot". Handler names are play-global, so a notify ran only the last
one defined - pi_disable_onboard_bluetooth's - and with that role's `when:`. On every
host where onboard Bluetooth stays on, the handler was skipped and nothing that asked
for a reboot ever got one: not a changed dtoverlay, not a hostname change, not the Pi 5
kernel. Seen on musicdolphin, where a new HiFiBerry overlay sat unapplied in
config.txt after a clean run.

Each role now notifies a handler only it defines.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-02 21:21:37 +02:00

defaults

Switch musicdolphin from a Pi 4 to a Pi 5

2026-09-21 12:17:53 +02:00

handlers

Give each role's reboot handler its own name

2026-10-02 21:21:37 +02:00

README.md

pi_hifiberry_amp

Deactivates the Pi's onboard analog audio and activates a HiFiBerry amp/DAC overlay instead.

Key vars: hifiberry_overlay, hifiberry_powers_pi

hifiberry_powers_pi (default false) is for a Pi fed through the HiFiBerry board's GPIO header. On a Pi 5 that sets usb_max_current_enable=1, or USB is capped at 600mA.