Aqara Cube T1 Pro actions are not registered and this error is showing

[sharpcall]

The problem

I have Sonoff Zigbee USB attached to server and Aqara T1 Cube Pro has registered and shows as a device but the actions of the Aqara Cube is not registering in HaOS. I see the following in Matter logs repeating many times.

2025-01-29 02:51:35.718 (Dummy-2) CHIP_ERROR [chip.native.DIS] Packet to small for mDNS data: 4 bytes
2025-01-29 03:01:16.625 (MainThread) INFO [matter_server.server.device_controller] <Node:1> No new update found.

And listening to zha_events or zha_event does not show any events when the Aqara Cube is moved which is should but simulating a zha_event from HaOS works and shows in zha listener. The registration process from the Aqara Cube shows in the zha listener but after that there are no other events that show.

What is causing this bug?

What version of Home Assistant Core has the issue?

core-2025.1.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 Aqara Cube T1 Pro

Link to integration documentation on our website

No response

Diagnostics information

Example YAML snippet

Anything in the logs that might be useful for us?

2025-01-29 02:51:35.718 (Dummy-2) CHIP_ERROR [chip.native.DIS] Packet to small for mDNS data: 4 bytes
2025-01-29 03:01:16.625 (MainThread) INFO [matter_server.server.device_controller] <Node:1> No new update found.

Additional information

No response

[home-assistant]

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)}}

[marcelveldt]

Why did this issue got tagged as Matter while it is a zigbee device ?
Did you mean the ZHA integration perhaps ?

[sharpcall]

Why did this issue got tagged as Matter while it is a zigbee device ? Did you mean the ZHA integration perhaps ?

Hi, how to change the tag to Zigbee please?

[home-assistant]

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)}}