(EDGE Driver-Mc): Zigbee Light Multifunction Mc

Thanks for your help.

I need complete clusters data to see if it can work

Below is complete cluster data, could you please add to driver. It is Aqara motion sensor which stopped working

I have five (5) of them and it looks right, but here are the screenshots from the Thing Mc driver in case I am missing something…

<< updated… new user, won’t allow pictures Here is a link to the Google stored images: https://photos.app.goo.gl/yFtHV5w5Kerh2uKy9 >>

I also checked the Samsung site/API and here is the copy/paste:

Network ID
0A3A
Created
Jul 26, 2023, 9:43 PM
Manufacturer
SmartThingsCommunity
Manufacturer Code
FeeBit RGBW
Model
FB56-ZCW20FB1.2

Network ID
3764
Created
Jul 26, 2023, 9:59 PM
Manufacturer
SmartThingsCommunity
Manufacturer Code
FeeBit RGBW
Model
FB56-ZCW20FB1.2

Network ID
840F
Created
Jul 26, 2023, 9:45 PM
Manufacturer
SmartThingsCommunity
Manufacturer Code
FeeBit RGBW
Model
FB56-ZCW20FB1.2

Network ID
1828
Created
Jul 26, 2023, 9:48 PM
Manufacturer
SmartThingsCommunity
Manufacturer Code
FeeBit RGBW
Model
FB56-ZCW20FB1.2

Network ID
0EC8
Created
Jul 31, 2023, 5:47 PM
Manufacturer
SmartThingsCommunity
Manufacturer Code
FeeBit RGBW
Model
FB56-ZCW20FB1.2

If fingerprint is correct Then it must be works fine

I thought the same thing, but for whatever reason SmartThings will not show that as a valid driver for these devices. :confused:

Anyone else have ideas, thoughts on why it isn’t matching and therefore selectable (in either the app or the website)?

Try with this driver version

───────────────────────────────────────────────────
 Name         Zigbee Light Multifunction Mc             
 Version      2023-08-01T20:40:48.35548803
───────────────────────────────────────────────────

Added to this driver version, try it

───────────────────────────────────────────────────
 Name         Zigbee Motion Sensor Mc
 Version      2023-08-01T21:00:00.506272798        
───────────────────────────────────────────────────
- id: "LUMI/sensor_motion.aq2"
    deviceLabel: Aqara Motion Sensor
    manufacturer: LUMI
    model: lumi.sensor_motion.aq2
    deviceProfileName: motion-illuminance

Whatever you did, worked! All five (5) accepted the new driver and I can actually turn the lights on and off (it is the little things) and change the colors. :slight_smile:

Thank you so much for this and all the work you are doing!!!

I’m glad it works.

I made it pair by model only and disregard manufacturer.

The manufacturer has something, a blank space, … I don’t know

Perhaps the manufacturer of the device could help by saying what characters it has

Could you confirm if your Aqara Device worked with Mariano’s addition?

Yeah, they weren’t very forthcoming on details. I have a follow-up issue. The lights come on, but I cannot turn them off. They come on 88% and stay there (regardless of what brightness I set) and when I try to turn them off, it just β€œblinks” (a very quick off, then back on). Colors change just fine.

Any ideas?

I don’t know why that happens.

The device may have a transition time set for turning it off and on. Try to factory reset it.

If it doesn’t work, I would have to see the logs with the CLI when the level changes or shuts down, to see if any error occurs.

I had already done a factory reset, but went ahead and tried everything β€œfresh” again. No change.

Here are the two log segments from the driver, during an β€œoff” and β€œdim” request:

Off Request: zb-multi-mc_off-before.log - Google Drive
Dim Request: zb-multi-mc_dim-before.log - Google Drive

I did another reset, readded to SmartThings, and recorded (and labeled) the logs in one file doing both an off / on sequence, as well as a dim β€œdown” and β€œup” sequence.

All 4 Requests: zlm-after.log - Google Drive

Do these help?

Hi @Mariano_Colmenarejo
I want to control the downlight(zigbee) device from Smart Things.
Can you add it?

Hi @oxtr2869
Added to this driver version

───────────────────────────────────────────────────
 Name         Zigbee Light Multifunction Mc        2      
 Version      2023-08-04T13:35:49.653505209        
───────────────────────────────────────────────────
- id: "_TZ3210_pz9zmxjj/TS0502B"
    deviceLabel: TS0502B LED
    manufacturer: _TZ3210_pz9zmxjj
    model: TS0502B
    deviceProfileName: level-colortemp-2000-6500

In the logs there are no errors, the Off command is sent to the device:

2023-08-03T22:33:28.144300053+00:00 PRINT Zigbee Light Multifunction Mc Turn OFF >>>>>>>>>>>>>>>>
2023-08-03T22:33:28.145185845+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xDF88, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < Off || > > >

and the device responds with default response success and the defaults emit the off event in the App and platform:

2023-08-03T22:33:28.402389636+00:00 TRACE Zigbee Light Multifunction Mc Received event with handler zigbee
2023-08-03T22:33:28.403054053+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDF88, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -69, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
2023-08-03T22:33:28.411770178+00:00 TRACE Zigbee Light Multifunction Mc Found ZigbeeMessageDispatcher handler in zigbee_light_multifunctions
2023-08-03T22:33:28.417785720+00:00 INFO Zigbee Light Multifunction Mc Executing ZclGlobalCommandHandler: cluster: OnOff, command: DefaultResponse
2023-08-03T22:33:28.419020595+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> emitting event: {β€œcapability_id”:β€œswitch”,β€œattribute_id”:β€œswitch”,β€œstate”:{β€œvalue”:β€œoff”},β€œcomponent_id”:β€œmain”}

If light has not turned off, then the device is lying and does not execute the command

There are no errors in the logs.
The app command is received to set level to 99%

2023-08-03T22:34:36.413215995+00:00 TRACE Zigbee Light Multifunction Mc Received event with handler capability
2023-08-03T22:34:36.414875954+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> received command: {β€œargs”: {"level ":99},β€œcomponent”:β€œmain”,β€œpositional_args”:[99],β€œcommand”:β€œsetLevel”,β€œcapability”:β€œswitchLevel”}

The MoveToLevelWithOnOff command is sent with level 99% (0xFB) to the device and since it determines that it is off, the On command is also sent:

2023-08-03T22:34:36.416975287+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> sending Zigbee message: < Zigbe eMessageTx || Uint16: 0x0000, <AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xDF88, dest_endpoint: 0x0B, profile: 0x0104, cluster: Level >, < ZCLMessageBody || <ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x04 >, <MoveToLevelWithOnOff || level: 0xFB, transition_time: 0xFFFF, options_mask: 0x00, options_override: 0x00 > > >
2023-08-03T22:34:36.432710329+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> sending Zigbee message: < Zigbe eMessageTx || Uint16: 0x0000, <AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xDF88, dest_endpoint: 0x0B, profile: 0x0104, cluster: OnOff >, < ZCLMessageBody || <ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x01 >, < On || > > >

The device responds with default response successful for both the MoveToLevelWithOnOff command and the On command:

2023-08-03T22:34:36.831577912+00:00 TRACE Zigbee Light Multifunction Mc Received event with handler zigbee**
2023-08-03T22:34:36.838017578+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> received Zigbee message: < Zig beeMessageRx || type: 0x00, <AddressHeader || src_addr: 0xDF88, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xFF, rssi: -59, body_length: 0x0005, < ZCLMessageBody || <ZCLHeader || frame_ctrl: 0x18, seqno: 0x7F, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x04, ZclStatus: SUCCESS > > >
2023-08-03T22:34:36.842438870+00:00 DEBUG Zigbee Light Multifunction Mc FeeBit RGBW device thread event handled**
2023-08-03T22:34:37.461899328+00:00 DEBUG Zigbee Light Multifunction Mc FeeBit RGBW device thread event handled**
2023-08-03T22:34:37.665952412+00:00 TRACE Zigbee Light Multifunction Mc Received event with handler zigbee**
2023-08-03T22:34:37.666607870+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> received Zigbee message: < Zig beeMessageRx || type: 0x00, <AddressHeader || src_addr: 0xDF88, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xFF, rssi: -59, body_length: 0x0008, < ZCLMessageBody || <ZCLHeader || frame_ctrl: 0x18, seqno: 0x01, ZCLCommandId: 0x01 >, < ReadAttributeResponse || <AttributeRecord || AttributeId: 0x0000, lStatus: SUCCESS, DataType: Boolean, OnOff: true > > > >

Defaults emit the on event in the App and platform.

2 sec later the currentLevel attribute is read and the device returns success and a value of 88% (0xE0) and the level 88% is issued

2023-08-03T22:34:38.094375537+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> received Zigbee message: < Zig beeMessageRx || type: 0x00, <AddressHeader || src_addr: 0xDF88, src_endpoint: 0x0B, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Level >, lqi: 0xFF, rssi: -59, body_length: 0x0008, < ZCLMessageBody || <ZCLHeader || frame_ctrl: 0x18, seqno: 0x02, ZCLCommandId: 0x01 >, < ReadAttributeResponse || <AttributeRecord || AttributeId: 0x0000, ZclStatus: SUCCESS, DataType: Uint8, CurrentLevel: 0xE0 > > > >
2023-08-03T22:34:38.106495620+00:00 INFO Zigbee Light Multifunction Mc Executing ZclClusterAttributeValueHandler: cluster: Level, attribute: CurrentLevel
2023-08-03T22:34:38.111613412+00:00 INFO Zigbee Light Multifunction Mc <ZigbeeDevice: f95d196c-13f5-4bee-b31e-45d282159d96 [0xDF88] (Upper Cabinet 3)> emitting event: {β€œcapability_id”: β€œswitchLevel” ,β€œattribute_id”:"level",β€œstate”:{β€œvalue”:88},β€œcomponent_id”:β€œmain”}

I don’t know why the device has not executed the command to set level 99%, there is no error in the driver process

I also have the Aqara little motion sensor, I’m using the Zigbee Motion Sensor Mc but on the app It doesn’t show anything but β€œwaiting Zigbee Messages”

I have created a log maybe someone can help here.
Thanks,
Gil

 9   00425c55-0932-416f-a1ba-78fae98ab614  Zigbee Motion Sensor Mc
 10  1eef4c45-5c94-4442-a771-0edfe41c8f4a  Zigbee Multi Sensor Mc
────────────────────────────────────────────────────────────────────────────────
 11  f2e891c6-00cc-446c-9192-8ebda63d9898  Zigbee Switch
 12  8bf71a5d-677b-4391-93c2-e76471f3d7eb  Zigbee Thing
 13  d692640b-402a-4d91-9151-d643ad4771f0  Zigbee Thing Mc
 14  4a07c6fd-b0fc-403c-bd07-4cd13f9bef88  Zigbee Valve
────────────────────────────────────────────────────────────────────────────────
? Select a driver. 9
connecting... connected
2023-08-04T15:59:51.821873417+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-08-04T16:00:20.998265098+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:21.012556573+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD8, rssi: -83, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x45, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0003 > > > >
2023-08-04T16:00:21.017735161+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:21.062514873+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:00:21.063862880+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:00:21.069462345+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:21.082215385+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:21.083046467+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD0, rssi: -83, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x46, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:00:21.087835194+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:21.090976430+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:00:21.102149681+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:00:21.103499355+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:21.835980413+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-08-04T16:00:27.908579864+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:27.932367085+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD0, rssi: -79, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x47, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0002 > > > >
2023-08-04T16:00:28.109275162+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:28.132152928+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:00:28.155018355+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:00:28.437196374+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:28.457072641+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:28.471474171+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD4, rssi: -79, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x48, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:00:28.513956735+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:28.527560534+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:00:28.542137485+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:00:28.543771635+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:35.162847188+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:35.163984423+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD4, rssi: -84, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x49, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0003 > > > >
2023-08-04T16:00:35.169435147+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:35.172907549+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:00:35.182112482+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:00:35.202462652+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:35.203320748+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:35.204488665+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD2, rssi: -81, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:00:35.209846009+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:35.213754295+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:00:35.222102801+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:00:35.223443137+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:42.104060062+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:42.105448756+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD6, rssi: -81, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4B, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0000 > > > >
2023-08-04T16:00:42.125817269+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:42.129657188+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:00:42.131509447+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":0}}
2023-08-04T16:00:42.162540621+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:42.163409389+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:42.164586644+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD0, rssi: -81, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4C, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:00:42.170540953+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:00:42.174246805+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:00:42.182143084+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:00:42.183498428+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:45.272487819+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:00:45.273620052+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xD4, rssi: -80, body_length: 0x001D, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0005, DataType: CharString, ModelIdentifier: "lumi.sensor_motion.aq2" > > > >
2023-08-04T16:00:45.275543346+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:00:51.822199707+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-08-04T16:01:21.822420940+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-08-04T16:01:49.189073953+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:01:49.197316287+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xCC, rssi: -82, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0003 > > > >
2023-08-04T16:01:49.222002953+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:01:49.241972620+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:01:49.243743287+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:01:49.262496620+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:01:49.263356620+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:01:49.264717620+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD2, rssi: -80, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x4F, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:01:49.290209953+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:01:49.293417287+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:01:49.302142287+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:01:49.303814953+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:01:51.831887621+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-08-04T16:01:54.669828956+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:01:54.672854289+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD6, rssi: -82, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x50, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0002 > > > >
2023-08-04T16:01:54.762519956+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:01:54.763366623+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:01:54.765048623+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:01:54.782519289+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:01:54.783376956+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:01:54.784551623+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xCE, rssi: -80, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x51, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:01:54.791144289+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:01:54.794797289+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:01:54.800851956+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:01:54.802339289+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:01:59.951247292+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:01:59.961807625+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD6, rssi: -80, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x52, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x035C > > > >
2023-08-04T16:01:59.982933625+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:01:59.983767292+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:01:59.991565625+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:01:59.998151625+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:01:59.999409292+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:02:00.003492625+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD6, rssi: -80, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x53, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:02:00.015395292+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:02:00.018920625+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:02:00.024532958+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:02:00.026022292+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:02:05.439250628+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:02:05.440907961+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IlluminanceMeasurement >, lqi: 0xD8, rssi: -80, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x54, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Uint16, MeasuredValue: 0x0024 > > > >
2023-08-04T16:02:05.457141294+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:02:05.467345294+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IlluminanceMeasurement, attribute: MeasuredValue
2023-08-04T16:02:05.468881628+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> emitting event: {"capability_id":"illuminanceMeasurement","attribute_id":"illuminance","component_id":"main","state":{"value":1}}
2023-08-04T16:02:05.483963628+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:02:05.497846294+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-08-04T16:02:05.512801628+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: d4e66a98-9eb0-43e2-92b4-1938f693ad7a [0x2F13] (Aqara Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x2F13, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OccupancySensing >, lqi: 0xD6, rssi: -80, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x55, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Bitmap8, Occupancy: Occupancy[0x01] > > > >
2023-08-04T16:02:05.514263628+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-08-04T16:02:05.515600628+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: OccupancySensing, attribute: Occupancy
2023-08-04T16:02:05.517651294+00:00 WARN Zigbee Motion Sensor Mc  Attempted to generate event for d4e66a98-9eb0-43e2-92b4-1938f693ad7a.main but it does not support capability Occupancy Sensor
2023-08-04T16:02:05.521652294+00:00 DEBUG Zigbee Motion Sensor Mc  Aqara Motion Sensor device thread event handled
2023-08-04T16:02:21.841857635+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled


since I can port only 1 image…