-
Notifications
You must be signed in to change notification settings - Fork 675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Device Support Request] Circuit Breaker 63A with Power Monitoring and Threshold TS011F | _TZ3000_lepzuhto #2652
Comments
Tongou TO-Q-SY2-163JZT - TS011F _TZ3000_cayepv1a. Wrong amperes (always show 62-63), wrong measurements (kWh), no threshold. |
Same problem with Tongou TO-Q-SY2-163JZT - TS011F _TZ3000_cayepv1a { Ampere is x 1000 Cumulated power is x 100 Edit on 29 march 24 |
TS011F by _TZ3000_cayepv1a
|
If we are talking abut the same device (TO-Q-SY2-163JZT) , and I think we are, the integration into ZHA needs a lot of work. As it is right now this device function as TO-Q-SY1 device, which is just a normal breaker with an ON/OFF button and displaying some power values.
This is the zigbee2mqtt page for this device: https://www.zigbee2mqtt.io/devices/TO-Q-SY2-163JZT.html Will be good to see the same kind of functionality in ZHA too because with out that it will just acts like a dumb TO-Q-SY1 device offering no protection at all. The pic below shows what this device exposes in zigbee2mqtt: |
Hello, I just received this device.
@dartvader1234 : you correctly detected the problem (1). You should have a look at the following discussion. Someone had the same problem with another device and solved (1) with a custom quirck (but not (2)). The problem (2) was identified in the thread above but not solved. If you check P=UI you will see that the power value is incorrect. Are everyone here using 220v? Anyone using 11v? The guess from the other thread is that TUYA calculate power from 110v. I hope someone will be able to write a custom quirck inspired from this one: |
9After some more testing, here are more info. 2/ about the values measured by _TZ3000_cayepv1a:
Value measured with an external tool (simple AC clamp meter) = 0.130A Let's simplify for now and says that there is a x1000 factor. There will still be a huge difference between 130 and 194. Can it be explained by the relatively low current and the method (AC clamp)?? Later I'll connect an amperemeter to get a more precise value.
Unfortunately I'm not able to write a custom quirk. I hope those info will help someone write one on the basis of this one: custom quirk for tuya clamp For all others: you can make a simple correction using templates |
@dartvader1234: can you please double check your power value? are your sure you do not read a value/2 ?? |
You are rigth, me wrong, cumulated power is x 100 |
Hi, Taken from here: |
Thank you mortiy. 👍 |
I have TO-Q-SY2-JZT - TS011F _TZ3000_cayepv1a with There is a quirk for similar device _TZ3000_qeuvnohg having the same descriptor, but with slightly reordered clusters:
I suppose tweaking this quirk should help to identify the _TZ3000_cayepv1a device properly? |
Hi, please excuse the simple question, I too have this device (TO-Q-SY2-163JZT) and am using ZHA, and have noticed the lack of exposed sensors compared to Zigbee2mqtt (within this thread), will this be updated/rectified overtime, are there manual interventions/configuration changes needed to identify the current product? I am primarily using the switching function (noted the wrong current values) the other sensors are nice to have. Thanks in advance… |
Another vote for fixing this please. |
I can send one TS011F by _TZ3000_cayepv1a to the developper team, for free to resolve this problem. If your are interested, please contact me. I will reply you by email |
I create a custom quirk for this device here |
I updated the file to make use of the quirk v2 features to expose the attributes to HA entities |
Updated version with quirks v2 support |
Problem description
Electrical measurements in this device not working properly - current and summation delivered (kWh) are too high.
Solution description
Please correct the current multiplier
Screenshots/Video
Screenshots/Video
[Paste/upload your
media here]
Device signature
Device signature
Diagnostic information
Diagnostic information
Logs
Logs
Custom quirk
Custom quirk
Additional information
No response
The text was updated successfully, but these errors were encountered: