Technical article · Energy management

Home Assistant as an energy manager

The hardware question is asked first almost every time, and it is almost always the wrong one. What the system can do later is decided by the installation type – and by whether the storage survives the write load that energy metering produces.

First decision
Operating-system installation or container
Storage
SSD rather than memory card – measurements are write load
Connectivity
network before Modbus RTU before radio
Backup
off the device, and restored once for real
Status
October 2026 · primary sources below, with the date checked
Author
Julian Haag, state-certified electrical engineering technician

The decision that drives all the others

Home Assistant runs on almost anything. The question is therefore not whether a given piece of hardware is enough, but which installation type it allows – and that determines what the system can do later.

The documentation distinguishes two routes. The Home Assistant Operating System brings everything with it: apps (add-ons), one-click updates, built-in backups. It is explicitly the recommended type. The container requires your own system with Docker, has no apps, and wants updating by hand.

For energy management this is not a matter of taste. Precisely the tools needed here – an MQTT broker, a time-series database, an optimiser – are distributed as apps. Choosing the container means assembling them yourself. That works, but it is a deliberate choice for more work, not a detail.

Installation type and connection Top: two installation types. Home Assistant Operating System: apps, one-click updates, built-in backups; the recommended type. Container: your own system with Docker, no apps, updates by hand. Below: MQTT broker, time-series database and optimiser are distributed as apps. Bottom: connection, most reliable first: network with Modbus TCP or MQTT, then Modbus RTU over RS-485, then radio, for sensors only. Operating System (HA OS) apps (add-ons) one-click update built-in backups Container own system with Docker no apps manual updates recommended MQTT broker, time-series DB, optimiser come as apps; container: build yourself Connection, most reliable first Network Modbus TCP, MQTT RS-485 Modbus RTU, termination Radio Zigbee etc., sensors only
The first decision from the section above and the order of connection routes from the section on extension. A switching command to the heat pump does not belong on a radio link.

Hardware classes

Storage and backup

Energy management produces more data than anything else in the house: every meter, every transformer, every battery reports values, continuously. Two things follow.

First, the storage medium is a wear part. An SSD tolerates the write load; an SD card does not. Second, the retention period should be set before the database is large. Home Assistant keeps raw states for ten days by default; hourly values of sensors with a state class are kept indefinitely, with no extra software at all. Wanting to keep raw states longer means choosing a growing database. What belongs where, and when a separate time-series database pays off, is covered in the article Long-term data in Home Assistant.

And backups: built into the recommended installation type, but only useful if they live off the device and if a restore has actually been tried once. A backup sitting next to the original on the same SSD is self-reassurance.

Getting devices in

Three routes matter for energy management, and they differ more in reliability than in cost.

USB versus LAN: USB radio sticks sit at the computer and are therefore tied to its location – usually the worst spot for radio, right next to the power supply and the SSD. A network coordinator can go where reception is good and survives moving the computer. Given the choice, take the network.

What you do not need

What is needed first instead is measurement – without it the system controls blind. How to build it in the distribution board is covered in energy metering in the distribution board.

Sources

Statements about installation types and data retention come from the official documentation. Hardware recommendations are experience, not manufacturer claims – check the datasheets of the device classes named before buying.

Hardware and software change faster than this text. What counts is the project's current documentation.

Links marked with an asterisk are affiliate links. As an Amazon Associate I earn from qualifying purchases; the price is unchanged for you. What I recommend does not depend on it.

Want to set up energy management without getting lost in hardware questions – and measure properly from the start? I can set it up for you – the first conversation is free.