Certainly, will do this as soon as i get home from work. Do you want me to post the ticket number here after?
Ticket # 197762, I gave as much detail as I thought relevant regarding the testing I have done.
1 Like
To others who are looking for a solution/update on this issue.
I have tested 1.12.3 and the issue persists, but the names pulled through from iHost to Google Home are shorter and possibly take some information from the assigned name in iHost.
I have reported this and more and hope that a final solution will come soon.
1 Like
Hi,do you have any good news with patch version 1.12.4?
The good news is that I have finally managed to pair iHost with Google Home. The app showed all the devices listed on ā¦/#/matter/support as supported, and the Google platform displays as āaddedā in iHost. This is where the good news ends. All devices in Google Home are listed as āofflineā and cannot be controlled and their property cards cannot be edited. Device names are strings (presumably with some logic in it) of letters and digits.
Now for the most interesting part of this story. Pairing with Amazon Alexa still fails with the same message as in previous firmware versions. However, I decided to take the opportunity to share the Google Home pairing code with Alexa. It worked!
As for Amazon Alexa paired via Google Home, editing names is possible. Names like āFirst plugā or āSecond plugā were assigned automatically by Alexa platform. With 1.12.4, restarting iHost does not change the manually assigned names in Alexa. However, you see the note āDevice is unresponsiveā on the tiles of most of them. This is not true, as control of such devices is possible. With a small delay they turn on eventually. Once this is done, the note disappears. All devices from the ā¦/#/matter/support list in iHost are present in Alexa, including Zigbee sensors.
Deleting the connection to the Google platform in iHost does not destroy the pairing with Alexa (made via the Home app). I will try connecting Google Home with the code from Alexa.
Google Home and Alexa both need Hub for matter controlling. If you had any one?
What kind of hub do you have on mind?
What is this table supposed to help with?
How do I install the latest version? My iHost is stuck in 1.2.20. Thanks.
Why it pairs with keychain? To me this is a bit suspicious
By pairing to Apple Keychains all the credentials generated from the Matter network will be stored thereā¦ You can also keep using iHost with other Matter Platforms even if you remove from Apple HomeKit since its all stored in the Keychain. It works like that on Android as well, Google will store the credencials in Google Play Services instead (I might be wrong on this, Google also have a Thread Play Services but Iām not sure if its only available for Thread or if Matter is also included). Unlike Apple, Google wonāt report their Keychain as a separate service for Matter, not sure why or even if it makes any difference at all.
1 Like
So far my testing of 1.12.4 has not been successful. I am currently trying a few more things before sending my report to help centre again.
I received version 1.12.4 to test the reported problem, and it was fixed. Now I can easily integrate Matter with Homekit.
I did a quick test and it also solved the problem of losing device names after restarting Ihost, but this case needs some more testing.
Iāve tested 1.12.4 and the issue of loosing assigned names and credentials is still present for me in Google Home.
Iād be interested to hear if anyone else has resolved this issue with GH yet.
I can confirm thisā¦ for me it was working fine on 1.12.4 with the names not changing and device not repairing after reboot on Apple HomeKit, but after 1.13.0 the issue came back, Iām checking the logs to see if I spot something that could help debug this issue
1 Like
Unfortunately, on the Google Home app I had the repairing and device credential loss issue through all firmware revisions from 1.12.0 to 1.13.0.
Is there any latest news?
Not yet, I tried to cross reference the logs but Iām still trying to figure it out how things are connected. It would help a lot if there was any documentation or even a diagram describing how the the components are tied and which depends on which to start.
From what I could tell from the logs, the Matter bridge is waiting for the zigbee bridge to start but not zigbee2cube to start. If possible, it would help a lot to add a āZigbee2CUBE startedā message so I can cross check the timestamps.
Or provide your sys logs to me ?
1 Like