06-12-2025 01:29 AM
We use the voice command "Set the [lightName] to 5000 kelvins" to set the color temperature of our lights.
However, Google Assistant responds with:
"Alright, I changed the [lightName] to daylight",
which is not the expected result.
We’ve tested this command on different phones. When using the same voice command on iOS devices, the response is:
"Got it, changing the [lightName] to 5000 kelvins",
and the color temperature is set correctly.
On some Android phones, however, the command doesn't behave as expected, and the response remains "changed to daylight", without applying the exact color temperature we specified.
Question:
Does the behavior of voice commands vary depending on the operating system (iOS vs Android)?
Is this a known compatibility issue, and how can we resolve it to ensure consistent execution of color temperature settings across all devices?
Thank you.
Answered! Go to the Recommended Answer.
06-12-2025 11:30 AM - edited 06-12-2025 11:30 AM
This appears to be a platform-specific inconsistency. Google Assistant on iOS interprets the command more precisely, while Android seems to map "5000 kelvins" to a general preset like "daylight" without applying the exact value. This could be due to differences in how each OS handles Assistant intents or interprets color temperature APIs. For now, try using alternate phrasing like "set [lightName] to cool white" on Android to see if results vary.
If the issue is still there, file a bug on public Issue Tracker and share the bug ID here. So that we can monitor the bug.
06-12-2025 11:30 AM - edited 06-12-2025 11:30 AM
This appears to be a platform-specific inconsistency. Google Assistant on iOS interprets the command more precisely, while Android seems to map "5000 kelvins" to a general preset like "daylight" without applying the exact value. This could be due to differences in how each OS handles Assistant intents or interprets color temperature APIs. For now, try using alternate phrasing like "set [lightName] to cool white" on Android to see if results vary.
If the issue is still there, file a bug on public Issue Tracker and share the bug ID here. So that we can monitor the bug.