[Device Support Request] _TZE204_81yrt3lo TS0601 Zigbee power meter with clamp #2549
Comments
|
I saw there is quirk data for z2m, so I created a /config/zha_quirks/ folder, create the file Tuya_TZE204_81yrt3lo.js with this data, and added custom_quirks_path: /config/zha_quirks/ to configuration.yaml. But after reboot and repair, still no sensors. Must I delete pycache?Have no idea how to do it... const fz = require('zigbee-herdsman-converters/converters/fromZigbee'); const valueConverter = { const definition = { meta: { module.exports = definition; |
|
I think the quirk it's not applied, but I can't figure why... I followed all the steps... this is the log: "manufacturer": "_TZE204_81yrt3lo", |
|
In the opening post you have signature and diagnostic from the coordinator and not the device you have described. |
|
Sorry, wrong device..... Fixed now. ( I Hope) :-) |
|
Tried to add custom quirk to ZHA following https://github.com/home-assistant/home-assistant.io/pull/23884/files/e03462d75c7ad37c611ab3cf4d47210f7114bc94#diff-f6bd4d42fd2565238968333a466474a25384fb4eecddc0235902e5ff5e798c8d but still no sensors. I am sure I followed all steps, creating the quirks folder and adding to yaml... |
|
|
|
I created a file called TS0601_Router.py inside "customs_zha_quirks" folder. And This is wrong? I have some devices apart of this one I'd like to fix to contribute. I'm on the learning process :-) |
|
You have posting Z2M code in the ZHA quirk and its not working. |
|
I think one good start i using this quirk and caning it so its working for your device if that is using the same DPs (tuya MCU commands). |
|
I bought the same device and had the same problem. I found this information : Koenkk/zigbee2mqtt#18419 (comment) Hope it can help to fix the problem. |
|
Quirk applied finally, and getting some data. Only Total power delivered and Power factor. Log: |
|
This sentences make the difference. With this, quirk isn't applied, and device have no sensor. Doesn't matter if the signature is right, quirk isn't applied. I have no idea what means the numbers or where find how it work,,,not much info about quirks development out there, anyway, I'll keep trying.... |
|
Hello, I've just read your post, even following your parameters I don't get the power entities. Can you post your file ts0601_din_power.py for _TZE204_81yrt3lo please? Do you confirm that once the file is placed in the custom_zha_quirks folder, I have to clear the ts0601_din_power.cpython-311.pyc cache and reboot HA? and rebuild or do I have to delete the device and reinstall it? |
|
Yes, every time I do any change I delete the device, delete pycache file inside zha_quirks folder, and reboot HA. And this after reboot again HA (one more sensor is discovered, "Summation delivered"). More HA reboots don't add more sensors. from zhaquirks import Bus, LocalDataCluster import logging TUYA_TOTAL_ENERGY_ATTR = 0x0201 #total energy /100 0x0211 class TuyaManufClusterDinPower(TuyaManufClusterAttributes): class TuyaPowerMeasurement(LocalDataCluster, ElectricalMeasurement): class TuyaElectricalMeasurement(LocalDataCluster, Metering): class TuyaPowerMeter(TuyaSwitch): class TuyaPowerMeter_GPP(TuyaSwitch): |
|
Do you think you could send me the whole file at once? I've gone step by step, but it doesn't work. Are file indentations mandatory (as in YAML)? After trying several times, still nothing. Once the file has been created according to your model, I don't get the "Power Factor" entity on the first startup, and nothing either on the second startup. |
|
The folder must be pointed in configuration.raml, something like zha: Pointing to your quirks folder. |
|
Yes !! for your information, the second "Summation delivered" sensor appeared with the clamp closed (currently at 0.0kWh), my blank assembly. I'm going back to my temporary set-up to measure a significant current. But I'm going to ask you again, and maybe you won't be able to answer me, the model I have has 2 sensors, and I can only see one :-( Do you have any idea how to activate the second sensor to help me in my search? I didn't go through TUYA, I don't have an independent gateway, and I didn't manage to associate it in Zigbee on the application. thanks again, I'm desperate after 150 restarts. |
|
Mine have two sensors plug too, for use with solar or wind generators. I use only one because I have no generators i+right now. This device have much more sensors, like voltage, actual consumption, etc... I am trying to get all working, but there is info (or I can't find it) about quirks creation, so I am blindfolding, just trying things....you can see all the sensors available and the entrypoints here Koenkk/zigbee2mqtt#18419 (comment) but I don't know how translate from z2mqtt to ZHA. Any progress I will post here, if any... any suggestion, progress, you make, please let me know... |
|
OK I'm looking |
|
ts0601_din_power_MatSee.zip |
|
👍 Great |
|
You make my day, it works like charm... just have a doubt about the active power... a current of 2.4Ah at 235volts = 566 W... but indicate 4122 w... It seems there is something wrong... |
|
This is the screen capture of Tuya app. It seems to need some calibration too, (is possible to modify calibration factor in the app). Last number in active power must be decimal... and seems in this quirk "summation delivered" refers to reverse energy, not forward energy as TuyaPowerMeter_GPP do..... but you did a GREAT job. Thanks. BiduleMac could confirm this, I have only one clamp for forward energy because I have no solar generator yet. |
|
Great , |
|
Concerning the two sensors, I noticed with the latest version of @maccmaic that both sensors are present (in Manage Zigbee device) and the values updated, but I don't understand how to make them appear as entities. In fact, I'm trying to understand the structure of the file, but the display part escapes me ;-(. |
|
from what I saw in the code only the attributes energy_deliver_reported and energy_deliver_reported |
|
I have tried to change delivered/recived but the integration not working. If someone know why? For channel B, I tried to report the CURRENT_TIER1_DELIVERED_ID attribute of the TuyaElectricalMeasurement class but it didn't work either. The bad thing is that when I modify things that should not affect the rest, it stops showing all the entities. |
|
in my searches on Github, I don't see any TS601 displaying 2 sensors .... what's surprising is that the data from the 2 sensors do indeed show up in ZHA, you can see them vary in the "manage Zigbee device" menu, then "MatSeeManufClusterDinPower" and current & currentB with the values 0x000 and 0X001, and this is also true for power and current.
I can't figure out how to define the transition to entities. |
|
Hi Guru, out there.
|
|
Hi @jeverley , thanks so much for this quirk. This was the last device I needed to get working so now my home is complete. I have some questions for you if you have time:
Sorry if I've missed any of these in the comments above. Many thanks for your work on this. |
You need to enable the entities. |
|
i mis the type TZE204_81yrt3lo in https://github.com/jeverley/zha-device-handlers/blob/ts0601_energy_meter_devices/zhaquirks/tuya/ts0601_din_power.py |
Hi, the file is not availible anymore? |
The link works for me. |
|
I'm a bit confused with the triple sensors :
Sometimes the 1st of the 3 is at 0 value or Unknown, sometimes it's the 3rd one. |
Same question here |
This helped me understand it |
I also confirm this one works for me (HAOS Home Assistant OS 13.1 - HA core-2024.9.0). How can we vote somewhere to push this quirk to standard? |
Were you able to understand this?? I have the same doubt. |
Yes, the two first ones are the individual clamps. |
I can finally confirm that this thing works for 2 clamp power meter _TZE204_81yrt3lo. A bit of testing is ahead to see if measurements are fine. |
I've got the same issue. Anyone have workaround ? |
|
Having the same with this one as well, Quirk is loading, but not getting any sensors. The one earlier in the thread did load but it only showed voltage, and nothing else. here is the diag.. EDIT: weirdly, this just suddenly started working. No idea what happened but all the sensors appeared. |
copied this quirk but no entities and values. what is wrong? |
|
Hi all, it's been a while since I looked at this due to moving house. The existing draft quirk here https://github.com/jeverley/zha-device-handlers/blob/ts0601_energy_meter_devices/zhaquirks/tuya/ts0601_energy_meter.py should continue to work (and it's what I'm currently using personally), but I'll update here once I've got a v2 version ready for testing. |
|
Hi, this - https://github.com/jeverley/zha-device-handlers/blob/ts0601_energy_meter_devices/zhaquirks/tuya/ts0601_energy_meter.py quirk is working for me. but some fields are "Unknown" like Voltage. only one field of voltage is filed. is it supposed to be like that? The same for the AC frequency only one field is populated. |
|
Hi there! I've been wanting to report my experience with this little thing for a while, so here it is. I'm using this quirk and since the beginning it was reporting negative values on all endpoints of But I thought maybe I interpreted the cable directions wrong (this house connections are a mess) and I read somewhere that inverting those cables may fix it. And it did, but then all endpoints got I tried removing and adding again this device but to no aval. I even tried resetting the values to 0 but they return again after a short time. That makes me think... maybe it's the device the one persisting this data? I searched and found no info on how to factory reset it. And at this point I'm not exactly sure what to do next: reverting the cables back to factory specification maybe fixes the stuck values, but then it will return to negative values. If I keep it I have cool graphs and all but I still cannot use HA energy feature as the values needed are stuck. I also tried to create a counter but unit was in W and couldn't find a way to change it to Wh. Any suggestions or tests to perform are welcomed. Thanks for this quirk @jeverley |
|
Hi @ml0renz0, it's been a while since I had to do it, but if I remember correctly holding down the reset button for 8 seconds can factory reset the device. |
|
@ml0renz0 @jeverley Maybe it can be done in the quirk code? adding abs() to the result? |
|
I have created a helper in HA and assigned it to the energy meter sensor so that it always provides a positive value. I have also checked and verified that reversing the direction of the clamp reverses the +- values and that switching the position of the black and red leads in the device does the same thing. So there are 3 simple ways to correct the negative value of the sensor, 4 if you include ensuring that the clamp used is on the same phase as the power supplying the device. I can also confirm what others have mentioned when adding a new device. HA needs to be restarted in order for the new device to display all the entities. Simply adding and pairing a new device does not populate all the sensors. I had to restart HA in order for the new device to display its entities. I am still trying to figure out why I am getting the exact same values reported for both the A and B lines. The values reported were all the same initially and after a restart they appeared to be working properly (different for the different circuits) but when I checked back the values had all reverted to displaying the same for both clamps. Any Ideas? and, as an aside, what gauge wire are people using to supply power to the actual device? |
|
Tried it... I even stuck my finger on the button for a long 30 seconds and
still didn't work. It seems ot cannot be reseted...
El vie, 10 ene 2025, 10:49, Jack ***@***.***> escribió:
… Hi @ml0renz0 <https://github.com/ml0renz0>, it's been a while since I had
to do it, but if I remember correctly holding down the reset button for 8
seconds can factory reset the device.
—
Reply to this email directly, view it on GitHub
<#2549 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACZM4PTXIKV3S7ME5YSD3LD2J6JSJAVCNFSM6AAAAAA4BL7B72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSGIZDENZXHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@ml0renz0 This is the info I have but it looks like it might only be related to their app. However, if it is clearing any data for the app it might be also clearing everything on the device? The 5 presses might do it or maybe you would have to connect to the app to do the clear? Sometimes clearing data can be done by pressing the button on some of these devices after disconnecting from power and then holding the button down. Just guessing. |
I think I am wrong here. I think my issue was naming the entities incorrectly. I am in the process of trying to check this out but I believe I might have mistakenly assigned the A and B channels to the wrong sensors. I believe the correct setup is sensor with no number is A, sensor_2 is B and sensor_3 is the total. |
|
Hi all,
Here are the values in HA per day compared to the one my electricity provider has. Is there any way to calibrate the device, or modify the custom quirk to correct the values ? Thanks |
TheJulianJES
added
the
device support request
and others
Problem description
The device is discovered, but with no sensors. I have all connected fine, I can see total and instantaneous power in Tuya app. Where to start?
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": "0x0104", "device_type": "0x0051", "input_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "output_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": "0xa1e0", "device_type": "0x0061", "input_clusters": [], "output_clusters": [ "0x0021" ] } }, "manufacturer": "_TZE204_81yrt3lo", "model": "TS0601", "class": "zigpy.device.Device" }Diagnostic information
Diagnostic information
{ "home_assistant": { "installation_type": "Home Assistant Supervised", "version": "2023.5.4", "dev": false, "hassio": true, "virtualenv": false, "python_version": "3.10.11", "docker": true, "arch": "armv7l", "timezone": "Europe/Madrid", "os_name": "Linux", "os_version": "5.10.103-v7l+", "supervisor": "2023.08.1", "host_os": "Raspbian GNU/Linux 10 (buster)", "docker_version": "20.10.14", "chassis": "", "run_as_root": true }, "custom_components": { "sonoff": { "version": "3.5.2", "requirements": [ "pycryptodome>=3.6.6" ] }, "smartir": { "version": "1.17.7", "requirements": [ "aiofiles>=0.6.0" ] }, "hacs": { "version": "1.32.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "localtuya": { "version": "5.2.1", "requirements": [] }, "midea_ac_lan": { "version": "v0.3.18", "requirements": [] } }, "integration_manifest": { "domain": "zha", "name": "Zigbee Home Automation", "after_dependencies": [ "onboarding", "usb" ], "codeowners": [ "@dmulcahey", "@adminiuga", "@puddly" ], "config_flow": true, "dependencies": [ "file_upload" ], "documentation": "https://www.home-assistant.io/integrations/zha", "iot_class": "local_polling", "loggers": [ "aiosqlite", "bellows", "crccheck", "pure_pcapy3", "zhaquirks", "zigpy", "zigpy_deconz", "zigpy_xbee", "zigpy_zigate", "zigpy_znp" ], "requirements": [ "bellows==0.35.5", "pyserial==3.5", "pyserial-asyncio==0.6", "zha-quirks==0.0.99", "zigpy-deconz==0.21.0", "zigpy==0.55.0", "zigpy-xbee==0.18.0", "zigpy-zigate==0.11.0", "zigpy-znp==0.11.1" ], "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" ] } ], "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*" } ], "is_built_in": true }, "data": { "ieee": "**REDACTED**", "nwk": 11971, "manufacturer": "_TZE204_81yrt3lo", "model": "TS0601", "name": "_TZE204_81yrt3lo TS0601", "quirk_applied": false, "quirk_class": "zigpy.device.Device", "manufacturer_code": 4417, "power_source": "Mains", "lqi": 128, "rssi": -68, "last_seen": "2023-08-28T21:08:34", "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": "0x0104", "device_type": "0x0051", "input_clusters": [ "0x0000", "0x0004", "0x0005", "0xef00" ], "output_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": "0xa1e0", "device_type": "0x0061", "input_clusters": [], "output_clusters": [ "0x0021" ] } }, "manufacturer": "_TZE204_81yrt3lo", "model": "TS0601" }, "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": "c7f139fc3dc0c3829df8cef20d87199b", "area_id": "594729d4701c4d73b9edf7c14a5818d8", "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_81yrt3lo" }, "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: