Pod Point EV charger support in 1app.energy

Pod Point chargers are common in UK homes. The charger does the important charger job, and the Pod Home app remains the main place for Pod Point-specific setup, schedules, solar settings, Boost, lock settings and account support.

The 1app.energy job is different.

1app.energy brings the EV charger into the same whole-home view as solar, battery, grid and tariff data. That matters when the home has a battery, a smart tariff or solar export, because the useful question is not only "is the charger on?".

The better question is:

What is EV charging doing to the rest of the home?

That is the reason we have added Pod Point support.

If you want the short side-by-side view, read the 1app.energy vs Pod Point comparison.

If you want the wider context before connecting a charger, read the 1app.energy onboarding and settings guide, the Solis, zappi and Octopus setup checklist, the guide on why Octopus can appear to drain a home battery, and the manual tariff setup guide for solar, battery and EV homes.

What 1app.energy adds for Pod Point homes

For compatible Pod Point accounts, 1app.energy can connect the charger account, verify access, select the correct charger where more than one is available, and show supported charger context inside the customer dashboard.

That context can include:

• charger connection state;
• charging or idle state where available;
• selected session context;
• schedule or charge-mode context where available;
• whole-home EV context beside solar, battery, grid and tariff data;
• supported Boost, Smart or Stop mode controls only where control is enabled for the home.

This does not make Pod Point a battery inverter, supplier account or live measured-power authority.

Where the backend cannot prove trusted live charger watts, the dashboard treats Pod Point as status and session context. It does not use untrusted Pod Point watts as confident live power flow.

What stays in Pod Home

Pod Home remains the right place for Pod Point-native charger setup.

Use Pod Home for:

• Wi-Fi setup and charger account management;
• ready-by targets;
• full charger schedules;
• solar charging settings;
• multiple vehicle setup;
• Boost and lock behaviour where you prefer to manage it directly in Pod Home;
• firmware, installer support and Pod Point account support.

The official Pod Point material describes app features such as schedules, energy and cost activity, multiple EVs, Boost and solar settings on the Pod Home app page. The Solo charger page also describes the Solo home charger, app control, solar integration, activity insight, Boost and remote lock features.

1app.energy should not pretend to replace all of that. It adds whole-home energy context around it.

How to connect Pod Point in 1app.energy

From the 1app.energy app:

1. Open Settings.
2. Go to Devices.
3. Choose Add device.
4. Select Pod Point Charger.
5. Enter the Pod Point account email and password used for the charger.
6. If the account has more than one charger, select the correct charger for the home.
7. Save the connection.

1app.energy verifies the account before saving the connection. The password is used to verify access and obtain provider access tokens; the frontend does not ask the customer to find a Firebase API key.

That is important. Customers should connect with the account they already use for the charger. They should not need to dig through unofficial code or browser traffic to find a hidden key.

Compatibility notes

This integration is based on the available Pod Point cloud behaviour and public community evidence, including the unofficial Pod Point Home Assistant component. That project documents support for Pod Point Solo and Solo 3 chargers, charger state, energy/session-related data and supported switches, but it is not an official Pod Point API contract.

Because the interface is unofficial, compatibility can change if Pod Point changes authentication, app behaviour, eligibility rules or cloud endpoints.

In practical terms:

• some accounts may need the customer to update or reset their Pod Point login before connection works;
• accounts with extra verification requirements may need a provider-side change before third-party access works;
• more than one charger on the same account requires selecting the charger that belongs to the 1app.energy home;
• unsupported or changed provider responses are treated as connection failures rather than silent success.

That is the safe behaviour. A connected-device app should verify access before showing the charger as connected.

How this helps solar and battery homes

EV charging can be one of the biggest flexible loads in a home.

If the charger runs at the wrong time, the customer may see:

• the home battery drain into the car;
• grid import during an expensive period;
• missed export value;
• confusing daily energy totals;
• several apps that each show only one part of the story.

1app.energy helps by showing Pod Point charger context alongside the inverter, battery and tariff context.

For example, a customer can see whether an EV session happened during a cheap period, whether battery reserve was protected, and whether the EV load should be treated as part of the whole-home energy plan.

The charger still belongs to Pod Point. The whole-home explanation belongs in 1app.energy.

Frequently asked questions

Is this an official Pod Point partnership?

No. 1app.energy is an independent interface unless we explicitly state otherwise. Pod Point, Pod Home and Solo remain Pod Point products.

Do I need a Pod Point Firebase API key?

No. The 1app.energy frontend connection flow asks for the Pod Point account email and password. The backend handles the provider connection flow and stores connection tokens securely after verification.

Can 1app.energy set a Pod Point kWh target?

No. Pod Point support is mode-based where enabled. Ready-by targets and full scheduling stay in Pod Home.

Can 1app.energy show live Pod Point power?

Only if the backend marks charger watts as trusted. If trusted watts are not available, 1app.energy shows charger status and session context without treating Pod Point as a measured live-power source.

What if my Pod Point account has two chargers?

1app.energy asks you to select the charger for this home. That prevents one account from accidentally connecting the wrong charger to the wrong installation.

What if Pod Point changes the app API?

The integration may need an update. If provider access changes, 1app.energy should fail closed, keep the existing home safe, and explain the connection problem rather than pretending the charger is still fully available.