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

[1.2] IOS-Google Home Connect failed #33923

Closed
kagami555 opened this issue Jun 14, 2024 · 1 comment
Closed

[1.2] IOS-Google Home Connect failed #33923

kagami555 opened this issue Jun 14, 2024 · 1 comment
Labels

Comments

@kagami555
Copy link

Reproduction steps

1.Built chip-lighting-app in linux using command : ./scripts/examples/gn_build_example.sh examples/lighting-app/linux out/ax 'target_cpu="arm" target_os="linux"'
2.Brought up DUT using commnad : ./chip-lighting-app --ble-device 0 --wifi
3.When I use the Google Home software on the iOS platform to add a device, it shows that the device cannot be added.

I checked the device log and saw that it has been successfully connected to the Internet and communicated via UDP. However, after receiving the message ClusterId = 0x3c, CommandId = 0x2, it shows Received command to close commissioning window. What is the problem? This device can be paired normally through other methods, including Android Google Home and iOS HomeKit.

Android_Google.log is the device log of Google Home connected to Android platform
IOS_Google.log is the device log of Google Home connected to IOS platform
IOS_Homekit.log is the device log of HomeKit connected to IOS platform
matter.sh.txt is the startup script of chip-lighting-app
Android_Google.log
IOS_Google.log
IOS_Homekit.log
matter.sh.txt

Bug prevalence

Always

GitHub hash of the SDK that was being used

437c574

Platform

other

Platform Version(s)

1.2

Type

Platform Issue

Anything else?

No response

@kagami555 kagami555 added bug Something isn't working needs triage labels Jun 14, 2024
@bzbarsky-apple
Copy link
Contributor

bzbarsky-apple commented Jun 14, 2024

@kagami555 This sounds like an issue you should report to Google through their bug reporting channels, not a bug in the Matter SDK.

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

No branches or pull requests

2 participants