AMPERE POINT Q Series and Home Assistant step-by-step guide banner with a dashboard of live charger data

Full Home Assistant Integration for Ampere Point Q Series Chargers — Step-by-Step Guide

Jan Prószyński

This guide connects your Ampere Point Q Series charger to Home Assistant and opens a ready-made control panel. We use the official Tuya integration and the AmperePoint integration installed through HACS or the Marketplace. Standard setup uses the interface, without editing YAML or creating a Tuya Developer account.

Updated: 4 November 2026 · Q11, Q22, Q37, Q74 · integration reference version: 0.6.1. Available readings and commands depend on the charger generation and firmware.

1. What you need

  • A Q Series charger paired with Tuya Smart or Smart Life and working in the app; use 2.4 GHz Wi-Fi for pairing.
  • Home Assistant 2025.2.0 or later on a device that stays on.
  • Internet access for HA and the charger: this Q Series setup uses the Tuya cloud.
  • HACS or the Marketplace and a GitHub account to authorize adding a custom repository.
  • Your phone with the Tuya app and a second screen to display the QR code.

2. Install Home Assistant if you do not have it yet

Install Home Assistant if you do not have it yet

If Home Assistant is already running for you, go straight to section 3.

Option A: dedicated device, recommended long term

On a Raspberry Pi, mini PC or older laptop, the easiest route is Home Assistant OS. It is a complete system that handles Home Assistant, updates and backups. Official instructions for each platform are available here: home-assistant.io/installation. After installation, the dashboard is usually available in a browser at http://homeassistant.local:8123.

Option B: Windows computer using Docker

This is a good starting point for testing. Home Assistant runs in a container on your normal computer. Remember that automations work only when the computer is turned on and Docker is running.

  1. Install WSL2, which Docker needs on Windows. Right-click the Start menu, open Terminal (administrator), enter wsl --install, confirm and restart the computer when it finishes. Microsoft instructions: learn.microsoft.com/pl-pl/windows/wsl/install.
  2. Install Docker Desktop: docker.com/products/docker-desktop. During installation, keep the WSL 2 option enabled. After launching Docker Desktop, wait until the status shows that it is running. Creating a Docker account can be skipped.
  3. Start Home Assistant. Open Terminal without administrator privileges and paste:
    mkdir C:\HomeAssistant\config
    docker run -d --name homeassistant --restart=unless-stopped -e TZ=Europe/Warsaw -v "C:\HomeAssistant\config:/config" -p 8123:8123 ghcr.io/home-assistant/home-assistant:stable
    The first launch downloads about 1.5 GB and usually takes a few minutes.
  4. Open http://localhost:8123 in your browser. If it does not load immediately, wait one or two minutes and refresh.

With the Docker option, restart Home Assistant in Docker Desktop: Containers → homeassistant → restart icon. You can also use docker restart homeassistant. The restart button may not appear in the Home Assistant menu in this setup, which is normal. You will need to restart a few times in the next steps.

First launch for both options

The welcome wizard will ask you to create a local account, choose location and set units. Save the username and password in a safe place. You can skip the list of automatically discovered devices at this stage.

3. HACS or the Marketplace

On HA 2026.11 and later, open Settings → Marketplace. According to HA documentation, the Marketplace is built in and takes over from HACS.

On HA 2026.10 and earlier, open HACS in the sidebar. If it is not installed, follow the official download instructions for your installation type, restart HA, then add the HACS integration and authorize it with GitHub.

When ready, open HACS or the Marketplace. This is where you add the AmperePoint repository. HA app/add-on repositories are a separate location. Marketplace documentation.

4. Connect the official Tuya integration

  1. In HA, open Settings → Devices & services → Add integration → Tuya.
  2. In Tuya Smart or Smart Life, find Me → Settings → Account and Security → User Code. Enter that code in HA.
  3. Scan the QR code using the same app and account that owns the charger, and confirm the sign-in.
  4. Check that the charger appears among the devices of the Tuya integration before continuing. Official Tuya instructions.

5. Download AmperePoint

  1. Open HACS → ⋮ → Custom repositories. In the Marketplace, use the custom repository option; the button below provides a shortcut.
  2. Paste the full address below, select Integration as the type and click Add.
  3. Search for TuyaExtend AmperePoint, open its page and download the current published release.
  4. Restart Home Assistant, then refresh your browser. With a Container installation, you can restart the container.
  5. Downloading files and adding a device are separate steps. After the restart, complete the next section.

Repository type: Integration

Open the repository in my Home Assistant

Paste the address into the repository field in HACS/Marketplace without adding a file or folder path. The store name is TuyaExtend AmperePoint; in HA settings, search for AmperePoint.

6. Add the charger and open the panel

  1. Open Settings → Devices & services → Add integration and search for AmperePoint. If HA has already added the charger entry automatically, open that entry.
  2. Choose the detected-charger setup option, select the correct device and give it a name. This Q Series setup uses the Tuya source.
  3. Set your energy tariff and currency, review the remaining settings and finish the wizard.
  4. Open Ampere Point - Tuya dashboard in the sidebar. The shared panel is created automatically; with several chargers, select the device in its header.

7. Readings and controls

Check that the panel shows the correct charger and current readings. Available functions include status, power, session energy, current limit, start/stop and diagnostics.

Coverage depends on the device and the data supplied by Tuya. Phase measurements, a total counter and an energy target appear only when the source supports them.

While changing the current limit, the panel previews the selected value. After sending a command, wait for confirmation from the charger. Keep the HA limit within the range allowed by the charger and the electrical installation.

Example Ampere Point charger panel in Home Assistant
Example panel view. Readings, layout and available functions may vary with the version and charger.

8. Add the charger to Energy

  1. Select the charger in the AmperePoint panel and expand Energy in Home Assistant above the footer. It gives the exact entity ID for Charging energy.
  2. In Energy settings, add that entity as an individual device. Add each physical charger once. Session energy, last-session energy and the diagnostic power-derived energy sensor are not extra sources for the same consumption.
  3. Recorder must record the entity. The new meter starts at zero; old statistics are not merged automatically. Charts need time to collect data. The panel session cost is an estimate based on energy and the tariff, not an allocation of historical prices. Measurement and migration details.

9. Planner and solar power

The built-in planner saves weekdays, multiple time windows and a current limit for each window. Manual overrides include charging for a chosen duration or to an energy target.

The planner runs its commands in HA. Home Assistant and the charger connection must remain available when charging should stop too. Coordinate the schedule with the Tuya app and other automations to avoid conflicting commands.

From 0.6.1, PV mode can adjust current to solar surplus for a Tuya source or mapped entities. In the integration options, select PV production and signed grid power or separate import/export readings; check the units and import sign.

AmperePoint Local (LAN) entries do not have PV settings yet. The mode is off by default; this release tested the controller with synthetic data, without testing PV charging on a physical charger. PV configuration and limits.

10. Installation troubleshooting

HACS cannot find the repository or reports a missing folder

Compare the entered address with the field above and select the Integration type. Open the repository in a browser. If the error remains, save its full text, the entered address and your HA and HACS/Marketplace versions. A missing-folder message alone does not establish the cause.

AmperePoint is missing after downloading

Restart HA and refresh the browser. Then open Add integration under Devices & services and search for AmperePoint.

The wizard cannot detect the charger

Check that it is online in the app and visible in the official Tuya integration in HA. Reload Tuya if needed.

The panel reports invalid configuration or shows an old version

Perform a hard browser refresh and check the footer version. If it persists, send the error and the Lovelace resource list including types. Removing the card URL’s ?v= suffix is not a permanent fix.

Phase readings or other values are missing

Coverage depends on the model, firmware and Tuya source. A missing reading does not by itself mean setup failed.

Energy has no chart yet

Check the Charging energy entity and Recorder recording, then allow time for statistics to build.

11. Updates and other connection options

Back up HA before updating. Download the new release through HACS or the Marketplace, restart HA and refresh the panel. Check the footer version. During migration, keep working entries and check dependent automations before removing them.

Tuya Local and Xtend Tuya can be additional sources for existing or advanced setups. The Q Series setup above needs only the official Tuya integration and AmperePoint. Local control has a separate Tuya Local guide. Wallbox PRIME uses a different LAN route; see the connection guide.

If you get stuck, email hello@amperepoint.com. Include the model, firmware, HA, integration and HACS/Marketplace versions, the step and a screenshot of the full error. Do not send passwords, local keys or tokens.

Back to blog