cancel
Showing results for 
Search instead for 
Did you mean: 

EXECUTE(OnOff=false) is not received when user issues “turn off” command for humidifier device

MaxMei
Community Member

 

Hello Google Smart Home Support,

We are encountering an issue with a humidifier device integrated through Smart Home. The device supports the OnOff trait and correctly reports its on/off status through QUERY. Users can turn the device on, and can also adjust fan speed, mode, and toggles without any problem. All these EXECUTE commands reach our backend normally.

However, when the user issues the command “Turn off <device>”, our server does not receive any EXECUTE request containing "on": false. Moreover, Google Assistant responds with “I do not know how to do that”, which is unexpected.

Below are the relevant details. User-related identifiers have been masked for privacy.


1. SYNC payload (abridged)

{
"agentUserId": "MASKED_USER_ID",
"payload": {
"devices": [
{
"id": "MASKED_DEVICE_ID",
"type": "action.devices.types.HUMIDIFIER",
"traits": [
"action.devices.traits.HumiditySetting",
"action.devices.traits.OnOff",
"action.devices.traits.FanSpeed",
"action.devices.traits.Modes",
"action.devices.traits.Toggles"
],
"willReportState": true,
"name": { "name": "Humidifier" },
"roomHint": "living room",
"attributes": {
"availableFanSpeeds": { "ordered": true, "speeds": [ ... ] },
"availableModes": [
{
"name": "Mode",
"ordered": true,
"settings": [ ... ]
}
],
"availableToggles": [ ... ],
"humiditySetpointRange": { "minPercent": 30, "maxPercent": 90 },
"commandOnlyFanSpeed": true
},
"deviceInfo": {
"manufacturer": "smart-home-inc",
"model": "iot",
"swVersion": "1.0.1"
}
}
]
},
"requestId": "14938024066259619326"
}

2. QUERY response (abridged)

{
"agentUserId": "MASKED_USER_ID",
"payload": {
"devices": {
"MASKED_DEVICE_ID": {
"online": true,
"on": false,
"currentFanSpeedSetting": "two",
"currentModeSettings": { "Mode": "Auto" },
"humiditySetpointPercent": 40,
"humidityAmbientPercent": 38,
"currentToggleSettings": { "Ambient_Light": true }
}
}
},
"requestId": "8235970864254045430"
}

The device correctly reports "on": true and "on": false, so QUERY logic appears to work normally.


3. Steps to reproduce

  1. User says: “Turn off <Humidifier>”

  2. Google Assistant responds: “I do not know how to do that”

  3. No EXECUTE request with {"on": false} is delivered to our endpoint

  4. Other EXECUTE commands (On, FanSpeed, Mode, Toggle) are delivered normally

  5. The issue currently occurs only with this specific humidifier model; other devices with OnOff trait do not show the same behavior


4. Assistance requested

We would appreciate help checking the following:

  • Whether Google successfully generated an EXECUTE(OnOff=false) for the “turn off” command

  • If it was generated, whether it was routed correctly

  • If it was not generated, whether NLU or intent parsing may have prevented the OnOff=false command

  • We can provide full logs, timestamps, or other identifiers if needed

Thank you for your support.

Best regards,
Max Mei
Dreo IoT Team

1 Recommended Answer

arm_dpe
Solutions Expert
Solutions Expert

Thank you for reaching out and submitting your issue report. We have successfully received your ticket and confirmed it is in our system. Our team will review the details and provide an update to you as soon as possible.

Please note: To ensure timely processing and to prevent automated system flags, kindly avoid sending duplicate reports for the same issue. Duplicate submissions may lead to the unintended deletion of your ticket due to spam filtering.

We appreciate your patience while we investigate this.

View Recommended Answer in original post

2 REPLIES 2

MaxMei
Community Member

I submitted multiple Issue Tracker tickets (IDs: 468061900, 468061902) successfully, but I cannot access them due to permission restrictions. Since I don’t have access, I’m posting here on the community forum to follow up. Has anyone else experienced this behavior with the new interface?

arm_dpe
Solutions Expert
Solutions Expert

Thank you for reaching out and submitting your issue report. We have successfully received your ticket and confirmed it is in our system. Our team will review the details and provide an update to you as soon as possible.

Please note: To ensure timely processing and to prevent automated system flags, kindly avoid sending duplicate reports for the same issue. Duplicate submissions may lead to the unintended deletion of your ticket due to spam filtering.

We appreciate your patience while we investigate this.