Replies: 1 comment 9 replies
-
|
When you have a look at the lugs then there is the main commissioning low with apple within some Seconds and then there is a break 13:24:07-13:24:52 before shone Assistent connects again to subscribe to all states. So for me the question is why hass have this delay? Maybe hass side logs from the same process helps? |
Beta Was this translation helpful? Give feedback.
9 replies
-
|
Here more logs from another user, they said the pairing succeeded but then the devices went offline shortly after: https://gist.github.com/itsopti/3109d3bf5e9c54f414439cd4ebb0bdf7#file-nr-log HA core logs: HA Matter logs: |
Beta Was this translation helpful? Give feedback.
-
|
These are the logs from my own environment, where the bridge stopped responding on both Apple Home (primary controller) and Home Assistant (secondary controller). Home Assistant logs: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry but it starts to get confusing. Just a hass log is not helpful because I do not know the semantics yet and so I could only understand it with a matching matter.js log. Additionally: which node-red node? Did someone build a node red node with matter.js? Please link. Alexa has also no known issues beside that it somehow have issues in discovery sometimes. Reasons unknown and honestly: apple and google are the proof that matter.js is doing right. So I would more ask what maybe Amazon does wrong ;-) Hass uses Chip tool logic under the hood. Alexa should use something else because integrated in the echo device firmware. But yes interoperability is a challenge. So for short: for hass please add matching logs. Else it is guessing. But yes I will read through all above to maybe guess a bit. |
Beta Was this translation helpful? Give feedback.
-
|
Ok ... hass matter log ValueError: 0 is not a valid EventPriority In fact 0 is a valid value. So sounds more like a hass issue? |
Beta Was this translation helpful? Give feedback.
-
|
In the other log the hass log states about not received datareport and subscription timeout. Given the last full log we checked where hass did send two subscribes it could be that it expects a response to the first subscription a d that's why times out - but that first subscription gets overruled by second. But as said without logs from the same try from both sides it is just guessing. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm testing out the Home Assistant Matter integration and I noticed that adding devices to my Raspberry Pi 4 HassOS server is taking much longer than when I try to add it from Apple Home.
In both cases the device is created using the example provided in this repository, but when added to Home Assistant it takes a long time. Below are the full logs. Any idea?
Beta Was this translation helpful? Give feedback.
All reactions