Command execution for covers fails with execution state failed in Overkiz

[limbas]

The problem

All my Somfy covers and awnings can not opened/closed any more. I use the Somfy TaHoma Switch as gateway with enabled developer mode. The integration find all devices and the registration is successful. The current state and identify functions works well but the open/close/myposition functions doesn't work. There is no difference whether I integrate locally or over the cloud except the log.

Over the Tahoma App all devices can be controlled. (except for that annoying "manual mode" message)

Deviceinformation of the first device: Firmware: 5071665X10 Hardware: io:HorizontalAwningIOComponent

What version of Home Assistant Core has the issue?

core-2024.10.2

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz

Diagnostics information

2024-10-23 18:25:28.638 DEBUG (MainThread) [homeassistant.components.overkiz] Finished fetching device events data in 0.069 seconds (success: True)

######## cloud modus ########

 DEBUG (MainThread) [homeassistant.components.overkiz] Event(name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, timestamp=1729700830940, setupoid=_CountingAttr(counter=308, _default=None, repr=<function obfuscate_id at 0xffff6def0220>, eq=True, order=True, hash=None, init=True, on_setattr=None, alias=None, metadata={}), owner_key=XXXX, type=1, sub_type=1, time_to_next_state=-1, failed_commands=[{'device_url': 'io://XXXX', 'rank': 0, 'failure_type': 'PRIORITY_LOCK__USER'}], failure_type_code=<FailureType.PRIORITY_LOCK__USER: 168>, failure_type='PRIORITY_LOCK__USER', condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='XXXX', device_url=None, device_states=[], old_state=<ExecutionState.TRANSMITTED: 'TRANSMITTED'>, new_state=<ExecutionState.FAILED: 'FAILED'>)

######## local modus ########

 DEBUG (MainThread) [homeassistant.components.overkiz] Event(name=<EventName.EXECUTION_STATE_CHANGED: 'ExecutionStateChangedEvent'>, timestamp=None, setupoid=_CountingAttr(counter=308, _default=None, repr=<function obfuscate_id at 0xffff6def0220>, eq=True, order=True, hash=None, init=True, on_setattr=None, alias=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=[{'device_url': 'io://XXXX', 'rank': 0, 'failure_type': 'UNKNOWN_ERROR'}], failure_type_code=None, failure_type='UNKNOWN_ERROR', condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=None, exec_id='XXXX', device_url=None, device_states=[], old_state=<ExecutionState.INITIALIZED: 'INITIALIZED'>, new_state=<ExecutionState.FAILED: 'FAILED'>)

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @imicknl, @vlebourl, @tetienne, @nyrodev, @tronix117, @alexfp14, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `overkiz` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign overkiz` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

overkiz documentation overkiz source _{^{(message by IssueLinks)}}

[on4amg]

Same issue here with HA core 10.4...I reverted back to HA core 10.3 and now Overkiz is working again!

[talalalisnotavailable]

Same issue here. Reload hub fixes temporarily but at some point reverts to previous behaviour, at last attempt it stopped working after one successful action. Can see devices, click buttons, but no response. Error message: “ Failed to perform the action cover/open_cover. Cannot connect to host gateway-XXXX-XXXX-XXXX.local:XXXX ssl:<ssl.SSLContext object at 0xffff6bc6d150> [Invalid argument]”

Removed gateway code here but it’s correct.

update: it works sporadically. Error code sometimes, other times works.. on the same device too

[regda1986]

Same issue here with 2024.10.4 and OS 13.2...

[gacopl]

same here and issue persists in 11.0 and 11.1, 10.3 works fine. anything above i get tcp timeouts here and there some covers work some don't have to retry to open/close all of them morning/evening

[iMicknl]

Please don't just add same issue without anymore details, @on4amg, @talalalisnotavailable, @regda1986 and @gacopl. The original post is most likely a different issue and this makes it very hard to debug. Cannot connect issues are different to this issue, and cannot be resolved by the integration. This is an issue of the local API on the Somfy side.

@limbas what do you mean with "except for that annoying "manual mode" message"? Can you share a screenshot? Did this behavior occur at the same time as the issues with Overkiz? I don't think we add an override for the 'manual mode' and thus all commands will fail through Overkiz.

Can you perhaps contact Somfy support to see if they can remove the 'manual mode'?

[gacopl]

Dear Mick what part of downgrade to 10.3 resolves the issue you did not understand ? and how this would be local api issue if downgrading ha helps ? Blaming local api without details does not help either :)

On one thing you might be right that the main issue is probably not related sorry about that

[iMicknl]

@gacopl please create a new issue if you want to investigate your specific issue.