Tesla Megapack 2 XL

Compatibility

Direct Edge integration not yet verified

Tesla documents Powerhub exports and telemetry integration with third-party DERMS. Its public support page does not supply the project API schema or a local Modbus map. Use the site’s Powerhub access first; agree the endpoint, authentication and available read fields once with the project team. A direct Edge installation remains unverified.

Megapack 2 XL part family 1848844-x*y*-z* in Tesla emergency guide revision 2.8. Confirm exact project hardware, software, warranty, service and site-control contract. No Tesla, protection, fire or market authority is transferred.

Models

Specifications

Powerhub combines site meters, individual battery blocks and other energy assets in one monitoring platform. Tesla documents historical trends, custom reports, data export and telemetry integration into third-party DERMS.¹

Exact family

Megapack 2 XL, part family 1848844-x*y*-z*²

Maximum system voltage

Below 1,230 V DC; 480 V AC²

Maximum mass

38,100 kg²

Published software boundary

Powerhub site and battery-block views, historical reports, exports and a project API/DERMS integration route¹

Third-party interface

Powerhub documents telemetry integration into third-party DERMS; local addresses and the project API schema are not in the public support article^1, 2

Safety scope

Emergency response and high-voltage isolation remain under Tesla and the approved site plan²

Interface

Documented measurements and integration boundaries for Megapack 2 XL.

• Potential identity, availability, state, power, energy, state of charge, temperatures and alarms require a Tesla-approved project interface.
• Megapack, site controller, revenue meter, protection relay and market platform values remain distinct records with source and timestamp.
• Fire detection, emergency response, high-voltage isolation and service procedures remain solely under Tesla and the approved site plan.
• No dispatch, charge, discharge, reactive-power, grid-service, protection, reset or emergency command is approved by this guide.

Setup

1. Confirm the delivered system

   Record every enclosure, battery rack, PCS, BMS, EMS, meter and controller identity, plus firmware, software, network and contract revisions.

2. Map authority before data

   Document which system owns charge and discharge, protection, fire and life safety, grid control, market dispatch, settlement, warranty and emergency response.

3. Start with a Powerhub export

   Use the site’s Powerhub account to inspect a historical trend and export a report. Identify which series belongs to the site meter and which to an individual battery block; retain the export’s time zone, interval and units. For automated collection, request the project telemetry interface and available read fields from Tesla. The public page describes the capability, not a universal API URL or register map.

4. Compare the battery feeder with the site meter

   Compare battery-block data with the battery AC feeder meter over the same recorded interval. Treat the whole-site meter separately because it also includes other loads and generation. Check power direction during an existing scheduled charge and discharge, and mark missing or delayed cloud data rather than turning it into zero power. Keep dispatch in the existing Tesla or site-control system.