Raspberry Pi 4 devices on balena no longer reboot in a loop

If your Raspberry Pi 4 gets Anthias from the official balena fleet and kept restarting after 2026.05.2 came out, it's fixed and you don't need to do anything. Every Pi 4 on that fleet was caught in the loop and couldn't take the release.

The fleet is screenly_ose/anthias-pi4. Its setting was corrected by hand as soon as it was found, which stopped the loop before this release, and Anthias 2026.06.0 puts the same fix into the release itself, so the next release doesn't bring the loop back.

The fleet's boot settings come from balena-host-config.json in the repository, which the release workflow started applying in 2026.05.2. For the Pi 4 it set dtparam to i2c_arm=on,spi=on,audio=on, and balena never settled on that comma-joined value, so the device kept rewriting its boot configuration and rebooting. Anthias 2026.06.0 sets it to audio=on, the same line the Anthias installer writes on Raspberry Pi OS. Onboard audio keeps working. The fleet configuration no longer turns on the I2C and SPI buses. Anthias doesn't use them, and the installer on Raspberry Pi OS never turned them on.

If you run your own Pi 4 fleet and set BALENA_HOST_CONFIG_dtparam, give it a single value.