cancel
Showing results for 
Search instead for 
Did you mean: 

Matter gone?

fabnapp
Community Member

Hey, it seems Matter support is gone for the moment?

 

All my Matter devices in Google Home (Eve devices over Thread) now show as offline and when adding devices the top option Matter is gone

 

Anybody Else? 

4 Recommended AnswerS

nRF-N00b
Community Member

Hi @Juni , just to follow up. Is there any one at Google looking into this issue? Is it a bug or has Matter commissioning via Google Home app been turned off? A status update or advice would be appreciated as I need to get matter working with Google Nest Hub.

Let me know if you need any further info or details. Thanks.

View Recommended Answer in original post

Sutty5
Community Member

Has this same issue for months. This is completely broken. Is someone at Google actually aware of and actively working on the issues? I have matter devices I cannot commission because the option keeps disappearing from Android. I had it 2 weeks ago, haven't been able to force it back in any way since. Despite having border routers and devices ready to commission.

View Recommended Answer in original post

sipriyadarshi
Solutions Expert
Solutions Expert

 

adb shell dumpsys package com.google.android.gms | grep "versionName"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.optional_home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.policy_home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.threadnetwork"

adb shell dumpsys package com.google.android.apps.chromecast.app | grep versionName

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "Enabled features" | grep -i "home"

adb shell getprop ro.build.version.release

adb shell getprop ro.build.version.sdk

 

 

We have made changes that should impact this issue and would like to confirm if you're still experiencing the problem. If you are still experiencing the problem, please check the versions on your phone (command above). If you have versions < prefixes 23.05 / 2305, please ensure the home app and play services are up to date and check again. If you have versions >= 2305 and still experience the issue, please share here.

View Recommended Answer in original post

fabnapp
Community Member

The latest update fixed it... for a day

Now it is gone again.

Please Please Please somebody from Google tell what is going on? Is this the desired experience?

@sipriyadarshi ?

View Recommended Answer in original post

45 REPLIES 45

JeffWelder
Community Member

I'm also getting "Device not responding" on my network.

nRF-N00b
Community Member

I can't commission Thread or WiFi Matter devices as well. Option to select Matter-enabled devices is gone and I only see option for "Seamless Setup device" which then makes me install NEST app : (

fabnapp
Community Member

Seems only Google can clarify what's going on

fabnapp
Community Member

So, the Matter Devices are back online now, the option to add more Matter in the App is still MIA but it seems work is going on on the servers

nRF-N00b
Community Member

I managed to resolve by uninstalling and reinstalling the Google Home app. When I tried to recommission the Matter-Enables Devices option was back.

Juni
Community Specialist
Community Specialist

Hi folks,

 

Thanks for reaching out and sorry for the late response. I’m glad your issue is resolved now. I’ll keep this thread open for 1 more day. If you need further help, let me know.

 

Regards,

Juni

nRF-N00b
Community Member

Hi @Juni , just to follow up. Is there any one at Google looking into this issue? Is it a bug or has Matter commissioning via Google Home app been turned off? A status update or advice would be appreciated as I need to get matter working with Google Nest Hub.

Let me know if you need any further info or details. Thanks.

nRF-N00b
Community Member

Hi @Juni ,

Is there any to help on this? Even if it's being looked at by someone we'd appreciate some update. Please help.

Regards,

nRF-N00b

nRF-N00b
Community Member

Hi Juni! Thanks for your reply, please keep this open as the problem has returned. But this time even though I try to reinstall Home app it does not resolve the problem. Meaning since last week I have not been able to commission any Matter devices cause I no longer see option to add "Matter Enabled" device when the app scans for advertising nodes that are looking to be commissioned : (

Need your advice on this. Do let me know if you need further info. Thanks!

BatVanyo
Community Member

Aside from saying "me too" (Matter support recently disappeared from my Samsung S20FE and does not re-appear after re-installing the Google Home app) I would share that the Matter support so far from Google - for developing/comissioning Matter-enabled devices - had been "nothing short" of a complete disaster. 

It is now two months since I'm stuck with the chip-tool only and can't test with a "real" Controller and Comissioner like the Nest + Android phone combo.

The recent and sudden disappearing of the Matter support from my phone and possibly from the Nest device is the tip of the iceberg. Like without any trace why, how, when it would be restored. Before that, I was never able to commission my device actually, which just uses the Matter SDK and commissions just fine with chip-tool. Nor was I able to commission an **example** from the Matter SDK itself! And these things are normal in the early days, I get it. What is not normal is - when commissioning fails - to only get the idiotic "can't commission right now" end user message. **NO** developer oriented error messages, nothing. Black box. How are you guys diagnosing errors with the Google controller/commissioner stack? Was not able to find anything on the internet.Did I miss the elephant in the room? Pathetic.

BatVanyo
Community Member

(Replying to myself) W.r.t. the previous "cannot pair" error, I've apparently had been hitting this issue: https://github.com/google-home/sample-app-for-matter-android/issues/61#issuecomment-1357472540

 

Also the ADB logs at least output like two error lines (not very helpful but still). So when/if Matter supports co.es back to my Android phone (any ETA? Any idea why it had disappeared?) I can test again with the Google comissio ers/controllers.

fabnapp
Community Member

the appearance/dissaperance is random it seams. I have add matter on on one device that did not have it before and gone an another

Google Folks here - i really appreciate your work in this community. I often see you ask people for more details, what i miss from you is giving ANY feedback on the status of reported issues, can you lease change that and then drown in Kudos? tks!!! 

BatVanyo
Community Member

Is it random? I just did a factory reset on another device, upgraded Android and then installed the Home app.

No sign of Matter.

 

BatVanyo
Community Member

You are right: it is random. I restarted the "clean" Android phone and commissioning with Matter somehow started working on it!

Strangest thing is, on the other, non-working phone - the bug seems to be commissioning related only. I can otherwise control the "device" from that phone; in other words, that phone still speaks Matter... UPDATE: On a second thought, it is the Nest device that speaks Matter actually, I doubt the phone does anything else Matter-related besides commissioning... Anyway.

nRF-N00b
Community Member

Just to share an update, I had a Thread-Matter Node broadcasting for commission (at the time I was not using Home app to commission anything yet) and a "Connect Matter Device" notification popped up on my colleagues Xiaomi phone (Android 11) : p

 

Surprised at this, I got my colleague to connect to Google Nest Hub and try to the commission process of the Thread Matter node I had on. There was some data exchange happening until Google Home app shows a message saying that a Thread Border Router is needed. This is strange since the Nest Hub (Gen 2) that's already connected is a Thread Border Router.

 

So the finding is sort of pointing to an issue with Thread on the Hub? Still investigating... Would be great to get ANY input from Google or a specialist. @Juni 

fabnapp
Community Member

Screenshot_2023-02-02-07-52-45-11_2d2bd67b5e15ae98c151ac739cd6881e.jpg

Google friends, @Juni can you please acknowledge that this is a thing?

nRF-N00b
Community Member

thanks for sharing that @fabnapp ! that's what i see (or don't see) too!

fabnapp
Community Member

Screenshot_2023-02-02-07-55-04-28_f7aa348215f5d566f9e4ca860f474209.jpg

Latest client, Android12 phone with January System updates so... no excuse tbh.

nRF-N00b
Community Member

same with my ecosystem test too.. using Android 12 and Google Home app version (2.63.1.12)

Android 13 on Galaxy S20FE - same story.

MrMister76
Community Member

Unfortunately I have the same issue. I have already deleted the app data but the Matter option doesn't appear anymore.

mdrileynyc
Community Member

Same issue - no options for adding matter devices. O/S, all apps and security fixes are up-to-date on Pixel 7 Pro. Anybody from Google looking at this?

sconix
Community Member

For me the matter support always disappears after rebooting phone or just stopping the Google Home app. Only way to get it back is to re-install the Google Home app. Also just updating it when ever there is an update brings it back, but its always available only until the app gets closed.

Sutty5
Community Member

Has this same issue for months. This is completely broken. Is someone at Google actually aware of and actively working on the issues? I have matter devices I cannot commission because the option keeps disappearing from Android. I had it 2 weeks ago, haven't been able to force it back in any way since. Despite having border routers and devices ready to commission.

Spacefish
Community Member

Same issue.. The matter component of the Google Play Services is not installed.. I can force the installation by installating an app which uses the matter API (causes "installing play services component" dialog), afterwards "Matter device" is availiable in GHA as well..
Google WTF... why not automatically push this to all phones / GHA installations?
You have a release version of the component, but you choose to not deploy it on most phones by default..

PapaLanc
Community Member

What app are you installing to get it to work?

I saw SpaceFish's message and tried uninstalling and reinstalling Google Play. The Matter menus appeared.  I had tried the same thing a few days earlier and it didn't help. In both cases everything else was up-to-date. Go figure.

sconix
Community Member

For me its the Google Home app, reinstalling it or updating it brings back matter support until the Google Home apps gets closed (force stopped manually or closed by the system) or I restart the phone. My phone is Pixel so bit annoyed that this does not work properly even on Googles own phones.

sipriyadarshi
Solutions Expert
Solutions Expert

 

adb shell dumpsys package com.google.android.gms | grep "versionName"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.optional_home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.policy_home"

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.threadnetwork"

adb shell dumpsys package com.google.android.apps.chromecast.app | grep versionName

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "Enabled features" | grep -i "home"

adb shell getprop ro.build.version.release

adb shell getprop ro.build.version.sdk

 

 

We have made changes that should impact this issue and would like to confirm if you're still experiencing the problem. If you are still experiencing the problem, please check the versions on your phone (command above). If you have versions < prefixes 23.05 / 2305, please ensure the home app and play services are up to date and check again. If you have versions >= 2305 and still experience the issue, please share here.

Thanks for the info, my versions seemed to be prefixed with 23.07. Did reinstall home app to get the matter support back and restarted the phone and matter support was still there! So it looks like it might actually work now, will post again if I will loose it again due to some action, but at least until now I always lost the support with single restart.

Still having the problem, here is the output oft the commands

adb shell dumpsys package com.google.android.gms | grep "versionName"
versionName=23.08.15 (190400-512743456)
versionName=22.46.17 (190408-491726958)

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.home"
com.google.android.gms.homegraph [v230815000]

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.optional_home"
com.google.android.gms.optional_homegraph [230815057] [23.08.15 (100000-0)] [Download:0000008b/dl-Homegraph.optional_230815100000.apk] [download:/Homegraph.optional/230815100000:Homegraph.optional:230815100000]

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.policy_home"
NO OUTPUT

 

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "com.google.android.gms.threadnetwork"
com.google.android.gms.threadnetwork [v230815000]

adb shell dumpsys package com.google.android.apps.chromecast.app | grep versionName
versionName=2.63.1.12

adb shell dumpsys activity provider com.google.android.gms.chimera.container.GmsModuleProvider | grep "Enabled features" | grep -i "home"
Enabled features: brella_dynamite, fast_pair, game_platform, games, homegraph, mlkit.barcode.ui, mlkit.docscan.crop, mlkit.docscan.detect, mlkit.docscan.enhance, mlkit.ocr.common, usonia, usonia_iam, vision.barcode, vision.custom.ica, vision.face

adb shell getprop ro.build.version.release
13

adb shell getprop ro.build.version.sdk
33

MrMister76
Community Member

Play services Version: 23.06.17 (190408-511787759)

Matter is gone again, it worked yesterday. Normally it comes back when I delete Google home and reinstall it. I already had to do this 3 times or so. 

This is really a killer.. 

fabnapp
Community Member

still dont see it after reinstalling home to latest playstore version. What other debug steps work? Like what other app would trigger the service install?

sconix
Community Member

Its also gone for me again. So weird, this time it was available for a week which is longer than ever before, but this is ridiculous how can feature come on go like this. Does not make any sense.

Spacefish
Community Member

After an update to the Home App it will be there for 1-2 days, as the play service module for matter get´s installed during the update by play store, but after some time it seems to get removed automatically again, don´t know why.

Sutty5
Community Member

Yep, the option came back after the latest Google home app update, but now it's gone again!

fabnapp
Community Member

Same. I mean... @#€_&-+*"?! 

Kacperhq
Community Member

I have the same problem.

Spacefish
Community Member

Ok, i have two matter devices now.. (via Ethernet / WiFi)..
If the starts allign and the matter module is installed in GMS and i try to link them, all the handshake and key exchanges work fine, but as soon as the home app tries to read the base information cluster from the matter device the matter module in GMS just crashes as it tries to access a library function in a native library which doesn´t exist, thereby hard killing the gms process / the matter module..

So even if you get it to install / keep it installed, you won´t be able to pair a device sucessfully, at least not a standard compliant one :D... It´s so broken 😞