Energy metrics not working in Home assistant? (TS011F - _TZ3000_typdpbpg)

Hi,

I just received two smart plugs (Device _TZ3000_typdpbpg, model TS011F). Adding them as Sensor using Phoscon (from Home Assistant) works, but they show up under Lights and not Sensors.

When I use deCONZ I can select the On/Off plugin unit and read the Electrical Measurement (RMS Voltage and RMS Current).

In Home Assistant a Device 'On/Off plug-in unit' is created. And I'm able to control the On/Off switch.
Also two entities (Consumption and Power) are created, but they don't get updated.

I'm using HA version 2022.2.9, deCONZ (Add-on version 6.12.0 (with auto-update on), deCONZ version 2.14.1), with a Conbee II stick.

How can I get the Energy metrics working in Home Assistant?

Regards,
Guido

Same issue.

Device info

TS011F
by _TZ3000_u5u4cakc

Zigbee info

Quirk: zhaquirks.tuya.ts011f_plug.Plug

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x010a",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0702",
        "0x0b04",
        "0xe000",
        "0xe001"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZ3000_u5u4cakc",
  "model": "TS011F",
  "class": "zhaquirks.tuya.ts011f_plug.Plug"
}

There is just one step, no update since

Home Assistant 2022.3.5

Nothing too exciting about the Energy endopint in the quirks

This looks relevant.

How can I check if this is already merged in my version?

PS: This workaround via zha-toolkit works Add support for Polled clusters and use it for ts011f plug Metering by 3v1n0 ¡ Pull Request #1226 ¡ zigpy/zha-device-handlers ¡ GitHub

automation

id: '1647956180789'
alias: Update boiler energy reading
description: ''
trigger:
  - platform: time_pattern
    minutes: /5
condition: []
action:
  - service: zha_toolkit.attr_read
    data:
      ieee: sensor.boilerzb_smartenergy_metering_summation_delivered
      cluster: 1794
      attribute: 0
mode: single
1 Like

Have you added the quirk by manually copy to custom quirks path added in HA’s YAML configuration?

https://www.home-assistant.io/integrations/zha#configuration—yaml

If not then it has not been added as its “open” not even merged (closed as “merged”) or released

https://github.com/zigpy/zha-device-handlers/pulls?q=is%3Apr+is%3Aclosed

https://github.com/zigpy/zha-device-handlers/releases

Only after it is part of a release version can it be added to future version of ZHA in Home Assistant core:

https://github.com/home-assistant/core/pulls?q=is%3Apr+zha

Thanks for the explanation.

The workaround works quite well. I think I will just watch the issue and hope it will be merged soon. :blush:

I have the same issue too, I tried new install and tried to poll state from Node red flow every minute thinking that i will be grab the info from the smart plug directly, but the value does not change, The poll state node seems to get always the same value. It only gets updated when restarting HA, which means that it can be fixed from HA.
I’d like stay away from Quirks as much as possible, I really hope there will be a fix soon as I have ordered 8 Plugs to monitor energy for most of my appliances at home.

Hope if someone knows when a fix for this issue can be integrated into HA / expected date.

Devices that deviate from the standard and do not follow the Zigbee specifications will always need quirks, but you will not need to manually add a custom qurik as long as someone already submitted a quirk that has both been merged into https://github.com/zigpy/zha-device-handlers/ and is part of a zha-quirks release version that to be updated in Home Assistant core.

https://github.com/zigpy/zha-device-handlers/pull/1226

If not then you need to manually add that as a custom quirk. Again, if your specific device ID is not covered by that then make sure it’s reported as a “Device support request” for reference and tracking:

https://github.com/zigpy/zha-device-handlers/issues

You can read why this is the case here:

https://www.home-assistant.io/integrations/zha#zha-exception-and-deviation-handling

Note that quirks should not be needed for standard devices that follow the Zigbee specifications:

https://www.home-assistant.io/integrations/zha#knowing-which-devices-are-supported

PS: Something similar is done for all Zigbee solutions/platforms, so this is not just a ZHA thing.

But I suppose the quirks will end up in ZHA when they are merged upstream?

I just didn’t want to bother with custom quirks if the fix is already in the pipeline and the workaround cheap and easy.

Yes, zha-quirks releases get updated (“bumped”) for the ZHA component inside Home Assistant core:

https://github.com/zigpy/zha-device-handlers/releases

https://pypi.org/project/zha-quirks/

https://github.com/home-assistant/core/pulls?q=is%3Apr+zha+AND+quirks

Merged pull requests (closed as accepted) usually get put into a new zha-quirks release once a month:

https://github.com/zigpy/zha-device-handlers/pulls?q=

It then sometimes take another month or so before devs bump a new zha-quirks released in HA core.

If there is not an open or closed as an accepted pull request then can assume that it is not in pipeline:

https://github.com/zigpy/zha-device-handlers/issues?q=is%3Aopen+is%3Apr

https://github.com/zigpy/zha-device-handlers/pulls?q=is%3Apr+is%3Aclosed

Still, best is always to check existing issues if there is any custom quirks being work on pre-merging:

https://github.com/zigpy/zha-device-handlers/issues

1 Like

same here!

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x010a",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0702",
        "0x0b04",
        "0xe000",
        "0xe001"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZ3000_w0qqde0g",
  "model": "TS011F",
  "class": "zhaquirks.tuya.ts011f_plug.Plug"
}

I have another issue with the same plugs, specifically each of my six Tuya plugs behaves the same way. In regular periods, the measurement drops to 0kW for exactly 5 seconds. Then it measures again.

Detail:

Isn’t this behavior related to the one discussed here? I am using Z2M with Sonoff coordinator.

Z2M reports it as _TZ3000_gvn91tmx and firmware is updated. Z2M does not report the firmware version.

Im having the same issue, but im using the ZHA intergration:

Would this have something to do with the polling of the information?