Quick Summary (TL;DR)
Choose Tesla Powerwall if you want a largely turnkey home battery with coordinated solar, reserve management and installer support. Choose a properly engineered Victron ESS if integration flexibility, local network data and mixed equipment matter more than a one-box purchase. A third category—open monitoring built around a compatible hybrid inverter and a documented Modbus interface—can be a compelling middle ground, but it is not automatically an open control platform.
For Home Assistant, Tesla Powerwall 2 and Powerwall 3 can be monitored via the official local integration, although Powerwall 3’s local API exposes fewer entities and control features. Tesla’s Fleet integration offers cloud-based energy-site commands subject to account and authorisation requirements. Victron GX exposes a local MQTT integration and supports documented ESS configuration, provided the particular inverter/charger, gateway, battery and battery-management system are compatible. The battery’s safety controls must always remain independent of Home Assistant.
The buying decision is about the installed energy system—not the battery enclosure alone. Check capacity, continuous output, backup arrangement, phase layout, battery chemistry, energy-management permissions, installer accountability and warranty exclusions. Price comparisons only make sense with all of those items included in written quotations.
What the three choices actually mean
A home battery stores electrical energy, but Home Assistant can only see or influence the system through the interfaces exposed by the inverter, gateway, site meter and battery controller. That difference explains why two batteries that each claim 10–15 kWh can produce radically different smart-home experiences.
Tesla Powerwall is an integrated product ecosystem. Tesla supplies the battery and associated power electronics and offers the Tesla app, site monitoring, self-consumption and tariff-aware modes. The required backup arrangement depends on the product and system design. You normally get a coherent operating experience and a single product family to maintain, at the expense of less direct control over internal logic.
Victron is a configurable energy-storage architecture, not one universal battery SKU. A typical grid-connected ESS uses a MultiPlus or Quattro inverter/charger, a GX gateway such as Cerbo GX, a properly matched battery with its BMS, a suitable meter where required and correct protection and switching. Configuration can be more adaptable, but wiring, BMS selection and installer experience become central purchasing risks.
An open-leaning hybrid-inverter system may include a compatible inverter and battery stack from manufacturers whose models provide local Modbus or another documented interface. It may be much easier to monitor locally than to change its dispatch mode. An RS485 connector or an unofficial Home Assistant integration does not, by itself, establish safe writable control or future firmware compatibility.
| Buying dimension | Tesla Powerwall ecosystem | Victron ESS plus compatible battery | Hybrid inverter with documented local API |
|---|---|---|---|
| Main attraction | Turnkey product and coordinated operation | System-design and integration flexibility | Potentially simpler local monitoring at a range of budgets |
| Where battery control lives | Tesla controller and supported app/API modes | GX/ESS logic, inverter and battery BMS | Manufacturer inverter/BMS and firmware |
| Home Assistant starting point | Local Tesla Powerwall integration for data; Fleet for supported cloud commands | Built-in Victron GX integration over local MQTT | Exact model’s official interface, usually Modbus or a vendor gateway |
| Cloud-free monitoring | Possible for supported local data; Powerwall 3 limitations | Strong option on supported GX hardware | Model-dependent: verify before purchase |
| Arbitrary charge/discharge commands | Do not assume; supported cloud/site commands differ from direct low-level control | More possibilities, with documented safeguards and system constraints | Highly variable; write support often absent or restricted |
| Installer responsibility | Tesla-qualified installation and system configuration | More design and integration responsibility | Depends on hybrid system and third-party batteries |
| Best suited to | Homeowners who value convenience and support | Integrators, complex solar/backup projects and advanced local monitoring | Value-oriented local telemetry when complete compatibility is proven |
Powerwall 3 versus Powerwall 2: buy the model, not the family name
Tesla’s UK documentation lists 13.5 kWh nominal energy capacity for both Powerwall 2 and Powerwall 3. Powerwall 3 integrates solar-inverter functions and is offered with output capabilities dependent on local electrical conditions and configuration; UK documentation gives up to 11.04 kW, not a universal output guarantee. Check the exact region-specific electrical specification, permissible continuous discharge rating and installed grid protection. A US split-phase rating must not be copied into a European 230 V design.
Powerwall 3 also has expansion options, but the expansion units, base-unit quantity, installation constraints and Powerwall 2/3 interoperability are specific. Tesla says that Powerwall 3 cannot be added to a Powerwall 2 system. A quote stating only “Powerwall compatible” is not adequate for a long-term expansion plan. A battery’s nominal stored energy is also distinct from its usable energy during backup, which depends on reserve settings and the operating load.
An often-overlooked distinction is backup versus non-backup installation. Tesla documents a UK Powerwall 3 non-backup configuration that retains self-consumption and savings functions but does not provide the same outage reserve, Storm Watch or off-grid functions. Confirm the specific Backup Gateway and essential-load arrangement in the contract, not just whether the salesperson describes the battery as capable of backup.
| Powerwall question | What to verify in the written quote | Why it matters |
|---|---|---|
| Generation and model | Powerwall 2, 3 and any expansion modules | Internal inverter architecture and local integrations differ |
| Usable battery capacity | Configuration and usable-energy warranty terms | Nominal kWh are not all available under every reserve and temperature condition |
| Continuous power | Region-specific rated kW and any export cap | A large kWh capacity does not ensure whole-home peak-load coverage |
| Solar coupling | Existing inverter compatibility, integrated PV inputs, AC/DC coupling | May change rewiring, inverter replacement and solar-operating modes |
| Backup equipment | Gateway model, critical-load subpanel, islanding and phase handling | Determines which loads survive a power cut |
| Expansion | Supported modules, maximum number and installation clearances | Future extra batteries may not be a simple retrofit |
| Home Assistant | Gateway generation, firmware and available entities | Powerwall 3 has fewer local features than Powerwall 2 |
| Warranty | Country-specific coverage, throughput conditions and installation terms | A headline “10-year warranty” is not the whole contract |
Tesla’s UK Powerwall comparison, Powerwall 3 guide and UK owner’s document library are the starting references. Manufacturer specifications and commissioning conditions take precedence over generic reseller advertising.
How Tesla Powerwall integrates with Home Assistant
There are two distinct routes to understand: local telemetry and authenticated Tesla-account services. They should not be described as interchangeable, and turning on one does not guarantee the capabilities of the other.
1. Built-in Tesla Powerwall integration: local monitoring
Home Assistant’s built-in Tesla Powerwall integration communicates with the Powerwall or Backup Gateway on the local network. It is officially classified as local polling. Supported aggregate entities can include battery state of charge, battery power, site/grid power, solar power, home load, grid status and cumulative imported/exported energy. The exact set depends on generation and installed metering.
For Powerwall 3, Home Assistant explicitly documents a more restricted local HTTP API: per-battery sensors, backup-reserve entities and the off-grid switch are among the features unavailable through this local path. Importantly, aggregate power, charge, lifetime energy and some grid-state sensors remain available. Do not promise a Powerwall 3 buyer the richer Powerwall 2 entity set merely because screenshots show those entities on another installation.
To set up local monitoring, connect Home Assistant and the Powerwall Gateway to the same appropriately secured network. In Home Assistant go to Settings → Devices & services → Add Integration → Tesla Powerwall; use discovery or enter the device’s local address. Follow the current integration’s documented authentication flow. Reserve a DHCP address or set a DHCP reservation once the gateway is identified. Check the Energy dashboard only after confirming that energy entities actually exist, have the right units and update reliably.
2. Tesla Fleet integration: authorised cloud energy-site controls
The separate Tesla Fleet integration uses the Tesla Fleet API and requires developer/app credentials, public-key hosting and appropriate permissions. Its documented energy-site entities include charge level and power flow along with, where supported, commands such as backup reserve, operation mode, export permissions and grid charging. These are account- and site-authorised features, not evidence of an unrestricted local battery-control protocol.
The Fleet integration has a cloud dependency and different reliability and security characteristics from the local Powerwall integration. Tesla states energy-product API use is free, but the broader Fleet application setup and terms can change; check the current Home Assistant instructions and Tesla developer conditions before relying on a particular automation.
Paid third-party services such as Teslemetry and Tessie have their own authentication, subscription and local-control capabilities. If considering them, compare what each service actually does today instead of assuming its name indicates official direct access. For installations participating in virtual power plants or utility demand-response schemes, verify whether operator commands can override your preferred battery dispatch schedule.
| Powerwall interface | Local data | Home Assistant control possibilities | Key caveat |
|---|---|---|---|
| Tesla Powerwall built-in integration | Yes, for supported gateways | Local functionality is limited; Powerwall 3 more restricted | Not a general-purpose charge/discharge command interface |
| Tesla Fleet integration | Account/cloud API | Supported energy-site mode and reserve controls | Cloud authorisation and integration setup required |
| Teslemetry/Tessie or other third parties | Depends on service and pairing | Service-specific | Extra account, pricing and permission considerations |
| Tesla app | Product’s native experience | Manufacturer-provided modes and tariffs | Cannot assume app options are exposed identically to HA |
How Victron ESS integrates with Home Assistant
Victron’s architecture is more modular and more explicit about local communications. The built-in Victron GX integration connects to a GX device running Venus OS using local MQTT. It can discover installed system components and expose grid, inverter/charger, solar charger and battery values, subject to the actual configuration. Older or more customised projects may use raw MQTT topics or the GX’s documented Modbus TCP server.
The Victron ESS design manual describes a grid-connected ESS around an inverter/charger, a GX device and a battery system. On a managed lithium system, the BMS and GX communications remain safety-critical: charge and discharge allowances, temperatures and limits are not decisions Home Assistant should invent. Inverters must obey the manufacturer’s ESS mode, grid-code, metering and battery constraints.
The GX configuration manual documents separate options for MQTT access and the Modbus TCP server, including Modbus access permissions. Home Assistant’s built-in Victron integration is generally the easiest path for most current installations. Modbus is useful for deliberate read-only register sets or a separate building-management/PLC application. Writing registers or changing ESS setpoints requires a supported design and stronger authorisation controls.
Choosing a battery for a Victron installation
Do not buy a pack solely because it has an RJ45 socket marked CAN. Victron’s battery compatibility list contains numerous manufacturers and specific model guidance; compatibility can depend on battery voltage family, firmware, GX CAN port configuration and BMS protocol. A manufacturer’s model may support several inverter brands through different CAN profiles. The list also explains that additional batteries may work with supplier support, but model-specific engineering is required.
For example, Victron’s BYD compatibility notes document supported low-voltage BYD B-Box families and explicitly say the BYD HVS/HVM high-voltage range is not compatible with Victron in that integration. “BYD works with Victron” is therefore dangerously imprecise purchasing advice. Ask the installer to put the exact battery product code, BMS firmware and inverter compatibility document in the bill of materials.
A Victron system is open in the sense that its documented monitoring and configuration options give integrators more freedom. It is not a free-for-all for battery chemistry, cell balancing, pack fuses, earthing or grid-parallel export behaviour. A self-built lithium pack may be a hobby electronics project, but it is not a sensible default for a household grid-connected ESS.
| Victron component | Buying check | Hidden cost or integration risk |
|---|---|---|
| MultiPlus/Quattro inverter/charger | Exact model, AC power, VE.Bus, backup/ESS capability, phase layout | Number of units, protection and complex commissioning |
| Cerbo GX or other Venus OS gateway | Port count, GX firmware, CAN interface, local network reliability | Gateway and cabling are separate from the battery price |
| Battery modules and BMS | Exact model listed as compatible, supported CAN protocol and firmware | A battery can be electrically similar but protocol-incompatible |
| Energy meterAliExpress price | Utility boundary, direct meter versus CT type, phase configuration | Incorrect topology causes wrong ESS regulation or reporting |
| Solar system | DC MPPT or AC-coupled PV and manufacturer design rules | Existing PV may require redesign for backup operation |
| Installer/commissioning | VEConfigure, ESS Assistant, local grid code and testing | A cheap parts basket can become an expensive installed project |
Open ecosystems: what actually counts as open?
The term open battery is used for three very different promises. First is open telemetry: you can read power, energy, state of charge and alarms without a proprietary cloud. Second is open control: you can modify a documented setpoint or charge permission safely, with vendor support. Third is interchangeable hardware: you can choose among battery packs, inverters, gateways and firmware without losing support. A product may satisfy the first but neither of the others.
For a hybrid inverter with a Modbus RTU or TCP interface, verify the specific register map for the exact model and firmware, whether it exposes cumulative charge/discharge energy counters, and whether write access is officially permitted. A community Home Assistant integration demonstrates possible functionality but is not the same as a supported contract. Check availability of firmware updates, data polling without cloud credentials, the LAN gateway’s behaviour during an internet outage and any vendor-imposed export restriction.
Examples worth investigating include carefully matched low-voltage battery/inverter systems and supported high-voltage hybrid systems, but they must not be mixed casually. Battery voltage, required communications and anti-islanding design are fundamental architecture constraints. Some proprietary ecosystems have excellent local visibility while retaining closed BMS dispatch control. That can still be the right purchase if the priority is a trustworthy Energy dashboard rather than automating the battery itself.
Enphase IQ Gateway’s Home Assistant integration illustrates the nuance. Battery-related entities can be present, but availability varies with gateway model, firmware, installed CTs and the particular battery generation. The documentation specifically warns that some production/consumption metrics depend on meter equipment and that firmware behaviour can change. Always test the exact system offered in your quotation rather than assuming the entire brand family exposes a standard battery API.
Monitoring is not dispatch control
Before buying, decide which of the following actions you genuinely need:
| Desired function | Usually achievable? | What must be confirmed |
|---|---|---|
| Show battery percentage and charging/discharging power | Yes on well-integrated systems | Local API, update interval and signs of power readings |
| Add battery charging/discharging totals to Home Assistant Energy | Often | Separate cumulative energy counters or reliable integration sensors |
| Alert on low state of charge or a grid outage | Often | Sensor quality, communications path and fallback behaviour |
| Reserve energy before a storm or blackout | Depends on product/site | Native reserve control, permissions and backup arrangement |
| Automatically shift charging to cheaper tariffs | Native function in many systems | Approved operating modes and utility restrictions |
| Force arbitrary kW charge/discharge every minute | Not a safe general assumption | Explicitly supported writable control and battery/inverter constraints |
| Participate in VPP or export arbitrage | Region, contract and programme specific | Grid export permissions, contract, tax and warranty conditions |
| Keep loads supplied during grid outage | Only with engineered backup/islanding | Gateway, transfer arrangement, protected circuits and power limit |
A practical approach is to let the manufacturer’s ESS controller handle its protection loops and use Home Assistant for observation, tariff inputs, non-critical load scheduling and alerts. A home automation server rebooting during a grid fault must not remove a battery’s protection. For demand-response and emergency reserve, use the vendor’s native settings unless the installer has validated a supported integration path.
Home Assistant Energy dashboard: choosing the correct sensors
The Energy dashboard needs energy measured over time, not merely the live watts displayed by a battery. Prefer separately reported lifetime battery charge energy and battery discharge energy in kWh. Use the integration’s appropriate energy sensors where available. State of charge (percentage) is useful as a graph and automation condition but cannot replace kWh charge/discharge measurements.
For a local Powerwall installation, the integration documentation lists aggregated energy flow counters. For a Victron system, identify whether the relevant battery figures come from a BMS, DC shunt or inverter gateway, and understand what that boundary measures. If a metric only represents inverter AC energy while battery energy is measured on DC, round-trip and conversion losses mean the figures will differ. This is not necessarily an integration bug.
Follow Home Assistant’s battery integration guidance and inspect sensor device class, state class, units, sign and statistics history before adding them to the dashboard. Do not add the same battery flow twice through an inverter integration and a separate shunt. Similarly, grid import and export must refer to the utility connection point—not a CT on one solar branch or a battery inverter feed.
A useful sanity check is a 30-minute discharge of about 2 kW, which corresponds to roughly 1 kWh delivered at the point where that power is measured. If the dashboard shows 30 kWh, look for a W-versus-kW conversion or cumulative-versus-instantaneous entity mistake. The simple calculation is power in kilowatts multiplied by time in hours; it does not imply a particular system efficiency.
Recommended first-day checklist
- Confirm Home Assistant can still read the battery with the home’s internet connection temporarily disconnected, without taking the inverter offline.
- Identify battery state of charge, signed charge/discharge power, grid import/export and solar production.
- Record the sensor units and direction conventions while the battery is clearly charging and then discharging.
- Check whether battery energy totals survive a gateway restart and whether Home Assistant’s long-term statistics remain continuous.
- Use a site meter or electricity bill to reconcile grid import/export over a sensible period.
- Keep the first automations read-only. Only consider writable controls after identifying owner, installer and manufacturer permissions.
Backup design matters more than the battery label
A 13.5 kWh battery does not automatically run an entire three-phase house during a blackout. Backup duration depends on usable reserve and actual demand, while backup capability depends on inverter output, transfer design, protection, permitted phases and whether the solar inverter can continue producing while islanded. A battery can be perfectly capable of daily self-consumption and still be installed without any backup mode.
Suppose a backup system has 10 kWh actually available to essential loads after reserve and conversion assumptions, and essential appliances draw an average 500 W. The simplified theoretical duration is 10 kWh / 0.5 kW = 20 hours. At a 2 kW average load it becomes five hours. Both are illustrative, not product performance promises. Real loads cycle and battery/inverter efficiency, weather and minimum state-of-charge constraints reduce the practical result.
Backup wiring must be discussed with the installer: does the changeover protect just a fridge, networking and lighting, or the whole dwelling? Can a heat pump compressor or EV charger exceed the inverter’s continuous or surge rating? How do three-phase circuits behave if the installed inverter only backs up one phase? Is the system approved to restart automatically and operate solar during islanding? These are electrical design questions, not Home Assistant YAML questions.
For systems with export control or dynamic pricing, check the relevant local grid-code, utility contract and connection approval. In the UK and EU, single/three-phase arrangements and export permission differ by territory and utility. The installed electrical system, certification and backup configuration must satisfy local rules rather than a generic online how-to.
True cost of ownership: compare the completed system
Comparing the price of a single battery pack against a fully installed Powerwall quote is misleading. An honest total-cost model must include the inverter, compatible BMS, controller/gateway, battery capacity, metering, electrical distribution work, isolators, fuses, network access, commissioning, labour, certification, structural support and any required backup gateway or protected-load circuits.
| Cost item | Tesla-style integrated quote | Victron/modular quote | Questions for the installer |
|---|---|---|---|
| Battery and power electronics | May be bundled in defined product | Often separate inverter/charger and battery modules | Which components and kWh are included? |
| Backup switching and distribution | Can be an additional site design cost | Often substantial site-specific work | Which circuits and phases are actually backed up? |
| Metering and gateways | Tesla gateway/site metering; verify quote | GX gateway and compatible grid meter as needed | Are all meters and CTs included? |
| Engineering and labour | Product-specific approved installation | More design, integration and commissioning | Who accepts responsibility for full system compatibility? |
| Software/API | Native app; local integration plus optional Fleet | Local MQTT/Modbus and Victron ESS | Are the promised controls documented and supported? |
| Servicing and failures | Qualified support channel | Multiple product suppliers and installer | Who diagnoses BMS, inverter and gateway disagreements? |
| Warranty | Product and region-specific terms | Separate battery/inverter/accessory warranties | What happens with unsupported batteries or third-party control? |
A worked economic example—not a promised payback
Imagine a hypothetical battery can reliably shift 6 kWh/day from a lower-cost period to a higher-cost period, on 250 days a year. If the effective saving after losses, lost export value and tariff differences is £0.12 per shifted kWh, the annual benefit would be 6 × 250 × £0.12 = £180. If the effective difference is only £0.04/kWh, that falls to £60. If the home exports valuable solar power instead of storing it, even the positive saving may disappear.
This example is an accounting illustration, not a price forecast or battery-specific efficiency claim. Actual return depends heavily on your tariff, solar output profile, export payment, reserve policy, cycle life, warranty throughput terms and battery degradation. For a meaningful quotation request a model using 12 months of your own consumption and solar generation, not a manufacturer’s generic ROI figure. Backup resilience may be valuable even if the monetary return is modest.
Region-specific questions: UK, EU and Greece
Do not assume a UK Powerwall model, US power rating or North American Tesla software function is offered with identical regulatory approvals in Greece or another EU market. Ask the installer to identify the market-specific product code, AC connection type, maximum import/export, backup capability and commissioning approval. The applicable DSO requirements, electrical certificate and export/zero-export policy matter even when the hardware itself appears identical.
For a three-phase European home, confirm whether the battery inverter backs up one or three phases, how net import/export is measured, and whether the installation supports the desired loads during an outage. For a UK retrofit, ask how the existing solar inverter, generation meter, export arrangements and any protected-load board interact with the new battery. For both, obtain the warranty document applicable to the territory in which the battery is installed.
Tesla’s UK guidance describes Powerwall 3 backup and non-backup arrangements separately; a non-backup design is not a substitute for an emergency supply. Victron ESS systems offer more wiring choices, but these choices expand the commissioning workload. The local authority or network operator—not a community integration—determines permissible grid interaction.
Security and reliability: assume Home Assistant will sometimes fail
A production household battery should keep its native protective systems operating if Home Assistant, its database, the home router or the internet connection disappears. Keep gateway firmware updated by the supported path, back up configuration, segment energy devices appropriately and disable exposed remote-management ports. Modbus TCP commonly lacks authentication; do not expose it to the public internet. Use a secured LAN/VPN and preferably read-only permissions where available.
For Powerwall, test local monitoring independently of Tesla cloud services, but do not assume Fleet API dispatch commands work offline. For Victron, test the GX’s own ESS modes and alarms with Home Assistant disconnected. If using dynamic-tariff optimisers or community add-ons, document the safe fallback mode and when installer servicing will temporarily disable the automation.
Pay special attention to warranties and utility programmes. A ten-year product term does not mean every charge strategy, unsupported BMS or unofficial forced-dispatch script is permitted. Grid-code settings, battery current limits, manufacturer software and utility restrictions must remain authoritative. For virtual power plant enrolment, understand the times when your battery may be dispatched by the programme rather than your own schedule.
Which should you buy?
Choose Powerwall when a local certified installer can supply the exact generation and backup design you need, a consistent app/controller matters more than custom protocol access, and the supported monitoring data is sufficient. If Home Assistant matters, evaluate Powerwall 3’s specific local entity limitations before ordering. Use Tesla’s built-in energy management and officially supported account-level controls rather than attempting undocumented commands.
Choose Victron ESS when you need a configurable mix of PV, grid, battery and backup equipment, value local MQTT and a documented ESS architecture, and have an installer experienced with the precise battery/BMS combination. The hardware and commissioning costs can be significant; the benefit is flexibility, not an automatic saving compared with Powerwall.
Choose another compatible hybrid-inverter ecosystem when an integrated inverter-and-battery package meets your site and warranty needs, and the exact model’s current firmware exposes the read-only local telemetry you actually want. Make writable dispatch a separately verified requirement. A cheaper battery with a cloud-only logger can become a poor Home Assistant choice even if its nameplate kWh looks attractive.
For most readers whose main goal is an accurate Home Assistant energy dashboard, choose the battery installation that best fits the electrical and financial needs, then verify its telemetry before signing the contract. Home Assistant should inform the purchase, not override fundamental safety, warranty or backup requirements.
Frequently asked questions
Can Home Assistant force a Tesla Powerwall to charge?
The local Powerwall integration primarily provides monitoring and has generation-specific limits. Some Tesla Fleet energy-site controls support approved operating modes, charging-related permissions and backup-reserve settings, but these are not unrestricted direct power commands. Availability depends on site configuration and region. Use the current Fleet integration documentation and Tesla account permissions rather than an undocumented local endpoint.
Can I use a BYD battery with Victron?
Some specific low-voltage BYD B-Box models appear in Victron’s compatibility guidance, subject to firmware and BMS conditions. The BYD HVS/HVM high-voltage ranges are explicitly excluded in Victron’s documented integration. You need the exact battery model—not just the BYD logo.
Does local data mean the battery will keep recording while Home Assistant is off?
Not necessarily. The inverter or GX controller may record its own history, but whether Home Assistant recovers every missing energy interval after reconnecting depends on the API, counter availability and integration behaviour. Prefer persistent cumulative energy readings and verify by a controlled, non-disruptive monitoring test.
Should I choose the battery with the most kWh?
Not without checking continuous output power, permitted charge power, usable capacity, phase configuration and backup topology. A large battery with an inverter that cannot meet peak load may be less useful in an outage than a smaller battery with the correct protected-load design.
Can a DIY battery be as reliable as a commercial ESS?
Building a cell pack is not the same as engineering a code-compliant grid-connected energy-storage system. Battery fire protection, BMS permissions, isolation, fault currents, enclosure suitability, warranty, installer sign-off and insurance are additional concerns. For most domestic installations, choose certified supported hardware and professional installation.
Official documentation and useful related guides
- Tesla Powerwall integration — Home Assistant — supported devices, local sensors and Powerwall 3 limitations.
- Tesla Fleet integration — Home Assistant — authenticated energy-site controls and requirements.
- Powerwall 2 and 3 — Tesla UK — regional capacity, output and backup information.
- Powerwall owner documents — Tesla UK — regional manuals, specifications and warranty documents.
- Victron GX integration — Home Assistant — local MQTT setup and available device types.
- Victron ESS design and installation manual — overall ESS architecture and system constraints.
- Victron battery compatibility — managed batteries, BMS details and limitations.
- Victron and BYD compatibility — exact supported battery families and firmware.
- Enphase Envoy integration — Home Assistant — local monitoring considerations and battery-entity scope.
- Home Assistant battery-energy guidance — monitoring and dashboard entity selection.
- ESP32 Modbus energy meter with Home Assistant — local metering background.
- Home Assistant Energy Dashboard troubleshooting for ESPHome — energy sensors and statistics.