Tuya TS011F_plug_3 detected as TS011F_plug_1 (probably)

[Pathen85]

Hey,
so I bought the Tuya Plug with energy monitoring capabilities. When I connect it to Z2M it gets immediately picked up as TS011F_plug_1

According to the Z2M website, this device works by reporting its energy status in a set interval. However, for me it just reported Null for the power, current, voltage and energy values. On/Off works fine. So what I did was opening the Dev Console and poll the mentioned values from the device.

As you can see, the plug correctly measures those paremeters and responds to my poll. After that those values show up under 'Details', however they won't refresh on their own.

As you can see in the screenshot, the plug is turned off but still shows the same values. So what I assume happened here, is that I got the plug with the newer firmware that doesn't suppot automatic reporting, but it was somehow still detected as plug_1. Is there any way to tell Z2M to handle it as plug_3? Or am I able to set up automatic polling for this plug?

Thanks in advance!
Henrik

[Koenkk]

Can you provide the data/database.db entry of this plug?

[Pathen85]

Of course! Thanks for looking into this!

{
  "id": 28,
  "type": "Router",
  "ieeeAddr": "0x70b3d52b6001bc58",
  "nwkAddr": 14003,
  "manufId": 4660,
  "manufName": "_TZ3000_okaz9tjs",
  "powerSource": "Mains (single phase)",
  "modelId": "TS011F",
  "epList": [
    1
  ],
  "endpoints": {
    "1": {
      "profId": 260,
      "epId": 1,
      "devId": 81,
      "inClusterList": [
        0,
        6,
        3,
        4,
        5,
        57345,
        2820,
        1794
      ],
      "outClusterList": [],
      "clusters": {
        "genBasic": {
          "attributes": {
            "manufacturerName": "_TZ3000_okaz9tjs",
            "zclVersion": 2,
            "appVersion": 100,
            "modelId": "TS011F",
            "powerSource": 1
          }
        },
        "haElectricalMeasurement": {
          "attributes": {
            "activePower": 3,
            "rmsVoltage": 227,
            "rmsCurrent": 23
          }
        },
        "genOnOff": {
          "attributes": {
            "onOff": 1
          }
        },
        "seMetering": {
          "attributes": {
            "currentSummDelivered": [
              0,
              1
            ]
          }
        }
      },
      "binds": [
        {
          "cluster": 6,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0029dedea9",
          "endpointID": 1
        },
        {
          "cluster": 2820,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0029dedea9",
          "endpointID": 1
        },
        {
          "cluster": 1794,
          "type": "endpoint",
          "deviceIeeeAddress": "0x00124b0029dedea9",
          "endpointID": 1
        }
      ],
      "configuredReportings": [],
      "meta": {}
    }
  },
  "appVersion": 100,
  "stackVersion": 1,
  "hwVersion": 3,
  "dateCode": "20210625",
  "swBuildId": "20B+TZSKT11BS108",
  "zclVersion": 2,
  "interviewCompleted": true,
  "meta": {},
  "lastSeen": 1673468096862,
  "defaultSendRequestWhen": "immediate"
}

[Koenkk]

This has already been fixed in the dev branch and the fix will be include in the 1 February release. (https://www.zigbee2mqtt.io/advanced/more/switch-to-dev-branch.html)

[Pathen85]

Thanks for the info and I appreciate you taking your time to look into this!

[Pathen85]

I switched to the dev branch and it works now.