Battery capacity, power and warranty still matter, but the software layer can change how useful a home battery is day to day. Before buying, check what the app can only show, what it can actually control, where automation decisions are made, what happens if internet, cloud or tariff data is unavailable, and whether third-party access is official, local, cloud-based, read-only or read-write. A “smart tariff compatible” or “API-enabled” label is not enough on its own. The useful buying question is whether the exact model, market and configuration give you the control and fallback behaviour you expect. This guide turns those claims into questions you can verify before choosing the hardware.
In short
Treat the app, automation and control path as part of the product. Verify what you can monitor, what you can change, whether decisions depend on the cloud or a tariff service, what happens when a dependency fails, and whether any API or smart-home integration provides the level of access you actually need.
What should a home battery app actually let you control?
Start by separating visibility from authority. A home battery app may provide monitoring, control or both; seeing battery data does not by itself prove that the app can change charging behaviour. For each feature, ask what the owner can do directly, what requires installer access, and which functions depend on the internet or another service.
Monitoring is not the same as control
A dashboard can be useful without giving you control. It may show battery state, household flows or price data while changes to charging behaviour are handled elsewhere. Ask the seller to demonstrate the exact controls available to the homeowner rather than relying on screenshots of graphs or status pages.
Manual override, schedules and reserve settings
These controls answer different questions. A schedule tells the battery what to do at set times; a manual override lets you intervene now; a reserve setting limits how far the battery is intended to discharge under the relevant mode. Ask what happens when these settings conflict and which rule has priority.
Check the current Sunpura smart-meter options for measuring household energy flows.
How does smart tariff automation actually work?
“Smart tariff” can describe several very different control arrangements. The battery might follow a fixed schedule you set, use price data to change its own charging behaviour, or be controlled by a supplier or optimisation service. Before buying, identify which route applies to the exact product and tariff you plan to use.
Fixed schedules vs dynamic-price optimisation
A fixed schedule can charge during a known off-peak window without needing prices to change throughout the day. Dynamic-price optimisation is different: it needs a price signal and logic that decides when charging or discharging should move. A current GivEnergy tariff guide, for example, treats manual charge windows, smart tariff integrations and dynamic-tariff automation as separate control methods.
Manufacturer-controlled vs supplier-controlled automation
Manufacturer-controlled automation usually means the battery maker’s software decides what the battery should do, using the data available to that system. Supplier-controlled automation means the energy supplier or its service may issue or coordinate charging and discharging instructions. Those arrangements can have different compatibility, account and control-ownership requirements.
Who has control when more than one service is connected?
Do not assume several controllers can safely optimise the same battery at once. At the time of writing, on 22 September 2026, Octopus Energy’s Charge Pack guidance says the service is not stackable with other smart-battery optimisation products. That is a current supplier-specific example, not a universal rule and not evidence that any particular Sunpura model is supported by Octopus.
Ask who is allowed to send commands, what happens if two services request different actions, whether manual override remains available and whether disconnecting one service requires a reset, reauthorisation or installer action.
What happens if your internet or the battery cloud goes down?
There is no universal offline answer. Behaviour varies by system: basic battery operation may continue while remote monitoring, updates or smart services stop. The buying task is to separate each dependency and ask what the exact model does when that dependency is unavailable.
Home broadband failure
Ask the installer or manufacturer to describe the system state after the router or broadband connection fails. The important distinction is between the battery continuing its basic local operation and you still having access to remote monitoring, fresh price data or cloud-based automation.
Manufacturer cloud failure
A working home internet connection does not help if the service the app depends on is unavailable. Ask which functions are executed in the battery or local controller and which are executed or authorised by the manufacturer’s cloud. Also ask whether stored settings remain active and how you regain control when the service returns.
A power cut is a different test
Do not treat “works without internet” and “works during a power cut” as the same claim. Backup behaviour depends on the electrical design and the exact product configuration. Ask what remains powered, through which output or circuits, and under what limits rather than inferring backup capability from an app or connectivity feature.
Local control, cloud control and APIs: what is the difference?
Local and cloud describe where the control path runs; an API describes an interface. They are not three equivalent categories. A battery can have a local API, a cloud API, both or neither, and the existence of an API does not tell you whether it can change settings.
An API can be local or cloud-based
A local control path communicates within the home or local network without routing the command through a remote service. A cloud control path relies on an external service. An API can sit in either place, so “has an API” does not automatically mean the battery can be controlled without the internet.
Read-only vs read-write access
Read-only access can expose status, energy flows or other telemetry without allowing an external system to change battery behaviour. Read-write access may allow commands or setting changes, but the exact actions, limits and permissions still need to be documented for the specific model and software version.
Official vs community integrations
An official integration normally has a defined support owner and documented scope. A community integration may still be useful, but you should ask who maintains it, what interface it relies on, whether it is read-only or read-write, and what happens if the manufacturer changes its software. Do not treat a logo, forum thread or community project as proof of official support.
How should you verify Home Assistant, Tibber, Shelly and other integrations?
Verify the exact device, market, software path and permissions before relying on any named integration. “Compatible” may refer to a native connection, a third-party service, an API, monitoring only or full control. Those are materially different claims.
For Home Assistant, Tibber, Shelly or any other named platform, ask for model-specific documentation rather than assuming that an ecosystem reference proves a working UK integration. Also check whether the connection is local or cloud-based and whether it can only read data or can actually issue commands.
What data and privacy questions should you ask?
Ask what information leaves your home, why it is collected, who receives it and how long it is kept. A battery app may involve household energy data, account data and device information, so the useful pre-purchase check is whether the current privacy documentation clearly explains the data path and the controls available to you.
Also check whether data is processed outside the UK, how to delete an account, whether you can export your data, how to revoke a third-party connection, whether an installer retains access after commissioning and whether multi-factor authentication (MFA) is available. Do not treat a marketing claim as a substitute for current privacy documentation.
Your home battery software due-diligence checklist
Before you commit to the hardware, try to get clear answers to these ten questions for the exact model and UK configuration you are considering.
Software due-diligence checklist
What can you currently verify about the Sunpura S2400?
As checked on 22 September 2026, the current UK S2400 product page says the system can retrieve dynamic electricity prices and adjust charging and discharging in response. It also says the Sunpura app can show solar generation, consumption, battery status and available price data. The same page qualifies those features: availability depends on the configuration, compatible devices and available price data, and savings are not guaranteed.
See the current Sunpura S2400 specification, app overview and product documents.
Those statements do not establish a documented local API, local read/write control, specific behaviour when broadband or Sunpura Cloud is unavailable, or support for Home Assistant, Tibber, Shelly or a named UK supplier. Those points should be treated as separate checks until current model-specific documentation confirms them.
Current product example
Sunpura S2400
A current UK home battery with app-based energy visibility and a current product-page claim for automatic response to available dynamic electricity-price data. Check the current product page and documentation for the exact configuration and supported functions.
View the Sunpura S2400