Error with setting up Matter (BETA)

[my-cla4ik-f0rmy]

The problem

Hi! My problem is that when connecting a new Matter device on Tasmota firmware, it connects to the Matter Server Add-on

but gives an error when configuring the Integration Matter (BETA)

I installed the Espressif-Matter application and in it I was able to connect to the Tasmota device and control it, so I think the problem is not in Tasmota itself

I tried to install beta versions of Home Assistant and Matter Server, but the problem is the same

What version of Home Assistant Core has the issue?

core-2024.5.0b1

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 (BETA)

Link to integration documentation on our website

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

Diagnostics information

home-assistant_matter_2024-04-27T17-03-12.472Z.log

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

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]

This issue will be fixed in the next Home Assistant release