Fake offline indications appear every about four hours

muro · June 8, 2023, 3:40am

Often when my door sensor or motion sensor (mostly tuya) is idle, SmartThings reports it as offline.
But it becomes online as soon as the door is opened or motion is detected.
Or wait about four hours and it will come back online Usually, these fake offline indications appear every about four hours.

I wanted to solve this problem for a long time, but I couldn’t find any items like offline timeout value or health check value anywhere

Is there a way we can solve this?

Mariano_Colmenarejo · June 8, 2023, 8:17am

Hi @muro

This is because periodic status messages are not received for the time specified in the hub’s firmware.

It can be due to several reasons:

The device itself is not configured correctly and does not send periodic reports.
The reports are sent but the signal is very weak and is lost without reaching the Hub, because they are usually in far places from hub
You can put zigbee repeaters between the device and the Hub and see if that fixes it.

You can see the strength and quality of the signal received by the hub in the details view.

I have a similar one, quite far from the hub with a repeater nearby and it works fine.

If you send me a cli log of the messages received for about 10 minutes, without activity, I can check if periodic reports configured every 5 minutes are received.

If you send me cli logs of the pairing with the driver, I could see if there is a correct response from the device to the reports configuration

AurElHA · June 8, 2023, 6:54pm

It happens to me but only with Sonoff Motion and contact sensors, the closer is just like 1 meter from hub but still after around 4 hours show as offline, then go back online when report movement, happens with stock driver and Mariano Driver as well, I have other devices like Tuya motion sensor and Linkind contact sensor both using Mariano’s drivers and they are more far away than the Sonoff ones and they are all good, never reports as disconnected, also when I restart the hub all Sonoff device didn’t came back online by itself, I need to go and walk in front of the sensors or open and close contact sensors in order to make it appear as Online again, and again Tuya and Linkind devices works fine no need to force motion/open to get them re connected, they connected by itself

Mariano_Colmenarejo · June 8, 2023, 7:27pm

Hi @AurElHA

If your sonoff motion devices are model “MS01” or “ms01” and the contact ones are from the manufacturer “eWeLink” then should not be offline with my driver.

AurElHA · June 8, 2023, 7:53pm

Hola Mariano,
Motion Sensors are MS01, and Contact Sensors are also the Ewelink device that you stated, and yes I can confirm even with your driver I do have offline status about a couple of hours after they detect movement or contact actions.

Mariano_Colmenarejo · June 8, 2023, 9:29pm

Hola Jose Aureliano,

Try to see with these versions of the drivers.

I don’t know what could have changed so that what worked well doesn’t work now

There is a timer that is started for these devices when the infoChanged lifecycle is received, which is triggered every 1 hour.
I will observe to see if the lifecycle infoChanged every 1 hour is no longer triggered

───────────────────────────────────────────────────
 Name         Zigbee Motion Sensor Mc
 Version      2023-06-08T21:21:20.041007267        
───────────────────────────────────────────────────
             
───────────────────────────────────────────────────
 Name         Zigbee Contact Mc
 Version      2023-06-08T21:21:38.753445377        
───────────────────────────────────────────────────

AurElHA · June 8, 2023, 9:44pm

Gracias amigo!
I will try and let you know…

muro · June 9, 2023, 6:39am

2023-06-09T05:35:10.035707415+00:00 INFO Zigbee Motion Sensor Mc  Doing health check read for [BFB6]:0500:0002
2023-06-09T05:35:10.044120082+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: f39e5039-800a-438e-85e3-87c06c54ce10 [0xBFB6] (택배 ty)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >


2023-06-09T05:51:10.328392761+00:00 INFO Zigbee Motion Sensor Mc  Doing health check read for [5A91]:0500:0002
2023-06-09T05:51:10.415327428+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 3b01f811-39eb-47b8-a6b2-6a7a195ccc25 [0x5A91] (싱크대 모션 hej)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5A91, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-06-09T05:51:10.452484428+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-06-09T05:51:40.346115863+00:00 INFO Zigbee Motion Sensor Mc  Doing health check read for [ABA0]:0500:0002
2023-06-09T05:51:40.378070196+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: cf512f57-e04c-4a05-8214-658c942ab69f [0xABA0] (베란다 모션 Hej)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xABA0, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-06-09T05:51:40.380110196+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-06-09T05:52:02.163080873+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-06-09T05:52:02.166783206+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 24ac83aa-e006-4e0d-8130-c1fab8594ec9 [0x1439] (안방 모션 ty)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1439, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -55, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0xFF, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0000 > > > >
2023-06-09T05:52:02.184865873+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T05:52:02.188286206+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-06-09T05:52:02.195198206+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 24ac83aa-e006-4e0d-8130-c1fab8594ec9 [0x1439] (안방 모션 ty)> emitting event: {"attribute_id":"motion","capability_id":"motionSensor","component_id":"main","state":{"value":"inactive"}}
2023-06-09T05:52:02.201753206+00:00 DEBUG Zigbee Motion Sensor Mc  안방 모션 ty device thread event handled
2023-06-09T05:52:10.268310543+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled
2023-06-09T05:52:34.435642555+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-06-09T05:52:34.437722555+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: cf512f57-e04c-4a05-8214-658c942ab69f [0xABA0] (베란다 모션 Hej)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xABA0, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCC, rssi: -49, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1E >, < AttributeRecord || AttributeId: 0x0021, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
2023-06-09T05:52:34.458958888+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T05:52:34.462916222+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-06-09T05:52:34.471026222+00:00 WARN Zigbee Motion Sensor Mc  The device reported a voltage, but the driver was not configured to handle it.
2023-06-09T05:52:34.473300555+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T05:52:34.476538222+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-06-09T05:52:34.478312555+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: cf512f57-e04c-4a05-8214-658c942ab69f [0xABA0] (베란다 모션 Hej)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2023/06/09 Time: 05:52<BR><b>DNI: </b>0xABA0  <b> LQI: </b>204  <b>RSSI: </b>-49dbm</em><BR>"},"visibility":{"displayed":true}}
2023-06-09T05:52:34.581874555+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: cf512f57-e04c-4a05-8214-658c942ab69f [0xABA0] (베란다 모션 Hej)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":100}}
2023-06-09T05:52:34.632671888+00:00 DEBUG Zigbee Motion Sensor Mc  베란다 모션 Hej device thread event handled
2023-06-09T05:52:40.317604891+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled

2023-06-09T07:56:03.469907701+00:00 TRACE Zigbee Motion Sensor Mc  Received event with handler zigbee
2023-06-09T07:56:03.491878367+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 80c4f79d-db67-4d8a-8d24-3a4dfa4b29f5 [0xDC42] (거실 모션 ik)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xDC42, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC4, rssi: -49, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x70, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x20 > > > >
2023-06-09T07:56:03.727726367+00:00 TRACE Zigbee Motion Sensor Mc  Found ZigbeeMessageDispatcher handler in zigbee-motion -> battery voltage
2023-06-09T07:56:03.757372034+00:00 INFO Zigbee Motion Sensor Mc  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-06-09T07:56:03.759162034+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 80c4f79d-db67-4d8a-8d24-3a4dfa4b29f5 [0xDC42] (거실 모션 ik)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2023/06/09 Time: 07:56<BR><b>DNI: </b>0xDC42  <b> LQI: </b>196  <b>RSSI: </b>-49dbm</em><BR>"},"visibility":{"displayed":true}}
2023-06-09T07:56:03.822751368+00:00 INFO Zigbee Motion Sensor Mc  <ZigbeeDevice: 80c4f79d-db67-4d8a-8d24-3a4dfa4b29f5 [0xDC42] (거실 모션 ik)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":100}}
2023-06-09T07:56:03.895294368+00:00 DEBUG Zigbee Motion Sensor Mc  거실 모션 ik device thread event handled
2023-06-09T07:56:12.949830908+00:00 DEBUG Zigbee Motion Sensor Mc  driver device thread event handled


2023-06-09T06:08:28.983319090+00:00 TRACE Zigbee Contact Mc  Received event with handler zigbee
2023-06-09T06:08:28.984611090+00:00 INFO Zigbee Contact Mc  <ZigbeeDevice: e7241c31-22c3-4c4b-9f57-41c6beabc669 [0x9D60] (뒷베란다문 ty)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9D60, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCE, rssi: -67, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x67, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1C >, < AttributeRecord || AttributeId: 0x0021, DataType: Uint8, BatteryPercentageRemaining: 0xA2 > > > >
2023-06-09T06:08:29.004770423+00:00 TRACE Zigbee Contact Mc  Found ZigbeeMessageDispatcher handler in zigbee_contact
2023-06-09T06:08:29.005636423+00:00 INFO Zigbee Contact Mc  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-06-09T06:08:29.007552757+00:00 WARN Zigbee Contact Mc  The device reported a voltage, but the driver was not configured to handle it.
2023-06-09T06:08:29.013343423+00:00 TRACE Zigbee Contact Mc  Found ZigbeeMessageDispatcher handler in zigbee_contact
2023-06-09T06:08:29.017355757+00:00 INFO Zigbee Contact Mc  Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-06-09T06:08:29.022885090+00:00 INFO Zigbee Contact Mc  <ZigbeeDevice: e7241c31-22c3-4c4b-9f57-41c6beabc669 [0x9D60] (뒷베란다문 ty)> emitting event: {"attribute_id":"signalMetrics","capability_id":"legendabsolute60149.signalMetrics","component_id":"main","state":{"value":"<em table style='font-size:70%';'font-weight: bold'</em><b>GMT: </b>2023/06/09 Time: 06:08<BR><b>DNI: </b>0x9D60  <b> LQI: </b>206  <b>RSSI: </b>-67dbm</em><BR>"},"visibility":{"displayed":true}}
2023-06-09T06:08:29.042081423+00:00 PRINT Zigbee Contact Mc  raw_value >>>>     162
2023-06-09T06:08:29.045544423+00:00 INFO Zigbee Contact Mc  <ZigbeeDevice: e7241c31-22c3-4c4b-9f57-41c6beabc669 [0x9D60] (뒷베란다문 ty)> emitting event: {"attribute_id":"battery","capability_id":"battery","component_id":"main","state":{"value":81}}
2023-06-09T06:08:29.062164090+00:00 DEBUG Zigbee Contact Mc  뒷베란다문 ty device thread event handled

Thanks for the answer
But I have a bunch of repeaters and the distance between the hub and the devices is not far, maybe 5 meters at most.

I spent about an hour tracing the CLI logs for the 4 motion & 1 contact sensor causing the problem, but only got a very small portion of it

TUYATEC-smmlguju/RH3040
<ZigbeeDevice: 3b01f811-39eb-47b8-a6b2-6a7a195ccc25 [0x5A91] (싱크대 모션 hej)>
<ZigbeeDevice: cf512f57-e04c-4a05-8214-658c942ab69f [0xABA0] (베란다 모션 Hej)>

IKEA TRADFRI on/off switch
<ZigbeeDevice: 80c4f79d-db67-4d8a-8d24-3a4dfa4b29f5 [0xDC42] (거실 모션 ik)>

TUYATEC-zn9wyqtr / RH3040
<ZigbeeDevice: f39e5039-800a-438e-85e3-87c06c54ce10 [0xBFB6] (택배 ty)>.

TUYATEC-rkqiqvcs / RH3001
<ZigbeeDevice: e7241c31-22c3-4c4b-9f57-41c6beabc669 [0x9D60] (뒷베란다문 ty)>

These sensors do not appear to be responding to HealthCheck
However, they do send Zigbee messages(lines above the WARN message) every few hours.

Mariano_Colmenarejo · June 9, 2023, 9:32am

This confirms that devices are not sending periodic reports every 5 minutes.
To confirm if it is because the driver has not sent the configuration or the device has not accepted it, the following would be necessary:

Open the CLI window to see the driver logs
Uninstall one of the conflicting sensors with the App
Re-add the sensor with the app, search nearby option
When paired, the logs will appear in the CLI window.
Capture at least 2 minutes since the fingerprints of the added device appear in the log.
Copy and paste, but please, don’t put the format developer </>, I prefer to see them as they are seen in the CLI and not have to move the line cursor left and right constantly to see the full messages.

They are sending the battery reports. The Warn is due to these devices send the voltage value and the battery percentage in the same message and only the percentage value is used to emit the battery value. This is not a problem.

I suppose that when these messages are received, the device will be online again, right?

muro · June 9, 2023, 11:19am

Your comment about this case is correct
I haven’t looked at the logs for 4 hours so I can’t be sure, but the device appeared to be coming online at the time of receiving this message.
Let’s work on getting the pairing logs.
Thanks as always for your support

muro · June 9, 2023, 12:32pm

Please understand that there are many unnecessary logs due to unrelated devices.
log of pairing of these four devices

IKEA TRADFRI on/off switch
ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)

TUYATEC-zn9wyqtr / RH3040
ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)

TUYATEC-smmlguju/RH3040
ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)

TUYATEC-rkqiqvcs / RH3001
ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)

Are there any hints in the logs?

Manufacturer: IKEA of Sweden Model: TRADFRI motion sensor
[1]: Basic, PowerConfiguration, Identify, Alarms, PollControl, TouchlinkCommissioning, 0xFC7C
2023-06-09T11:35:28.349811548+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received lifecycle event: added
2023-06-09T11:35:28.441300548+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
2023-06-09T11:35:28.452785882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received lifecycle event: doConfigure
2023-06-09T11:35:28.472835215+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion → ikea motion sensor
2023-06-09T11:35:28.473678215+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
2023-06-09T11:35:28.512078882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“inactive”}}
2023-06-09T11:35:28.528191548+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:28.589699882+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2023-06-09T11:35:28.807168215+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2023-06-09T11:35:28.859045549+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:28.861955549+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion → ikea motion sensor
2023-06-09T11:35:28.863261882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEB7FFE0, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:35:28.877514882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:35:29.032837882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0033 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < MgmtBindRequest || start_index: 0x00 > > >
2023-06-09T11:35:29.072488549+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEB7FFE0, src_endpoint: 0x01, cluster: OnOff, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:35:29.132204882+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, 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 > > > >
2023-06-09T11:35:29.133700882+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:29.178774549+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:29.179652549+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:30.658111216+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:30.693403883+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xD0, rssi: -52, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x10, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0x64 > > > >
2023-06-09T11:35:30.699524883+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:30.712421216+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCE, rssi: -51, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x71 >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:35:30.752089883+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T11:35:30.782606883+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-06-09T11:35:30.787214883+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 11:35
DNI: 0x1E5D LQI: 208 RSSI: -52dbm
”},“visibility”:{“displayed”:false}}
2023-06-09T11:35:30.838935549+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:50}}
2023-06-09T11:35:30.854353550+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:30.858266883+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:30.863029216+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC6, rssi: -52, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x11, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2023-06-09T11:35:30.905288883+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:30.907777883+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:30.909053216+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8033 >, lqi: 0xC4, rssi: -51, body_length: 0x001A, < ZDOMessageBody || < ZDOHeader || seqno: 0x72 >, < MgmtBindResponse || Status: 0x00, TotalBindingTableEntryCount: 0x01, StartIndex: 0x00, BindingTableListCount: 0x01, < BindingTableListRecord || src_addr: EC1BBDFFFEB7FFE0, src_endpoint: 0x01, cluster_id: PowerConfiguration, dest_addr_mode: 0x03, dest_addr: 286D97000204AA7D, dest_endpoint: 0x01 > > > >
2023-06-09T11:35:30.983192216+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:30.984054883+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:30.985261883+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xC8, rssi: -52, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x73 >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:35:31.323454550+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion → ikea motion sensor
2023-06-09T11:35:31.361838550+00:00 INFO Zigbee Motion Sensor Mc Executing ZdoHandler
2023-06-09T11:35:31.363547216+00:00 PRINT Zigbee Motion Sensor Mc <<<<zdo_binding_table_handler >>>>>
2023-06-09T11:35:31.778476883+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < AddGroup || group_id: 0x0000, group_name: “Group-0” > > >
2023-06-09T11:35:32.013182883+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:32.014481550+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:32.015934217+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: OnOff >, lqi: 0xCE, rssi: -52, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x12, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: UNSUPPORTED_ATTRIBUTE, direction: 0x00, attr_id: 0x0000 > > > >
2023-06-09T11:35:32.222772883+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:32.232097883+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:32.233727217+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 24ac83aa-e006-4e0d-8130-c1fab8594ec9 [0x1439] (안방 모션 ty)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1439, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -55, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x5A, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0002, DataType: Bitmap16, ZoneStatus: 0x0000 > > > >
2023-06-09T11:35:32.478020217+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:32.495899217+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
2023-06-09T11:35:32.513454884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received lifecycle event: infoChanged
2023-06-09T11:35:32.514812884+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T11:35:32.516022550+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
2023-06-09T11:35:32.517709550+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 24ac83aa-e006-4e0d-8130-c1fab8594ec9 [0x1439] (안방 모션 ty)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“inactive”}}
2023-06-09T11:35:32.773105550+00:00 DEBUG Zigbee Motion Sensor Mc 안방 모션 ty device thread event handled
2023-06-09T11:35:32.795081884+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2023-06-09T11:35:32.796373884+00:00 PRINT Zigbee Motion Sensor Mc ***** infoChanged *********
2023-06-09T11:35:32.807837217+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2023-06-09T11:35:32.808676550+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
2023-06-09T11:35:32.823551884+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= preferences: version
2023-06-09T11:35:32.824399884+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> version nil
2023-06-09T11:35:32.826058884+00:00 PRINT Zigbee Motion Sensor Mc Device ID >>> <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)>
2023-06-09T11:35:32.827338550+00:00 PRINT Zigbee Motion Sensor Mc Manufacturer >>> IKEA of Sweden Manufacturer_Len >>> 14
2023-06-09T11:35:32.841508217+00:00 PRINT Zigbee Motion Sensor Mc Model >>> TRADFRI motion sensor Model_len >>> 21
2023-06-09T11:35:32.842375550+00:00 PRINT Zigbee Motion Sensor Mc Memory >>>>>>> 1552.1982421875 Kbytes
2023-06-09T11:35:32.843602217+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:32.844794217+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:32.845975884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Groups >, lqi: 0xCE, rssi: -52, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x13, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: UNSUPPORTED_CLUSTER > > >
2023-06-09T11:35:32.868596884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEB7FFE0, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:35:32.936381550+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:35:32.959239217+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: EC1BBDFFFEB7FFE0, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:35:33.068109884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x1E5D, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0020, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:35:33.103798884+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.159611884+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.206194884+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.752915551+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:33.754180884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xC4, rssi: -52, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x75 >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:35:33.806553884+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:33.807813884+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCE, rssi: -52, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x76 >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:35:33.873529551+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.874399551+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:33.875599218+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC2, rssi: -52, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x15, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2023-06-09T11:35:33.952569884+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.954081551+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:35:33.955540218+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: b3c41918-8e50-45fd-81f8-8d86800e1f3d [0x1E5D] (IKEA motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x1E5D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xB8, rssi: -52, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x14, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || ZclStatus: SUCCESS > > >
2023-06-09T11:35:33.964168884+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:33.969990218+00:00 DEBUG Zigbee Motion Sensor Mc IKEA motion Sensor device thread event handled
2023-06-09T11:35:35.860262885+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee

muro · June 9, 2023, 12:38pm

Manufacturer: TUYATEC-zn9wyqtr Model: RH3040
[1]: Basic, PowerConfiguration, IASZone

11:50:16.484153376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received lifecycle event: added
11:50:16.560480709+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
11:50:16.561638042+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received lifecycle event: doConfigure
11:50:16.572881376+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:16.574103376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCC, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x03, ZCLCommandId: 0x01 >, < ZoneEnrollRequest || IasZoneType: MOTION_SENSOR, manufacturer_code: 0x1002 > > >
11:50:16.643486376+00:00 TRACE Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received unhandled lifecycle event: added
11:50:16.652742376+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:16.654037709+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:16.655230376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -66, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x04, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0000, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
11:50:16.691671042+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
11:50:16.695681376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
11:50:16.784220709+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:16.785105042+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
11:50:16.786417042+00:00 TRACE Zigbee Motion Sensor Mc Found CapabilityCommandDispatcher handler in zigbee-motion
11:50:16.787636042+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
11:50:16.803046376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
11:50:16.815783042+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 847127FFFE29B610, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
11:50:16.848750043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
11:50:16.851176709+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 847127FFFE29B610, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
11:50:16.942551043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
11:50:16.989459376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
11:50:17.052505043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
11:50:17.102216709+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.103088709+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler capability
11:50:17.211672043+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.223796709+00:00 DEBUG Zigbee Motion Sensor Mc driver device thread event handled
11:50:17.250570376+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.313405043+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
11:50:17.338834376+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
11:50:17.355842043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“inactive”}}
11:50:17.436133709+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.471196043+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:17.472792376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCE, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3B, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
11:50:17.479598709+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.480891376+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:17.492779043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCA, rssi: -66, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x05, ZCLCommandId: 0x01 >, < ZoneEnrollRequest || IasZoneType: MOTION_SENSOR, manufacturer_code: 0x1002 > > >
11:50:17.522187709+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
11:50:17.557008043+00:00 TRACE Zigbee Motion Sensor Mc Found CapabilityCommandDispatcher handler in zigbee-motion
11:50:17.566020043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
11:50:17.577292376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
11:50:17.670429710+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:17.678662376+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:17.745335376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -66, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0002, ZclStatus: SUCCESS, DataType: Bitmap16, ZoneStatus: 0x0001 > > > >
11:50:17.752387376+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
11:50:17.759797710+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
11:50:17.763825710+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 11:50
DNI: 0xBFB6 LQI: 206 RSSI: -66dbm
”},“visibility”:{“displayed”:false}}
11:50:17.853135043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
11:50:18.046232043+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:18.052835376+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:18.058924376+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCC, rssi: -66, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x63 >, < BindRequestResponse || status: 0x00 > > >
11:50:18.142855710+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:18.152395710+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:18.246835043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xD0, rssi: -66, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3D, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
11:50:18.266514377+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
11:50:18.314671710+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: ZoneStatus
11:50:18.316471710+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“active”}}
11:50:18.433358043+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:18.442875377+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:18.444353377+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCC, rssi: -66, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x06, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0x01, delay: 0x0000 > > >
11:50:18.553834043+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:18.591920710+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:18.593400377+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0x82, rssi: -65, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x64 >, < BindRequestResponse || status: 0x00 > > >
11:50:18.832322710+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:18.862054043+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:18.863427043+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -66, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x3F, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
11:50:18.930025377+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
11:50:18.931309377+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
11:50:18.957776044+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“active”}}
11:50:19.557614044+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:19.575136710+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:19.591893377+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -66, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x40, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
11:50:19.767741711+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:19.783074711+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:19.783955377+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -66, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x41, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
11:50:19.877711711+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:19.880877377+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
11:50:19.882265044+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xBFB6, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCE, rssi: -66, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x42, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
11:50:20.043909377+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:20.047597044+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
11:50:20.053492711+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> received lifecycle event: infoChanged
11:50:20.058724711+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:20.059983044+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
11:50:20.061184711+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
11:50:20.075184044+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 11:50
DNI: 0xBFB6 LQI: 206 RSSI: -66dbm
”},“visibility”:{“displayed”:false}}
11:50:20.082240377+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
11:50:20.342151711+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:20.347152378+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
11:50:20.353475711+00:00 PRINT Zigbee Motion Sensor Mc ***** infoChanged *********
11:50:20.354309378+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
11:50:20.355541711+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
11:50:20.356727044+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= preferences: version
11:50:20.372908044+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> version nil
11:50:20.377521378+00:00 PRINT Zigbee Motion Sensor Mc Device ID >>> <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)>
11:50:20.381653711+00:00 PRINT Zigbee Motion Sensor Mc Manufacturer >>> TUYATEC-zn9wyqtr Manufacturer_Len >>> 16
11:50:20.400052711+00:00 PRINT Zigbee Motion Sensor Mc Model >>> RH3040 Model_len >>> 6
11:50:20.403751378+00:00 PRINT Zigbee Motion Sensor Mc Memory >>>>>>> 1790.9267578125 Kbytes
11:50:20.411727711+00:00 DEBUG Zigbee Motion Sensor Mc Samotech Motion Sensor device thread event handled
11:50:20.454956711+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 861f0526-17e3-4dff-9786-94d8e86e2933 [0xBFB6] (Samotech Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xBFB6, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 847127FFFE29B610, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >

muro · June 9, 2023, 12:39pm

Manufacturer: TUYATEC-smmlguju Model: RH3040
[1]: Basic, PowerConfiguration, Identify, IASZone
2023-06-09T11:56:01.978435299+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received lifecycle event: added
2023-06-09T11:56:02.042442965+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
2023-06-09T11:56:02.065017965+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received lifecycle event: doConfigure
2023-06-09T11:56:02.066348965+00:00 TRACE Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received unhandled lifecycle event: added
2023-06-09T11:56:02.067601299+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:02.206017299+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2023-06-09T11:56:02.217586965+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2023-06-09T11:56:02.265476965+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:02.367436632+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2023-06-09T11:56:02.385427299+00:00 TRACE Zigbee Motion Sensor Mc Found CapabilityCommandDispatcher handler in zigbee-motion
2023-06-09T11:56:02.401920965+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
2023-06-09T11:56:02.422116632+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
2023-06-09T11:56:02.456262632+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 14B457FFFE2DDB29, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:56:02.604429299+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:56:02.682487966+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 14B457FFFE2DDB29, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:56:02.761778299+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
2023-06-09T11:56:02.799928299+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
2023-06-09T11:56:02.829528632+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
2023-06-09T11:56:02.885333299+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:02.917748966+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:02.943706966+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:03.545091966+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:03.548676633+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCC, rssi: -71, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x66, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
2023-06-09T11:56:03.760202966+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
2023-06-09T11:56:03.769953966+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-06-09T11:56:03.772967966+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 11:56
DNI: 0x4881 LQI: 204 RSSI: -71dbm
”},“visibility”:{“displayed”:false}}
2023-06-09T11:56:03.881883300+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
2023-06-09T11:56:04.240432633+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:04.243831966+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:04.245130966+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD2, rssi: -71, body_length: 0x0003, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x67, ZCLCommandId: 0x01 >, < ReadAttributeResponse || > > >
2023-06-09T11:56:04.376105300+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:04.392339966+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:04.393610300+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCA, rssi: -71, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x1C >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:56:04.477380633+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:04.478671300+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xD0, rssi: -75, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x68, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2023-06-09T11:56:04.565257633+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:04.568410633+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:04.569682966+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xD0, rssi: -71, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x1D >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:56:04.722478300+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:04.825779633+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:04.842101633+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCC, rssi: -71, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6A, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2023-06-09T11:56:05.637425967+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:05.641104967+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:05.663530967+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
2023-06-09T11:56:05.668461967+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received lifecycle event: infoChanged
2023-06-09T11:56:05.672475634+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 14B457FFFE2DDB29, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:56:05.817505300+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:56:05.852315300+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 14B457FFFE2DDB29, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:56:06.022518967+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
2023-06-09T11:56:06.032225967+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
2023-06-09T11:56:06.591389301+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x4881, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
2023-06-09T11:56:06.796680968+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:06.815146634+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:06.823647634+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCE, rssi: -74, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x69, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2023-06-09T11:56:06.952818968+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
2023-06-09T11:56:06.956931301+00:00 PRINT Zigbee Motion Sensor Mc ***** infoChanged *********
2023-06-09T11:56:06.977958968+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2023-06-09T11:56:06.978846968+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
2023-06-09T11:56:06.982653301+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= preferences: version
2023-06-09T11:56:06.983881634+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> version nil
2023-06-09T11:56:06.985065301+00:00 PRINT Zigbee Motion Sensor Mc Device ID >>> <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)>
2023-06-09T11:56:07.018960301+00:00 PRINT Zigbee Motion Sensor Mc Manufacturer >>> TUYATEC-smmlguju Manufacturer_Len >>> 16
2023-06-09T11:56:07.020835634+00:00 PRINT Zigbee Motion Sensor Mc Model >>> RH3040 Model_len >>> 6
2023-06-09T11:56:07.022182968+00:00 PRINT Zigbee Motion Sensor Mc Memory >>>>>>> 1408.921875 Kbytes
2023-06-09T11:56:07.023392301+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:07.024569968+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
2023-06-09T11:56:07.025755968+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x02, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: Basic >, lqi: 0xD8, rssi: -52, body_length: 0x000B, < ZDOMessageBody || < ZDOHeader || seqno: 0x88 >, GenericBody: 7D AA 04 02 00 97 6D 28 00 00 > >
2023-06-09T11:56:07.082815301+00:00 DEBUG Zigbee Motion Sensor Mc RH3040 Motion Sensor device thread event handled
2023-06-09T11:56:07.085542301+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee

muro · June 9, 2023, 12:40pm

Manufacturer: TUYATEC-rkqiqvcs Model: RH3001
[1]: Basic, PowerConfiguration, Identify, IASZone
2023-06-09T11:59:54.164398036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received lifecycle event: added
2023-06-09T11:59:54.166184369+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-06-09T11:59:54.167448036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received lifecycle event: doConfigure
2023-06-09T11:59:54.175715036+00:00 TRACE Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received unhandled lifecycle event: added
2023-06-09T11:59:54.178936036+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:54.196961036+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact
2023-06-09T11:59:54.200693036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2023-06-09T11:59:54.213183369+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:54.253564036+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact
2023-06-09T11:59:54.264592036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: CCCCCCFFFED83883, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:59:54.355832369+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-06-09T11:59:54.582538703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: CCCCCCFFFED83883, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
2023-06-09T11:59:54.645844703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
2023-06-09T11:59:54.712877036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
2023-06-09T11:59:54.763053369+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x9424, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
2023-06-09T11:59:54.832524703+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:54.860560703+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:54.861657369+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:54.863249703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: Basic >, lqi: 0xCA, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7D, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0001, DataType: Uint8, ApplicationVersion: 0x4D > > > >
2023-06-09T11:59:54.883912036+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:54.884842369+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:54.886125703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0xFF, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCC, rssi: -61, body_length: 0x000B, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x7E, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0020, DataType: Uint8, BatteryVoltage: 0x1C >, < AttributeRecord || AttributeId: 0x0021, DataType: Uint8, BatteryPercentageRemaining: 0xA2 > > > >
2023-06-09T11:59:54.917193036+00:00 TRACE Zigbee Contact Mc Found ZigbeeMessageDispatcher handler in zigbee_contact
2023-06-09T11:59:54.929952703+00:00 INFO Zigbee Contact Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryVoltage
2023-06-09T11:59:54.942666369+00:00 WARN Zigbee Contact Mc The device reported a voltage, but the driver was not configured to handle it.
2023-06-09T11:59:54.944453369+00:00 TRACE Zigbee Contact Mc Found ZigbeeMessageDispatcher handler in zigbee_contact
2023-06-09T11:59:54.945714036+00:00 INFO Zigbee Contact Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2023-06-09T11:59:54.947478703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 11:59
DNI: 0x9424 LQI: 204 RSSI: -61dbm
”},“visibility”:{“displayed”:false}}
2023-06-09T11:59:54.966273369+00:00 PRINT Zigbee Contact Mc raw_value >>>> 162
2023-06-09T11:59:54.973835036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:81}}
2023-06-09T11:59:54.987696036+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:55.117525703+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:55.183575370+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCC, rssi: -62, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0C, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2023-06-09T11:59:55.339450703+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:55.352881703+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:55.354420703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCC, rssi: -61, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x51 >, < BindRequestResponse || status: 0x00 > > >
2023-06-09T11:59:55.546961036+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:55.550209036+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:55.551649036+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC8, rssi: -61, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x0D, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2023-06-09T11:59:55.754726703+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:56.310431037+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:56.501023703+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCE, rssi: -61, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x0E, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2023-06-09T11:59:56.654314704+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:56.978753704+00:00 TRACE Zigbee Contact Mc Received event with handler device_lifecycle
2023-06-09T11:59:57.081067370+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received lifecycle event: infoChanged
2023-06-09T11:59:57.192505037+00:00 TRACE Zigbee Contact Mc Found DeviceLifecycleDispatcher handler in zigbee_contact
2023-06-09T11:59:57.197423370+00:00 PRINT Zigbee Contact Mc ***** infoChanged *********
2023-06-09T11:59:57.198326037+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2023-06-09T11:59:57.244782371+00:00 PRINT Zigbee Contact Mc << Preference changed name: signalMetricsVisibles old value: nil new value: No
2023-06-09T11:59:57.245692371+00:00 PRINT Zigbee Contact Mc device.preferences[infoChanged]= preferences: version
2023-06-09T11:59:57.247056371+00:00 PRINT Zigbee Contact Mc << Preference changed name: version old value: nil new value:
2023-06-09T11:59:57.250861037+00:00 PRINT Zigbee Contact Mc Device ID <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)>
2023-06-09T11:59:57.252522371+00:00 PRINT Zigbee Contact Mc Manufacturer >>> TUYATEC-rkqiqvcs Manufacturer_Len >>> 16
2023-06-09T11:59:57.253800704+00:00 PRINT Zigbee Contact Mc Model >>> RH3001 Model_len >>> 6
2023-06-09T11:59:57.370973037+00:00 PRINT Zigbee Contact Mc Memory >>>>>>> 1125.9248046875 Kbytes
2023-06-09T11:59:57.377879704+00:00 PRINT Zigbee Contact Mc <<<<< Firmware Version >>>>> Unknown
2023-06-09T11:59:57.383491371+00:00 DEBUG Zigbee Contact Mc RH3001 Open/Close Sensor device thread event handled
2023-06-09T11:59:57.398972704+00:00 TRACE Zigbee Contact Mc Received event with handler zigbee
2023-06-09T11:59:57.399878037+00:00 INFO Zigbee Contact Mc <ZigbeeDevice: 2455e0bb-4677-494b-9be2-0a33f2279397 [0x9424] (RH3001 Open/Close Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x9424, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC4, rssi: -61, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0x7F, ZCLCommandId: 0x01 >, < ZoneEnrollRequest || IasZoneType: CONTACT_SWITCH, manufacturer_code: 0x0000 > > >

Mariano_Colmenarejo · June 9, 2023, 2:25pm

Does the Ikea sensor also stay offline?

The others I see an error similar to the one that occurs with the sonoff sensors, the binding and enrolling are carried out but the reporting intervals are not configured correctly.

2023-06-09T11:56:06.823647634+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: 8af7c4db-4de1-4c60-bcd8-fe3299b46722 [0x4881] (RH3040 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4881, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCE, rssi: -74, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x08, seqno: 0x69, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >

It would be necessary to apply the same solution as to the sonoff.

I have to modify the drivers for both these and sonoff as the infoChanged lifecycle no longer runs every hour.

I will notify you when they are modified.

Could you send a log of the pairing of a sensor that works well for you, to compare it with these?

muro · June 9, 2023, 3:54pm

IKEA sensor went offline 4 hours after pairing
TUYATEC-zn9wyqtr / RH3040 (Samotech Motion Sensor) went offline 2 hours and 30 minutes after last sensing
Since there is no normal RH3040, we attach the pairing log of TS2020 motion sensor
I don’t know if this will help

Manufacturer: _TZ3040_bb6xaihh Model: TS0202
[1]: PowerConfiguration, Identify, Groups, IASZone, Basic

15:34:28.881906867+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received lifecycle event: added
15:34:28.897283200+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
15:34:28.906705200+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received lifecycle event: doConfigure
15:34:28.949137200+00:00 TRACE Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received unhandled lifecycle event: added
15:34:28.952300534+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:28.992545867+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
15:34:28.993842534+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
15:34:29.005442200+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:29.053656534+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
15:34:29.054531534+00:00 TRACE Zigbee Motion Sensor Mc Found CapabilityCommandDispatcher handler in zigbee-motion
15:34:29.055753867+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
15:34:29.076028867+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
15:34:29.084805200+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138CDF9F5E18C, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
15:34:29.148092534+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
15:34:29.173793200+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138CDF9F5E18C, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
15:34:29.198956534+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
15:34:29.277221867+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
15:34:29.372875867+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
15:34:29.408841534+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:29.500200867+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:29.506496867+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:30.501786201+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler device_lifecycle
15:34:30.504705201+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received lifecycle event: infoChanged
15:34:30.576409868+00:00 TRACE Zigbee Motion Sensor Mc Found DeviceLifecycleDispatcher handler in zigbee-motion
15:34:30.579473868+00:00 PRINT Zigbee Motion Sensor Mc ***** infoChanged *********
15:34:30.590376868+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= preferences: version
15:34:30.592018868+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> version nil
15:34:30.593257868+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= 2 preferences: motionSensitivity
15:34:30.594448868+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> motionSensitivity nil 2
15:34:30.602791534+00:00 PRINT Zigbee Motion Sensor Mc <<< Write Sensitivity Level >>>
15:34:30.604004534+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0013, DataType: Uint8, data: 0x02 > > > >
15:34:30.638433534+00:00 PRINT Zigbee Motion Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
15:34:30.644084201+00:00 PRINT Zigbee Motion Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
15:34:30.645398534+00:00 PRINT Zigbee Motion Sensor Mc Device ID >>> <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)>
15:34:30.646686868+00:00 PRINT Zigbee Motion Sensor Mc Manufacturer >>> _TZ3040_bb6xaihh Manufacturer_Len >>> 16
15:34:30.647888534+00:00 PRINT Zigbee Motion Sensor Mc Model >>> TS0202 Model_len >>> 6
15:34:30.649090868+00:00 PRINT Zigbee Motion Sensor Mc Memory >>>>>>> 1213.529296875 Kbytes
15:34:30.650291201+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:30.684602201+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:31.032494201+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138CDF9F5E18C, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
15:34:31.155666535+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
15:34:31.281446201+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C138CDF9F5E18C, src_endpoint: 0x01, cluster: IASZone, dest_addr_mode: 0x03, dest_address: 286D97000204AA7D, dest_endpoint: 0x01 > > >
15:34:31.430722868+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0002, DataType: Bitmap16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C > > > >
15:34:31.557283868+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0010, DataType: IEEEAddress, data: 286D97000204AA7D > > > >
15:34:31.838605868+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x01, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneEnrollResponse || EnrollResponseCode: SUCCESS, zone_id: 0x00 > > >
15:34:31.933883868+00:00 PRINT Zigbee Motion Sensor Mc <<< Write Sensitivity Level >>>
15:34:31.979433202+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0013, DataType: Uint8, data: 0x02 > > > >
15:34:33.513729869+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:33.518596869+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:33.519901203+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCE, rssi: -63, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x69, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
15:34:34.025681203+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:34.034922869+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:34.048878869+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCE, rssi: -56, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x6B, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0021 > > > >
15:34:34.443990536+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:34.452197870+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
15:34:34.460377870+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 15:34
DNI: 0x6A6E LQI: 206 RSSI: -63dbm
”},“visibility”:{“displayed”:false}}
15:34:34.633169536+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
15:34:34.747884536+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:34.751841536+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:34.769733203+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xCA, rssi: -56, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x09 >, < BindRequestResponse || status: 0x00 > > >
15:34:34.886219870+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:34.887514870+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:34.892286537+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0x72, rssi: -55, body_length: 0x0007, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x71, ZCLCommandId: 0x07 >, < ConfigureReportingResponse || < ConfigureReportingResponseRecord || ZclStatus: SUCCESS, direction: 0x00, attr_id: 0x0002 > > > >
15:34:34.972869870+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:34.973731203+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:34.982566203+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC6, rssi: -56, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0xB2, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0x10, delay: 0x0000 > > >
15:34:35.043164203+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.044040870+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:35.045274870+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCC, rssi: -56, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x72, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
15:34:35.115093203+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:35.138231870+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
15:34:35.169198870+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“active”}}
15:34:35.272495870+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.284260537+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:35.285120870+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCA, rssi: -56, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x73, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x00, ZclStatus: SUCCESS > > >
15:34:35.415553537+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.420484870+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:35.421876203+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC4, rssi: -57, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x74, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
15:34:35.684675537+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.702449537+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.709701204+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:35.710533870+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xCA, rssi: -56, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x69, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
15:34:35.983280537+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:35.984581870+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:35.985845204+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xCC, rssi: -56, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x09, seqno: 0xB5, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0x00, delay: 0x0000 > > >
15:34:36.437281537+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:36.442137537+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
15:34:36.453231204+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 15:34
DNI: 0x6A6E LQI: 202 RSSI: -56dbm
”},“visibility”:{“displayed”:false}}
15:34:36.726366871+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
15:34:36.838846537+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:36.843513204+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:36.851754871+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
15:34:36.853473871+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“motion”,“capability_id”:“motionSensor”,“component_id”:“main”,“state”:{“value”:“active”}}
15:34:36.973000538+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:36.981921538+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:36.985013204+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xC6, rssi: -56, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x78, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0013, ZclStatus: SUCCESS, DataType: Uint8, CurrentZoneSensitivityLevel: 0x02 > > > >
15:34:37.241579538+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
15:34:37.415914204+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x6A6E, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0002 > > >
15:34:38.306427871+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:38.320328205+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:38.358581871+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0x9E, rssi: -56, body_length: 0x0006, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x79, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0012, ZclStatus: UNSUPPORTED_ATTRIBUTE > > > >
15:34:38.690364872+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:38.726206538+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: CurrentZoneSensitivityLevel
15:34:38.735076205+00:00 PRINT Zigbee Motion Sensor Mc currentZoneSensitivityLevel >>>>>>>>> 2
15:34:38.742794205+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“sensorSensitivity”,“capability_id”:“legendabsolute60149.sensorSensitivity”,“component_id”:“main”,“state”:{“value”:“2”}}
15:34:38.815653872+00:00 PRINT Zigbee Motion Sensor Mc <<<<<< currentZoneSensitivityLevel Status >>>>>>> 0
15:34:38.816524205+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 15:34
DNI: 0x6A6E LQI: 198 RSSI: -56dbm
”},“visibility”:{“displayed”:false}}
15:34:38.963693872+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:38.967605872+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:38.982029872+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xD0, rssi: -56, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7B, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0013, ZclStatus: SUCCESS, DataType: Uint8, CurrentZoneSensitivityLevel: 0x02 > > > >
15:34:39.183189205+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled
15:34:39.184486872+00:00 TRACE Zigbee Motion Sensor Mc Received event with handler zigbee
15:34:39.185953872+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x6A6E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xC6, rssi: -56, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x7C, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0xC8 > > > >
15:34:39.244014205+00:00 TRACE Zigbee Motion Sensor Mc Found ZigbeeMessageDispatcher handler in zigbee-motion
15:34:39.252412205+00:00 INFO Zigbee Motion Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: IASZone, attribute: CurrentZoneSensitivityLevel
15:34:39.254355205+00:00 PRINT Zigbee Motion Sensor Mc currentZoneSensitivityLevel >>>>>>>>> 2
15:34:39.255558872+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“sensorSensitivity”,“capability_id”:“legendabsolute60149.sensorSensitivity”,“component_id”:“main”,“state”:{“value”:“2”}}
15:34:39.286695539+00:00 PRINT Zigbee Motion Sensor Mc <<<<<< currentZoneSensitivityLevel Status >>>>>>> 0
15:34:39.294616872+00:00 INFO Zigbee Motion Sensor Mc <ZigbeeDevice: f4968e41-9536-4c8c-9efc-8c02dd275fc1 [0x6A6E] (TS0202 Motion Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“<em table style=‘font-size:70%’;‘font-weight: bold’GMT: 2023/06/09 Time: 15:34
DNI: 0x6A6E LQI: 208 RSSI: -56dbm
”},“visibility”:{“displayed”:false}}
15:34:39.361124539+00:00 DEBUG Zigbee Motion Sensor Mc TS0202 Motion Sensor device thread event handled

Mariano_Colmenarejo · June 9, 2023, 4:05pm

In this device it can be seen that it responds as success in the response to the IASZone configuration

I have not modified anything from the Ikea device with respect to the stock driver.
You can try to see if the stock driver works well.

Now in a while I’ll give you the modified versions

Mariano_Colmenarejo · June 9, 2023, 4:55pm

Hi @muro, @AurElHA

These modified versions should solve the offline problem of sonoff contact and motion and TUYA motion sensors: “TUYATEC-smmlguju” , “TUYATEC-zn9wyqtr” and contact: “TUYATEC-rkqiqvcs”

They can be installed manually with the CLI or let them update automatically.

───────────────────────────────────────────────────
 Name         Zigbee Motion Sensor Mc
 Version      2023-06-09T16:35:39.627056075        
───────────────────────────────────────────────────

───────────────────────────────────────────────────
 Name         Zigbee Contact Mc
 Version      2023-06-09T16:26:28.433962407        
───────────────────────────────────────────────────

AurElHA · June 9, 2023, 7:30pm

Thank you Sir, let me try and I will give you my feedback

muro · June 10, 2023, 2:26am

The driver was updated two hours ago and we’re keeping an eye on it.
Unfortunately, I won’t be able to use my PC for a while, so I can check the logs after 4 days.
But everything is fine on the ST app
Thanks as always for your support mariano
I learned a lot this time

Fake offline indications appear every about four hours

Customers

Developers

Download the SmartThings App