Tuya Water Sensor Not Behaving Properly (keeps going offline)

[briankitt]

I have a number of these water sensors:
https://www.amazon.com/dp/B0CLJ951YS

They work perfectly, however, they do not appear to ‘report status’ often enough, and SmartThings thinks they go offline. When they do report status, then SmartThings says they are back online.
So all day long, they go offline, then online, then offline, then online, then offline, then online.
When they are reported as ‘offline’, I have dropped them in water as a test, and the second they get wet, they imediately report ‘online’, then ‘wet’. So the devices work perfectly, they just don’t report often enough for the driver to think they are working.

I’ve tried the default ‘Zigbee Thing’ driver
I’ve tried the ‘Zigbee Moisture Sensor MC’ by Mariano
Both behave identically, the only difference is the icon that shows.

I want to re-iterate, this is NOT a connectivity issue. I’m positive of that. By watching event history, I can see every single device cycle offline/online in regular intervals. I’d bet my paycheck this is simply a matter that the ‘keep alive’ signal just doesn’t report to SmartThings at the frequency that SmartThings wants. I say this based on the regular frequency that every device goes offline/online, and the fact that all other devices never drop offline.

I am a software developer by trade, and really wouldn’t mind digging into the driver and fixing it. However, I figure I can’t be the first one with this issue.

[JDRoberts]

@briankitt

However, I figure I can’t be the first one with this issue.

Correct: you are one of dozens, if not hundreds. Just search the forum for “offline“ and you’ll find more threads than you can count. But unfortunately none of them will help.

“Off-line“ status is a construct that SmartThings has developed for themselves and it just doesn’t work great. There have been at least four official announcements that they were going to improve the algorithm, but people keep reporting issues like you have seen. And, yes, it’s usually just that a device doesn’t report quite the way that SmartThings expects, whether that’s a timing issue or something else.

The problem most commonly occurs with inexpensive Zigbee devices, including tuya made devices like the one you have, but it can occur with others as well.

Some specific models do have custom Edge drivers which can adjust the reporting frequency, but at the cost of battery life and it doesn’t always work.

So you have three options

1. try to find a custom edge driver that works with the model and then ask the author if there’s a way to adjust the reporting frequency. But there may not be.

2. try a different repeater, usually a smart plug of a different brand. Sometimes this helps, sometimes it doesn’t. For example, some people find that IKEA Smart plugs are very good repeaters while others find that they are problematic. Remember that you will have to do a Zigbee heal each time you add a new Smart plug or physically relocate one.

3. check to see if the sensor model is one which works with a matter bridge from Tuya. If so, connecting it to that bridge and then bringing it in to SmartThings that way usually takes care of the off-line problem.

[Olli-Pekka_Kurppa]

I just decided to ignore the notifications by disabling them for those devices in settings. Notification history fills but my phone and tablet keeps quiet. I hope this will be fixed someday.

[briankitt]

Have you reported this to the driver team? If not, I will. This should be a super easy fix.

[briankitt]

Where in settings? This is all I see?

[JDRoberts]

@briankitt

Have you reported this to the driver team? If not, I will. This should be a super easy fix.

Not all device manufacturers offer firmware which allows the reporting frequency to be changed. Typically, this is out of a desire to protect the battery life to avoid customer dissatisfaction or sometimes to meet safety certification requirements. Sometimes, it’s just a cost savings issue: devices that can change these kinds of parameters have to be smarter, which typically increases developer costs.

As always, the first rule of Home Automation applies: “the model number matters.“

[JDRoberts]

@briankitt

I’ve tried the ‘Zigbee Moisture Sensor MC’ by Mariano

As you probably already know, all of the “MC“ edge drivers are community – created by Mariano. Have you tried asking in his author thread to see if there’s a way to change the reporting frequency with that driver? He’s usually very responsive if parameter setting changes are possible.

(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices

[Olli-Pekka_Kurppa]

It’s in SmartThings general settings: Menu>gear icon>Notifications>three dots>Notification settings. There you can enable/disable notifications per device.

[JDRoberts]

@Olli-Pekka_Kurppa

It’s in SmartThings general settings: Menu>gear icon>Notifications>three dots>Notification settings. There you can enable/disable notifications per device.

I think the two of you are talking about two different device classifications.

Your method will turn off all notifications for the device running the SmartThings app (your mobile, or tablet).

The OP is, I suspect, looking for notifications for the individual end device, in this case, a leak sensor.

I may be mistaken, but I don’t think there’s a way in SmartThings to turn off notifications for just one end device.

edited to update: as @Olli-Pekka_Kurppa points out below, the app does have the option to turn off end device notifications on a device by device level. My apologies for any confusion and I appreciate the correction.

[briankitt]

I plan too, I just wanted to see if anyone else did. I too am a developer, and I know it can be overwhelming to have a dozen people ask you the same exact question.
So before I asked, I wanted to see if the question was already asked.

[briankitt]

Correct, I ONLY want to turn off that device, not everything.

[Olli-Pekka_Kurppa]

@briankitt

Correct, I ONLY want to turn off that device, not everything.

If you go to notification settings in SmartThings app (I’m on Android) you really don’t see individual on/off switches for each and every device (sensor, switch etc) you have in your ST system? Or do you mean that you have already switched off notifications for your troublesome water sensors, but those still notify offline-online constantly?

[JDRoberts]

@Olli-Pekka_Kurppa

@briankitt

Correct, I ONLY want to turn off that device, not everything.

If you go to notification settings in SmartThings app (I’m on Android) you really don’t see individual on/off switches for each and every device (sensor, switch etc) you have in your ST system? Or do you mean that you have already switched off notifications for your troublesome water sensors, but those still notify offline-online constantly?

Wow— I didn’t know that was there! On iOS, it’s there, but you have to click on “Filter” to get to it and it’s not obvious that that’s actionable for the purpose of turning off individual device notifications.

Thanks for the correction!

[dotan_shai]

@Mariano_Colmenarejo , have you read through this thread?
Is there something you can do from driver side that eliminate the false “Offline” notification ? Maybe increase the time for offline declaration from 1 hour to 3 hours ?
I also have these faulty notifications on Water Leak sensors , that comes back to “online” after some time. I have a good RSSI reading of my Aqara Leak sensor of -35dbm, so I don’t think it is a reception problem.

[Mariano_Colmenarejo]

@dotan_shai

have you read through this thread?

I don’t think it’s a radio problem.

When they disconnect and reconnect when motion or water is detected, it is usually because the device does not send periodic reports.
Normally these devices, some TS0207, do not accept the configuration correctly and that is why they do not send periodic reports, only when there is an event. This causes smartthings to mark them offline and online when it receives a message

Viewing the pairing logs with the CLI could be better analyzed

smartthings firmware decides when to mark offline, the driver does not intervene in that decision

[dotan_shai]

Here is a log when trying to pair after I manually removed one of my sensors.

There is an error…

ERROR Zigbee Aqara Water Leak Sensor Mc Aqara Water Leak Sensor thread encountered error: [string “st/dispatcher.lua”]:267: Error encountered while processing event for <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)>:
arg1: doConfigure
arg2: {device_already_existed=true}
“[string “init.lua”]:39: attempt to perform arithmetic on a nil value (field ‘maxTime’)”

Here is a complete LOG. A refresh exist at the end

LOG

2024-08-29T16:31:49.822421484Z DEBUG Zigbee Aqara Water Leak Sensor Mc חיישן נזילה מזגן תקרה סלון device thread event handled
2024-08-29T16:32:12.302024404Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:32:42.305761980Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:33:12.307202805Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:33:42.316309433Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:34:12.327004020Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:34:42.329797649Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:35:12.348440236Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:35:42.350589906Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:36:12.360391410Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:36:42.370491434Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:37:12.389406851Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:37:42.396391688Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:38:12.404422941Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:38:42.415805236Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:38:59.545547113Z TRACE Zigbee Aqara Water Leak Sensor Mc Received event with handler device_lifecycle
2024-08-29T16:38:59.572283030Z WARN Zigbee Aqara Water Leak Sensor Mc Device does not support cluster 0x0500 not adding configured attribute
2024-08-29T16:38:59.573853655Z INFO Zigbee Aqara Water Leak Sensor Mc Device does not support cluster 0x0500 not adding monitored attribute
2024-08-29T16:38:59.575579280Z TRACE Zigbee Aqara Water Leak Sensor Mc Zigbee Device: d9d27748-0f35-46e9-af79-78c86edb4650
Manufacturer: LUMI Model: lumi.sensor_wleak.aq1
[1]: server: Basic, Identify, PowerConfiguration | client: OTAUpgrade
2024-08-29T16:38:59.576799905Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> received lifecycle event: added
2024-08-29T16:38:59.582124280Z TRACE Zigbee Aqara Water Leak Sensor Mc Received event with handler device_lifecycle
2024-08-29T16:38:59.583754697Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> received lifecycle event: doConfigure
2024-08-29T16:38:59.586411363Z TRACE Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> received unhandled lifecycle event: added
2024-08-29T16:38:59.587489488Z DEBUG Zigbee Aqara Water Leak Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T16:38:59.590229197Z TRACE Zigbee Aqara Water Leak Sensor Mc Found DeviceLifecycleDispatcher handler in aqara-water
2024-08-29T16:38:59.591777863Z ERROR Zigbee Aqara Water Leak Sensor Mc Aqara Water Leak Sensor thread encountered error: [string “st/dispatcher.lua”]:267: Error encountered while processing event for <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)>:
arg1: doConfigure
arg2: {device_already_existed=true}
“[string “init.lua”]:39: attempt to perform arithmetic on a nil value (field ‘maxTime’)”
2024-08-29T16:38:59.594236488Z FATAL Zigbee Aqara Water Leak Sensor Mc Driver thread error
2024-08-29T16:38:59.598735738Z TRACE Zigbee Aqara Water Leak Sensor Mc Found DeviceLifecycleDispatcher handler in aqara-water
2024-08-29T16:38:59.599233155Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2024-08-29T16:38:59.608120697Z DEBUG Zigbee Aqara Water Leak Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T16:39:12.425270323Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:39:42.435376035Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:40:12.453261622Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:40:42.454308062Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:41:12.466009988Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:41:42.475530325Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:42:12.485641996Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:42:42.488084874Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:43:12.498727044Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:43:42.508564506Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:44:12.516189385Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:44:42.518148388Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:45:04.901677813Z TRACE Zigbee Aqara Water Leak Sensor Mc Received event with handler capability
2024-08-29T16:45:04.902374521Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> received command: {“args”:{},“capability”:“refresh”,“command”:“refresh”,“component”:“main”,“positional_args”:{}}
2024-08-29T16:45:04.903194021Z TRACE Zigbee Aqara Water Leak Sensor Mc Found CapabilityCommandDispatcher handler in aqara-water
2024-08-29T16:45:04.903632438Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5707, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
2024-08-29T16:45:04.923343188Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5707, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0xFF01 > > >
2024-08-29T16:45:04.927856104Z INFO Zigbee Aqara Water Leak Sensor Mc <ZigbeeDevice: d9d27748-0f35-46e9-af79-78c86edb4650 [0x5707] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x5707, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0xFF02 > > >
2024-08-29T16:45:04.931021771Z DEBUG Zigbee Aqara Water Leak Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T16:45:12.531420397Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:45:42.551741984Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:46:12.561671737Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:46:42.571699783Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event handled
2024-08-29T16:47:12.574533786Z DEBUG Zigbee Aqara Water Leak Sensor Mc driver device thread event

[Mariano_Colmenarejo]

@dotan_shai

2024-08-29T16:38:59.572283030Z WARN Zigbee Aqara Water Leak Sensor Mc Device does not support cluster 0x0500 not adding configured attribute
2024-08-29T16:38:59.573853655Z INFO Zigbee Aqara Water Leak Sensor Mc Device does not support cluster 0x0500 not adding monitored attribute
2024-08-29T16:38:59.575579280Z TRACE Zigbee Aqara Water Leak Sensor Mc Zigbee Device: d9d27748-0f35-46e9-af79-78c86edb4650
Manufacturer: LUMI Model: lumi.sensor_wleak.aq1
[1]: server: Basic, Identify, PowerConfiguration | client: OTAUpgrade

in the logs I see message Device does not support cluster 0x0500 not adding configured attribute
2024-08-29T16:38:59.573853655Z INFO Zigbee Aqara Water Leak Sensor Mc Device does not support cluster 0x0500 then it no be configured. It is strange due to this is used to detect water leak alarm.

Zigbee Aqara Water Leak Sensor Mc is obsolete, try using this driver version

───────────────────────────────────────────────────
 Name         Zigbee Moisture Sensor Mc
 Version      2024-08-29T20:27:23.97652833
───────────────────────────────────────────────────

[dotan_shai]

Here is a Pairing LOG with Zigbee Moisture Sensor Mc
No errors found, I’ve also did a quick wet / dry test. All seems to be working fine.
Cluster 0x0500 warning appear again , still you were easily able to detect wet and dry

LOG

connecting… connected
2024-08-29T22:20:30.387941127Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:21:00.395933714Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:21:30.404972301Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:22:00.416616138Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:22:30.425589100Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:22:31.762995100Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-29T22:22:31.785306017Z WARN Zigbee Moisture Sensor Mc Device does not support cluster 0x0500 not adding configured attribute
2024-08-29T22:22:31.786800683Z INFO Zigbee Moisture Sensor Mc Device does not support cluster 0x0500 not adding monitored attribute
2024-08-29T22:22:31.788810517Z TRACE Zigbee Moisture Sensor Mc Zigbee Device: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7
Manufacturer: LUMI Model: lumi.sensor_wleak.aq1
[1]: server: Basic, Identify, PowerConfiguration | client: OTAUpgrade
2024-08-29T22:22:31.790227017Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received lifecycle event: added
2024-08-29T22:22:31.795475642Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-29T22:22:31.796992808Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received lifecycle event: doConfigure
2024-08-29T22:22:31.823832392Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-29T22:22:31.825802558Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2024-08-29T22:22:31.835954433Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x384E, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
2024-08-29T22:22:31.839161642Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:31.877178350Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-29T22:22:31.921093142Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x384E, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: 00158D0006518781, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: D052A8A4E1940001, dest_endpoint: 0x01 > > >
2024-08-29T22:22:31.925905308Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x384E, 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 > > > >
2024-08-29T22:22:31.929046183Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:31.930271225Z DEBUG Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> doConfigure callback did not fail, transitioning device to “PROVISIONED”
2024-08-29T22:22:31.966923683Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture → SmartThings multi sensor
2024-08-29T22:22:31.968624475Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:31.982359808Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:32.436609725Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-29T22:22:32.437222058Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received lifecycle event: infoChanged
2024-08-29T22:22:33.237866100Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-29T22:22:33.238720392Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2024-08-29T22:22:33.239312600Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
2024-08-29T22:22:33.239883767Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= false preferences: childBatteries
2024-08-29T22:22:33.240447392Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> childBatteries nil false
2024-08-29T22:22:33.241052267Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= preferences: version
2024-08-29T22:22:33.241619892Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> version nil
2024-08-29T22:22:33.242319850Z PRINT Zigbee Moisture Sensor Mc Device ID <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)>
2024-08-29T22:22:33.242907475Z PRINT Zigbee Moisture Sensor Mc Manufacturer >>> LUMI Manufacturer_Len >>> 4
2024-08-29T22:22:33.243461183Z PRINT Zigbee Moisture Sensor Mc Model >>> lumi.sensor_wleak.aq1 Model_len >>> 21
2024-08-29T22:22:33.244026933Z PRINT Zigbee Moisture Sensor Mc Memory >>>>>>> 1035.33984375 Kbytes
2024-08-29T22:22:33.244587058Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:33.981429934Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:22:33.982049975Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x384E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xFF, rssi: -69, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x77, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0x00 > > > >
2024-08-29T22:22:34.012184725Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-29T22:22:34.013337392Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2024-08-29T22:22:34.015233100Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“2024/08/29 GMT: 22:22, LQI: 255 … rssi: -69”},“visibility”:{“displayed”:false}}
2024-08-29T22:22:34.023716559Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:0}}
2024-08-29T22:22:34.032540975Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:34.198122725Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:22:34.198747309Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x384E, src_endpoint: 0x00, dest_addr: 0x0000, dest_endpoint: 0x00, profile: 0x0000, cluster: 0x8021 >, lqi: 0xFF, rssi: -67, body_length: 0x0002, < ZDOMessageBody || < ZDOHeader || seqno: 0x43 >, < BindRequestResponse || status: 0x00 > > >
2024-08-29T22:22:34.226973684Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:22:34.381656642Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:22:34.386198309Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x384E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xFF, rssi: -69, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x78, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2024-08-29T22:22:34.416542350Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:23:00.441443758Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:23:14.146092134Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:23:14.148173634Z WARN Zigbee Moisture Sensor Mc Zigbee string reported length 34 but was actually only 33 bytes long
2024-08-29T22:23:14.150616009Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 6db79a22-2fa6-4483-8cc6-2ecd4d10e81a [0x4EFF] (חיישן נזילה מזגן תקרה סלון)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x4EFF, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -39, body_length: 0x002A, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x36, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0xFF01, DataType: CharString, CharString: “\x01\x21\xD1\x0B\x03\x28\x1D\x04\x21\xA8\x43\x05\x21\x0E\x00\x06\x24\x01\x00\x00\x00\x00\x08\x21\x06\x02\x0A\x21\xE6\xE7\x64\x10\x00” > > > >
2024-08-29T22:23:14.180479218Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-29T22:23:14.181800968Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF01
2024-08-29T22:23:14.183733551Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 6db79a22-2fa6-4483-8cc6-2ecd4d10e81a [0x4EFF] (חיישן נזילה מזגן תקרה סלון)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“2024/08/29 GMT: 22:23, LQI: 255 … rssi: -39”},“visibility”:{“displayed”:true}}
2024-08-29T22:23:14.194437551Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 6db79a22-2fa6-4483-8cc6-2ecd4d10e81a [0x4EFF] (חיישן נזילה מזגן תקרה סלון)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
2024-08-29T22:23:14.212457343Z DEBUG Zigbee Moisture Sensor Mc חיישן נזילה מזגן תקרה סלון device thread event handled
2024-08-29T22:23:30.445994553Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:24:00.461438723Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:24:30.481437268Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:24:55.849435480Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:24:55.850057313Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x384E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -61, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x00, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0001, extended_status: 0x00, zone_id: 0xFF, delay: 0x0000 > > >
2024-08-29T22:24:55.878373563Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-29T22:24:55.879452396Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2024-08-29T22:24:55.881387563Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“water”,“capability_id”:“waterSensor”,“component_id”:“main”,“state”:{“value”:“wet”}}
2024-08-29T22:24:55.889682105Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:25:00.489195730Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:25:02.538831189Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-29T22:25:02.539560272Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x384E, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFF, rssi: -55, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x19, seqno: 0x01, ZCLCommandId: 0x00 >, < ZoneStatusChangeNotification || zone_status: 0x0000, extended_status: 0x00, zone_id: 0xFF, delay: 0x0000 > > >
2024-08-29T22:25:02.567400189Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-29T22:25:02.568491814Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterCommandHandler: cluster: IASZone, command: ZoneEnrollResponse
2024-08-29T22:25:02.570365105Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 4c5e6eec-537a-4857-9aa3-0b1b91c5f5b7 [0x384E] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“water”,“capability_id”:“waterSensor”,“component_id”:“main”,“state”:{“value”:“dry”}}
2024-08-29T22:25:02.578759814Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-29T22:25:30.496036942Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:26:00.504418571Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-29T22:26:30.515025991Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled

[Mariano_Colmenarejo]

@dotan_shai

Cluster 0x0500 warning appear again

I don’t know if it’s a problem with your specific device or this model in general, the cluster 0500 is not visible for the smartthings driver and does not try to configure it.

@dotan_shai

[1]: server: Basic, Identify, PowerConfiguration | client: OTAUpgrad

Only 0000, 0001, 0003 clusters are visible

Try with this driver version. I modified it to force cluster 0500 configuration reports

───────────────────────────────────────────────────
 Name         Zigbee Moisture Sensor Mc
 Version      2024-08-30T08:49:55.135344015        
───────────────────────────────────────────────────

[dotan_shai]

Here it is with your new Zigbee Moisture Sensor Mc 2024-08-30T08:49:55.135344015

LOG

? Select a driver. 28
connecting… connected
2024-08-30T11:04:39.701325660Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:04:44.852766410Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-30T11:04:44.853488660Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 32a82c1f-124d-487d-a408-63d3effddf67 [0x14C6] (גלאי נזילה - כיור מקלחת הורים)> received lifecycle event: removed
2024-08-30T11:04:44.904474577Z TRACE Zigbee Moisture Sensor Mc <ZigbeeDevice: 32a82c1f-124d-487d-a408-63d3effddf67 [0x14C6] (גלאי נזילה - כיור מקלחת הורים)> received unhandled lifecycle event: removed
2024-08-30T11:04:44.906673910Z DEBUG Zigbee Moisture Sensor Mc גלאי נזילה - כיור מקלחת הורים device thread event handled
2024-08-30T11:04:44.920841410Z DEBUG Zigbee Moisture Sensor Mc גלאי נזילה - כיור מקלחת הורים device thread event handled
2024-08-30T11:05:09.698824038Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:05:39.705785458Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:06:09.722233545Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:06:39.715951215Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:07:09.724595236Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:07:39.742787928Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:08:09.735369515Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:08:39.744499018Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:09:09.751283605Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:09:39.758540359Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:10:09.768977029Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:10:39.775398907Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:11:09.787870443Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:11:38.012194764Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-30T11:11:38.036617514Z WARN Zigbee Moisture Sensor Mc Device does not support cluster 0x0500 not adding configured attribute
2024-08-30T11:11:38.038059889Z INFO Zigbee Moisture Sensor Mc Device does not support cluster 0x0500 not adding monitored attribute
2024-08-30T11:11:38.039721180Z TRACE Zigbee Moisture Sensor Mc Zigbee Device: 7daebd18-586c-4597-b44e-cb818c1ade5c
Manufacturer: LUMI Model: lumi.sensor_wleak.aq1
[1]: server: Basic, Identify, PowerConfiguration | client: OTAUpgrade
2024-08-30T11:11:38.040985972Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received lifecycle event: added
2024-08-30T11:11:38.045894930Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-30T11:11:38.047377972Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received lifecycle event: doConfigure
2024-08-30T11:11:38.074404972Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-30T11:11:38.076093555Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“Waiting Zigbee Message”},“visibility”:{“displayed”:false}}
2024-08-30T11:11:38.156772889Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xF87D, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0021 > > >
2024-08-30T11:11:38.160232430Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:38.224689389Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-30T11:11:38.312651472Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xF87D, 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: 0x0258 > > > >
2024-08-30T11:11:38.316577555Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:38.318881597Z DEBUG Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> doConfigure callback did not fail, transitioning device to “PROVISIONED”
2024-08-30T11:11:38.364667764Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture → SmartThings multi sensor
2024-08-30T11:11:38.366348889Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:38.374432972Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:38.833773097Z TRACE Zigbee Moisture Sensor Mc Received event with handler device_lifecycle
2024-08-30T11:11:38.834382305Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received lifecycle event: infoChanged
2024-08-30T11:11:38.993679097Z TRACE Zigbee Moisture Sensor Mc Found DeviceLifecycleDispatcher handler in st-zigbee-moisture
2024-08-30T11:11:38.994924889Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= false preferences: childBatteries
2024-08-30T11:11:39.001496139Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> childBatteries nil false
2024-08-30T11:11:39.562816972Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= preferences: version
2024-08-30T11:11:39.972447222Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> version nil
2024-08-30T11:11:39.978668597Z PRINT Zigbee Moisture Sensor Mc device.preferences[infoChanged]= No preferences: signalMetricsVisibles
2024-08-30T11:11:39.981735514Z PRINT Zigbee Moisture Sensor Mc << Preference changed: name, old, new >> signalMetricsVisibles nil No
2024-08-30T11:11:39.982300097Z PRINT Zigbee Moisture Sensor Mc Device ID <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)>
2024-08-30T11:11:39.982864389Z PRINT Zigbee Moisture Sensor Mc Manufacturer >>> LUMI Manufacturer_Len >>> 4
2024-08-30T11:11:39.983726847Z PRINT Zigbee Moisture Sensor Mc Model >>> lumi.sensor_wleak.aq1 Model_len >>> 21
2024-08-30T11:11:39.987407639Z PRINT Zigbee Moisture Sensor Mc Memory >>>>>>> 1018.759765625 Kbytes
2024-08-30T11:11:39.988143722Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:39.989287014Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-30T11:11:39.998656431Z WARN Zigbee Moisture Sensor Mc Zigbee string reported length 34 but was actually only 33 bytes long
2024-08-30T11:11:40.003595764Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF87D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Basic >, lqi: 0xFF, rssi: -69, body_length: 0x0043, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x1C, mfg_code: 0x115F, seqno: 0x02, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0005, DataType: CharString, ModelIdentifier: “lumi.sensor_wleak.aq1” >, < AttributeRecord || AttributeId: 0xFF01, DataType: CharString, CharString: “\x01\x21\xE5\x0B\x03\x28\x26\x04\x21\xA8\x01\x05\x21\x83\x00\x06\x24\x00\x00\x01\x00\x00\x08\x21\x06\x02\x0A\x21\x00\x00\x64\x10\x00” > > > >
2024-08-30T11:11:40.042885264Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> Lazy loaded driver into dispatcher: SmartThings multi sensor
2024-08-30T11:11:40.044553764Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-30T11:11:40.045609264Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: Basic, attribute: 0xFF01
2024-08-30T11:11:40.047562472Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“2024/08/30 GMT: 11:11, LQI: 255 … rssi: -69”},“visibility”:{“displayed”:false}}
2024-08-30T11:11:40.153297681Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:100}}
2024-08-30T11:11:40.172628722Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:40.173127556Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-30T11:11:40.173562556Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF87D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, lqi: 0xFF, rssi: -68, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x48, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0021, ZclStatus: SUCCESS, DataType: Uint8, BatteryPercentageRemaining: 0x00 > > > >
2024-08-30T11:11:40.212640056Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:11:40.214547597Z TRACE Zigbee Moisture Sensor Mc Received event with handler zigbee
2024-08-30T11:11:40.227171764Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0xF87D, src_endpoint: 0x01, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: IASZone >, lqi: 0xFE, rssi: -68, body_length: 0x0005, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x49, ZCLCommandId: 0x0B >, < DefaultResponse || cmd: 0x06, ZclStatus: UNSUP_GENERAL_COMMAND > > >
2024-08-30T11:11:40.255729139Z TRACE Zigbee Moisture Sensor Mc Found ZigbeeMessageDispatcher handler in st-zigbee-moisture
2024-08-30T11:11:40.257277097Z INFO Zigbee Moisture Sensor Mc Executing ZclClusterAttributeValueHandler: cluster: PowerConfiguration, attribute: BatteryPercentageRemaining
2024-08-30T11:11:40.259166389Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“signalMetrics”,“capability_id”:“legendabsolute60149.signalMetrics”,“component_id”:“main”,“state”:{“value”:“2024/08/30 GMT: 11:11, LQI: 255 … rssi: -68”},“visibility”:{“displayed”:false}}
2024-08-30T11:11:40.267356139Z INFO Zigbee Moisture Sensor Mc <ZigbeeDevice: 7daebd18-586c-4597-b44e-cb818c1ade5c [0xF87D] (Aqara Water Leak Sensor)> emitting event: {“attribute_id”:“battery”,“capability_id”:“battery”,“component_id”:“main”,“state”:{“value”:0}}
2024-08-30T11:11:40.282642389Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:11:40.329562056Z DEBUG Zigbee Moisture Sensor Mc Aqara Water Leak Sensor device thread event handled
2024-08-30T11:12:10.011430601Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:12:40.018127229Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:13:10.027332316Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled
2024-08-30T11:13:40.048822903Z DEBUG Zigbee Moisture Sensor Mc driver device thread event handled