You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a VPN is configured on the user’s device, the commissioning process fails consistently (100% of the time).
During the commissioning process, the screen displays “Checking network connectivity to .” After a few minutes, the message “Can’t reach device” is shown.
Root Cause (Suspected):
The issue seems to occur after the Bluetooth-based data exchange phase. Once this phase is completed, the commissioning process appears unable to communicate with the Matter device over the local area network (LAN).
Additional Context:
The LAN itself should be accessible. For instance, I can still successfully communicate with my Thread Border Router, which suggests the issue is specific to how the communication is managed by the Google Home Mobile SDK and/or connectedhomeip library used by it.
The text was updated successfully, but these errors were encountered:
Issue Description:
When a VPN is configured on the user’s device, the commissioning process fails consistently (100% of the time).
During the commissioning process, the screen displays “Checking network connectivity to .” After a few minutes, the message “Can’t reach device” is shown.
Root Cause (Suspected):
The issue seems to occur after the Bluetooth-based data exchange phase. Once this phase is completed, the commissioning process appears unable to communicate with the Matter device over the local area network (LAN).
Additional Context:
The LAN itself should be accessible. For instance, I can still successfully communicate with my Thread Border Router, which suggests the issue is specific to how the communication is managed by the Google Home Mobile SDK and/or connectedhomeip library used by it.
The text was updated successfully, but these errors were encountered: