home-assistant/core

Somfy covers do not open/close but get status and identify

Opened this issue · 2 comments

limbas commented

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

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)

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