Feature Request: Local API for Tesla Powerwall & Solar Inverter

[erikgieseler]

Description

On behalf of many users, we request an officially supported, documented, and stable local API (LAN) that allows end users to directly access relevant status and energy data from their Tesla Powerwall 2/3 and Tesla Solar Inverter — without routing through the Tesla cloud.

Background

Currently, access to local energy data is only possible via unofficial or undocumented interfaces. These are unstable, undocumented, and often affected by firmware updates. Robust local access is crucial for many use cases — e.g., integration with energy management systems or operation during internet outages.

Benefits

• Privacy: No need to send sensitive energy data to cloud services
• Reliability: Access data even when internet or cloud services are down
• Smart Home Integration: Easy connection to local systems (e.g., Home Assistant, OpenHAB)
• Interoperability: Enables integration with existing local energy infrastructures (e.g., PV inverters, charging stations, storage systems)

Requirements for Local API

• Access via LAN over HTTPS or standardized industrial protocols
• Two possible options:
  • JSON-based REST API:
    • Documented endpoints like https://<ip>/api/...
    • Authentication via locally generated token or local account
  • Alternatively: Support for Modbus TCP:
    • Industry standard in energy and building automation
    • Easily integrated into energy management and home automation systems
    • Broad compatibility with third-party and open platforms
• Provide at least the following data points:
  • State of Energy (SoE) of the Powerwall
  • Grid import/export
  • PV generation (including directly from the inverter)
  • Household consumption
  • Device status / error codes
• Low latency for real-time applications

Suggested Implementation

• Official release and documentation of existing local APIs
• Extension to include solar inverter-specific data points
• Optional Modbus TCP support with published register mapping
• Activation option in Tesla app (e.g., “Enable Local API”)

Comparable Solutions by Other Manufacturers

• SMA
• Fronius
• SolarEdge

Additional Notes

Please forward this request to the responsible developer teams or product owners and do not close it prematurely.

Thank you on behalf of all Tesla Solar owners!

[Nexarian]

Use case

String data monitoring is a critical way for homeowners to determine if their solar array is healthy or not. Without this data, homeowners are effectively blind (Compare with Enphase's per-panel monitoring!). I was able to use this data on the current/unstable API to find that my system was underproducing so badly (intermittent strings) that 6 months would be added to my payback period had I taken no action!

Refining the ask

Also note that our community is not asking for access that would damage or endanger the operation of the system. We do understand that this is professional power equipment and certain settings are best left to professionals. Our primary concern is read-only data access for system health monitoring and perhaps the ability to reset the inverter (Nothing more than what Tesla One already provides)

A final exhortation

Friends and family often ask me what solar solution I would recommend. Having a solid commitment from Tesla on API support described above would make a Tesla recommendation very easy. Otherwise, I would guide them elsewhere!

[martinmanyhats]

This would be very welcome as ongoing data logging has already assisted in locating solar panel installation issues.

As already mentioned, this is strictly about read-only access to PW data.

[slyglif]

I would also appreciate this. I've already used the per powerwall data on my PW2s to report a failed unit, and not having this capability on my PW3s is concerning.

[jasonacox]

There is a large community of Tesla Solar Energy enthusiast that would love to help make this a robust and easy to use feature. As mentioned, the request is for read-only metrics ONLY and via simple and secure local LAN access. Besides being cloud-based only, FleetAPI is missing several key data points that would be helpful to trend, troubleshoot and brag about system performance, including vitals such as string data (voltage, current, power, state), voltages, frequencies, temperatures (ambient), inverter fan performance, and system alerts.

I'm sure many of us would be more than happy to contribute in any way possible. ❤

Thanks for your consideration! 🙏

[danmalone326]

Adding my support for this. Living in a rural area, when grid power goes out, our regional ISP goes down too. In these situations, having local access to the Powerwall is essential for home automation systems to detect outages and provide visual cues to the rest of the family. The Powerwall works great—so well that the family usually doesn’t even realize the power is out. That’s why those visual cues really matter. They make us think twice before doing something like baking a lasagna at 425°F for 80 minutes.

[drreality41]

I concur with OP. Powerwall is an amazing piece of kit, however, it is severely restrictive. I just wish that Tesla offer local API access which gives a good visibility.

[Scrub000]

If no local mode is allowed I will never buy Tesla again

I want read and write access, local only

For now, I've physically removed the cellular connection from the Powerwall and blocked firmware updates as any new firmware update is harmful

[cstout1]

This local API connection has been a great asset for energy production and usage tracking, but where it's really shined for me is on the diagnostics side. I've been able to find and report warranty hardware issues before Tesla could. This API connection is vital for me to ensure my investment is protected and working properly.

Firmware 25.10.1 has negatively impacted this vital reporting capability and my hope is that Tesla will see, consider, and reverse this terrible decision that's been made. Thank you!

[mdcollins05]

Having a local API would mean I could integrate this into Home Assistant even when my internet connection is down. This does happen during extended power outages. Being limited to using just my phone doesn't allow any sort of automation, only manual actions by myself.

With a local API, I could automate various steps to conserve energy during outages, like adjusting thermostat temperatures or turning off certain switches and plugs that have heavy electrical loads (resistive heaters, fans, gaming devices, car chargers, etc). This kind of automation would make the system far more useful and responsive in real-world scenarios.

It would also strengthen the list of "pros" when weighing a Tesla system versus others on the market.

While I'd prefer the ability to make changes to settings via the local API, even a read-only API would be a huge win for smart home integration. I really hope this is implemented.

[michalperth]

What is the point of hiding the parameters reading from the end user while on the ethernet? I hope this is not intentional firmware bug. Please fix this. Thanks.

[hobbymachinist]

It's a good system, well built but let down by lack of proper local API control. I'll be using Sungrow or something else that provides better local control next time.