Does anyone know off-hand of an alternative that DOES work with HE?
These were nice because they don't have a large lcd screen (like some wifi devices) that I don't need.
I am happy with the Frient Smart Plug , it is supported natively in the latest HE platform version (works also with this driver as an alternative), but the price is a higher than Tuya.
And also the SmartThigs plug. I don't have it, but it is a classic metering plug device.
1 Like
I just put a warning in the first post. Unfortunately, such problems happen often with Tuya devices.
1 Like
Thanks Krassimir - much appreciated.
I'm sure the additional warning to the original post will be helpful to HE users.
Derek
1 Like
I have added into the dev. branch version 1.6.5 a new device - ZigBee Energy Meter 80A with Current Transformer Clamp.
Reports energy, power, voltage, and current.
A big advantage in my opinion is the possibility to attach the measuring clamp to any high-power consuming appliance - up to 19 Kilowatts!
Disadvantages - the power factor is measured, but is not reported individually; this device is a bit chatty (sends 'online check' requests to the hub every 5 seconds).
3 Likes
I bought 3 20A Tuya Zigbee Smart Plug Mini US Power Outlet from AliExpress using the link in the first post in this thread. I had the same problem as other users, they do not work (_TZ3000_okaz9tjs application A0). If you could put a warning 'DO NOT BUY' beside the link, it would be great.
If ever you need me to test something, just let me know.
Thank you for the update, @tux89 . I have added the warning in the first post.
Hopefully there will be a solution in Hubitat for this problem soon, as it is quite possible the same SoC to start be used in other Zigbee products.
Hi
Is this working with the smartthings plug please?
Yes, it should.
In the code I have commented out the fingerprints for Samsung plugs because these are already supported from the HE inbuilt Zigbee Plug driver and there is no reason that this driver is automatically selected when paired for the first time. But you can always change the drivers manually.
Hello, I just recibe model TS0601 (Brough direct from aliexpress link in the first post)
I put the driver but I having issues because is not reporting anything and I can't turn on or off from HE.
Thanks for you help
Hi @jorge ,
It seems that one year later, Hiking have started selling a newer device with different electronic and firmware under the same name as the old one.. 
We will make it work, but I will need your help and it may take some time.
I will need the device fingerprint. Please change manually the driver to the HE inbuilt one named 'device' and click on the Get Info button. Copy and past the 'fingerprint' info from the device log.
Thanks you for your time and fast response! here is the fingerprint that show the logs
dev:1322022-12-17 13:56:38.873infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0004,0005,EF00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_bkkmqmyo"
dev:1322022-12-17 13:56:38.656traceZCL version:03
dev:1322022-12-17 13:56:38.588traceSoftware Build Id:unknown
dev:1322022-12-17 13:56:38.586traceModel:TS0601
dev:1322022-12-17 13:56:38.584traceManufacturer:_TZE200_bkkmqmyo
dev:1322022-12-17 13:56:38.496debuggetting info for unknown Zigbee device...
Can you try, without any changes in n the driver just to pair it again to HE?
i remove from my devices, but when I add it again as a new device hubitat use the driver "Tuya Temperature Humidity Illuminance LCD Display with a Clock". I change to "Tuya zigbee meetering Plug" and then to Device and I get this now
Summary
dev:1332022-12-17 15:10:16.612infoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 F60B 01 00 0000 02 01 006E6D02000400000024, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F60B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 6E, 6D, 02, 00, 04, 00, 00, 00, 24]]
dev:1332022-12-17 15:10:15.599infoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 F60B 01 00 0000 02 01 006D6702000400000130, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:F60B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 6D, 67, 02, 00, 04, 00, 00, 01, 30]]
dev:1332022-12-17 15:10:15.169infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0004,0005,EF00", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_bkkmqmyo"
dev:1332022-12-17 15:10:15.115traceZCL version:03
dev:1332022-12-17 15:10:15.113traceSoftware Build Id:unknown
dev:1332022-12-17 15:10:15.112traceModel:TS0601
dev:1332022-12-17 15:10:15.111traceManufacturer:_TZE200_bkkmqmyo
dev:1332022-12-17 15:10:15.046debuggetting info for unknown Zigbee device...
Don’t remove the device, just manually assign it the Tuya Metering Plug driver first, and the pair it again.
i do it but is the same, is not reporting nothing and on/off command is not working
Summary
dev:1332022-12-17 15:47:09.509warnmedidor general Unprocessed global command: cluster=EF00 command=02 attrId=null value=null data=[00, 56, 06, 00, 00, 0F, 00, 00, 01, 28, 00, 00, 00, 93, 02, E9, 00, 06, CF, 08, ED]
dev:1332022-12-17 15:47:09.506debugmedidor general parse: Desc Map: [raw:catchall: 0104 EF00 01 01 0040 00 BD73 01 00 0000 02 01 00560600000F000001280000009302E90006CF08ED, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:BD73, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 56, 06, 00, 00, 0F, 00, 00, 01, 28, 00, 00, 00, 93, 02, E9, 00, 06, CF, 08, ED]]
dev:1332022-12-17 15:47:09.502debugmedidor general parse: description is catchall: 0104 EF00 01 01 0040 00 BD73 01 00 0000 02 01 00560600000F000001280000009302E90006CF08ED
dev:1332022-12-17 15:47:08.488warnmedidor general Unprocessed global command: cluster=EF00 command=02 attrId=null value=null data=[00, 55, 10, 01, 00, 01, 01]
dev:1332022-12-17 15:47:08.485debugmedidor general parse: Desc Map: [raw:catchall: 0104 EF00 01 01 0040 00 BD73 01 00 0000 02 01 00551001000101, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:BD73, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 55, 10, 01, 00, 01, 01]]
dev:1332022-12-17 15:47:08.482debugmedidor general parse: description is catchall: 0104 EF00 01 01 0040 00 BD73 01 00 0000 02 01 00551001000101
dev:1332022-12-17 15:47:00.397tracemedidor general descMap = [raw:catchall: 0104 0006 01 01 0040 00 BD73 00 00 0000 01 01 000086, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:BD73, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 00, 86]]
dev:1332022-12-17 15:47:00.396warnmedidor general Switch polling is not supported -> Switch polling will be disabled.
dev:1332022-12-17 15:47:00.393debugmedidor general parse: Desc Map: [raw:catchall: 0104 0006 01 01 0040 00 BD73 00 00 0000 01 01 000086, profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:BD73, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 00, 86]]
dev:1332022-12-17 15:47:00.389debugmedidor general parse: description is catchall: 0104 0006 01 01 0040 00 BD73 00 00 0000 01 01 000086
dev:1332022-12-17 15:47:00.329tracemedidor general sendZigbeeCommands : [he rattr 0xBD73 0x01 6 0 {}, delay 2000]
dev:1332022-12-17 15:47:00.280debugmedidor general polling.. refreshAll is true
dev:1332022-12-17 15:47:00.277infomedidor general refresh()...
The development branch was updated to version 1.6.5. (the link is in the second post) with the fingerprint and the commands for decoding this DIN rail model.
As there were a lot of changes and this device is different than mine, I can't test it, so we will need to go back and forth in several iterations probably to make everything work,
@jorge I am sending you a DM (direct message), please send me the debug logs there.
1 Like
Eres español???
Well, after a lot of messages @kkossev make it work! Thanks you a lot!
Here is a graph using grafana of hourly energy and power in the last hours. The peak showed is because I put the dishwasher
1 Like
I have two tuya plugs that do not seem to function properly. They can be paired and the driver can toggle the switches a couple of times right after pairing. Also some metering data is shown. After a few seconds the devices just stop toggling on/off and the presence is then reported not present.
I can see in the debug logs that this model is being warned of being problematic with hubitat. Does this apply for basic switching also or is it just for the energy reporting?
Pairing info:
Device pairing info
Manufacturer: _TZ3000_r6buo8ba
Endpoint 01 application: A0
Endpoint 01 endpointId: 01
Endpoint 01 idAsInt: 1
Endpoint 01 inClusters: 0000,0006,0003,0004,0005,E001,0B04,0702
Endpoint 01 initialized: true
Endpoint 01 manufacturer: _TZ3000_r6buo8ba
Endpoint 01 model: TS011F
Endpoint 01 profileId: 0104
Endpoint 01 stage: 4
