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

Unable to add Siegenia window sensor to HomeAssistant by Matter #119071

Closed
matthias987654 opened this issue Jun 7, 2024 · 10 comments
Closed

Unable to add Siegenia window sensor to HomeAssistant by Matter #119071

matthias987654 opened this issue Jun 7, 2024 · 10 comments

Comments

@matthias987654
Copy link

The problem

We are unable to add the Siegenia window sensor to HomeAssistant by Matter. The device is working with the Apple Home without any problems. But we can't add the device to HomeAssistant. We discussed that topic on the discord server without a solution. I tested it with the official release of the matter server and the beta version 6.1. It is the same error behaviour.

What version of Home Assistant Core has the issue?

2024.6.0

What was the last working version of Home Assistant Core?

Unknown

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter

Link to integration documentation on our website

Matter

Diagnostics information

(Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'SendComplete': 'IM Error 0x00000501: General error: 0x01 (FAILURE)'

Example YAML snippet

No response

Anything in the logs that might be useful for us?

(Dummy-2) CHIP_ERROR [chip.native.CTL] Error on commissioning step 'SendComplete': 'IM Error 0x00000501: General error: 0x01 (FAILURE)'

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jun 7, 2024

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)

@agners
Copy link
Member

agners commented Jun 11, 2024

Hm, it seems that late during the commissioning the device sens an error back to our Matter controller, which causes the device to drop.

The whole commissioning flow is pretty much straight from the official Matter SDK, so it is a bit surprising that this does not affect Apple 🤔

Did you commission it first with Apple and then with HA?

Did you try factory reset and do the opposite: Pair first with HA (and then with Apple?).

@matthias987654
Copy link
Author

matthias987654 commented Jun 12, 2024

Yes - first Apple Home and then HomeAssistant. I didn't test it the other way around.

@lboue
Copy link
Contributor

lboue commented Jun 15, 2024

@matthias987654 Did you try to factory reset the device and give a another try?

@matthias987654
Copy link
Author

Yes, same error after that. I am able to add the device as new device. But there is no possibility to add a second platform like Apple Home.

@lboue
Copy link
Contributor

lboue commented Jun 15, 2024

Yes, same error after that. I am able to add the device as new device. But there is no possibility to add a second platform like Apple Home.

You could use the 'Share device' function for that. If it doesn't work, it's due to a limit on the number of Matter fabric on the device.

image

@matthias987654
Copy link
Author

matthias987654 commented Jun 15, 2024

I used that. But it ends with an error during the enrollment on Apple Home, too.

@lboue
Copy link
Contributor

lboue commented Jun 15, 2024

I used that. But it ends with an error during the enrollment on Apple Home, too.

So it's an device issue.

@matthias987654
Copy link
Author

Siegenia is working on that topic. I am waiting for feedback from the developers of Siegenia.

@marcelveldt
Copy link
Member

This appears to be a device issue where the device can not handle Multi admin correctly (something we see more often with 1.0 devices). It will probably/hopefully be fixed by the vendor at some point. Its not a bug in HA Matter, so I'll close here.

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

5 participants