Overview

A huge number of budget smart home brands — including Energizer, and many unbranded devices sold on marketplaces — actually run on the same underlying Tuya platform. Instead of juggling a different app for every rebranded product, integrating them into Home Assistant via Tuya lets you manage them all from one place, alongside every other device in your setup.

This guide covers connecting Tuya-based devices (including Energizer-branded hardware) to an existing Home Assistant instance.

Requirements

  • Home Assistant already installed and running (see my Home Assistant on Proxmox guide if you haven’t set this up yet).
  • Tuya-based device(s) already set up and working in their original app (Tuya Smart, Smart Life, or a rebranded equivalent like the Energizer Connect app).
  • A Tuya IoT Platform account — required to generate the API credentials Home Assistant needs to authenticate.

🌐 Prerequisite: Setting up a free Tuya IoT Platform project (to obtain your Client ID and Secret) takes a few extra minutes compared to Tapo — this is normal for Tuya-based integrations and only needs to be done once.

Procedure

  1. Create a free account at the Tuya IoT Platform and set up a new Cloud Project.
  2. Link the account you use in your device’s app (Tuya Smart / Smart Life / Energizer Connect) to this new Cloud Project — this step is required for the API to see your existing devices.
  3. From your Cloud Project, note down the Client ID and Client Secret — you’ll need both in the next step.
  4. In Home Assistant, go to Settings → Devices & Services.
  5. Click Add Integration and search for Tuya.
  6. Enter your Client ID, Client Secret, and select the correct data center region for your account.
  7. Once authenticated, Home Assistant will pull in all devices linked to that Tuya account, ready to add to dashboards and automations.
  8. Test by toggling a device directly from the Home Assistant UI to confirm the connection is live.

Notes

  • The Tuya cloud integration relies on TP-Link’s/Tuya’s servers being reachable — expect slightly higher latency than fully local integrations like Zigbee.
  • If a device doesn’t appear after linking, confirm it’s shared under the same Tuya account used to create the Cloud Project.