[Device Support Request] _TZE204_ac0fhfiq TS0601 BiDirectional ZigBee Energy Meter with 150A Clamp Current Sensor #2420
Comments
stombi
changed the title
|
I am also looking to get this device supported. The seller mentioned that they could provide configuration assistance for z2m so I have asked them for this information, if I get a response I will share it here. |
|
I just got one of those. I tried to make it work by adding a TS0601.js file with the parameters for a _TZE204_cjbofhxw : `const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const fzLocal = { const definition = { module.exports = definition;` I modified the model. The energy value (datapoint 101) works (seems to work). But the rest is either null or 0 when I try other datapoints. Hope this helps. |
|
Most likely the same quirk can be used as the one resulting from #1973. Probably only need to add the additional device name. |
|
I'm really new to this, I know nothing about Zigbee, I couldnt get #1973 to work. I managed to use @jkfamillerosier TS0601.js , I found out that you need to have current in the wire with the clamp before you pair the device. Then it gave me another datapoint 102 wich is 0 or 0.1 depending on the direction of the clamp. The energy datapoint 101 seems ok, it gave me 0.03Kwh The sort of "manual" that came with the device gives a hint about how to see the way the current is going, apparently the end number of power I guess is supposed to be 1 or 0 |
I took the quirk from that issue and changed the MODELS_INFO in TuyaPowerMeter to: After removing the device, deleting pycache, restarting and re-pairing, the quirk is not shown in the device. |
|
I did some testing with this js , 101 datapoint is definitly the instantaneous power in W (mesured with a fan with 3 speed buttons 35W/41W/49W) |
Did you define the custom_quirks_path in your configuration.yaml as described f.e. here? |
|
Yep, I even have enable_quirks out of desperation. In the logs for HA I do see "Loaded custom quirks". Are there normally further log messages about custom quirks? |
Is working OK in my test systems and getting tuya DP commands in the log. |
|
Thanks @MattWestb, I have at least got the quirk loaded now. In my logs I saw the following: So I added the missing endpoint (242) to the #1973 quirk with and this to the ENDPOINTS dictionary Which gets me to this Does the need for this additional endpoint possibly suggest I have a different variant? There are about 30 of these, are they the problem? |
|
EDIT: As shown in later posts, the quirk file listed in this message (from #1973) does NOT work for the _TZE204_ac0fhfiq device. I do leave my original message as reference used when starting the discussion, but it's contents should NOT be used for this device by readers.
|
2023.5.4
My quirk is identical to that, except for the model identifier and the
The clamp is attached to the main live line entering my house, I have also tried the neutral line.
I have restarted several times since adding the device, no new entities have appeared
[zigpy.appdb] Current database version is v11 (table version v11)
I also have some zb tuya monitoring plugs that are working but also show the power factor as Unknown, so I guess that is a "feature" In the logs did see a number I made the following changes to the datapoints (converters removed for now), the Some progress... The active power seems to be correct. Turning on an electric shower increased the value to ~10KW. I have no experience with quirks or python so I have no idea what I am doing lol. @stombi, how did you identify the datapoints? Are they all showing the correct values for you? How are these datapoints supposed to work? |
I know nothing, I'm discovering about all this because my device didnt work :-) @reef-actor can you share your quirk file to see if it works on my system? |
|
|
Thank you! Same as before for me it throws an error, unfortunatly I know almost nothing about python |
|
Is is possible you are using an older version? dp_type was removed recently (and caused a lot of people using custom quirks to see errors like yours) . If you search in the quirk file in this comment and search for dp_type you will see where you need to add them. Bear in mind you will need to remove them again if you update... |
|
This code works for me. This code works for me, I can't change the name for current and voltage, which gives consumption and production |
|
I have found that changing datapoint 1 & 2 to the following I can also get the summation delivered (i.e. total energy consumption) [Updated with x10 scaling factors for correct values] |
|
So far the Active Power and Summation Delivered/Received values seem to be good, but my logs were filled with the errors like these (filtered for clarity): I noticed in another tuya energy quirk they are using a definition like this With a bit of playing around I have datapoint 6 to Which results in The rms_current value is not quite right though (!). By my calculation in this instance it should be about 10.5A, And I can't understand why active_power is creating errors as it seems to be reporting the correct values in HA. |
|
Just in case you don't have this: |
|
Thanks @fred-c1 The result is this Neither seem quite right to me? Perhaps I misunderstand ac power calculations? |
|
@reef-actor : I also bought a unit here: Debug info from zigbee2mqtt: The above table was provided by the seller last week. (Active) power = RMS_voltage * RMS_current only works for pure sine waves with no delay For active power, you should use dpID 101 and 102 |
|
So I think I have a working datapoint definition.
The current value returned seems to not require /1000 as the document states (maybe HA is doing some conversion of its own?). So now I have:
I don't have any power generation, which I think is why I don't see Summation received or the power direction indication in HA. If anyone has experience in tidying this up and getting it prepared for pushing upstream without stomping over the existing ts601_din_power.py, I think it is ready. Full quirk: |
|
1 small correction: |
|
dpID 1 and 2 updated: |
|
Hi @reef-actor I am trying to setup a different device but it is very similar to the device that you have been working with. I have a 3-phase Tuya Power Meter. It is not bidirectional, not sure if this is important. I used your quirk and after changing MODELS_INFO and manufacturer_code ZHA accepted this quirk for my device. Do you have any ideas what I should do next to make it work? I am glad that I did not switched my network from ZHA to zigbee2mqtt because it looks like this device works fine there. Or created a Tuya gateway and connected it to HA, which is not cool and not secure solution anyway. I had no experience in quirks or python before but I learn fast so hope to solve it instead of buying another power meter. I got this far anyway. |
|
Enable debug logging as described here. The device is probably using different endpoint IDs (data items like voltage, current, power are "endpoints"). With the logging enabled you might see some messages like "unhandled/undefined endpoint" (unsure of the exact wording) in the HA log. Without a device datasheet it is a guessing game for which data point is which value and what scaling needs to be applied. In the case of the device this issue is originally about current and voltage are combined in one endpoint which required picking out specific bytes from the endpoint value which would have been close to impossible without the datasheet. Try changing the endpoint IDs with the ones you see in your HA logs, delete the pycache dir and restart HA. Hopefully you will start to see some new entities and you can work out which values are which. Good luck! (Oh, and for power factor, I think it is added by default. I have never seen it provide any value for any of my power monitors so just disable the entity) |
Thank you for all your suggestions! I got it working! Used attribute 1 to get total consumed kW and attribute 6 to get rms_current and rms_voltage. Was not able to get data for all 3 phases but not really need it right now, can just use the total data since I got only one phase connected anyway. See some other values in logs - lots of zeroes - that are probable other phase data. Got value 50 - that is probably 50Hz. Obviously got some results only 10 minutes after I ordered a 1-phase power meter because found a working quirk for it somewhere in another issue. Classic I now understand a bit better how the world works and will be joining a club for python haters tomorrow. P.S. Can't get active power without voodoo magic but can probably do this and it will work fine. Not sure about RMS and non-RMS though and will I get correct power out of it, need to google that later. that looks horrible but not sure if this can be done any other way P.P.S. It looks like to get any values (even if your quirk is correct) you need to add a device, make sure that it uses your quirk and then reboot HA. Others you will get stuck with only Power Factor sensor being unknown and no other sensors P.P.P.S. Is there a way to calculate summation power together with some static value that can be changed in HA ? |
|
For calculating active power, I unfortunately think you're right about AC, it's not so straightforward. If I remember the formula involves the power factor. The power factor or the values needed to calculate it (phase angle?) aren't exposed, so if you want an accurate active power value it needs to come from the monitor. I was also thinking about the possibility of syncing the sum delivered to the actual meter. It's possible that there may be a zb command to overwrite the stored value, but my current idea is a template sensor with an offset value. |
Actually, since we are getting RMS values it means that we can just do rms_current * rms_voltage and get the correct value. If it was not-RMS - then yea, it would be a problem. And this is just for one phase only (but I only have one phase in the house so it is ok). I have checked it with 5kW heater and it is very accurate. And since it is not something that we increment and the error can stack - I think I will use this for now |
|
For syncing with the actual meter, HA has the utility meter helper which has a "calibrate" service to which you give the reading on your meter so they match up. |
|
oh yea, thx for that hint. I created all types of energy meters that can reset daily hourly and monthly and even a day/night tarries. P.S. after setting up all the energy meters and stuff I found out the Power panel/dashboard and it does this automatically based on summation counter and shows it so much better then normal UI's that I created in the main panel |
|
@reef-actor Any idea how to show 3 pairs of data for this device? Actually 4 - 3 phases and 1 total. Like "RMS Voltage A", "RMS Voltage B", etc I have an idea of how to find correct datapoint IDs for all the data : writing a script that will look at logs and show me some info and I will be able to see what is what based on that. But without the ability to create datapoints for different phases - that would be pointless. |
@reef-actor have you had to update the quirk? Using your one, my Active Power is off and the Summation is always 0
|
|
Still working for me. Looking at the log message, dp102 is for the power direction (which didn't show for me because I have no solar etc). Could be worth seeing what happens if you turn the clamp to face the other direction? |
I don't have solar ether. I turned it around and have the same issue. These devices are really weird |
|
Hi, |
I think that is just the behaviour of the official app. Over zigbee the direction comes in as a seperate datapoint (DP102, line 177 in this quirk). However I have no energy production equipment to test against so have not seen this value received - it might need more work. |
|
no it isn't another endpoint : the DP102 is not provided by the device (in my case). The summation delivered only increase if this third digit is 1. |
|
Hi, how a can report the value of current_summ_received in HA that could see into the zigbee tool ? I confirm the information of "lesissous" we could sse the direction of the current into the field "rms_current" |
|
Hi, In the quick I made the rms current relative in order to create a helper in HA that will apply the sign to the power. The last decimal of the current seem to be the only way to get the direction... 6: DPToAttributeMapping(
TuyaPowerMeasurement.ep_attribute,
("rms_current","rms_voltage"),
converter=lambda x: (
(int.from_bytes(x.serialize()[-6:-3], "big")) * (((int.from_bytes(x.serialize()[-6:-3], "big")) % 2) * 2 - 1),
(int.from_bytes(x.serialize()[-8:-6], "big")) / 10,
),
),In HA I created a helper with a template (I used the default device name) don't use this version, a better one is available at the end of the comment : It uses the rms current divided by its absolute value in order to get the sign. Then It's multiplied to the active power to get the relative power. I'm quite new to HA so there is certainly a more elegant solution. PS: A friend rightfully pointed out an issue with my original template. When the current was zero, the division break (of course...). |
Aims to address device support requests: 2 bidirectional clamps: zigpy#2549 (_TZE204_81yrt3lo) zigpy#2650 (_TZE200_rks0sgb7) 1 bidirectional clamp: zigpy#2420 (_TZE204_ac0fhfiq) 1 clamp: zigpy#1973 (_TZE204_cjbofhxw) @jmuf I've just spotted that in parallel you've also been working on zigpy#2870 for _TZE200_rks0sgb7, shall we pool ideas?
Hi May you share which quirk to use to have total energy Summation? |
|
Hello! |
|
I would be surprised if it was a quirk issue, certainly seems like something odd is going on with the device. Does it report the correct active power use? I think current development support for these devices has moved to #2961, so probably best to get the new quirk from there and contribute to that discussion. Hopefully we will have native support for these soon! |
Hi, I have same issue my total energy consuming is block now at 8388 :-( I using Zigbee2mqtt) , other values still correct. |
|
8,388,607 happens to be the largest number (signed int) that can be represented in 3 bytes. Which suggests that it might be value saturation. The comment from fred-c1 #2420 (comment) says summation_delivered is 4 bytes (max > 2m kWh) but I wonder if the scaling prevents the full range being used. |
Thanks for your interresting answer. It seems to be the correct explanation. did some body have found a way to reset the counters on this equipement ? |
|
Maybe this process could be used? I'm at 3,700kWh so haven't encountered this yet but it seems like it is something I will have to deal with at some point. |
Thanks i have already this process on this device. But it doesn't work. |
|
ohoh, same pb here, counter is lock at 8388.6 kwh. Someone find a solution ? |
|
I stubbled on a Tuya datapoint documentation for a different device. I don't have the 
|
|
Hello. This is what works for me. {% if (rc 1000)%10 ==0 %} {{ap}} |
TheJulianJES
added
the
device support request
Problem description
Hi I would like to request device support for the _TZE204_ac0fhfiq TS0601 BiDirectional ZigBee Energy Meter with 150A Clamp Current Sensor.
It apears in HA, but without any sensor.
product link : https://www.aliexpress.com/item/1005005466228073.html
Solution description
Any
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]
Device signature
Device signature
{ "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": "0x0051", "in_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } }, "manufacturer": "_TZE204_ac0fhfiq", "model": "TS0601", "class": "zigpy.device.Device" }Diagnostic information
Diagnostic information
{ "home_assistant": { "installation_type": "Home Assistant Container", "version": "2023.2.5", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "Europe/Paris", "os_name": "Linux", "os_version": "5.10.0-21-amd64", "run_as_root": true }, "custom_components": {}, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "config_flow": true, "documentation": "https://www.home-assistant.io/integrations/zha", "requirements": [ "bellows==0.34.7", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.92", "zigpy-deconz==0.19.2", "zigpy==0.53.0", "zigpy-xbee==0.16.2", "zigpy-zigate==0.10.3", "zigpy-znp==0.9.2" ], "usb": [ { "vid": "10C4", "pid": "EA60", "description": "*2652*", "known_devices": [ "slae.sh cc2652rb stick" ] }, { "vid": "1A86", "pid": "55D4", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus v2" ] }, { "vid": "10C4", "pid": "EA60", "description": "*sonoff*plus*", "known_devices": [ "sonoff zigbee dongle plus" ] }, { "vid": "10C4", "pid": "EA60", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*tubeszb*", "known_devices": [ "TubesZB Coordinator" ] }, { "vid": "1A86", "pid": "7523", "description": "*zigstar*", "known_devices": [ "ZigStar Coordinators" ] }, { "vid": "1CF1", "pid": "0030", "description": "*conbee*", "known_devices": [ "Conbee II" ] }, { "vid": "10C4", "pid": "8A2A", "description": "*zigbee*", "known_devices": [ "Nortek HUSBZB-1" ] }, { "vid": "0403", "pid": "6015", "description": "*zigate*", "known_devices": [ "ZiGate+" ] }, { "vid": "10C4", "pid": "EA60", "description": "*zigate*", "known_devices": [ "ZiGate" ] }, { "vid": "10C4", "pid": "8B34", "description": "*bv 2010/10*", "known_devices": [ "Bitron Video AV2010/10" ] } ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "zeroconf": [ { "type": "_esphomelib._tcp.local.", "name": "tube*" }, { "type": "_zigate-zigbee-gateway._tcp.local.", "name": "*zigate*" }, { "type": "_zigstar_gw._tcp.local.", "name": "*zigstar*" }, { "type": "_slzb-06._tcp.local.", "name": "slzb-06*" } ], "dependencies": [ "file_upload" ], "after_dependencies": [ "onboarding", "usb", "zeroconf" ], "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 64567, "manufacturer": "_TZE204_ac0fhfiq", "model": "TS0601", "name": "_TZE204_ac0fhfiq TS0601", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4417, "power_source": "Mains", "lqi": 120, "rssi": null, "last_seen": "2023-05-29T13:52:11", "available": true, "device_type": "Router", "signature": { "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": "0x0051", "in_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "out_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } } }, "active_coordinator": false, "entities": [], "neighbors": [], "routes": [], "endpoint_names": [ { "name": "SMART_PLUG" }, { "name": "unknown 97 device_type of 0xa1e0 profile id" } ], "user_given_name": null, "device_reg_id": "9dce80159cb1f043f40e7a51ddbb311c", "area_id": "salon", "cluster_details": { "1": { "device_type": { "name": "SMART_PLUG", "id": 81 }, "profile_id": 260, "in_clusters": { "0x0004": { "endpoint_attribute": "groups", "attributes": {}, "unsupported_attributes": {} }, "0x0005": { "endpoint_attribute": "scenes", "attributes": {}, "unsupported_attributes": {} }, "0xef00": { "endpoint_attribute": null, "attributes": {}, "unsupported_attributes": {} }, "0x0000": { "endpoint_attribute": "basic", "attributes": { "0x0001": { "attribute_name": "app_version", "value": 74 }, "0x0004": { "attribute_name": "manufacturer", "value": "_TZE204_ac0fhfiq" }, "0x0005": { "attribute_name": "model", "value": "TS0601" } }, "unsupported_attributes": {} } }, "out_clusters": { "0x0019": { "endpoint_attribute": "ota", "attributes": {}, "unsupported_attributes": {} }, "0x000a": { "endpoint_attribute": "time", "attributes": {}, "unsupported_attributes": {} } } }, "242": { "device_type": { "name": "unknown", "id": 97 }, "profile_id": 41440, "in_clusters": {}, "out_clusters": { "0x0021": { "endpoint_attribute": "green_power", "attributes": {}, "unsupported_attributes": {} } } } } } }Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: