I'm developing a Smart Home action for Actions on Google. I have two Smart Home actions with draft status. Each action returns an idencial SYNC response that includes a thermostat device, as shown below.
{
"payload": {
"agentUserId": "1234",
"devices": [
{
"id": "my-test-device-id",
"type": "action.devices.types.THERMOSTAT",
"deviceInfo": {
"model": "L",
"manufacturer": "L",
"hwVersion": "1.0.0",
"swVersion": "2.0.0"
},
"traits": [
"action.devices.traits.TemperatureSetting"
],
"willReportState": false,
"name": {
"name": "My AC"
},
"attributes": {
"thermostatTemperatureUnit": "C",
"availableThermostatModes": [
"off",
"heat",
"cool",
"on"
]
}
}
]
},
"requestId": "1695631778966374749"
}
When I link these actions in Google Home app on Google Pixel 3 (Android 11), thermostat's touch control is available for one action, but not the other. When touch control is unavailable, the thermostat receives a gear icon. When I press that icon, "Device settings" screen appears and I cannot change the temperature. What could be the cause of this difference?
Tested on Google Pixel 3 (Android 11)
I have come to the conclusion that my Google project ID is receiving special treatment from Google to disable thermostat touch control in my smart home action.
Specifically, if the project ID is prefixed with nature-remo-smart-home
then thermostat touch control is not available. However, If I create a new project with a different prefix, touch control is available.