[RELEASE] Tuya Zigbee Metering Plug (w/ healthStatus)

[jw970065]

@kkossev

If you DELETE the device from HE web page and then pair it again as a new device, will this driver be assigned automatically?

It's registered as Xiaomi's product.
So I updated the version of the plug on Tuya Hub.
After that, I deleted everything from HE and registered it again.
The result is very successful. I checked that the plug is working in both directions.

Summary

dev:51512022-09-08 01:29:14.857 am info여과기모터용P 20A voltage is 220 V

dev:51512022-09-08 01:29:09.826 am info여과기모터용P 20A was turned off [digital]

dev:51512022-09-08 01:29:08.797 am info여과기모터용P 20A was turned on [digital]

dev:51512022-09-08 01:29:06.797 am info여과기모터용P 20A was turned off [physical]

dev:51512022-09-08 01:29:06.093 am info여과기모터용P 20A was turned on [physical]

dev:51512022-09-08 01:28:27.875 am info여과기모터용P 20A voltage is 219 V

dev:51512022-09-08 01:27:29.671 am infoTuya Zigbee Metering Plug voltage is 220 V

dev:51512022-09-08 01:27:27.726 am infoTuya Zigbee Metering Plug switch is off

dev:51512022-09-08 01:27:27.355 am info configure()..

dev:51512022-09-08 01:27:27.354 am infoconfiguring the switch and energy reporting..

dev:51512022-09-08 01:27:27.353 am infoAuto polling is enabled, polling interval is 60 seconds

dev:51512022-09-08 01:27:27.310 am infoDebug logging is false Description text logging is true

dev:51512022-09-08 01:27:27.309 am infoUpdating null (Tuya Zigbee Metering Plug) model TS011F presence: present AlwaysOn is false

dev:51512022-09-08 01:27:27.280 am infoTuya Zigbee Metering Plug InitializeVars()... fullInit = true

dev:51512022-09-08 01:27:27.259 am infoTuya Zigbee Metering Plug Initialize()...

dev:51512022-09-08 01:27:24.593 am infoTuya Zigbee Metering Plug voltage is 220 V

dev:51512022-09-08 01:27:22.779 am infoTuya Zigbee Metering Plug switch is off

dev:51512022-09-08 01:27:22.276 am info configure()..

dev:51512022-09-08 01:27:22.221 am infoTuya Zigbee Metering Plug InitializeVars()... fullInit = true

dev:51512022-09-08 01:27:22.219 am infoTuya Zigbee Metering Plug Installed()...

[kkossev]

1.0.13

This update hopefully fixes the nasty self-resetting bug in Tuya plugs from the last one year!

[jw970065]

Most of the Tuya plugs have been updated for a long time, but it's strange that this plug doesn't. I have to use it after updating all 5 plugs I bought.
20A is said to be a bit of a fake spec. However, it is larger than 16A.

[kkossev]

Driver version was updated in HPM to 1.5.2 - added _TZ3000_cehuw1lw _TZ3000_typdpbpg;

I have also added in the first post some more pictures and links to models that are supported by this diver.

[kkossev]

Hi @tim.ocallag ,

Please update the driver from the link on the second post (dev. branch version 1.6.0 2022/09/09 3:40 PM). The only change related to your device is that its fingerpint was added and this driver should be now selected automatically when pairing to HE. Please let me know if there is any change, if not we will go from here.

[mpoole32]

I would be nice to have these 2 additional pieces of info added to your driver if possible.

[kkossev]

How are you using these custom states/attributes? For displaying directly on HE dashboard?

In addition, this will require as a minimum:

• Command 'Reset Energy'
• Preference/parameter 'Cent per kWh'

Update: I got it, the screenshot is from Kevin's "Zooz Power Switch" z-wave driver.
Thank you, I will surely 'borrow' some ideas from here!

[mpoole32]

Outstanding! I've never understood why Kevin's method was not the standard for power reporting. While it is useful to see watts and amps the bottom line most times is the bottom line $s, how much is it costing me to run this device.

[tim.ocallag]

I updated the driver, removed and readded the device and did an initialize--here is what the logs said
dev:8192022-09-09 10:36:39.448 am traceHotTub sendZigbeeCommands received : [he raw 0x5CD3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x5CD3 0x01 6 0 {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 00 0B 05 05 05 08 05}, delay 200, he raw 0x5CD3 1 0x01 0x0702 {10 00 00 00 00}, delay 2000, zdo bind 0x5CD3 0x01 0x01 6 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 6 0 16 0 600 {}, delay 2000, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 1794 0 37 60 3600 {} {}, delay 2000]

dev:8192022-09-09 10:36:39.416 am traceHotTub polling all

dev:8192022-09-09 10:36:39.414 am traceHotTub polling.. refreshAll is true

dev:8192022-09-09 10:36:39.413 am infoHotTub refresh()...

dev:8192022-09-09 10:36:39.409 am infoHotTub configure()..

dev:8192022-09-09 10:36:39.408 am infoHotTub configuring the switch and energy reporting..

dev:8192022-09-09 10:36:39.407 am infoHotTub Auto polling is enabled, polling interval is 60 seconds

dev:8192022-09-09 10:36:39.380 am infoHotTub Debug logging will be automatically switched off after 24 hours

dev:8192022-09-09 10:36:39.352 am infoHotTub Debug logging is true Description text logging is true

dev:8192022-09-09 10:36:39.351 am infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

dev:8192022-09-09 10:36:39.350 am traceHotTub destinationEP = 01

dev:8192022-09-09 10:36:39.348 am traceHotTub model = TS011F

dev:8192022-09-09 10:36:39.314 am infoHotTub InitializeVars()... fullInit = true

dev:8192022-09-09 10:36:39.294 am infoHotTub Initialize()...

dev:8192022-09-09 10:36:28.644 am traceHotTub polling all

dev:8192022-09-09 10:36:28.643 am traceHotTub polling.. refreshAll is false

dev:8192022-09-09 10:36:28.610 am debugHotTub autoPoll()

dev:8192022-09-09 10:35:28.661 am traceHotTub sendZigbeeCommands received : [he raw 0x5CD3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x5CD3 0x01 6 0 {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 00 0B 05 05 05 08 05}, delay 200, he raw 0x5CD3 1 0x01 0x0702 {10 00 00 00 00}, delay 2000, zdo bind 0x5CD3 0x01 0x01 6 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 6 0 16 0 600 {}, delay 2000, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 1794 0 37 60 3600 {} {}, delay 2000]

dev:8192022-09-09 10:35:28.629 am traceHotTub polling all

dev:8192022-09-09 10:35:28.628 am traceHotTub polling.. refreshAll is true

dev:8192022-09-09 10:35:28.626 am infoHotTub refresh()...

dev:8192022-09-09 10:35:28.623 am infoHotTub configure()..

dev:8192022-09-09 10:35:28.622 am infoHotTub configuring the switch and energy reporting..

dev:8192022-09-09 10:35:28.621 am infoHotTub Auto polling is enabled, polling interval is 60 seconds

dev:8192022-09-09 10:35:28.588 am infoHotTub Debug logging will be automatically switched off after 24 hours

dev:8192022-09-09 10:35:28.558 am infoHotTub Debug logging is true Description text logging is true

dev:8192022-09-09 10:35:28.556 am infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

when I tried ON and OFF, nothing happened, nor was there anything new in the logs

The data in the data section seems smaller than I remember but not sure : )

• endpointId: 01
• model: TS011F
• application: A0
• manufacturer: _TZ3000_okaz9tjs

[kkossev]

Please update the driver to the new version timeStamp 2022/09/09 7:25 PM.
Change line #50 from false to true, save the driver mod and press F5 :

@Field static final Boolean debug = true

Make sure the debug logging is on and click on the ActiveEndpoints button. I will need the debug logs from here.

Next, click on the 'Test' button. It is supposed to toggle the switch on/off. Please send me the debug logs after presing the test buton also.

[tim.ocallag]

thanks again for your amazing help... I think I followed your directions (note I did not remove and add)....Also what does F5 do ?

---

after clicking ActiveEndpoints

---

dev:8192022-09-09 11:38:31.754 am traceHotTub sendZigbeeCommands received : [he raw 5CD3 0 0 0x0005 {00 D35C} {0x0000}, he raw 5CD3 0 0 0x0004 {00 D35C 01} {0x0000}]
dev:8192022-09-09 11:38:15.020 am traceHotTub sendZigbeeCommands received : [he raw 0x5CD3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x5CD3 0x01 6 0 {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 00 0B 05 05 05 08 05}, delay 200, he raw 0x5CD3 1 0x01 0x0702 {10 00 00 00 00}, delay 2000, zdo bind 0x5CD3 0x01 0x01 6 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 6 0 16 0 600 {}, delay 2000, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 1794 0 37 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0702 {10 00 08 00 0000}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1291 41 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0B05}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1285 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0505}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1288 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0805}, delay 250]
dev:8192022-09-09 11:38:15.013 am traceHotTub configureReporting operation=Write, measurement=Amperage minTime=60, maxTime=3600, delta=0 )
dev:8192022-09-09 11:38:15.009 am traceHotTub configureReporting operation=Write, measurement=Voltage minTime=60, maxTime=3600, delta=0 )
dev:8192022-09-09 11:38:15.005 am traceHotTub configureReporting operation=Write, measurement=Power minTime=60, maxTime=3600, delta=0 )
dev:8192022-09-09 11:38:14.989 am traceHotTub configureReporting operation=Write, measurement=Energy minTime=60, maxTime=3600, delta=0 )
dev:8192022-09-09 11:38:14.949 am traceHotTub polling all
dev:8192022-09-09 11:38:14.948 am traceHotTub polling.. refreshAll is true
dev:8192022-09-09 11:38:14.946 am infoHotTub refresh()...
dev:8192022-09-09 11:38:14.942 am infoHotTub configure()..
dev:8192022-09-09 11:38:14.941 am infoHotTub configuring the switch and energy reporting..
dev:8192022-09-09 11:38:14.939 am infoHotTub Auto polling is enabled, polling interval is 60 seconds
dev:8192022-09-09 11:38:14.907 am infoHotTub Debug logging will be automatically switched off after 24 hours
dev:8192022-09-09 11:38:14.874 am infoHotTub Debug logging is true Description text logging is true
dev:8192022-09-09 11:38:14.872 am infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: not present AlwaysOn is false
dev:8192022-09-09 11:36:40.572 am infoHotTub updating the settings from driver version 1.6.0 2022/09/09 5:44 PM to 1.6.0 2022/09/09 7:25 PM

---

new ones since clicking Test

---

dev:8192022-09-09 11:39:23.859 am traceHotTub sendZigbeeCommands received : [zdo bind 0x5CD3 0x01 0x01 0x0006 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, he cmd 0x5CD3 0x01 6 2 {}, delay 200]
dev:8192022-09-09 11:39:23.857 am tracesending test: [zdo bind 0x5CD3 0x01 0x01 0x0006 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, he cmd 0x5CD3 0x01 6 2 {}, delay 200]
dev:8192022-09-09 11:39:14.953 am traceHotTub polling all
dev:8192022-09-09 11:39:14.952 am traceHotTub polling.. refreshAll is false
dev:8192022-09-09 11:39:14.924 am debugHotTub autoPoll()

[kkossev]

Thank you for the logs. They show that absolutely nonthing is received from the device as a response to the commnds sent.. In one of the first posts you wrote "... the physical side switch works" - do you mean it just simply switches the plug on and off, or you can also see on/off status updated in the driver?

If you go to Settings->Zigbe details->Zigbee Logs do you see any updates when you physically switch the device on/off? Like this:

@tim.ocallag

Also what does F5 do ?

F5 in most browsers refreshes the web page. This is needed when you make changes in the driver, as the list of the commands (buttons) will not refresh automatically.

I will search for more information on this device, but for now I haven't read anyhing special for it - just another Tuya plug, similar to others that work fine with HA / HE.

I suppose you have only one device? It happens some particular devices to be defective, although I don't think this is the case.

What Zigbee channel are you using?

[tim.ocallag]

Dang, I only bought 1 ....wanted to make sure it works...in retrospect I should have gotten 2
When I press the button on the side it does change the physical state of the light but nothing is reflected in the logs
Here is my zigbee channel

[kkossev]

All looks good... Is this the 16A or 20A version?
Are you pairing it really close (1-2 meters away) from the HE hub?

[tim.ocallag]

not so close...let me try that

[kkossev]

Delete it first and pair as a new device

[tim.ocallag]

Did that....unfortunately i think the logs are the same for initialize
dev:8202022-09-09 01:14:06.515 pm infoHotTub refresh()...

dev:8202022-09-09 01:14:06.512 pm infoHotTub configure()..

dev:8202022-09-09 01:14:06.511 pm infoHotTub configuring the switch and energy reporting..

dev:8202022-09-09 01:14:06.510 pm infoHotTub Auto polling is enabled, polling interval is 60 seconds

dev:8202022-09-09 01:14:06.469 pm infoHotTub Debug logging is false Description text logging is true

dev:8202022-09-09 01:14:06.468 pm infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

dev:8202022-09-09 01:14:06.377 pm infoHotTub Initialize()...

dev:8202022-09-09 01:14:04.110 pm traceHotTub sendZigbeeCommands received : [he raw 0x5CD3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x5CD3 0x01 6 0 {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 00 0B 05 05 05 08 05}, delay 200, he raw 0x5CD3 1 0x01 0x0702 {10 00 00 00 00}, delay 2000, zdo bind 0x5CD3 0x01 0x01 6 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 6 0 16 0 600 {}, delay 2000, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 1794 0 37 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0702 {10 00 08 00 0000}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1291 41 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0B05}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1285 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0505}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1288 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0805}, delay 250]

dev:8202022-09-09 01:14:04.107 pm traceHotTub configureReporting operation=Write, measurement=Amperage minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:14:04.104 pm traceHotTub configureReporting operation=Write, measurement=Voltage minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:14:04.101 pm traceHotTub configureReporting operation=Write, measurement=Power minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:14:04.098 pm traceHotTub configureReporting operation=Write, measurement=Energy minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:14:04.068 pm traceHotTub polling all

dev:8202022-09-09 01:14:04.067 pm traceHotTub polling.. refreshAll is true

dev:8202022-09-09 01:14:04.066 pm infoHotTub refresh()...

dev:8202022-09-09 01:14:04.063 pm infoHotTub configure()..

dev:8202022-09-09 01:14:04.062 pm infoHotTub configuring the switch and energy reporting..

dev:8202022-09-09 01:14:04.061 pm infoHotTub Auto polling is enabled, polling interval is 60 seconds

dev:8202022-09-09 01:14:04.035 pm infoHotTub Debug logging will be automatically switched off after 24 hours

dev:8202022-09-09 01:14:04.007 pm infoHotTub Debug logging is true Description text logging is true

dev:8202022-09-09 01:14:03.979 pm infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

dev:8202022-09-09 01:14:03.978 pm traceHotTub destinationEP = 01

dev:8202022-09-09 01:14:03.977 pm traceHotTub model = TS011F

dev:8202022-09-09 01:14:03.945 pm infoHotTub InitializeVars()... fullInit = true

dev:8202022-09-09 01:14:03.928 pm infoHotTub Initialize()...

dev:8202022-09-09 01:13:50.069 pm traceHotTub sendZigbeeCommands received : [he raw 0x5CD3 1 0x01 0x0000 {10 00 00 04 00 00 00 01 00 05 00 07 00 FE FF}, delay 200, he rattr 0x5CD3 0x01 6 0 {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 00 0B 05 05 05 08 05}, delay 200, he raw 0x5CD3 1 0x01 0x0702 {10 00 00 00 00}, delay 2000, zdo bind 0x5CD3 0x01 0x01 6 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 6 0 16 0 600 {}, delay 2000, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 1794 0 37 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0702 {10 00 08 00 0000}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1291 41 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0B05}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1285 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0505}, delay 250, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, delay 2000, he cr 0x5CD3 0x01 2820 1288 33 60 3600 {} {}, delay 2000, he raw 0x5CD3 1 0x01 0x0B04 {10 00 08 00 0805}, delay 250]

dev:8202022-09-09 01:13:50.064 pm traceHotTub configureReporting operation=Write, measurement=Amperage minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:13:50.061 pm traceHotTub configureReporting operation=Write, measurement=Voltage minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:13:50.057 pm traceHotTub configureReporting operation=Write, measurement=Power minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:13:50.053 pm traceHotTub configureReporting operation=Write, measurement=Energy minTime=60, maxTime=3600, delta=0 )

dev:8202022-09-09 01:13:50.023 pm traceHotTub polling all

dev:8202022-09-09 01:13:50.022 pm traceHotTub polling.. refreshAll is true

dev:8202022-09-09 01:13:50.021 pm infoHotTub refresh()...

dev:8202022-09-09 01:13:50.017 pm infoHotTub configure()..

dev:8202022-09-09 01:13:50.017 pm infoHotTub configuring the switch and energy reporting..

dev:8202022-09-09 01:13:50.015 pm infoHotTub Auto polling is enabled, polling interval is 60 seconds

dev:8202022-09-09 01:13:49.983 pm infoHotTub Debug logging will be automatically switched off after 24 hours

dev:8202022-09-09 01:13:49.957 pm infoHotTub Debug logging is true Description text logging is true

dev:8202022-09-09 01:13:49.956 pm infoHotTub Updating HotTub (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

dev:8202022-09-09 01:13:12.451 pm infoTuya Zigbee Metering Plug refresh()...

dev:8202022-09-09 01:13:12.447 pm infoTuya Zigbee Metering Plug configure()..

dev:8202022-09-09 01:13:12.445 pm infoTuya Zigbee Metering Plug configuring the switch and energy reporting..

dev:8202022-09-09 01:13:12.444 pm infoTuya Zigbee Metering Plug Auto polling is enabled, polling interval is 60 seconds

dev:8202022-09-09 01:13:12.411 pm infoTuya Zigbee Metering Plug Debug logging is false Description text logging is true

dev:8202022-09-09 01:13:12.409 pm infoTuya Zigbee Metering Plug Updating null (Tuya Zigbee Metering Plug) model TS011F presence: null AlwaysOn is false

dev:8202022-09-09 01:13:12.333 pm infoTuya Zigbee Metering Plug Initialize()...

dev:8202022-09-09 01:13:07.348 pm infoTuya Zigbee Metering Plug refresh()...

dev:8202022-09-09 01:13:07.344 pm infoTuya Zigbee Metering Plug configure()..

dev:8202022-09-09 01:13:07.278 pm infoTuya Zigbee Metering Plug Installed()...

and for test

dev:8202022-09-09 01:17:51.115 pm tracesending test: [zdo bind 0x5CD3 0x01 0x01 0x0006 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0702 {70B3D52B6000F426} {}, zdo bind 0x5CD3 0x01 0x01 0x0B04 {70B3D52B6000F426} {}, he cmd 0x5CD3 0x01 6 2 {}, delay 200]

so its quite possible this is defective....

[kkossev]

Yes, the logs are the same - nothing received from the device.
So it may be either defective, or something specific for HE during the inital pairing procedure prevents it from working here. Probably the fastest solution would be to return it of you can an get another zigbee plug.

[tim.ocallag]

will do...i really appreciate all of your help.... your driver really has a lot of options for digging in.Thx

[kkossev]

The development branch was updated to version 1.6.0, timeStamp 2022/09/10 1:02 PM .

The first major change is the return of the automatic reporting configuration for energy, power, voltage and amperate readings changes. Many thanks to @guyeeba for the feedback and bug fixes! In the recent Tuya firmware updates, it seems like the automatic reporting is back for some plugs. Whether the automatic reporting (not by polling!) will work or not for your device depends on the particular model and manufacturer and most importantly - depends on the Tuya device firmware version. In the past years Tuya was periodiclaly enabling, then disabling, then again enabling the automatic reporting for power/voltaga/amperage. So there is not a 100% sure way to determine whether a Tuya metering plug requres polling or not. The only way is to test it..

This new option (enabled by default!) will try to configure the automatic reporting each time when the 'Save' button from the Preferences section is clicked. As mentioned, even if the device returns 'succes' code (can be seen in the debug logs), there is no guarantee that the automaic reporting will work. This can be checked by switching off the old option " Automatic polling" and observing the logs. If there are new W/V/A events in the next few hours - then the automatic reporting works, otherwise - it does not work for your device and you must continue to use the software polling option in this driver. Both the new "Automatic Reporting Configuration" and the old "Automatic polling" can be enabled at the same time.

There are also individual reporting threshold parameters for the Energy, Power, Voltage and Amperage. If any of these are not needed for your use case, the reporting can be disabled using the existing 'off or on' switches.

The second addition is the "Reset Energy" command. Unlike the zWave devices, most of the Zigbee devices do not have an explicit Reset command supported in the firmware, so resetting the energy reading is simulated by storing the actual energy reading in a state and then subtracting it from the new energy readings. The custom 'resetEnergy' command can be invoked from RM5 rule every month or every week, etc..