Aqara Smart Smoke Detector is disconnected after a few hours.

[dudi-hendri]

The problem

Hello, I have the Aqara Smart Smoke Detector (lumi.sensor_smoke.acn03) im using ZHA and I noticed that after pairing the sensor works for several hours and then it becomes unavailable until I re-pair it.

What version of Home Assistant Core has the issue?

core-2024.1.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @dmulcahey, @adminiuga, @puddly, @thejulianjes, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `zha` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign zha` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zha documentation zha source _{^{(message by IssueLinks)}}

[dmulcahey]

This is most likely due to the mix of devices on your network. The non zigbee 3.0 Aqara devices sleep aggressively and older routers on the network drop them as a result. See here for more info: https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623

[dudi-hendri]

Hi, Thanks for the quick reply. Just to make sure i havent missed any important details: the Aqara sensor is connected to "SONOFF ZB Dongle-P" directly and has a good reception. Does it matter?

[dmulcahey]

Depends… do this for now: get the device connected / active then put ZHA in debug mode and leave it in debug mode until it becomes unavailable. Once that happens disable debug mode and attach the log it generates here.

[TheJulianJES]

I also have one, they're "Zigbee 3.0". I've never had any issues with it disconnecting, just sometimes not receiving commands to manually toggle the siren.

Can you attach both diagnostic files from the ZHA integration and from the device page itself? I'm mostly curious about the Z-Stack version. Your issue might be solved with Z-Stack firmware 20230507 and newer. However, those versions will crash/freeze your coordinator, so don't install them for now.

A workaround would be to pair the smoke sensor through another router (plug, bulb) — not directly to your coordinator.

[dudi-hendri]

zha-13fd1654d27854af8a1489ac7e04362b-LUMI lumi.sensor_smoke.acn03-560491a46e769013bf5544c7a5d3222a.json.txt is this what you need?

[unaif]

Same problem here. if i delete the sensor and pair it again works but after some hours it fails. I will update today to 2024.02.0.

Regards

[ChristBKK]

I have the same problem did you guys find a solution? @unaif @dudi-hendri ?

[unaif]

i change the sonoff single to e version and atarte d to work. maybe upgrading the firmaré should work buy i have not tried yet

El El mié, 1 may 2024 a las 12:56, Christian Josephs < @.***> escribió:

I have the same problem did you guys find a solution? @unaif https://github.com/unaif @dudi-hendri https://github.com/dudi-hendri ?

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/108705#issuecomment-2088287718, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC6WLFWAIK54SES4EETNJY3ZADC5LAVCNFSM6AAAAABCGPSV36VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGI4DONZRHA . You are receiving this because you were mentioned.Message ID: @.***>

[dudi-hendri]

I have the same problem did you guys find a solution? @unaif @dudi-hendri ?

I moved from ZHA to zigbee2mqtt and it works well. I also changed the zigbee adapter from sonoff P dongle to SMLIGHT SLZB-06

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.