The official AmperePoint Q Series device profile has been accepted into the main tuya-local repository. This gives Home Assistant a direct local-network connection to supported chargers, so routine readings and commands do not have to travel through the Tuya cloud.
Availability: the AmperePoint profile has been merged into the main tuya-local repository, but it is not included in stable release 2026.7.2. Before installing, check HACS for a later release whose notes include PR #5595.
What does local integration change?
Once configured, Home Assistant communicates with the charger over your LAN. tuya-local recognises supported Q Series variants using their Tuya product identifiers and the data points actually exposed by the device. Depending on the charger firmware and available data points, the profile can provide:
- charging and vehicle-connection status,
- start and stop control, current limit and charging mode,
- live power, session energy and total energy,
- temperature, faults and diagnostics,
- target energy and schedule data when supplied by the charger,
- phase measurements as optional diagnostic entities.
The profile contains the product identifiers from AmperePoint's Tuya manufacturer account, including older products that we continue to support. It is intentionally one AmperePoint Q Series profile rather than a set of profiles based on commercial model suffixes. The actual data points determine which optional entities appear.
Before you begin
- Home Assistant with HACS installed,
- a tuya-local release newer than 2026.7.2 that includes PR #5595,
- an AmperePoint Q Series charger already added to the official Smart Life or Tuya Smart app,
- Home Assistant and the charger on the same LAN, or on routed networks that permit communication between them,
- access to your router if automatic IP discovery does not find the charger.
Recommended: create a DHCP reservation for the charger. Automatic discovery is supported, but a fixed lease avoids problems after a router restart.
Do you need a Tuya Developer account?
Not for the recommended setup. The current tuya-local configuration flow can authorise access with a user code and a QR code from the Smart Life or Tuya Smart app. It retrieves the Device ID and Local Key and tries to discover the charger on the LAN. The tuya-local documentation explicitly states that this method does not require your own Tuya IoT Developer Platform account.
The cloud-assisted setup uses Tuya only during onboarding to retrieve device credentials. After configuration, routine readings and commands are exchanged locally. The charger may still maintain its own connection to Tuya; installing tuya-local does not automatically block Internet access.
1. Install or update tuya-local
- Open HACS → Integrations in Home Assistant.
- Search for Tuya Local from
make-all/tuya-local. - If it is not listed, add
https://github.com/make-all/tuya-localas a custom HACS repository in the Integration category. - Install tuya-local, or update it to a release that contains the AmperePoint profile.
- Restart Home Assistant. Downloading Python integration files in HACS does not load them until Home Assistant restarts.
2. Add the charger without a Developer account
- Go to Settings → Devices & services → Integrations.
- Select Add integration, search for Tuya Local and start the configuration.
- Choose the cloud-assisted SmartLife device setup. The flow will retrieve the Device ID and Local Key and attempt to find the device IP address.
- In Smart Life or Tuya Smart, open Me → Settings → Account and Security → User Code. Labels may differ slightly between app versions and languages.
- Enter the user code in tuya-local. Home Assistant will display a QR code.
- Scan the QR code with the scanner in the same Smart Life or Tuya Smart account that contains the charger, then approve the login.
- Return to Home Assistant and select the charger from your account's device list.
- Check the automatically filled Device ID and Local Key. If no IP address is found, enter the address shown in your router's DHCP client list.
- Start with the protocol version set to auto.
- Select the EV charger device profile. A successful match should show manufacturer AmperePoint and model Q Series.
If you are adding several chargers from the same Tuya account, the short-lived authorisation token can normally be reused until Home Assistant is restarted. Each charger still receives its own configuration entry and entities.
Security: never publish your Device ID, Local Key, user code or QR code. Pairing the charger again in the vendor app changes its Local Key, so the tuya-local entry must then be configured again.
Advanced alternative: Tuya Developer Platform and TinyTuya
This route is not required for a normal tuya-local installation. It can be useful for manual credential retrieval, data-point diagnostics or TinyTuya.
- Create an account at the Tuya Developer Platform and open Cloud → Development.
- Create a cloud project using the Smart Home development method.
- Select the data centre that serves the region configured in your Smart Life or Tuya Smart account. A mismatched region is a common reason for an empty device list.
- If requested, authorise the basic Smart Home API services required by the project wizard.
- Open Devices → Link Tuya App Account → Add App Account, scan the QR code with the app that contains the charger and approve the link.
- Find the charger in the device list and save its Device ID.
- Use Cloud → API Explorer → Device Management → Query Device Details in Bulk to retrieve the
local_key. - Read the IP address from your router and enter the host, Device ID and Local Key in tuya-local's manual setup. Start with protocol auto.
Tuya's free cloud-project entitlements and their duration may change. If the API does not return a Local Key, use the recommended QR flow. TinyTuya can also use the project's Access ID, Access Secret, a Device ID and the correct region to retrieve devices and scan the LAN. Treat all of these values as credentials.
3. Check the entities and test the connection
Open the device page in Home Assistant. The exact entity set depends on the charger firmware and data points. Optional measurements are only created when the charger actually supplies them.
- Confirm that the device is available and basic readings update.
- With no vehicle connected, test the current limit and start/stop control. The corresponding entity should confirm the new value after a few seconds.
- Restart Home Assistant and verify that the charger returns online without being configured again.
- If something fails, check Settings → System → Logs and search for
tuya_localbefore deleting the integration entry.
4. Use the local entities with the AmperePoint dashboard
tuya-local and TuyaExtend AmperePoint have different roles. tuya-local communicates with the charger over the LAN and creates Home Assistant entities. Our AmperePoint integration organises those values into an EV-focused interface with a dashboard, weekly planner, manual overrides, next-action preview and command confirmation.
Add or edit an AmperePoint integration entry and select the tuya-local entities as its source. The dashboard is described in our companion guide: AmperePoint Q Series dashboard and charging planner in Home Assistant.
Troubleshooting
The AmperePoint profile is missing
Check the installed tuya-local version. Stable release 2026.7.2 does not yet contain the profile; you need a later release that includes PR #5595. A profile present on the GitHub main branch is not automatically present in the release downloaded by HACS.
The charger is not listed after QR authorisation
Scan the QR code with the same official Smart Life or Tuya Smart account that owns the charger. An OEM-branded app may not work with this flow. For the Developer Platform route, check the app region, project data centre and app-account link.
Automatic discovery cannot find the IP address
Enter the address from your router's DHCP list. Discovery may be affected by VLANs, guest networks, Wi-Fi client isolation, multiple subnets, an open Tuya app or another local integration connected to the charger. Create a DHCP reservation instead of leaving a changing address.
The charger is unavailable
Check routing between Home Assistant and the charger, confirm that the IP address has not changed, and make sure another local integration is not holding a parallel connection. Close the Tuya app, reload the integration entry and check the LAN firewall rules.
Readings work but commands fail
Verify the Local Key and protocol version. An incorrect key can sometimes allow limited discovery while preventing control. If auto is unstable, test the protocol version identified by tuya-local and consult the project documentation.
It stopped working after the charger was paired again
This is expected: Tuya generates a new Local Key when a device is paired again. Reconfigure the tuya-local entry with the current key.
Updates and support
The AmperePoint profile is part of the upstream tuya-local project, so future fixes can reach users through normal HACS updates. We will maintain compatibility with supported Q Series variants. If a charger is not recognised or an entity available in the Tuya app is missing, report it in the AmperePoint issue tracker. Include the tuya-local version and charger firmware, but never include a Device ID, Local Key or login data.
Technical references
- AmperePoint profile — tuya-local PR #5595
- tuya-local installation and configuration
- Manual Device ID and Local Key retrieval
- Tuya Smart Home cloud project documentation
- Linking an app account to a Tuya project
- TuyaExtend AmperePoint on GitHub
tuya-local and Home Assistant are community projects and are not owned by AmperePoint. Work on an electrical installation must be carried out by a suitably qualified person. A software current limit does not replace correctly designed wiring, protection or the manufacturer's safety instructions.
