[RELEASE] Tuya Zigbee Metering Plug (w/ healthStatus)

Kulfsson · September 9, 2023, 8:17am

Thanks, here is the information. Also, I am pairing it to a C7, which I understand does not have Zigbee 3.0, but perhaps would be able to communicate via 1.2 to the Mini Plug 2?

I also do have a C8 in the drawer, but I haven´t been comfortable starting to use it yet due to the FW issues in the past few months.

I am wondering though, if I am eventually able to pair this mini plug 2 with my C7 and they talk 1.2, would it change to 3.0 once I have the C8 installed?

EDIT: So let me add, after I re-paired the plug, it now seems to be working. I am able to turn it off/on and it is showing energy information. Previously the LED was pulsing amber and I was unable to get a reaction.

EDIT 2: Added another plug without any issues. Not sure what went wrong the first time.

kkossev · September 9, 2023, 9:39am

Yes, sometimes it takes more than one trial to pair some new Zigbee 3.0 devices to a C-8 hub.
I had success in some cases using the pairing option "Pair trying to avoid Zigbee 3.0 repeaters".

Kulfsson · September 9, 2023, 9:50am

Thanks for the information. I am still running my C7, not sure when I will be brave enough to switch to the C8. I need the WAF to stay high

A question, I have turned on temperature reporting, but nothing comes through. I suspect that the Frient plug doesn´t have these capabilities, but it does have overtemp protection, so I would think it has a temperature chip, just not exposed.

Also, as I am installing several plugs, I was wondering if you know of a way to copy settings between them so I can basically set them all the same in a quicker manner?

kkossev · September 9, 2023, 9:59am

I have the older SPLZB-131 model and I don't see it reporting the temperature... I can dig further when I have the time.

There is an HE inbuilt app "Preference Manager", but I don't use it at the moment, you can experiment with it, although I am not sure how it will handle all the custom preferences.

C-7 and C-8 have different Zigbee radios inside, so it may be expected to observe some hickups when transferring a lot of old ZIgbee devices to the new hub. I chose the manual approach - it took me some time to manually move all (or most of) my Zigbee and Z-wave devices to the new C-8 hub, but I did a lot of cleanup of unused rules, drivers, etc.. Now running both hubs in a mesh.

mboisson · September 14, 2023, 2:11am

Hi @kkossev. I am using this driver for a Third Reality outlet, and there is a definite bug with the way energy is calculated.

I have been using this outlet for 26 days. The device uses a maximum of about 500W, which would make a theoretical maximum of 312kWh in 26 days (if it was using its peak power 24 hours a day, which it is not), and the driver is reporting 394 megawatt-hour (with a cost of 23k$, at 0.06$ per kWh which is also ludicrous).

I record the power usage every minute in a Prometheus database, and based on this, the actual energy utilized by that switch over that period is 110kWh… about 4000 times lower than what the drive calculates.

Any idea what is going wrong ?

kkossev · September 17, 2023, 7:04am

Hi @mboisson ,

As this driver is aimed to support mostly the Tuya models, it has the energy reports coefficients (dividers) hardcoded into it. So it is quite possible that the Third Reality dividers are not correct..

I can recommend trying Jonathan's driver : New: Third Reality Power monitoring plug - #60 by jonathanb . You can switch temporarily to the HE inbuilt 'Device' driver to clear all states and state variables, before you assign Jonathan's driver. It is written especially for the Third Reality outlets and tested by many other users.

If it reports the energy consumption correctly , please post the State Variables, I will use the information to correct this driver too.

mboisson · September 17, 2023, 1:30pm

Thanks. I have updated my drivers to the ones you pointed to. I will keep you updated whether it works or not.

mboisson · September 18, 2023, 12:31pm

It does seem to report it correctly (or at least, it is much closer). Here are the states variables.

values : {0=2.8, 1288=0.0, 1285=121, 1291=0.0}
attributes : {1536=1, 770=3600000, 771=255, 1541=10, 1540=1, 768=0, 1539=1000, 1538=1, 1537=10}

TomG · September 28, 2023, 8:16pm

@kkossev Any update on a driver for a Tuya Zigbee power reporting plug?

I used the ‘Generic Zigbee Outlet’ driver and was able to turn it on and off with the app. Power reporting does not appear to work so I switched to the ‘Third Reality Power Meter Plug’ driver which still did not report power even though I set the threshold at 1 watt.

I see this AFTER I bought the Tuya trying to find a driver

And these are the details of the Tuya plug I bought

kkossev · October 1, 2023, 5:35am

If you have managed to pair this plug to your C-8 (it’s very difficult!) and if you can control the on/off state using the HE inbuilt generic Zigbee driver, then the Tuya driver should also work with this device. You may see a warning in the logs that it is not supported, simply ignore it for now.

Do you see anything on the live logs when you turn the plug on/off from the physical knob?

TomG · October 1, 2023, 7:59pm

I was unaware of this driver. Installed and reporting with my C-7

Thanks again.

JumpJump · October 3, 2023, 8:46pm

There is a newer Frient energy monitor out. I ordered one that should arrive later this month.

github.com/zigpy/zha-device-handlers

[Device Support Request] Frient Electricity Meter Interface2 (EMIZB-141)

opened 10:44AM - 03 Oct 23 UTC

dalte-one

### Problem description in my setup ZHA is running with the Conbee II. I mana…ged to pair the device well and a power sensor is created. But the values are completely wrong because my electricity meter works with 10000 imp/kWh. And I can not find the value _pulse configuration_ unfortunately. ### Solution description it should be possible to change the pulse rate and see a normal power consumption. ### Screenshots/Video <details><summary>Screenshots/Video</summary> [Paste/upload your media here] </details> ### Device signature <details><summary>Device signature</summary> { "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4117, maximum_buffer_size=82, maximum_incoming_transfer_size=1500, server_mask=11264, maximum_outgoing_transfer_size=1500, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)", "endpoints": { "1": { "profile_id": "0xc0c9", "device_type": "0x0001", "input_clusters": [ "0x0005", "0x0006" ], "output_clusters": [] }, "2": { "profile_id": "0x0104", "device_type": "0x0053", "input_clusters": [ "0x0000", "0x0001", "0x0003", "0x0020", "0x0702", "0x0b01", "0x0b05" ], "output_clusters": [ "0x0003", "0x000a", "0x0019" ] } }, "manufacturer": "frient A/S", "model": "EMIZB-141", "class": "zigpy.device.Device" } </details> ### Diagnostic information <details><summary>Diagnostic information</summary> "manufacturer": "frient A/S", "model": "EMIZB-141" }, "active_coordinator": false, "entities": [ { "entity_id": "sensor.powermeter1_battery", "name": "frient A/S EMIZB-141" }, { "entity_id": "button.powermeter1_identify", "name": "frient A/S EMIZB-141" }, { "entity_id": "sensor.powermeter1_instantaneous_demand", "name": "frient A/S EMIZB-141" }, { "entity_id": "sensor.powermeter1_summation_delivered", "name": "frient A/S EMIZB-141" }, { "entity_id": "switch.powermeter1_switch", "name": "frient A/S EMIZB-141" } ], "neighbors": [], "routes": [], "endpoint_names": [ { "name": "unknown 1 device_type of 0xc0c9 profile id" }, { "name": "METER_INTERFACE" } ], "user_given_name": "Powermeter1", "device_reg_id": "*******************6088", "area_id": "keller", "cluster_details": { "1": { "device_type": { "name": "unknown", "id": 1 }, "profile_id": 49353, "in_clusters": { "0x0005": { "endpoint_attribute": "scenes", "attributes": {}, "unsupported_attributes": {} }, "0x0006": { "endpoint_attribute": "on_off", "attributes": {}, "unsupported_attributes": {} } }, "out_clusters": {} }, "2": { "device_type": { "name": "METER_INTERFACE", "id": 83 }, "profile_id": 260, "in_clusters": { "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0004": { "attribute_name": "manufacturer", "value": "frient A/S" }, "0x0005": { "attribute_name": "model", "value": "EMIZB-141" } }, "unsupported_attributes": {} }, "0x0001": { "endpoint_attribute": "power", "attributes": { "0x003e": { "attribute_name": "battery_alarm_state", "value": 0 }, "0x0021": { "attribute_name": "battery_percentage_remaining", "value": 200 }, "0x0033": { "attribute_name": "battery_quantity", "value": 2 }, "0x0031": { "attribute_name": "battery_size", "value": 3 }, "0x0020": { "attribute_name": "battery_voltage", "value": 30 } }, "unsupported_attributes": {} }, "0x0003": { "endpoint_attribute": "identify", "attributes": {}, "unsupported_attributes": {} }, "0x0020": { "endpoint_attribute": "poll_control", "attributes": { "0x0000": { "attribute_name": "checkin_interval", "value": 13200 } }, "unsupported_attributes": {} }, "0x0702": { "endpoint_attribute": "smartenergy_metering", "attributes": { "0x0000": { "attribute_name": "current_summ_delivered", "value": 90956 }, "0x0304": { "attribute_name": "demand_formatting", "value": 248 }, "0x0302": { "attribute_name": "divisor", "value": 1000 }, "0x0400": { "attribute_name": "instantaneous_demand", "value": 4826 }, "0x0306": { "attribute_name": "metering_device_type", "value": 0 }, "0x0301": { "attribute_name": "multiplier", "value": 1 }, "0x0200": { "attribute_name": "status", "value": 0 }, "0x0303": { "attribute_name": "summation_formatting", "value": 248 }, "0x0300": { "attribute_name": "unit_of_measure", "value": 0 } }, "unsupported_attributes": { "0x0100": { "attribute_name": "current_tier1_summ_delivered" }, "0x0102": { "attribute_name": "current_tier2_summ_delivered" }, "0x0104": { "attribute_name": "current_tier3_summ_delivered" }, "0x0106": { "attribute_name": "current_tier4_summ_delivered" }, "0x0108": { "attribute_name": "current_tier5_summ_delivered" }, "0x010a": { "attribute_name": "current_tier6_summ_delivered" } } }, "0x0b01": { "endpoint_attribute": "meter_id", "attributes": {}, "unsupported_attributes": {} }, "0x0b05": { "endpoint_attribute": "diagnostic", "attributes": {}, "unsupported_attributes": {} } }, "out_clusters": { "0x0003": { "endpoint_attribute": "identify", "attributes": {}, "unsupported_attributes": {} }, "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} }, "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": {} } } } } } } </details> ### Logs <details><summary>Logs</summary> ```python [Paste the logs here] ``` </details> ### Custom quirk <details><summary>Custom quirk</summary> ```python [Paste your custom quirk here] ``` </details> [### Additional information] https://www.develcoproducts.com/media/5110/emizb-141-technical-manual.pdf https://github.com/Koenkk/zigbee2mqtt/issues/19042 _No response_

kkossev · October 4, 2023, 9:24am

Develco are one of the few Zigbee devices manufacturers that provide technical documentation for their products.

kkossev · October 4, 2023, 11:25am

A sneak peek of the next version - what are the latest HE platform 'Status' column capabilities ...

JumpJump · October 4, 2023, 12:32pm

They are clearly an engineering company and high quality OEM. Do you know who they manufacture for other than Frient?

kkossev · October 4, 2023, 12:36pm

I think Frient is the only one.

velvetfoot · October 4, 2023, 12:44pm

So, do you think that Frient would be a company to look for when purchasing new Zigbee stuff, with an eye to quality, even if somewhat more expensive?

JumpJump · October 4, 2023, 1:31pm

I'm located in the US. So far it doesn't look like Frient has a US distributor even though they have an office in CA. It's probably just a token engineering office or perhaps the investment folks.

Not sure if you are a technical person, but their docs are detailed enough to generate drivers for HE.

velvetfoot · October 4, 2023, 1:40pm

It'd have to take a fair amount of study for me to get into this. Maybe over the winter.

JumpJump · October 13, 2023, 11:19pm

@kkossev FYI: I received my Frient Monitor 2 and grabbed your driver.

I made one edit of this line:

private boolean isDevelco() { device.getDataValue("model") == "EMIZB-132" }

to
private boolean isDevelco() { device.getDataValue("model") == "EMIZB-141" }

And it seems to work. I have not put it through many tests though.

I'm saddened that this device isn't waterproof at all. Looks like its meant for the indoors. Probably why it's not sold in the US where almost all meters are outdoors. I'll have to extend the sensor leads and waterproof the sensor with some conformal coatings etc.