Indevolt SolidFlex / PowerFlex¶
Omnibattery controls an Indevolt battery through the battery's local HTTP API. No cloud connection is required.
Do I need it?¶
Use it if you own an Indevolt SolidFlex or PowerFlex battery and Home Assistant can reach it on your local network. The SolidFlex 2000, the SolidFlex 3000 AC and the PowerFlex 2000 have been tested. The PowerFlex 3000, the SolidFlex and PowerFlex 1200 and the SolidFlex 3600 use the same API; please report your model and firmware if you use one of them. Batteries with solar panels on their own solar inputs have not been tested yet, so please report how that goes too. The BK1600 uses an older API and is not supported. The battery reports its model family, not the exact product, so Home Assistant shows for example SolidFlex/PowerFlex 3000 for a SolidFlex 3000 AC. Control works the same for all of them.
Use Omnibattery instead of the official Indevolt integration. Both poll the same battery, and the battery answers requests one at a time. Omnibattery shows the same measurements, including the AC energy counters for the Energy dashboard, so disable or remove the official integration for a battery that Omnibattery controls (see Moving from the official Indevolt integration).
Before you start¶
- In the Indevolt app, enable the local API with the HTTP protocol (not HTTP Digest), and give the battery a stable IP address. Omnibattery does not use Modbus TCP, so you can leave it off. In tests, the battery answered Modbus requests much more slowly than HTTP requests, and the Modbus connection was less stable and needed frequent reconnects.
- In the Indevolt app, set the working mode to Realtime (standby). Omnibattery controls the battery only in Realtime mode and never switches the mode itself (see why).
- The battery's reserve (backup SOC), max AC input and max AC output are the same settings as Omnibattery's minimum SOC, max charge power and max discharge power. Omnibattery keeps them in sync, so you can change them in either place.
- Disable the official Indevolt integration for this battery.
- If your solar panels are not connected to the battery's own solar inputs and you use a solar forecast, also set the Solar production sensor (see sensor setup). Omnibattery then compares the forecast with what your panels really produce.
How to add it¶
- In the Omnibattery setup flow, choose Indevolt SolidFlex / PowerFlex.
- Enter a descriptive Name and the battery's IP address.
- Keep HTTP port at
8080and pick a Request speed; Conservative (5s) is the default (see Choosing the request speed). - Omnibattery reads the battery's identity, working mode and power limits. It does not change anything on the battery.
- If the battery is not in Realtime mode, a notice says so. Setup continues; control starts once you select Realtime in the app.
- Choose the common power and state-of-charge limits. The form opens at the battery's own reserve and power settings, and the power sliders go up to the battery's hardware maximum. The first time Omnibattery starts, it takes over the battery's settings without writing anything, so change them afterwards, on the device page or in the Indevolt app. For MAC tracking, the MAC address is filled in from the battery.
What you will see¶
- Control starts by itself. As soon as the battery is in Realtime mode, Omnibattery sends a stop command, checks that the battery is idle and then takes over. The same happens after every Home Assistant restart.
- Control Status shows what the driver is doing:
active,starting,realtime_mode_required,handover_failed,telemetry_staleorunknown_model. - Request Interval (Effective), Read Latency (P95), Write Latency (P95) and Request Failures (diagnostic) show how the battery keeps up. Request Speed (diagnostic) shows the speed you chose. The interval normally matches it and grows when Omnibattery gives a slow battery more time; each latency is the slowest 5% (P95, so 95% of answers are faster) of the last 200 reads or writes, and shows how quickly the battery answers Omnibattery's requests, not how quickly it changes its power, which takes a few seconds (reads usually take tens of milliseconds, writes a few hundred); failures count timeouts and errors since Home Assistant started. Flash Writes (diagnostic) counts Omnibattery's writes of the reserve and power limits to the battery's flash memory (see Why Omnibattery writes settings only when you change them).
- Switching modes in the app is safe. If you select another working mode, Omnibattery pauses, shows a notification and leaves the battery alone. Switch back to Realtime and it resumes automatically.
- Response time. Omnibattery reads the battery once per interval of the request speed (5s by default, 2s at Maximum). A new setpoint goes out at least one interval after the previous setpoint and 2s after the previous request of any kind (1s at Normal and Fast; at Maximum 0.2s after the previous reply, at most one setpoint per second), and the battery follows within seconds.
- Near full. In the last part of a charge the battery lowers its charge power by itself, down to a few hundred watts, while it tops up its cells. Omnibattery then charges it with what it takes, plus at most 100W, instead of the full power, so the battery charges on to 100% rather than being reported as not delivering. PD Control Quality shows the battery as the limit meanwhile, and the extra solar goes to your other batteries or to the grid.
- Settings: Discharging Cutoff Capacity (the battery's reserve, which is Omnibattery's minimum SOC), Max Charge Power and Max Discharge Power. A change here is written to the battery; a change in the Indevolt app shows up here within a few minutes. The power sliders go up to the battery's hardware maximum. Charging Cutoff Capacity (maximum SOC) has no battery setting and is applied by Omnibattery only.
- Sensors: state of charge, battery power, AC power, working mode and firmware version, plus:
- AC Input Power and AC Output Power at the battery's AC connection (read every 10s), and Bypass Power through the bypass socket.
- Energy counters on two sides. Total AC Input Energy and Total AC Output Energy count at the AC connection: use these for the battery in the Energy dashboard. Total Charging Energy, Total Discharging Energy and the daily counters count on the battery side, after conversion losses. Off-Grid Output Energy and Bypass Input Energy count what went through the backup and bypass sockets.
- For a battery with solar panels connected: Solar Output Power, Daily Solar Energy and Total Solar Energy. Power, voltage and current per PV input are available but disabled by default.
- Temperatures: Inverter Battery Temperature for the battery built into the inverter unit, and Expansion Battery N Temperature for each expansion battery that is present; Internal Temperature, which Omnibattery's optional temperature charge limit uses to reduce charging when the battery is hot, is the warmest of those. A transformer temperature sensor is available but disabled by default.
- Diagnostics: Realtime Command shows what the battery's Realtime mode is doing (standby, charging or discharging). Operating Status shows what the battery itself is doing, for example deep sleep while idle, low-battery charging when it recharges itself to its reserve, or a scheduled full charge. Forced Full Charge Interval and Forced Full Charge Time show the battery's own periodic full charge (0 days is off); change it in the Indevolt app. Feed-in Limit and Grid Charging show those battery settings; change them in the Indevolt app. MAC Address shows the MAC address the battery reports; the panel also shows it under Device information. Right after a start from standby, Inverter State shows unknown until the battery has had time to start (up to 30s). Disabled by default: grid voltage and frequency, remaining charging and discharging time, device mode (standalone or cluster), the highest and lowest cell voltage of all batteries, and for each battery that is present (the one in the inverter unit and each expansion battery) its SOC, charge cycles, MOS temperature, voltage, current and serial number. Omnibattery reads those battery details only for the batteries that are present.
- Indevolt Meter Power (disabled by default) is the grid power reported by the meter that is paired with the battery in the Indevolt app. It lags your grid meter by 10–20s, so do not use it as Omnibattery's grid sensor.
Moving from the official Indevolt integration¶
Omnibattery shows the measurements of the official Indevolt integration under its own names, read in the requests it already makes. Point your dashboards, helpers and the Energy dashboard at the Omnibattery sensors, then remove the official integration.
| Official integration | Omnibattery | Note |
|---|---|---|
| Battery SOC | Battery SOC | |
| Battery power | Battery Power | Opposite sign: positive while charging |
| AC input power, AC output power | AC Input Power, AC Output Power | |
| AC Power | Output minus input: positive while discharging, as the Energy dashboard expects for battery power | |
| Bypass power | Bypass Power | |
| Total AC input energy, Total AC output energy | Total AC Input Energy, Total AC Output Energy | The Energy dashboard's energy going in to and coming out of the battery |
| Battery daily and total charging and discharging energy | Total Daily Charging Energy, Total Daily Discharging Energy, Total Charging Energy, Total Discharging Energy | |
| Off-grid output energy, Bypass input energy | Off-Grid Output Energy, Bypass Input Energy | Bypass input energy in kWh instead of Wh |
| DC output power, Daily production, Cumulative production | Solar Output Power, Daily Solar Energy, Total Solar Energy | Total solar energy in kWh instead of Wh |
| Meter power, Meter connected | Indevolt Meter Power, Indevolt Meter Connected | Disabled by default |
| Battery charge/discharge state | Inverter State | Standby, Charge or Discharge |
| Energy mode | Working Mode | Read only |
| Real-time mode, Real-time target SOC, Real-time power limit | Realtime Command, Realtime Target SOC, Realtime Command Power | |
| Rated capacity | Battery Total Energy | |
| Discharge limit, Max AC output power, Inverter input limit | Discharging Cutoff Capacity, Max Discharge Power, Max Charge Power | Settings, kept in sync with the battery |
| Feed-in power limit, Allow grid charging | Feed-in Limit, Grid Charging | Read only |
| Grid voltage and frequency, remaining charging and discharging time, device mode, PV input power, voltage and current, and per battery SOC, cycles, temperatures, voltage, current and serial number | Same names | Disabled by default, as in the official integration |
Omnibattery does not change the working mode, the LED indicator, the bypass socket, grid charging or the feed-in limit from Home Assistant: each is a permanent setting in the battery, so change it in the Indevolt app (see why). The official integration's stop button and charge and discharge actions would compete with Omnibattery's control; use Omnibattery's manual mode instead. The official integration's Equivalent full cycles shows the battery's full-charge interval in days, not a cycle count: Omnibattery shows it as Forced Full Charge Interval, and the per-battery Cycles sensors are the battery's own cycle counts.
Choosing the request speed¶
The Request speed sets how often Omnibattery talks to the battery. You choose it per battery when you add it, and change it later with Reconfigure on Omnibattery in Settings → Devices & services.
| Speed | Interval | When to use it |
|---|---|---|
| Maximum | 1s | Below Indevolt's documented minimum, at your own risk. Only useful with a grid meter that updates every second: a setpoint can go out every second, and a read follows a reply after 0.2s instead of waiting 1s. Reads stay at 2s; at most 1.5 requests per second. Set PD Min Cycle Interval to 0 as well (see the tip below). |
| Fast | 2s | A strong, stable connection, and you want the quickest reaction. It sends 50% more requests than Normal. |
| Normal | 3s | A grid meter that updates every 3s: quicker reactions than Conservative at a modest extra load. |
| Conservative (default) | 5s | Recommended by Indevolt, and enough for a grid meter that updates every 5s, the usual rate in Home Assistant. Also the choice on weak Wi-Fi, when other apps also poll the battery, or when Omnibattery reports the battery as slow. |
Everything faster than Indevolt's 5s is at your own risk, and you are responsible for checking that your battery, Home Assistant and network can keep up. On the battery's device page, Request Interval (Effective) should keep matching your choice, and Read Latency (P95) and Write Latency (P95) should stay well below 1s (reads usually take tens of milliseconds, writes a few hundred). If the interval keeps rising above your choice or a slow-battery notification appears, choose a slower speed. Feel free to try a faster speed: when the battery answers slowly or not at all, Omnibattery's Indevolt driver automatically steps back to a calmer pace until the response time has recovered.
A faster speed gets each new setpoint to the battery sooner, so it reacts sooner to meter changes, which can improve net zero. It does not make the battery's own ramp faster, and the battery refreshes its AC power only about every 6s. A speed faster than your grid meter gains nothing: with a meter that updates every 2s, choose Fast rather than Maximum. Apart from Maximum, Omnibattery never sends two requests closer than 1s apart, Indevolt's documented minimum (2s at Conservative). At Maximum it waits 0.2s after each reply instead, still with one request at a time, and steps back to Fast with the 1s spacing when the battery answers slowly. Whatever you choose, it slows down by itself when the battery answers slowly or not at all.
Only Indevolt batteries? Set PD Min Cycle Interval to 0
Omnibattery's PD Min Cycle Interval (default 1.0s) skips a meter update that arrives too soon after the previous control run, so a fast meter cannot flood a slow Modbus bridge, such as an Elfin EW11, with commands. The Indevolt driver already paces its own requests and only ever sends the newest setpoint, so for an Indevolt the interval protects nothing. It only adds delay: a skipped update waits for the next meter update or the 2s safety timer, so with a 1s meter it is acted on up to 1s later.
If every battery in Omnibattery is an Indevolt, set it to 0: open the Omnibattery sidebar panel, select Control, and in PD controller (advanced) set Min cycle interval to 0. It takes effect at once. The battery gets no extra requests, because the request speed still sets the pace. Keep the default if Omnibattery also controls a battery behind a slow Modbus bridge. The other PD settings are explained in Follow home consumption.
Why Omnibattery writes settings only when you change them¶
Realtime commands in working memory, settings only on request
A battery keeps two kinds of data. Its settings, such as the working mode, the reserve and the power limits, are stored in flash memory, so they survive a power cut. Flash wears out after a limited number of writes. Realtime commands are kept in working memory (RAM), which can be written as often as needed.
What wears flash out is how often it is written. A controller like Omnibattery may send a new command every few seconds; if those commands went to flash, they could wear out the battery's controller long before the end of its normal life. A setting you change a few times a year costs nothing.
We checked this with Indevolt's developers. They confirmed that only the realtime command (charge, discharge or stop, with a power and a target SOC) is kept in working memory, and that every other setting is stored in flash. So:
- Control only ever writes the realtime command, however often it runs.
- The reserve and the two power limits are written only when you change them, in Omnibattery's settings or on the device page. Omnibattery waits 3s for you to finish and skips the write when the battery already has the value. Nothing is written at startup.
- A safety net catches an automation or a bug that keeps writing them without anyone noticing; it is there to protect your battery, not to limit you. After 100 writes in a year (the three settings together), Omnibattery pauses these writes until you turn them back on in Settings → Repairs, which takes one click. Changing settings yourself stays far below that; an automation that changes the reserve every day reaches it after about 100 days. Changes made in the Indevolt app are still picked up. Flash Writes (diagnostic) on the device page counts every write so far.
- The working mode and every other setting are never written. Change them in the Indevolt app.
Safeguards in the code and automated tests enforce this, so a future change cannot add a write by accident.
Omnibattery enforces its own minimum and maximum SOC in software. Each command also carries a target SOC a few percent beyond the current charge in the commanded direction, which Omnibattery moves along as the battery charges or discharges. If Home Assistant stops in the middle of a command, the battery stops by itself within about 5% of state of charge.
If it does not work¶
| Symptom | Likely cause | What to check |
|---|---|---|
| The wizard cannot connect | The local API is off, or the address or port is wrong | Enable the local API in the Indevolt app and check the IP address and port 8080 |
| The wizard says the battery asks for a password | The local API is set to HTTP Digest | Select HTTP for the local API in the Indevolt app |
Control Status is realtime_mode_required |
The battery is in another working mode | Select Realtime (standby) in the Indevolt app; control resumes automatically |
| A notification says the battery is slow, or Request Interval (Effective) stays above the chosen speed | Another client is polling it too, or the Wi-Fi link is weak | Disable the official Indevolt integration for this battery, check the signal, or choose the Conservative (5s) request speed |
| A notification says a setting was not applied | The battery did not accept the value | The battery keeps its value; try again later, or change it in the Indevolt app |
| Repairs says Indevolt setting writes are paused | 100 writes of the reserve and power limits in a year, nearly always from an automation or a script | Check automations and scripts that set these numbers, then turn writing back on in Settings → Repairs (also if the changes were intended) |
Control Status is unknown_model |
The battery reports a model code Omnibattery does not support yet | Open a GitHub issue with the model code from the notification |
Control Status is handover_failed |
The battery did not confirm idle after the stop command | Check the battery in the Indevolt app; Omnibattery retries automatically |
Advanced details
All requests to one battery share a single budget: one request at a time, at least 1s apart (2s at Conservative and while slowed down to 5s or 10s), measured from start to start. Maximum measures from the previous reply instead: at least 0.2s after it, with commands at least 1s apart and reads every 2s. Reads come once per interval of the request speed. A pending command goes before a due read, at least that spacing after the previous request and at least one interval after the previous command. Omnibattery's own polling only reads a cache, so it never adds requests.
When the battery struggles, the interval steps along a fixed ladder: 2s, 3s, 5s, 10s (from Maximum, the first step is Fast with the 1s spacing). Two bad replies within 30s (a timeout, an error, a read slower than 1s or a write slower than 2s) move it one step up, at most one step per 10s; a single bad reply is treated as jitter. After 30s without a bad reply it moves one step back down, never below the speed you chose. 10s is the last step: slower would only make control steer on older data for longer. A single timeout does not pause control.
Telemetry is read in batches: power, AC power, working mode and SOC in every slot, the realtime status about every 30s, limits every few minutes and energy counters every minute. If the battery ever returns an incomplete batch, Omnibattery reads smaller batches until complete replies return.
The delivered AC power is the battery's total AC power minus the power on its bypass port, so a load or microinverter on that port is not counted as battery output.
Indevolt's minimum firmware for the local API is CMS V1406.07.002E for the 2000 family, V1409.08.3034 for the 3000 family and V1407.07.202E for the 1200 family. Omnibattery shows a notification when the battery reports an older version. Indevolt has not published a minimum for the SolidFlex 3600, so Omnibattery doesn't check it.
For shared runtime controls and system limits, see Choose your battery connection.