State query utterances like "Is [toggleName] on?" not triggering ReportState for Alexa.ToggleController

[zhhinternet]

Issue Description

When using Alexa.ToggleController with retrievable: true and properly configured capabilityResources.friendlyNames, user utterances of the form:

• "Alexa, is oscillation off on living room fan?"

do not consistently trigger a ReportState directive to the skill endpoint. In many cases, Alexa responds with:

"From tumblr.com: Although it is called oscillating, its oscillating mode can be turned off allowing the fresh breeze to rotate to other parts of the room, thereby cooling them down.Its high features include, having remote control, sleep timer and LCD display."

However, control utterances like:

• "Turn on oscillation on living room fan"

work reliably and correctly invoke TurnOn/TurnOff directives.

Expected Behavior

According to the Alexa.ToggleController documentation, when retrievable: true is set, the skill should support state reporting. Therefore, natural language state queries using the configured friendlyNames (e.g., "oscillation", "swing") should trigger a ReportState request so the skill can respond with the current toggleState.

Actual Behavior

• ReportState is not sent for state-query utterances involving ToggleController instances.
• No error is logged; the request simply never reaches the skill endpoint.
• This behavior is inconsistent with core interfaces like PowerController (e.g., "Is the light on?" works reliably).

Steps to Reproduce

1. Implement a Smart Home Skill with a device that includes:

   {
     "interface": "Alexa.ToggleController",
     "instance": "Fan.Oscillation",
     "properties": {
       "supported": [{"name": "toggleState"}],
       "retrievable": true,
       "proactivelyReported": true
     },
     "capabilityResources": {
       "friendlyNames": [
         {"value": {"text": "Oscillation", "locale": "en-US"}, "@type": "text"},
         {"value": {"text": "Swing", "locale": "en-US"}, "@type": "text"}
       ]
     }
   }