Rfxcom, somfy blinds and google openpercent errors

Ben_Barker · December 30, 2022, 11:52pm

I use the RFXComm plugin to control a number of somfy blinds. These blinds are simplex - I can tell them to go up, down, or stop, but can’t query their state.

I also sync these blinds with google home

When I ask google home to open/close them, the response is twofold:

Firstly, they do as requested, and open/close
Secondly, google assistant responds that “that mode is not supported”

Checking the logs, I can see:

`Error handling message {'inputs': [{'context': {'locale_country': 'GB', 'locale_language': 'en'}, 'intent': 'action.devices.EXECUTE', 'payload': {'commands': [{'devices': [{'customData': {'httpPort': 8123, 'uuid': '7a31224617cc4bb7ad92a83dc3d59bf6', 'webhookId': '0e7c5442293d51ca07f4add5204021e3059bd11c3dbae77a6a4dee9a42fe9e4d'}, 'id': 'cover.rfy_0000e8_0'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '00f38e7b450fc3d4722cbaf6668c4c6cb1898b31ffaaa9588442d775db074dbfdebd02bbc026d2dca5de369a330ee42fe91c8323c5eccbaea265cd9e06c5b9ab901e98c88128ca049d4ce1375f13d3a4a1ced57aa7b7', 'openPercent': 0}}]}, {'devices': [{'customData': {'httpPort': 8123, 'uuid': '7a31224617cc4bb7ad92a83dc3d59bf6', 'webhookId': '0e7c5442293d51ca07f4add5204021e3059bd11c3dbae77a6a4dee9a42fe9e4d'}, 'id': 'cover.velux_blind'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '00f38e7b45ae2c2742edf5fe931bf26e74d13a30898f87744d680800087490eda4e7180307881c83adcff5282c585b70f7e5a44dde0c36faaee0bd83a8d44940afcc46360c5fe548d856c2bc99bb24b4a81c0d54059a', 'openPercent': 0}}]}, {'devices': [{'customData': {'httpPort': 8123, 'uuid': '7a31224617cc4bb7ad92a83dc3d59bf6', 'webhookId': '0e7c5442293d51ca07f4add5204021e3059bd11c3dbae77a6a4dee9a42fe9e4d'}, 'id': 'cover.rfy_020606_0'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '00f38e7b45b782af3705786e102a23fc553a9003b95d91b458ffb75d4c8b3d5cb9f0b9f0e04111abd4b1ec31e49a078a4f84cfdfd97e4f1b990b684588f94b724b4ddb2077b93ab849fea966f8e877efc383091a4f8a', 'openPercent': 0}}]}, {'devices': [{'customData': {'httpPort': 8123, 'uuid': '7a31224617cc4bb7ad92a83dc3d59bf6', 'webhookId': '0e7c5442293d51ca07f4add5204021e3059bd11c3dbae77a6a4dee9a42fe9e4d'}, 'id': 'cover.rfy_0000fe_0'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '00f38e7b450bdb62f401c31e1491ebc4810f04257831a9a7f72cc0fb4d0f34c6d2e4d22559a7cf12e673fc94af01d01e9ac11ef56d31305d930126f8dda20b39523ecfddc90c0b636abf66a8f66694cb79d6a0c6b671', 'openPercent': 0}}]}, {'devices': [{'customData': {'httpPort': 8123, 'uuid': '7a31224617cc4bb7ad92a83dc3d59bf6', 'webhookId': '0e7c5442293d51ca07f4add5204021e3059bd11c3dbae77a6a4dee9a42fe9e4d'}, 'id': 'cover.rfy_0000ff_0'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'followUpToken': '00f38e7b4548412673f77ef02d72657294574bd0c9468b3bce96c43052223de60c40b3b90c5cb9ee0b7352696060863dc1bfc419de1d980feff733e1b058de7ec0ba346226289c5ee68771d1aa2778f71f1fdcc717b0', 'openPercent': 0}}]}]}}], 'requestId': '6421564048385402518'}: {'errorCode': 'notSupported'`}`

This suggests the error comes from a call to openPercent not being supported - which indeed it isn’t. But I’m not sure if the error here comes from HA reporting to google the devices have a capability they do not in fact have…?

It looks like this was discussed here:

github.com/home-assistant/core

Google assistant throws error when opening/closing cover in 0.92

opened 05:24PM - 26 Apr 19 UTC

closed 07:28AM - 28 Apr 19 UTC

wrosdfw4

**Home Assistant release with the issue:** 0.92.0 **Last working Home Assi…stant release (if known):** **Operating environment (Hass.io/Docker/Windows/etc.):** hass.io **Component/platform:** google_assistant **Description of problem:** As of 0.92, when I open or close a cover using Google Assistant it responds with "That mode isn't available for the Back Gate" and I get an error in the HA log (pasted below under traceback). I should note that the cover DOES open and close as expected through google, just with the errors from both Google and HA. This is with a stateless cover via ESPHome. **Problem-relevant `configuration.yaml` entries and (fill out even if it seems unimportant):** ```yaml ``` **Traceback (if applicable):** ``` Error handling message {'inputs': [{'context': {'locale_language': 'en'}, 'intent': 'action.devices.EXECUTE', 'payload': {'commands': [{'devices': [{'id': 'cover.back_gate'}], 'execution': [{'command': 'action.devices.commands.OpenClose', 'params': {'openPercent': 0}}]}]}}], 'requestId': '2573257550867487632'}: {'errorCode': 'notSupported'} ``` **Additional information:**

And may be a limitation of google home not handling stateless blinds…? However, the linked ticket:

github.com/home-assistant/core

Google Assistant: Return optimistic state when changing optimistic covers

home-assistant:dev ← home-assistant:google-ass-optimistic-cover

opened 06:19AM - 28 Apr 19 UTC

balloob

+84 -18

## Description: Google Assistant does not support querying state for optimistic… covers or covers with an unknown state. We were raising these errors too when querying the state after we got a command in, causing the command to succeed, but Google to report to the user a failure. With this PR, we will return the position as passed in by Google, so Google assumes the command worked. Since the state is optimistic or unknown, that's the best we can do. **Related issue (if applicable):** fixes #23226 ## Checklist: - [x] The code change is tested and works locally. - [x] Local tests pass with `tox`. **Your PR cannot be merged unless tests pass** - [x] There is no commented out code in this PR. If the code does not interact with devices: - [x] Tests have been added to verify that the new code works. [ex-manifest]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/mobile_app/manifest.json [ex-requir]: https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/mobile_app/manifest.json#L5 [manifest-docs]: https://developers.home-assistant.io/docs/en/development_checklist.html#_the-manifest-file_

Seems to suggest that this a should now work without an error if I can put the covers into “optimistic mode”

I created a customizations.yaml file, referenced from the main config.yaml, to give me:

cover.velux_blind:
device_class: blind
optimistic: true
cover.rfy_020606_0:
device_class: blind
optimistic: true
cover.rfy_0000e8_0:
device_class: blind
optimistic: true
cover.rfy_0000ff_0:
device_class: blind
optimistic: true
cover.rfy_0000fe_0:
device_class: blind
optimistic: true

However, whilst this parsed fine with no errors, any attempt to open or close blinds still does the same - so works, but also complains “that mode is not available for X”