Devices Not Showing in Google Home After Successful App Linking

chris63 — Wed, 29 Oct 2025 09:52:51 GMT

Hello,
Our customer reported an issue: the Google Home app successfully linked our application, and the backend returned the correct SYNC response. However, users report that no devices appear in Google Home.

Below is the SYNC response we returned (fields are included according to Google’s official requirements):

{

"payload": {

"agentUserId": "bd053de2b76f4c49a598492defc1f47e",

"devices": [{

"traits": ["action.devices.traits.ColorSetting", "action.devices.traits.Brightness", "action.devices.traits.OnOff"],

"otherDeviceIds": [{

"deviceId": "deb47c16a48342919c9208d9d9443f89"

}],

"roomHint": "My Home",

"customData": {

"userUuid": "bd053de2b76f4c49a598492defc1f47e",

"proxy": false,

"aesKey": "If93Qlb31orcBvAX",

"devicePassword": "3f7Z9gG4VZLF"

"type": "action.devices.types.LIGHT",

"deviceInfo": {

"swVersion": "3.15.05",

"model": "LK.light.A001497",

"hwVersion": "3.15.05",

"manufacturer": "AiDot"

"matterOriginalVendorId": "0x1168",

"matterOriginalProductId": "0x03e8",

"willReportState": true,

"name": {

"name": "New living room lamp"

"matterUniqueId": "deb47c16a48342919c9208d9d9443f89",

"attributes": {

"colorTemperatureRange": {

"temperatureMinK": 1800,

"temperatureMaxK": 6500

"colorModel": "hsv",

"commandOnlyColorSetting": false

"id": "deb47c16a48342919c9208d9d9443f89"

... (other devices remain the same)

]

"requestId": "1634066730132906003"

}

We have included all required fields according to Google’s guidelines, but the devices still do not appear in Google Home. Could you advise on what might be causing this issue and how to resolve it?

Thank you in advance!

Re: Devices Not Showing in Google Home After Successful App Linking

arm_dpe — Fri, 31 Oct 2025 17:01:31 GMT

Thanks for reaching out. The most probable causes relate to the way you've structured the device identifiers, especially concerning the Matter integration fields. In your device object, you are using the same value for three distinct ID fields: id, otherDeviceIds[].deviceId, and matterUniqueId. The core device ID (id) must be unique across all users and distinct from other identifiers:

id: This is the primary device ID used by Google's system to reference the device. It must be unique within your entire partner ecosystem.

In your response: "id": "deb47c16a48342919c9208d9d9443f89"

otherDeviceIds[].deviceId: This is an optional list for IDs used by your own platform, not Google's. It should typically be a different, internal ID, or it can be the same as the id if your internal ID is the same as the Google one, but it should not be the same as matterUniqueId.

In your response: "deviceId": "deb47c16a48342919c9208d9d9443f89"

matterUniqueId: This is the unique identifier for the Matter node (the pairing of a node ID and a fabric ID) and must be unique across all devices from your agent. It is strongly recommended that this be a different value from the primary id field, especially if you're mixing IDs used for traditional cloud-to-cloud and Matter integrations.

In your response: "matterUniqueId": "deb47c16a48342919c9208d9d9443f89"

Resolution: Change the primary id to be a globally unique ID for your device within the Google Home ecosystem. Ensure id, otherDeviceIds[].deviceId (if you keep it), and matterUniqueId are all different values to avoid ID conflicts, particularly if this device is intended to support both Cloud-to-cloud and Matter.

topic Devices Not Showing in Google Home After Successful App Linking in Smart Home Developer Forum

Devices Not Showing in Google Home After Successful App Linking

Re: Devices Not Showing in Google Home After Successful App Linking