TZ3000_bfn1w0mm no metering (TS011F Family)

Bought this item (https://it.aliexpress.com/item/1005003741939416.html?gatewayAdapt=glo2ita&spm=a2g0o.9042311.0.0.10124c4dhYaVI8) a 20Amp smart plug tuya Zigbee.
Model TZ3000_bfn1w0mm as shown on HA. No metering present.
Other similar products (i.e. TZ3000_bfn1w0mm same TS011F family but 16amp smart plug) have working metering!

Describe the solution you’d like
It would be appreciated if metering could be added to this new variant of the smart plug.

code


{
"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_gjnozsaz",
"model": "TS011F",
"class": "zhaquirks.tuya.ts011f_plug.Plug"
}

Anybody has a solution?:grinning_face_with_smiling_eyes:

Hello, this line tells me that it has actually been recognised correctly. That class does seem to include the electrical metering that you are looking for.

I wonder whether the entities under diagnostics marked as unavailable are the electrical measurement items. Maybe there was a problem during pairing, and you need to retry? I have devices that don’t pair properly unless they are really close to the Zigbee coordinator.

Post a issue to “ZHA Device Handlers” (if one does not already exist) or extend quirk and submit PR:

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

Each new variant might need the quirk to be tweaked since Tuya keeps deviating in most of its devices:

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

Hi, no…the hidden entities are radio quality sensors (never seen them before on other zigbee devices).
I think it is to do with som zha compatibility?

Okay, there is usually one of those.

Did you try repairing the device really close to the coordinator?

Yes but not changing. Still no metering

There’s many different variants of almost every Tuya device so existing quirk probably needs tweaking.

ZHA Device Handlers “quirks” is needed when device don’t follow Zigbee Cluster Library specifications:

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

https://www.home-assistant.io/integrations/zha#reporting-issues

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

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

These parse/translate/convert non-standard messages to ZCL R6 or R7 (ZCL6/ZCL7) specifications:

https://zigbeealliance.org/wp-content/uploads/2019/12/07-5123-06-zigbee-cluster-library-specification.pdf

PS: Zigbee2MQTT equivalent to zha-device-handlers/zha-quirks is called zigbee-herdsman-converters:

https://www.zigbee2mqtt.io/advanced/support-new-devices/01_support_new_devices.html

https://github.com/Koenkk/zigbee-herdsman-converters