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 provision ESP32-S3/C6 with Google Home on iOS (CON-1353) #1097

Open
AntoineSX opened this issue Sep 27, 2024 · 9 comments
Open

Unable to provision ESP32-S3/C6 with Google Home on iOS (CON-1353) #1097

AntoineSX opened this issue Sep 27, 2024 · 9 comments

Comments

@AntoineSX
Copy link

Describe the bug
When trying to add either an ESP32-C6 or ESP32-S3 as a Matter device in Google Home, I receive an error stating: "Unable to Add Accessory. Home couldn't connect to this accessory." The device successfully connects when provisioned with HomeKit on iOS, but not with Google Home on iOS. However, it works correctly when provisioned on Google Home using an Android device.

Environment

  • ESP-Matter Commit Id:
    Using esp_matter component version 1.3.0 which corresponds to this commit

  • ESP-IDF Commit Id:

  • ESP-IDF v5.2.2

  • SoC (eg: ESP32 or ESP32-C3):
    ESP32-C6 and ESP32-S3

  • Device Logs (Please attach the log file):
    logs-esp32s3.txt

  • Host Machine OS:
    Linux

  • Host Machine Python version:
    3.12

  • Commissioner app and versions if present:

  • Home hub app and versions if present:
    Google Home 3.23.102

  • Commissioner's logs if present:

Any additional details

  • I'm using an iPhone 15 Pro Max running on iOS 18.0, and I also tested on iOS 17.6.1.
  • I tested on two separate Wi-Fi networks and tried both Matter over OpenThread and Matter over Wi-Fi, but the issue persisted in all scenarios.
  • Same issue as this : Enable to add esp32c6 to Google home (CON-1228) #987
@github-actions github-actions bot changed the title Unable to provision ESP32-S3/C6 with Google Home on iOS Unable to provision ESP32-S3/C6 with Google Home on iOS (CON-1353) Sep 27, 2024
@sayondeep
Copy link
Contributor

@AntoineSX
I was able to recreate the issue. We are looking into it

@NomNom1992
Copy link

@sayondeep Hello, Im looking for this problem too. I try connect matter device by google home on IOS, and got same error. I tried that with a Tapo matter socket, running on a Realtek chip. It runs normally with the same test.

@mgoeller
Copy link

mgoeller commented Nov 15, 2024

Can we solve this please @sayondeep, @dhrishi, @chshu? I am experiencing this as well, and it is affecting the reputation of our devices sold! Please expedite this issue!

@9zigen
Copy link

9zigen commented Nov 15, 2024

I have the same issue.

@jzwyssig
Copy link

We are also experiencing this issue and it is significantly impacting our development process. A prompt resolution would be greatly appreciated. Please let us know if there's any additional information or testing needed from our side to assist in addressing this.

@thalesfsp
Copy link

3 months later and no answer...
cc: @sayondeep @dhrishi

@VaishaliAvhale
Copy link
Contributor

VaishaliAvhale commented Dec 16, 2024

@thalesfsp, I tried commissioning the ESP-Matter latest Thread and Wi-Fi light using ESP32-C6, and it was successfully commissioned and added to the iOS Google Home App.

Initially, when I attempted to commission the Thread light using the ESP32-C6, I encountered the same issue you mentioned. However, after retrying, it worked successfully.

Here are the details of my setup:

Google Home App Version: 3.26.103
Google Nest Hub (2nd Generation):
Fuchsia Version: 22.20240805.103.161
Software Version: 62.0.7.676990136

@thalesfsp
Copy link

So, it's. a matter of "keep retrying til it works". If this is a "solution", then close the issue. What else? Leave this ticket open for 9 years?

@shubhamdp
Copy link
Contributor

shubhamdp commented Dec 17, 2024

@thalesfsp Is this comment meant to be helpful, or are you just venting? What @VaishaliAvhale clearly mentioned is that she couldn’t reproduce the issue and has shared her setup details.

If you actually want this issue resolved, it would be more productive to provide useful information—such as reproduction steps, setup details, or logs—rather than speculative remarks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants