BESS Guardian: battery health and thermal alarms

How it works

This Coreflux LoT template reads battery management system data over Modbus TCP, lands it under raw/bess/<container>/..., and maps it into one clean record per container at plant/bess/<container>/telemetry. It adds cell temperature spread and a charging, discharging or idle state, then raises latched alarms when a container runs too hot on one side or leaves its safe state of charge band. It runs on the free Community licence.

Key features

• The MODBUS_TCP route marks every tag non-writable, so nothing writes back to the battery.
• The `BessTelemetry Model turns SoC, min and max cell temperature, current and power into one JSON record per container.
• BessDerive publishes derived/temp_spread, derived/state and derived/record.
• Thermal spread raises above 8 °C and clears below 5 °C. SoC alarms raise outside 10 to 95 % and clear at 15 and 90 %.
• An optional POSTGRESQL route stores every derived record in TimescaleDB, with Grafana in the included compose file.
• The core path uses 8 of the 24 LoT artifacts and 2 of the 3 routes the Community licence allows.

Prerequisites