Hi Fabio, I checked the code and the voltage, amperage, power and energy reporting should be supported for this device.
Did you pair it to the hub with the driver already installed? Was the Tuya driver selected automatically when you paired it to the hub for a first time?
If you meant why the 'powerPollingSupported' driver internal state variables are false - this is OK, because this clamp meter is automatically reporting the V/P/A/E periodically, i.e. there is no need to poll the device.
Put the clamp (over one of the load wires only!), if you have a load >3 watts you should see the amperage and the power readings.
Hello,
Ok thank you.
All ok for the installation/pairing. It was the false states and absence of results that was making me doubts.
As I don't have any load wire easily accessible to test, I did it on a smart switch load wire but certainly the consumption is to weak to be detected. I will try on an other device more powerful
Bought a metering plug from AliExpress and paired it with my Hubitat C-8 (running v. 2.3.6.146). Pairing went smoothly and this driver (v. 1.7.7) was selected automatically.
The problem is that it only works a minute or less, then the device is unresponsive. Can pair multiple times, and the results are always the same, works a short time and then nothing. No errors in (debug) logs. Data in Hubitat's end:
You can try to remove the device from Hubitat, re-pair it again, and, in the short interval that it stays paired, remove the power from the metering plug (remove it from the outlet) for a couple of minutes. Maybe also have a load connected in order to drain the capacitors quickly and kill the power to the zigbee module.
When you plug it back in, does it connect to HE and does it stays that way?
I am using the Third Reality model 3RSP02028BZ outlet with the Tuya Zigbee Metering Plug driver version 1.8.0 (8/7/2023).
It works well with the exception of energy reporting values which appear to be about 3.66 times the expected amount. This is based on multiple tests using a 60 watt incandescent light bulb over several hours for each test.
Is there a newer driver available that corrects this?
I have no idea how it is possible the energy to be off 3.66 the real consumption... Usually, if a divider is wrong then the difference is 10 or 100 times, but always a factor of 10.
The driver I use that is off by a factor of 3.66 is the Tuya ZigBee Metering Plug. I assume this driver was written by you? (kkossev).
I prefer your driver to the one written by jonathanb because your driver provides much better resolution for the energy parameter. Right now, I simply divide the number received from the device by 3.66 and it matches nicely with expected power consumption.
The 'Device' driver is the one assigned automatically by HE during the initial pairing to any device whose fingerprint is not defined in the rest of the system and custom drivers. It is often used to clear any pending scheduled jobs or old state variables when changing between different drivers.
As I mentioned before, I don't have any idea why is this 3.66-factor error with the Third Reality power monitoring plug. You can temporarily leave the correction inside the driver code and rename the driver name so that the changes don't get overwritten by a future update.
I received a new plug from china and its manufacturer signature is "_TZ3000_okaz9tjs"
In your release notes I see that this device is not compatible.
Fingerprints are commented out.
But when I try it with your driver, it successfully runs. On/off , power/amperage/power/voltage all shows fine.
What is not working ?
Should I add any fingerprint ?
You have been lucky to receive a _TZ3000_okaz9tjs plug that has managed to pair and to stay connected in your particular environment. Do not remove it, as usually it is very difficult to pair it again as a new device once being removed from the hub.
The ChildLock option prevents the plug from being turned on/off using the local physical button.
