fac31b4d3d
The daemon treats SIGTERM as system shutdown and clears PI_RUNNING, making the UPS cut power seconds after the addon stops. Trap the stop signal and SIGKILL the daemon instead so the UPS is never notified. When the daemon exits on its own because the UPS commanded a shutdown (button, low battery, auto shutdown), its init-0 trigger is useless in a container, so run.sh now performs a clean host shutdown through the Supervisor (requires hassio admin role). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
hassio-addon-lifepo4wered
Home Assistant OS addon for the LiFePO4wered/Pi+
UPS: runs lifepo4wered-daemon and publishes UPS stats to MQTT with Home
Assistant autodiscovery.
MQTT monitor
lifepo4wered_monitor.py polls lifepo4wered-cli get (default every 30 s)
and publishes all registers as one JSON payload to lifepo4wered/state.
Entities appear automatically under one device, "LiFePO4wered/Pi+":
- Sensors: input/battery/output voltage (V), output current (A)
- Binary sensor "External power": ON when
VIN >= VIN_THRESHOLD(i.e. OFF means running on battery) - Diagnostics: thresholds, timers, watchdog and state registers
- Availability:
lifepo4wered/availabilitywith MQTT Last Will, so entities go unavailable if the addon stops
MQTT connection details are taken automatically from the Supervisor when the
Mosquitto addon is installed. Addon options: poll_interval (seconds) and
optional mqtt_host/mqtt_port/mqtt_user/mqtt_password overrides.
Testing off the Pi
python3 -m unittest discover -s tests # unit tests, no deps needed
LIFEPO4WERED_FAKE=1 MQTT_HOST=... python3 hassio-addon-lifepo4wered/lifepo4wered_monitor.py
LIFEPO4WERED_FAKE=1 replaces the CLI with embedded sample data.
Stopping the addon vs. shutting down
Stopping the addon does not power off the Pi: the daemon is killed
without notifying the UPS, so power stays on (run.sh traps the stop
signal — the daemon would otherwise report "system shutting down" and the
UPS would cut power seconds later). While the addon is stopped, UPS-side
features (button shutdown, low-battery clean shutdown, boot watchdog
handshake) are inactive until it starts again.
When the UPS itself commands a shutdown (button press, low battery,
AUTO_SHDN_TIME after power loss), the addon performs a clean host
shutdown through the Supervisor, and the UPS cuts power once shutdown
completes.
Setup notes
https://www.linkedin.com/pulse/creating-your-first-home-assistant-add-on-issac-goldstand
https://lifepo4wered.com/files/LiFePO4wered-Pi+-Product-Brief.pdf
https://github.com/xorbit/LiFePO4wered-Pi/blob/master/Dockerfile
Uncomment line
dtparam=i2c_arm=on
in /mnt/boot/config.txt or /boot/config.txt or /boot/usercfg.txt
Load module at host startup
echo 'i2c-dev' > /etc/modules-load.d/i2c.conf