Xiaomi Mi Smart Plug (New Model) Device Handler

I know I am in the wrong forum but wondering if there would be any experts who can suggest a way to track the power consumption in my Meross plugs. Pairing with smartthings was very simple and automations work like a charm but without power tracking in the smartthings app. However, I am able to track power through the meross app which means the smart plug has energy monitoring feature so wondering if anyone has any DTH for this or can suggest any route?

Hi, I have also a Tapo p110 plug that does not report energy in SmartThings. What should I do ?

Does anyone know if theres an edge driver for this plug?

I have drivers for Xiomi plugs , but there are many models around, which one you have

Its the MI Smart socket zigbee model ZNCZ04LM

this model is supported

Its not showing power or any other value in my case.

some of the characteristics are updated several times a day, have you tested it with load?
Without the device and logs, it’s harder to debug

? Select a driver. 2
connecting… connected
2022-06-29T21:49:12.869619649+00:00 TRACE Xiaomi Plug Setup driver plug with lifecycle handlers:
DeviceLifecycleDispatcher: plug
default_handlers:
driverSwitched:
added:
doConfigure:
infoChanged:
child_dispatchers:

2022-06-29T21:49:12.875427983+00:00 TRACE Xiaomi Plug Setup driver plug with Capability handlers:
CapabilityCommandDispatcher: plug
default_handlers:
energyMeter:
resetEnergyMeter
refresh:
refresh
switch:
on
off
child_dispatchers:

2022-06-29T21:49:12.885899649+00:00 TRACE Xiaomi Plug Setup driver plug with Zigbee handlers:
ZigbeeMessageDispatcher: plug
default_handlers:
attr:
ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF02
ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF01
ZclClusterAttributeValueHandler: cluster: DeviceTemperatureConfiguration, attribute: CurrentTemperature
ZclClusterAttributeValueHandler: cluster: AnalogInput, attribute: PresentValue
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: InstantaneousDemand
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Multiplier
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: Divisor
ZclClusterAttributeValueHandler: cluster: SimpleMetering, attribute: CurrentSummationDelivered
ZclClusterAttributeValueHandler: cluster: OnOff, attribute: OnOff
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerMultiplier
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ACPowerDivisor
ZclClusterAttributeValueHandler: cluster: ElectricalMeasurement, attribute: ActivePower
global:
ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
cluster:
zdo:
child_dispatchers:

2022-06-29T21:49:12.933425316+00:00 TRACE Xiaomi Plug Zigbee Device: 62832676-f211-40ce-b27f-15085f7e9cbf
Manufacturer: LUMI Model: lumi.plug.mmeu01
[1]: Basic, DeviceTemperatureConfiguration, Identify, Groups, Scenes, OnOff, Alarms, SimpleMetering, ElectricalM
easurement [242]:
2022-06-29T21:49:12.942571649+00:00 DEBUG Xiaomi Plug driver device thread event handled
2022-06-29T21:49:12.948135316+00:00 TRACE Xiaomi Plug Received event with handler resync
2022-06-29T21:49:12.953307649+00:00 TRACE Xiaomi Plug Received event with handler environment_info
2022-06-29T21:49:12.966729983+00:00 TRACE Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xia
omi EU Plug)> received unhandled lifecycle event: init
2022-06-29T21:49:12.971831316+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:12.977342983+00:00 TRACE Xiaomi Plug Received event with handler environment_info
2022-06-29T21:49:12.982602316+00:00 DEBUG Xiaomi Plug Z-Wave hub node ID environment changed.
2022-06-29T21:49:12.989559983+00:00 TRACE Xiaomi Plug Received event with handler driver_lifecycle
2022-06-29T21:49:12.996266649+00:00 TRACE Xiaomi Plug Received event with handler driver_lifecycle
2022-06-29T21:49:13.003903316+00:00 TRACE Xiaomi Plug Received event with handler device_lifecycle
2022-06-29T21:49:13.009762316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received lifecycle event: added
2022-06-29T21:49:13.017512983+00:00 TRACE Xiaomi Plug Found DeviceLifecycleDispatcher handler in plug
2022-06-29T21:49:13.023268649+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:13.029365983+00:00 TRACE Xiaomi Plug Received event with handler device_lifecycle
2022-06-29T21:49:13.315539983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received lifecycle event: doConfigure
2022-06-29T21:49:13.328718983+00:00 TRACE Xiaomi Plug Found DeviceLifecycleDispatcher handler in plug
2022-06-29T21:49:13.334613983+00:00 TRACE Xiaomi Plug Found CapabilityCommandDispatcher handler in plug
2022-06-29T21:49:13.346325983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody |
| < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x050B > > >
2022-06-29T21:49:13.370284316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCL
Header || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-06-29T21:49:13.388727316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCL
Header || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0400 > > >
2022-06-29T21:49:13.406947316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader ||
frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0000 > > >
2022-06-29T21:49:13.439935316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader |
| seqno: 0x00 >, < BindRequest || src_address: 04CF8CDF3C7E5037, src_endpoint: 0x01, cluster: ElectricalMeasurement, des
t_addr_mode: 0x03, dest_address: 286D97000207E580, dest_endpoint: 0x01 > > >
2022-06-29T21:49:13.458841650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, < ZCLMessageBody |
| < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfig
uration || direction: 0x00, attr_id: 0x050B, DataType: Int16, minimum_reporting_interval: 0x0001, maximum_reporting_inte
rval: 0x0E10, reportable_change: 1 > > > >
2022-06-29T21:49:13.486624316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader |
| seqno: 0x00 >, < BindRequest || src_address: 04CF8CDF3C7E5037, src_endpoint: 0x01, cluster: SimpleMetering, dest_addr

mode: 0x03, dest_address: 286D97000207E580, dest_endpoint: 0x01 > > >

022-06-29T21:49:13.512011316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCL
Header || 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-06-29T21:49:13.535145316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, < ZCLMessageBody || < ZCL
Header || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration
|| direction: 0x00, attr_id: 0x0400, DataType: Int24, minimum_reporting_interval: 0x0001, maximum_reporting_interval: 0
x0E10, reportable_change: 1 > > > >
2022-06-29T21:49:13.558558983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader |
| seqno: 0x00 >, < BindRequest || src_address: 04CF8CDF3C7E5037, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x0
3, dest_address: 286D97000207E580, dest_endpoint: 0x01 > > >
2022-06-29T21:49:13.580604316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpo
int: 0x01, dest_addr: 0x3D80, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader ||
frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direc
tion: 0x00, attr_id: 0x0000, DataType: Boolean, minimum_reporting_interval: 0x0000, maximum_reporting_interval: 0x012C >

2022-06-29T21:49:13.603342650+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:13.611165316+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:13.646775316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xFCC0 >, lqi: 0xA8, rssi: -58, body_length: 0
x0046, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x03, ZCLCommandId: 0x0A >, < Repor
tAttribute || < AttributeRecord || AttributeId: 0x00F7, DataType: OctetString, OctetString: “\x64\x10\x00\x03\x28\x1C\x9
8\x39\x00\x00\x00\x00\x95\x39\x5E\x2A\xAF\x40\x96\x39\x00\x40\x12\x45\x97\x39\x00\x00\x00\x00\x05\x21\x01\x00\x9A\x20\x0
0\x08\x21\x16\x01\x07\x27\x00\x00\x00\x00\x00\x00\x00\x00\x09\x21\x00\x07\x0B\x20\x00\x9B\x10\x00” > > > >
2022-06-29T21:49:13.684489650+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:13.690491983+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:13.701122650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0xA8, rssi: -58,
body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7A, ZCLCommandId: 0x01 >, < ReadAttr
ibuteResponse || < AttributeRecord || AttributeId: 0x050B, ZclStatus: SUCCESS, DataType: Int16, ActivePower: 0 > > > >
2022-06-29T21:49:13.733147316+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:13.738955650+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:13.754656316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xA8, rssi: -58, body_l
ength: 0x000D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x01 >, < ReadAttributeRe
sponse || < AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint48, CurrentSummationDelivered: 0x0
00000001561 > > > >
2022-06-29T21:49:13.775958650+00:00 TRACE Xiaomi Plug Found ZigbeeMessageDispatcher handler in plug
2022-06-29T21:49:13.787699983+00:00 INFO Xiaomi Plug Executing ZclClusterAttributeValueHandler: cluster: ElectricalMeas
urement, attribute: ActivePower
2022-06-29T21:49:13.798133650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“component_id”:“main”,“state”:{“unit”:
“W”,“value”:0.0}}
2022-06-29T21:49:13.857531316+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:13.874554650+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:13.886588316+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xA4, rssi: -59, body_length: 0x
000E, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < Att
ributeRecord || AttributeId: 0x0000, DataType: Boolean, OnOff: false >, < AttributeRecord || AttributeId: 0x00F5, DataTy
pe: Uint32, Uint32: 0x02FFFF00 > > > >
2022-06-29T21:49:13.921364650+00:00 TRACE Xiaomi Plug Found ZigbeeMessageDispatcher handler in plug
2022-06-29T21:49:13.963001316+00:00 INFO Xiaomi Plug Executing ZclClusterAttributeValueHandler: cluster: SimpleMetering
, attribute: CurrentSummationDelivered
2022-06-29T21:49:13.972817650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> emitting event: {“attribute_id”:“energy”,“capability_id”:“energyMeter”,“component_id”:“main”,“state”:{"unit
":“kWh”,“value”:547.3}}
2022-06-29T21:49:13.996271983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.004413316+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.012844650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xA4, rssi: -59, body_l
ength: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7C, ZCLCommandId: 0x01 >, < ReadAttributeRe
sponse || < AttributeRecord || AttributeId: 0x0400, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
2022-06-29T21:49:14.077518317+00:00 TRACE Xiaomi Plug Found ZigbeeMessageDispatcher handler in plug
2022-06-29T21:49:14.086043317+00:00 INFO Xiaomi Plug Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribu
te: OnOff
2022-06-29T21:49:14.092759983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“o
ff”}}
2022-06-29T21:49:14.110373983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.118367650+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.130113650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xA4, rssi: -59, body_length: 0x
0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7D, ZCLCommandId: 0x01 >, < ReadAttributeResponse ||
< AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Boolean, OnOff: false > > > >
2022-06-29T21:49:14.143661983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.149183317+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.158188983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xA8, rssi: -58, body_length: 0
x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x53 >, < BindRequestResponse || status: 0x00 > > >
2022-06-29T21:49:14.172556650+00:00 TRACE Xiaomi Plug Found ZigbeeMessageDispatcher handler in plug
2022-06-29T21:49:14.177984317+00:00 INFO Xiaomi Plug Executing ZclClusterAttributeValueHandler: cluster: OnOff, attribu
te: OnOff
2022-06-29T21:49:14.184432983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> emitting event: {“attribute_id”:“switch”,“capability_id”:“switch”,“component_id”:“main”,“state”:{“value”:“o
ff”}}
2022-06-29T21:49:14.199499650+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.205049317+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.217689317+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: ElectricalMeasurement >, lqi: 0xA8, rssi: -58,
body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7E, ZCLCommandId: 0x07 >, < Configur
eReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: UNREPORTABLE_ATTRIBUTE, direction: 0x00, attr_id:
0x050B > > > >
2022-06-29T21:49:14.231257650+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.238501317+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.247984650+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xA8, rssi: -58, body_length: 0
x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x54 >, < BindRequestResponse || status: 0x00 > > >
2022-06-29T21:49:14.261885317+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.267613983+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.276989317+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xB8, rssi: -54, body_l
ength: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7F, ZCLCommandId: 0x07 >, < ConfigureReport
ingResponse || ZclStatus: SUCCESS > > >
2022-06-29T21:49:14.290295317+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.296053317+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.305099983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: SimpleMetering >, lqi: 0xAC, rssi: -57, body_l
ength: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x00, ZCLCommandId: 0x07 >, < ConfigureReport
ingResponse || < ConfigureReportingResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, direction: 0x00, attr_id: 0x0400

2022-06-29T21:49:14.318904650+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.325184650+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.333165983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xA8, rssi: -58, body_length: 0
x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x55 >, < BindRequestResponse || status: 0x00 > > >
2022-06-29T21:49:14.346960983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.352922317+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.362953983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xA4, rssi: -59, body_length: 0x
0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x01, ZCLCommandId: 0x07 >, < ConfigureReportingRespon
se || ZclStatus: SUCCESS > > >
2022-06-29T21:49:14.377202317+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.382720983+00:00 TRACE Xiaomi Plug Received event with handler device_lifecycle
2022-06-29T21:49:14.395448983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received lifecycle event: infoChanged
2022-06-29T21:49:14.402601983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.410262317+00:00 TRACE Xiaomi Plug Found DeviceLifecycleDispatcher handler in plug
2022-06-29T21:49:14.415419317+00:00 INFO Xiaomi Plug >>info changed: infoChanged
2022-06-29T21:49:14.423460983+00:00 INFO Xiaomi Plug {“242”:{“server_clusters”:,“client_clusters”:[33],“id”:242,“prof
ile_id”:41440,“device_id”:97},“1”:{“server_clusters”:[0,2,3,4,5,6,9,1794,2820],“client_clusters”:[10,25],“model”:“lumi.p
lug.mmeu01”,“device_id”:81,“id”:1,“profile_id”:260,“manufacturer”:“LUMI”}}
2022-06-29T21:49:14.429062983+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:14.621256983+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:49:14.629809983+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: 0xFCC0 >, lqi: 0xA4, rssi: -59, body_length: 0
x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x05, ZCLCommandId: 0x0A >, < Repor
tAttribute || < AttributeRecord || AttributeId: 0x0207, DataType: Boolean, Boolean: false > > > >
2022-06-29T21:49:14.643738317+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:49:42.904610664+00:00 DEBUG Xiaomi Plug driver device thread event handled
2022-06-29T21:50:06.154797250+00:00 TRACE Xiaomi Plug Received event with handler zigbee
2022-06-29T21:50:06.247686583+00:00 INFO Xiaomi Plug <ZigbeeDevice: 62832676-f211-40ce-b27f-15085f7e9cbf [0x3D80] (Xiao
mi EU Plug)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x3D80, src_endpoint
: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8001 >, lqi: 0xA4, rssi: -59, body_length: 0
x000C, < ZDOMessageBody || < ZDOHeader || seqno: 0x57 >, GenericBody: 00 37 50 7E 3C DF 8C CF 04 80 3D > >
2022-06-29T21:50:06.354794583+00:00 DEBUG Xiaomi Plug Xiaomi EU Plug device thread event handled
2022-06-29T21:50:12.914541586+00:00 DEBUG Xiaomi Plug driver device thread event handled
2022-06-29T21:50:42.925091934+00:00 DEBUG Xiaomi Plug driver device thread event handled
2022-06-29T21:51:12.924573948+00:00

what issue we are trying to fix here?

from your long log, I can see

emitting event: {“attribute_id”:“power”,“capability_id”:“powerMeter”,“component_id”:“main”,“state”:{“unit”:
“W”,“value”:0.0}}
emitting event: {“attribute_id”:“energy”,“capability_id”:“energyMeter”,“component_id”:“main”,“state”:{"unit
":“kWh”,“value”:547.3}}

In the app doesnt show any values for power and power consumption and in the logs its reports power as 0W and power consumption as 547.3 kWh. So i have no access to power monitoring. I can only turn it on/off.

maybe there is something with your app, the log doesn’t show any errors so the power and consumption values are delivered to the system.

What you can try is to connect a power hungry device to the plug and see the numbers in the log. Maybe the ST doesn’t update data if the power is 0. Try to re-install ST application or use another mobile device to see if the power monitoring is working.

I don’t know what happened but both in the app and in the web version it was not possible to see any values. On the fifth attempt of deleting and re-pairing the plug, more or less, it started to work for no apparent reason, and it already shows me the power values. But power consumption continues to report 547.4kWh, is this normal?

what you can see in the log?

there are current power consumption and summary energy consumption (over device lifetime?) There is neither UI nor API to reset the energy consumption.

If you have any ideas please share.

I see. If there is no way to reset the accumulated values, it is difficult to do anything with these values. The only way would be to ignore the summary energy consumption and manually add up all the values recorded in the current power consumption every X time/days.

this is how my Fibaro socket (official driver) looks like.
Thus, the chart shows consumption deltas but the total number has a little use.

Maybe you can create another topic with feature request to the ST team.

It looks nice, would definitely be a nice feature. Its a z-wave socket right?

Can i make a suggestion of a useful feature for your xiaomi plug driver?
Is it possible to automatically turn off the socket if the current power stays below a certain value for a certain period of time?
I created a piston on webcore for that, i can share with you if you were interested.