Repository navigation
Battery Neovolt
Battery connections · Connection methods and sensors · Configuration index
Choose the battery during initial setup. Later, use Settings > Devices & Services > PowerSync > Configure > Battery connection method & sensors to choose its telemetry/control route. Edit connection details under Configure > Neovolt connection.
| Connection method | What this route provides |
|---|---|
| Neovolt integration | Uses the selected companion integration. Required control entities must be present and writable; telemetry alone is insufficient. |
Select one route for PowerSync. A second integration using the same device connection can cause conflicts; the companion-integration route is appropriate when that integration should own communications. See source discovery and switching.
Full support for Neovolt / Bytewatt battery systems via the upstream Neovolt Modbus Home Assistant integration. PowerSync does not open a second Modbus session; it discovers the entities created by the Neovolt integration and sends commands through Home Assistant services.
- The Neovolt Modbus integration installed and working in Home Assistant.
- The upstream integration must expose the required telemetry sensors and dispatch controls before PowerSync setup.
- For independent inverter/battery stacks without a parallel kit or shared BMS coordination, configure each Neovolt inverter in the upstream integration as Host. Follower/read-only entries can provide telemetry, but PowerSync cannot coordinate both stacks unless the dispatch controls exist for each stack.
Parallel kit note: If your Neovolt batteries have a proper parallel/BMS coordination kit, let the Neovolt system coordinate the batteries natively. The guidance below is for sites with separate stacks that otherwise charge/discharge against each other.
PowerSync auto-discovers common Neovolt entity names from the selected Neovolt config entry.
| Purpose | Typical Entity Suffix |
|---|---|
| Battery power |
combined_battery_power or battery_power
|
| Battery SOC |
combined_battery_soc or battery_soc
|
| Grid power |
grid_total_active_power or grid_power_total
|
| Home load |
combined_house_load or total_house_load
|
| Solar power |
combined_pv_power, pv_total_active_power, or pv_power_total
|
| Dispatch mode |
dispatch_mode select |
| Dispatch power |
dispatch_power number |
| Dispatch duration |
dispatch_duration number |
| Charge target SOC |
dispatch_charge_target_soc or dispatch_charge_soc number |
| Discharge cutoff SOC |
dispatch_discharge_cutoff_soc or dispatch_discharge_soc number |
Optional entities include battery capacity, battery SOH, default discharging cutoff SOC, and a stop-dispatch button.
- Smart Optimization — PowerSync's built-in LP optimizer runs charge/discharge scheduling using Neovolt telemetry and dispatch controls.
- Force Charge / Discharge — Uses Neovolt dispatch mode, power, duration, and target/cutoff SOC entities. On independent multi-host stacks, force-charge commands prioritise the lower-SOC stack before charging higher-SOC stacks.
- Restore Normal — Returns dispatch mode to Normal, or presses the stop-dispatch button if available.
- Backup Reserve — Writes the default discharging cutoff SOC when the upstream entity exists.
- Independent Stack Surplus Balancing — On multi-host Neovolt systems without BMS coordination, PowerSync can temporarily force-charge an idle spare stack from measured solar export headroom, while keeping lower-SOC stacks ahead in the charge priority.
- AEMO Spike Export — Supported through the generic spike manager for Australian dynamic or VPP setups.
- Live Telemetry — Solar, grid, battery, load, SOC, battery capacity, SOH, and BMS max charge/discharge power where available.
-
Balancer Diagnostics —
sensor.power_sync_neovolt_surplus_balancershows whether the coordinator is charging, waiting, balancing the low stack, blocked by battery discharge, or disabled. - Auto-Sync Tariff Prices — Refreshes provider tariffs and updates PowerSync's tariff schedule sensor, dashboard, and optimizer inputs. Neovolt is Modbus-only, so PowerSync does not upload an onboard TOU schedule to the battery.
- Install and configure the Neovolt Modbus integration in Home Assistant.
- Confirm the required Neovolt entities are present and updating.
- Add the PowerSync integration and select Neovolt / Bytewatt as your battery system.
- Select the Neovolt config entry if you have more than one.
- Enter maximum charge power, maximum discharge power, and minimum SOC. These are used for dispatch defaults and optimizer modelling.
- For independent stacks without a parallel/BMS kit, leave Independent stack surplus balancing on Auto or set it to Enabled. If your batteries already have hardware BMS coordination, set it to Disabled.
- Set the SOC balance tolerance. The default is 5%, which means PowerSync prioritises the lower-SOC stack while another stack is more than 5% ahead.
Some Neovolt installations have two inverter/battery stacks that cannot talk to each other through a parallel kit. In that layout, leaving both stacks in Normal can make one battery discharge while the other charges, slowly wasting energy through conversion losses.
PowerSync handles this with a coordinator rather than true PV splitting:
- PV splitting is not possible through the Neovolt Modbus entities. PowerSync cannot tell 6 kW of DC solar to become 3 kW on each inverter.
- Keep the non-active stack in No Battery Charge or Idle (No Dispatch) when you need to prevent the batteries fighting each other.
- Optimizer and manual force-charge windows are SOC-aware. If one stack is 30% and another is 60%, PowerSync force-charges the lower-SOC stack at its configured maximum charge rate and parks the higher-SOC stack until the gap is inside the configured tolerance.
- When measured grid export is high enough, PowerSync can rotate surplus into a parked stack by starting a short force-charge burst on that stack.
- The surplus balancer follows the same SOC priority, so export headroom is only used where it will not worsen the stack imbalance.
- The balancer only starts when there is export headroom above the safety threshold, the target stack is below its charge target, and charging that stack will not worsen the SOC imbalance.
- If the site begins importing, export disappears, or another stack starts discharging, PowerSync stops the surplus charge and restores the target stack's previous dispatch mode and settings.
- This prevents battery-to-battery charging while still letting otherwise-exported solar top up the spare stack.
Expected behavior while the stacks are imbalanced:
- The lower-SOC stack shows
Force Charge, with dispatch power set up to that stack's configured charge limit. - The higher-SOC stack shows
No Battery ChargeorIdle (No Dispatch). -
sensor.power_sync_neovolt_surplus_balancershowsbalancing_low_stack, withlowest_soc_index,highest_soc_index, per-stack SOC, per-stack battery power, and dispatch modes in the attributes.
This is not a replacement for a Neovolt parallel kit. It is a software workaround for independent Host-mode stacks where the hardware cannot share BMS state.
Use sensor.power_sync_neovolt_surplus_balancer to see the coordinator's current decision. Useful states include:
| State | Meaning |
|---|---|
charging |
PowerSync is using export headroom to force-charge a parked stack |
balancing_low_stack |
A lower-SOC stack needs priority, so PowerSync is parking or avoiding charge on the higher-SOC stack |
waiting_for_export |
The target is eligible, but there is not enough export headroom |
blocked_source_discharging |
Another stack is discharging, so surplus charging is blocked |
stopped_importing |
The site began importing, so the temporary charge was stopped and restored |
disabled |
The feature is turned off in the Neovolt connection settings |
The sensor attributes include the active stack index, target stack index, per-stack SOC, per-stack battery power, per-stack grid power, dispatch modes, SOC delta, and configured tolerance.
- PowerSync depends on the upstream Neovolt integration's entity names and service behavior.
- If required dispatch entities are missing, setup aborts with a missing-entities error.
- If one stack's Neovolt entities are
unavailable,unknown, or stale, PowerSync cannot safely command that stack. Recover the upstream Neovolt/Modbus session first, then reload PowerSync if needed. - Auto-Sync does not program a tariff schedule into Neovolt hardware. Battery actions are sent live through the dispatch mode, power, duration, and SOC entities.
- DC solar curtailment is not a separate Neovolt path; use Smart Optimization or AC inverter curtailment if your site needs export control.
- PowerSync cannot split PV generation between Neovolt inverters. Independent-stack balancing uses AC-side surplus/export measurements only.
After saving connection changes, allow the integration reload to complete. Check fresh battery SOC, grid/solar/battery power and home-load readings for the selected site. Compare signs and totals with the vendor/upstream readings. Planning sensors can update on a monitoring route; that does not establish dispatch capability. Verify any permitted control separately using readback and measured power.
The tables use the current form labels and help text. They list the conditional field union: a field can be hidden for a different battery, provider, route or available integration. The instructions above explain those conditions. Existing saved/discovered values take precedence over fresh fallbacks. Rate units follow the provider; check the displayed currency/energy unit.
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| Maximum charge power | Maximum charge power in kW. Used by the LP optimizer and dispatch command limits. | Fallback 5.0; 0.5–50 kW; step 0.1 |
| Maximum discharge power | Maximum discharge power in kW. Used by the LP optimizer and dispatch command limits. | Fallback 5.0; 0.5–50 kW; step 0.1 |
| Stack battery capacities | Optional comma-separated usable battery capacities in kWh. With multiple Neovolt integrations, values follow the selected integration order. With one integration, multiple values are summed. Example: 20.1, 30.2. Leave blank to use Neovolt's capacity sensors. | Fallback blank (see retention/clear rules) |
| Independent stack surplus balancing | Controls independent NeoVolt stack balancing. Auto balances multiple selected Neovolt integrations whenever PowerSync is running; the Smart Optimization switch does not control it. Disable this if your batteries already have a parallel/BMS coordinator. | Saved/detected value or the form’s shown fallback |
| SOC balance tolerance | PowerSync will not force-charge a higher-SOC parked stack while another stack is behind by more than this percentage. | Fallback 5.0; 1–30 %; step 1 |
| Neovolt integrations | Select every Neovolt inverter entry PowerSync should read and control. | Saved/detected value or the form’s shown fallback |
| Field | Meaning / input | Fallback / limits |
|---|---|---|
| Neovolt integrations | Select every Neovolt inverter entry PowerSync should read and control. | Saved/detected value or the form’s shown fallback |
| Maximum charge power | Maximum charge power in kW. Used by the LP optimizer and dispatch command limits. | 0.5–50 kW; step 0.1 |
| Maximum discharge power | Maximum discharge power in kW. Used by the LP optimizer and dispatch command limits. | 0.5–50 kW; step 0.1 |
| Stack battery capacities | Optional comma-separated usable battery capacities in kWh. With multiple Neovolt integrations, values follow the selected integration order. With one integration, multiple values are summed. Example: 20.1, 30.2. Leave blank to use Neovolt's capacity sensors. | Saved/detected value or the form’s shown fallback |
| Independent stack surplus balancing | Controls independent NeoVolt stack balancing. Auto balances multiple selected Neovolt integrations whenever PowerSync is running; the Smart Optimization switch does not control it. Disable this if your batteries already have a parallel/BMS coordinator. | Saved/detected value or the form’s shown fallback |
| SOC balance tolerance | PowerSync will not force-charge a higher-SOC parked stack while another stack is behind by more than this percentage. | 1–30 %; step 1 |