# FAQs

## Integration

### What if we already do our own pairing and command orchestration?

If you link both vehicles and chargers AND directly control those chargers via our API, we've proactively **disabled** capability unlocking and command orchestration for your API clients.

Features [released previously to all customers](https://developers.enode.com/api/changelog/updates/2025-08-08-ev-charger-dynamic-pairing) still work: `pluggedInChargerId`, `pluggedInVehicleId`, and improved charge rate handling.

Contact your Customer Success Manager or Support to enable the full EV Charger Pairing solution.

### What if my user has a Tesla vehicle and charger?

You can simplify linking with [multi-type linking](https://developers.enode.com/docs/link-ui/multi-type-linking). This lets you link both devices in a single Tesla session.

### What edge cases should I be aware of?

See [Testing your integration](https://developers.enode.com/docs/ev-charger-pairing/integration-testing).

## Product behavior

### How does Enode identify which charger is plugged into a specific vehicle?

We compare plug-in timestamps, charging state transitions, charge rates, and location (when GPS is available). The algorithm is tuned to minimize false positives.

### What happens if I send commands directly to the charger when it's paired with a vehicle?

Commands sent to the Charger endpoint execute on the charger only. The Vehicle API reflects the updated state.

### What happens if a user has multiple vehicles or multiple chargers?

Capabilities unlock for each vehicle/charger combination linked to the same user. Commands aren't sent to a charger until we confirm it's plugged into a known vehicle.

### How does "improved charge rate handling" interact with "Enhanced Charge Rate Estimate"?

If Enhanced Charge Rate Estimate is enabled for your API client, the charge rate from the charger is **ignored**. We'll consolidate charge rate handling before General Availability to maximize accuracy.

### Do chargers report GPS coordinates?

No. Users can set an address in the first-party app, but this is unreliable. Only about 30% of users set an address, the address isn't always correct, and it can change without notice.

## Supporting end users

### Can I see and manage charging pairs in the Dashboard?

Not yet. We'll add pairing data to **Asset View**, **Asset History**, and **Insights** before General Availability.

### How can I investigate user issues when control has been orchestrated by Enode?

The `failureReason` field in the action response explains what went wrong, including which device was involved when relevant.

## Missing features

### Why aren't unified controls available through the Charger API?

Most customers start with vehicle integrations, so we focused on the Vehicle API first. We may add bi-directional support later, but it's not a priority.

### Can I control the max charging current or power through the pair?

No. We're not planning to add support for `setMaxCurrent` on the charger via the Vehicle API.
Instead we'll be introducing a `setChargeRateLimit` command that sets maximum **power** (in kW) for chargers. This `setChargeRateLimit` operation will also be available on the Vehicle API on vehicles paired with chargers.

### Will I be able to retrieve OEM charging session statistics for charging pairs?

Not yet, but it's on our radar.

The most accurate session statistics come from the charger OEM. They measure energy drawn from the grid before charging losses. We plan to add native statistics to our [Statistics API](https://developers.enode.com/docs/statistics) in the future.

When a vehicle is paired with a charger, we'll provide native statistics for that vehicle's sessions. You won't need to fetch them from the charger separately.