Edge Driver or Device Handeler for a TUYA (Zemismart) Zigbee plug with energy mesurment capabilities

Hi @allmac

That app is not available in my region and therefore I don’t know how it works or what devices work.

The driver uses the powerMeter and energyMeter stock capabilities, I don’t know if they don’t work in the app because they are the edge drive type instead of DTH

1 Like

Hi @allmac,

I try to use on mine. Unfortunately doesn’t shows on St Energy Life app.

@Mariano_Colmenarejo here a got the same problem reported by @Noe_Bailly.

Could you help with it?

This is my CLI report:

2022-08-30T13:51:14.295473987+00:00 DEBUG Zigbee Switch Power Mc driver device thread event handled
2022-08-30T13:51:27.614948322+00:00 PRINT Virtual Calendar Mc <<<< sun_rise_Offset: 271 Min
2022-08-30T13:51:27.621610655+00:00 PRINT Virtual Calendar Mc <<<< sun_set_offset: -424 Min
2022-08-30T13:51:27.631123655+00:00 INFO Virtual Calendar Mc <Device: cf2df8dd-6392-431b-abe4-c3748087ec2a (My Calendar)> emitting event: {“attribute_id”:“sunRiseOffset”,“capability_id”:“legendabsolute60149.sunRiseOffset1”,“component_id”:“main”,“state”:{“value”:271},“visibility”:{“displayed”:false}}
2022-08-30T13:51:27.658140655+00:00 INFO Virtual Calendar Mc <Device: cf2df8dd-6392-431b-abe4-c3748087ec2a (My Calendar)> emitting event: {“attribute_id”:“sunSetOffset”,“capability_id”:“legendabsolute60149.sunSetOffset1”,“component_id”:“main”,“state”:{“value”:-424},“visibility”:{“displayed”:false}}
2022-08-30T13:51:27.685918988+00:00 INFO Virtual Calendar Mc <Device: cf2df8dd-6392-431b-abe4-c3748087ec2a (My Calendar)> emitting event: {“attribute_id”:“localDate”,“capability_id”:“legendabsolute60149.localDate”,“component_id”:“main”,“state”:{“value”:“2022/08/30 10:51”},“visibility”:{“displayed”:false}}
2022-08-30T13:51:27.711333655+00:00 INFO Virtual Calendar Mc <Device: cf2df8dd-6392-431b-abe4-c3748087ec2a (My Calendar)> emitting event: {“attribute_id”:“localHour”,“capability_id”:“legendabsolute60149.localHour”,“component_id”:“main”,“state”:{“value”:1051},“visibility”:{“displayed”:false}}
2022-08-30T13:51:27.736654322+00:00 INFO Virtual Calendar Mc <Device: cf2df8dd-6392-431b-abe4-c3748087ec2a (My Calendar)> emitting event: {“attribute_id”:“localHourTwo”,“capability_id”:“legendabsolute60149.localHourTwo”,“component_id”:“main”,“state”:{“value”:1051},“visibility”:{“displayed”:false}}
2022-08-30T13:51:27.759291322+00:00 DEBUG Virtual Calendar Mc My Calendar device thread event handled
2022-08-30T13:51:31.364785322+00:00 ERROR Zigbee Siren Mc driver thread encountered error: [string “st/zigbee/device_management.lua”]:136: attempt to call a nil value (method ‘check_monitored_attributes’)
2022-08-30T13:51:32.983366655+00:00 DEBUG ST Zigbee Button Mc driver device thread event handled
2022-08-30T13:51:35.418465989+00:00 INFO Zigbee Motion Sensor Frient Doing health check read for [17B5]:0500:0002
2022-08-30T13:51:35.494101656+00:00 INFO Zigbee Motion Sensor Frient <ZigbeeDevice: ca74a434-26fc-43d9-b447-2420601e6304 [0x17B5] (Sensor do Lavabo)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x17B5, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2022-08-30T13:51:35.606271322+00:00 DEBUG Zigbee Motion Sensor Frient driver device thread event handled
2022-08-30T13:51:37.154975989+00:00 DEBUG Zigbee Contact Mc driver device thread event handled
2022-08-30T13:51:37.627152989+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-08-30T13:51:37.641406323+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received lifecycle event: infoChanged
2022-08-30T13:51:37.649194989+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-08-30T13:51:37.654953989+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]=
2022-08-30T13:51:37.660261989+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 1.0
2022-08-30T13:51:37.665523323+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 10
2022-08-30T13:51:37.671678323+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 255
2022-08-30T13:51:37.677819323+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 1.0
2022-08-30T13:51:37.683080656+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= Yes
2022-08-30T13:51:37.688754989+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 10
2022-08-30T13:51:37.694005989+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 0.0
2022-08-30T13:51:37.699224323+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= -3
2022-08-30T13:51:37.704845989+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= Plug
2022-08-30T13:51:37.710496323+00:00 PRINT Zigbee Switch Power Mc device.preferences[infoChanged]= 10.0
2022-08-30T13:51:37.716129989+00:00 PRINT Zigbee Switch Power Mc Device ID <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)>
2022-08-30T13:51:37.721271989+00:00 PRINT Zigbee Switch Power Mc Manufacturer >>> _TZ3000_9vo5icau Manufacturer_Len >>> 16
2022-08-30T13:51:37.726434323+00:00 PRINT Zigbee Switch Power Mc Model >>> TS011F Model_len >>> 6
2022-08-30T13:51:37.731580989+00:00 PRINT Zigbee Switch Power Mc Memory >>>>>>> 967.400390625 Kbytes
2022-08-30T13:51:37.737206989+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T13:51:44.303935990+00:00 DEBUG Zigbee Switch Power Mc driver device thread event handled

1 Like

Hi @Dienzora

What a problem?
could you be more specific? Thank you

1 Like

@Mariano_Colmenarejo many users are reporting that when they switched from DTH to Edge Drivers, they loose power repororting in Energy Life app.
With DTH energy was reported to Energy Life app, and with driver is not.
This is what we (you and @TAustin) tried to add to virtual meter, and ran into problem of not reporting.
Now this is affecting physical metering devices, such as plugs.
Maybe @nayelyz needs to report this to her team or provide what needs to be added to drivers to add this function back.

2 Likes

Hi Mariano, trigger is delayed and didn’t run automation.

1 Like

@jody.albritton
Also, it is ridiculous that region restrictions are applied to developers too. How can developers create successful driver or app, if they have thise restrictions. Devs from restricted areas are trying to develop drivers and apps for all regions. This should be changed.

2 Likes

Hi @Dienzora

Sorry, in that log I can’t see anything because there are events and messages from several devices and I don’t know which one is affected and I don’t know how the automation is done to know what I have to look for

1 Like

Edge drivers are not supported yet in the SmartThings Energy app, them being supported is on the roadmap, but there’s no ETA yet.

What do you mean by this? Which drivers don’t work in certain regions?
About “apps” are you referring to ST Energy? The statement above would explain the behavior of devices not appearing there.

1 Like

The automation is => 1 watt then turn on a light (I created just for testing) so until I refresh, it doesn’t trigger the automation.

In the device detail view power meter you can see the real power without refresh?

@nayelyz

I understand now that edge drivers are not supported yet in the energy Life app.
I don’t understand why devs have any regional restrictions. How can they create driver or app if they can’t see final results, when features are not available in their region. SmartLightning is another example
Devs can’t see if driver capabilities are showing in SmartLightning if they don’t have it

1 Like

Did do nothing, but this is the log:

2022-08-30T15:30:15.930635691+00:00 DEBUG Zigbee Switch Power Mc driver device thread event handled
2022-08-30T15:30:24.284866359+00:00 TRACE Zigbee Switch Power Mc Received event with handler capability
2022-08-30T15:30:24.293982359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2022-08-30T15:30:24.300250359+00:00 TRACE Zigbee Switch Power Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-08-30T15:30:24.307374025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1B1C, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2022-08-30T15:30:24.330315025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1B1C, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-08-30T15:30:24.357455692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1B1C, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0400 > > >
2022-08-30T15:30:24.383543359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1B1C, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-08-30T15:30:24.405334359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T15:30:24.482427025+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:30:24.504540025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x70, rssi: -72, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x70, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x050B, ZclStatus: SUCCESS, DataType: Int16, ActivePower: 7 > > > >
2022-08-30T15:30:24.521477359+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T15:30:24.527577025+00:00 INFO Zigbee Switch Power Mc Executing ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
2022-08-30T15:30:24.540193025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“component_id”:“main”,“state”:{“unit”:“W”,“value”:7.0}}
2022-08-30T15:30:24.583053025+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T15:30:24.593049025+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:30:24.607039359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x70, rssi: -72, body_length: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x71, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint48, CurrentSummationDelivered: 0x000000000219 > > > >
2022-08-30T15:30:24.627962359+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T15:30:24.916866692+00:00 INFO Zigbee Switch Power Mc Executing ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
2022-08-30T15:30:24.924501692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“energy”,“capability_id”:“energyMeter”,“component_id”:“main”,“state”:{“unit”:“kWh”,“value”:537.0}}
2022-08-30T15:30:24.946981359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T15:30:24.955730692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:30:24.964746359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x70, rssi: -72, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x72, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0400, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-08-30T15:30:24.984468692+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T15:30:24.990691359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:30:25.001556359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x6C, rssi: -73, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x73, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-08-30T15:30:25.017101025+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T15:30:25.022839692+00:00 INFO Zigbee Switch Power Mc Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
2022-08-30T15:30:25.031212692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“LQI: 108 … RSSI: -73 dBm”},“visibility”:{“displayed”:true}}
2022-08-30T15:30:25.068665025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-08-30T15:30:25.090657359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled

I found this event in the log: Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“component_id”:“main”,“state”:{“unit”:“W”,“value”:7.0}}

but it does’t call when I start to charging my phone, only when I refresh it.

Hi @Dienzora

The device is working fine, it emits the power 7.0w event.

If the automation does not fire, it may be that it is not well written or that the app does not work correctly in this attribute condition.

if you can share the automation and tag to @nayelyz or @andresg

Mariano, but only emits the power when I refreshed it. Is it normal?

@nayelyz, could you help with this?

This is my simple test automation:

I don’t know.
Can you send a log of when the device is off, you press On in the app and do not touch anything else?

Yeah!

Here is it (Turning On):

022-08-30T15:56:12.154377833+00:00 DEBUG Zigbee Switch Power Mc driver device thread event handled
2022-08-30T15:56:18.043821750+00:00 TRACE Zigbee Switch Power Mc Received event with handler capability
2022-08-30T15:56:18.052054865+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received command: {“args”:{},“capability”:“switch”,“command”:“on”,“component”:“main”,“positional_args”:{}}
2022-08-30T15:56:18.058004505+00:00 TRACE Zigbee Switch Power Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-08-30T15:56:18.077348839+00:00 DEBUG Zigbee Switch Power Mc Base de Carregamento device thread event handled
2022-08-30T15:56:18.151237098+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:56:18.159307464+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x74, rssi: -71, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x62, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x01, ZclStatus: SUCCESS > > >
2022-08-30T15:56:18.174908594+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T15:56:18.180165888+00:00 INFO Zigbee Switch Power Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-08-30T15:56:18.186522398+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“on”}}
2022-08-30T15:56:18.208111521+00:00 DEBUG Zigbee Switch Power Mc Base de Carregamento device thread event handled

(Turning Off):

2022-08-30T15:58:12.183934619+00:00 DEBUG Zigbee Switch Power Mc driver device thread event handled
2022-08-30T15:58:16.975288099+00:00 TRACE Zigbee Switch Power Mc Received event with handler capability
2022-08-30T15:58:16.984131185+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received command: {“args”:{},“capability”:“switch”,“command”:“off”,“component”:“main”,“positional_args”:{}}
2022-08-30T15:58:16.994092163+00:00 TRACE Zigbee Switch Power Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-08-30T15:58:17.012461676+00:00 DEBUG Zigbee Switch Power Mc Base de Carregamento device thread event handled
2022-08-30T15:58:17.141443135+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T15:58:17.150631060+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1B1C, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x70, rssi: -72, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x65, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2022-08-30T15:58:17.166626387+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T15:58:17.172772458+00:00 INFO Zigbee Switch Power Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2022-08-30T15:58:17.180591699+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: 964e335d-646a-4145-9f89-3f20b4992f17 [0x1B1C] (Base de Carregamento)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“off”}}
2022-08-30T15:58:17.201466798+00:00 DEBUG Zigbee Switch Power Mc Base de Carregamento device thread event handled

On and Off is logging well, power metering doesn’t .

It seems that the reports of cluster 0x0B04, attribute 0x050B, are not configured correctly and it only sends data when driver read it.

Please could you do the following:

  • Uninstall the device from the app
  • Prepare CLI to capture device entire pairing log
  • Add device with search nearby in app
  • Capture the entire log, which will take a few seconds to start, without touching anything in the app until the log stops, for at least 20 seconds, to see the responses of the device in each attribute

here is it: (Part I)

2022-08-30T16:17:33.180550692+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-08-30T16:17:33.208237359+00:00 TRACE Zigbee Switch Power Mc Zigbee Device: a3288c78-4d4d-4519-9e4f-c7d33dac257e Manufacturer: _TZ3000_9vo5icau Model: TS011F
[1]: Basic, Identify, Groups, Scenes, OnOff, SimpleMetering, ElectricalMeasurement, 0xE000, 0xE001 [242]:
2022-08-30T16:17:33.213705026+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received lifecycle event: added
2022-08-30T16:17:33.233083359+00:00 TRACE Zigbee Switch Power Mc Received event with handler device_lifecycle
2022-08-30T16:17:33.238646692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received lifecycle event: doConfigure
2022-08-30T16:17:33.246953359+00:00 TRACE Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received unhandled lifecycle event: added
2022-08-30T16:17:33.252956026+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:33.261183692+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-08-30T16:17:33.268541692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: ElectricalMeasurement, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:33.296915359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x050B, DataType: Int16, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-08-30T16:17:33.314683026+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:33.332544026+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-08-30T16:17:33.366067359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: SimpleMetering, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:33.443401692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0400, DataType: Int24, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-08-30T16:17:33.554471026+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint48, minimum_reporting_interval: 0x0005, maximum_reporting_interval: 0x0E10, reportable_change: 0x000000000001 > > > >
2022-08-30T16:17:33.669062359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0605 > > >
2022-08-30T16:17:33.767146692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0604 > > >
2022-08-30T16:17:33.885605026+00:00 ERROR Zigbee Siren Mc driver thread encountered error: [string “st/zigbee/device_management.lua”]:136: attempt to call a nil value (method ‘check_monitored_attributes’)
2022-08-30T16:17:34.025368026+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0302 > > >
2022-08-30T16:17:34.148144359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0301 > > >
2022-08-30T16:17:34.319304026+00:00 PRINT Zigbee Switch Power Mc <<<< random_state >>>>
2022-08-30T16:17:34.423413692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> emitting event: {“attribute_id”:“randomOnOff”,“capability_id”:“legendabsolute60149.randomOnOff2”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-08-30T16:17:34.524988692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> emitting event: {“attribute_id”:“randomNext”,“capability_id”:“legendabsolute60149.randomNextStep2”,“component_id”:“main”,“state”:{“value”:“Inactive”}}
2022-08-30T16:17:34.604897025+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: 49c06661-d38c-41ba-9996-e1ccf15e33c1 [0x8C95] (TS011F Plug)>
2022-08-30T16:17:34.614823359+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: 49c06661-d38c-41ba-9996-e1ccf15e33c1 [0x8C95] (TS011F Plug)> 1
2022-08-30T16:17:34.633957025+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: 49c06661-d38c-41ba-9996-e1ccf15e33c1 [0x8C95] (TS011F Plug)> 2
2022-08-30T16:17:34.654105692+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: 49c06661-d38c-41ba-9996-e1ccf15e33c1 [0x8C95] (TS011F Plug)> 14
2022-08-30T16:17:34.660826359+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)>
2022-08-30T16:17:34.666829692+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> 1
2022-08-30T16:17:34.674787359+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> 2
2022-08-30T16:17:34.687453359+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> 14
2022-08-30T16:17:34.704348359+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: 6835152e-5659-41cc-9046-43373f3deb38 [0x2E4D] (TS011F Plug)>
2022-08-30T16:17:34.721411359+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: 6835152e-5659-41cc-9046-43373f3deb38 [0x2E4D] (TS011F Plug)> 1
2022-08-30T16:17:34.733839359+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: 6835152e-5659-41cc-9046-43373f3deb38 [0x2E4D] (TS011F Plug)> 2
2022-08-30T16:17:34.740071692+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: 6835152e-5659-41cc-9046-43373f3deb38 [0x2E4D] (TS011F Plug)> 13
2022-08-30T16:17:34.751986692+00:00 PRINT Zigbee Switch Power Mc device_running[id]= <ZigbeeDevice: 79f92b74-4c56-4adc-a798-1146bf6b10d8 [0x9EBE] (TS011F Plug)>
2022-08-30T16:17:34.766115025+00:00 PRINT Zigbee Switch Power Mc device_running, random_Step= <ZigbeeDevice: 79f92b74-4c56-4adc-a798-1146bf6b10d8 [0x9EBE] (TS011F Plug)> 1
2022-08-30T16:17:34.776377025+00:00 PRINT Zigbee Switch Power Mc device_running, random_totalStep= <ZigbeeDevice: 79f92b74-4c56-4adc-a798-1146bf6b10d8 [0x9EBE] (TS011F Plug)> 2
2022-08-30T16:17:34.785114025+00:00 PRINT Zigbee Switch Power Mc device_running, random_timer= <ZigbeeDevice: 79f92b74-4c56-4adc-a798-1146bf6b10d8 [0x9EBE] (TS011F Plug)> 14
2022-08-30T16:17:34.793939025+00:00 PRINT Zigbee Switch Power Mc random_state >>>>> Inactive
2022-08-30T16:17:34.804210359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:34.814175692+00:00 TRACE Zigbee Switch Power Mc Found DeviceLifecycleDispatcher handler in Zigbee_Switch
2022-08-30T16:17:34.844282025+00:00 TRACE Zigbee Switch Power Mc Found CapabilityCommandDispatcher handler in Zigbee_Switch
2022-08-30T16:17:34.851882692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2022-08-30T16:17:34.883210692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-08-30T16:17:34.909160359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0400 > > >
2022-08-30T16:17:34.948870359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-08-30T16:17:34.978760359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: ElectricalMeasurement, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:35.008538692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x050B, DataType: Int16, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-08-30T16:17:35.085104692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:35.110964692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C > > > >
2022-08-30T16:17:35.169599359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 84BA20FFFE6D4BA4, src_endpoint: 0x01, cluster: SimpleMetering, dest_addr_mode: 0x03, dest_address: 286D97000200A55F, dest_endpoint: 0x01 > > >
2022-08-30T16:17:35.189399025+00:00 DEBUG ST Zigbee Button Mc driver device thread event handled
2022-08-30T16:17:35.248152359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0400, DataType: Int24, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0x0E10, reportable_change: 1 > > > >
2022-08-30T16:17:35.290796359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5E16, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint48, minimum_reporting_interval: 0x0005, maximum_reporting_interval: 0x0E10, reportable_change: 0x000000000001 > > > >
2022-08-30T16:17:35.316236692+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.334248025+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.344202692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x68, rssi: -74, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x64 >, < BindRequestResponse || status: 0x00 > > >
2022-08-30T16:17:35.403186692+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.409378692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.425370025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x68, rssi: -74, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7E, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2022-08-30T16:17:35.460421359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.477186692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.492100025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x68, rssi: -74, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x65 >, < BindRequestResponse || status: 0x00 > > >
2022-08-30T16:17:35.528992359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.543031359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.561917692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x68, rssi: -74, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7F, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2022-08-30T16:17:35.588084359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.594473359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.604198359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x68, rssi: -74, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x66 >, < BindRequestResponse || status: 0x00 > > >
2022-08-30T16:17:35.640087025+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.646685025+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.658846692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x68, rssi: -74, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x00, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, direction: 0x00, attr_id: 0x0400 > > > >
2022-08-30T16:17:35.688292692+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.694472359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.705117359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x68, rssi: -74, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x01, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2022-08-30T16:17:35.725552359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.731791359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.742121359+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x68, rssi: -74, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x02, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0605, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-08-30T16:17:35.762854359+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.769535359+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.779461692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x68, rssi: -74, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x03, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0604, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-08-30T16:17:35.800049692+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.806167692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.817108358+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x68, rssi: -74, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0302, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-08-30T16:17:35.838133358+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.844480692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.888682025+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0x68, rssi: -74, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x05, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0301, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-08-30T16:17:35.909753358+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.915829692+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.927407358+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0x68, rssi: -74, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x06, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x050B, ZclStatus: SUCCESS, DataType: Int16, ActivePower: 0 > > > >
2022-08-30T16:17:35.948478025+00:00 DEBUG Zigbee Switch Power Mc TS011F Plug device thread event handled
2022-08-30T16:17:35.954691358+00:00 TRACE Zigbee Switch Power Mc Received event with handler zigbee
2022-08-30T16:17:35.965603692+00:00 INFO Zigbee Switch Power Mc <ZigbeeDevice: a3288c78-4d4d-4519-9e4f-c7d33dac257e [0x5E16] (TS011F Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x5E16, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0x68, rssi: -74, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x07, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >
2022-08-30T16:17:35.985521692+00:00 TRACE Zigbee Switch Power Mc Found ZigbeeMessageDispatcher handler in Zigbee_Switch
2022-08-30T16:17:35.990683692+00:00 INFO Zigbee Switch Power Mc Executing ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower