Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aqara T2 and Nanoleaf LED Bulbs Matter Instability #138944

Open
DamoclesSword opened this issue Feb 20, 2025 · 1 comment
Open

Aqara T2 and Nanoleaf LED Bulbs Matter Instability #138944

DamoclesSword opened this issue Feb 20, 2025 · 1 comment

Comments

@DamoclesSword
Copy link

The problem

I have tried other support avenues, including contacting Aqara/Nanoleaf, but to no avail.

I have been trying to setup these bulbs with little success.

The Aqara bulbs connect to Apple Homekit fine, but when enabling pairing mode, the bulbs may or may not connect to Home Assistant. I have a strong Wi-Fi network and 3 Apple HomePod mini acting as border routers. Some bulbs take 5-10 tries to connect to HA

Out of my 5 bulbs:

2 connected to HA first, then were shared to Homekit,
2 connected to Homekit then were shared to HA (because they wouldnt connect to HA first)
1 connected to Homekit but wont share to HA at all.

In HA, the two I connected natively are connected fine but the two I shared keep becoming unavailable.

I also grouped them all via a helper, but when doing a group command only a couple bulbs respond. All bulbs respond well in Homekit though.

Looking at the logs, I get errors like I posted below, but even when the device is unavailable, I can ping the device fine.

I do have Unifi network but have everything setup correctly (I think).

For Nanoleaf, the bulbs are constantly losing their thread connection despite what I believe to be a strong thread network. I also have several ESP BLE Proxy devices setup throughout my home.

Here is one of the logs for Aqara:

2025-02-17 22:13:35.883 (MainThread) INFO [matter_server.server.device_controller] Node:138 Subscription failed with CHIP Error 0x00000032: Timeout, resubscription attempt 3 2025-02-17 22:13:35.883 (MainThread) ERROR [matter_server.server.client_handler] [140088973229952] Error while handling: device_command (node 138): src/protocols/secure_channel/CASESession.cpp:607: CHIP Error 0x00000032: Timeout 2025-02-17 22:14:00.135 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:35799i with Node: <0000000000000000, 0> S:0 M:19388841] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2025-02-17 22:14:10.509 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000008A, 1>. Current state was 4 2025-02-17 22:14:35.934 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:35808i with Node: <0000000000000000, 0> S:0 M:19388842] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2025-02-17 22:14:44.929 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000008A, 1>. Current state was 4 2025-02-17 22:15:11.397 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:35811i with Node: <0000000000000000, 0> S:0 M:19388843] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2025-02-17 22:15:19.349 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000008A, 1>. Current state was 4 2025-02-17 22:15:45.522 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:35816i with Node: <0000000000000000, 0> S:0 M:19388844] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2025-02-17 22:15:53.767 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000008A, 1>. Current state was 4 2025-02-17 22:16:20.397 (Dummy-2) CHIP_ERROR [chip.native.EM] <<5 [E:35826i with Node: <0000000000000000, 0> S:0 M:19388845] (U) Msg Retransmission to 0:0000000000000000 failure (max retries:4) 2025-02-17 22:16:28.186 (Dummy-2) CHIP_ERROR [chip.native.SC] CASESession timed out while waiting for a response from peer <000000000000008A, 1>. Current state was 4 2025-02-17 22:16:28.187 (Dummy-2) CHIP_ERROR [chip.native.DMG] Failed to establish CASE for re-subscription with error ‘src/protocols/secure_channel/CASESession.cpp:607: CHIP Error 0x00000032: Timeout’

What version of Home Assistant Core has the issue?

core-2025.2.4

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

Matter and Thread

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

No response

@home-assistant
Copy link

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter 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 matter 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)


matter documentation
matter source
(message by IssueLinks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant