Tuya local plug options

Configuration
1

I'm trying out the different versions of tuya

localTuya seems to just let you link up data points to different things And then it's up to you to choose the correct units and whether it's a selection etc.

Tuya local Makes You choose specific names of items and adds it as a complete device.

I'm trying to add some smart plugs how am I supposed to know which type it is?
and how can I try different types without deleting and adding again which takes about four or 5 minutes each time

image
image529×781 46.5 KB

I have two types of smart plug at the moment one is the Brilliant Smart Smart Plug.
together is a generic Ali one which has energy monitoring

2

That dropdown is doing you a favor. Tuya Local pre-filters the 1000+ profiles down to the ones whose data points partially match your device, so the entries near the top are your real candidates and the stuff further down (aroma diffuser, vacuum, window sensor) is just weak matches on a shared DP. No blind guessing needed, and the highlighted top entry is its best guess.

For an energy-monitoring plug, your candidates are the "Energy monitoring smartplug" group at the top:

  • smartplugv2_energy (the highlighted one, start here)
  • smartplugv2_energyv3
  • smartplugv2
  • smartplugv2_polled_power (use this if power/current read 0 until polled)

Ignore the "Energy meter" entries (those are clamp / DIN-rail meters, not plugs) and everything from the aroma diffuser down.

How to pick efficiently:

  1. Apply the highlighted smartplugv2_energy first. Confirm you get switch + power (W) + voltage + current + energy (kWh), with sane values (voltage ~230-240, power tracking the load).
  2. If a sensor is missing or stuck at 0, try the next variant. _energy / energyv3 differ mainly in the cumulative-energy DP layout; _polled_power is for plugs that only report power when asked.

To switch profiles without the 4-5 minute re-add: edit config/.storage/core.config_entries, find your device, change "type": "smartplugv2_energy" to the next one, save, and restart HA. Same connection details, new profile. (Back the file up first.)

If none line up cleanly, that's the case for LocalTuya instead, where there's no profile to guess: it shows the DPs and you map them yourself (switch on DP1, power DP19 ÷10 for W, voltage DP20 ÷10 for V, current DP18 ÷1000 for A).

For your plain Brilliant plug, it'll show its own shorter filtered list. If it has no energy reporting, smart_p01_socket or simple_switch will be the match.

The bulletproof way to be certain is the product_id: each profile declares the product_ids it supports, so if you pull your plug's product_id you can match it exactly instead of by trial and error.

3

in the case where it has some items which my device does not support and it's grayed out, Is it safe to just leave it?

I was wondering whether my goal was to find something that was an exact match

sometimes the detection seems to be wrong this is smart plug with energy but it's not showing the option

image
image562×560 15.2 KB

or is it just a fact you need to use a mix of [Tuya local] and LocalTuya? it seems like no single thing works consistently for everything

4

Is it just me or is using a smart plug on the freezer not really a good idea?
And especially if it's an tuya.

5

Grayed-out / unsupported entities: yes, safe to leave. When a profile includes a data point your particular model doesn't have, that entity just shows up unavailable. It does no harm, it simply never gets data. If the clutter bugs you, disable or hide those entities in HA. Nothing to worry about.

You don't need an exact product match, but you do want a good DP match. The goal isn't a profile literally named for your exact plug, it's one that maps the data points you actually care about (the switch plus power / voltage / current / energy). A close functional match is fine. What you want to avoid is a poor match where either your real DPs aren't mapped (you lose those readings) or a DP gets mapped to the wrong type/scale (wrong values). So match on the data points, not the name.

The wrong detection is the real issue here. That list (remote controller, pet feeder, curtain, keypad lock, water leak, doorbell) means it found almost no real overlap and is just showing weak partial matches. For an energy plug that almost always means the device hadn't reported its energy data points yet at the moment of detection, so the matcher only saw a generic switch DP. A few things to try:

  • Put a load on the plug, turn it on, give it a minute, then run detection again. Many Tuya plugs only report power/voltage/current once they've measured a load or been polled, and the energy smartplug profiles won't surface until those DPs show up.
  • Check the protocol version. If it's on auto and your plug is 3.4/3.5, the DPs can come through garbled and throw the matcher off. Try pinning the correct version.
  • Don't pick any of those unrelated types in the screenshot, they won't map your plug's DPs and you'll just end up with a wrong device.

If it still won't offer an energy-smartplug profile after that, this is exactly when LocalTuya is the better tool: no detection, you just map the DPs yourself (switch on DP1, power DP19 ÷10 for W, voltage DP20 ÷10 for V, current DP18 ÷1000 for A). The surest way to settle it either way is to look at the actual DPs your plug exposes (LocalTuya or the tuya-local debug shows them), or match by product_id.

Grabbing the product_id: easiest is tuya-cli wizard (the npm tool), which lists every device with its id, local_key, and product_id in one go. If you have the official Tuya cloud integration in HA, the device's diagnostics download shows it too, and tuya-local often logs the detected product_id in its debug log when you add the device. Once you have it, search the tuya-local repo under custom_components/tuya_local/devices/ for that id to find the profile built for your exact plug.