Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Somfy Cover regularly get their state stuck as opening/closing, preventing controling them from HA #121423

Open
JiDW opened this issue Jul 7, 2024 · 3 comments
Assignees

Comments

@JiDW
Copy link

JiDW commented Jul 7, 2024

The problem

Hello,

I have multiple Somfy Covers (IO) controlled by a DIN box and linked to HA with the cloud bridge. It's been running for 7 months, and this issue has always been here, but I feel like it has become more frequent recently.

They randomly but frequently get stuck in a "closing" or "opening" state in HA, which disables the UI controls (grayed up/down arrows).
I can perfectly control them from the Tahoma app.

image

Strangely, their state is often correctly reported in Tahoma (closed/opened) but sometimes also stuck in the Tahoma app. I don't know if that's a Tahoma issue or if it's because I usually only control them from HA. Nevertheless, even if their state is not correctly reported in Tahoma, the "Open" and "Close" commands still work perfectly in the app.

Using the "stop" button in HA does nothing, and I can only regain control after a HA reboot.
Controlling them from Tahoma does not change the state, but it can give me control back sometimes, but only in one direction:

  • If the cover was stuck in a "closing" state, controlling it from Tahoma gives me back the ability to open the cover
  • If the cover was stuck in an "opening" state, controlling it from Tahoma gives me back the ability to close the cover

The DIN box is using the latest firmware.

Let me know if I can provide more details or do some tests.
Thanks!

What version of Home Assistant Core has the issue?

core-2024.6.4

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

config_entry-overkiz-db3dcbe578223e9dc46747126ae3db89.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

home-assistant bot commented Jul 7, 2024

Hey there @iMicknl, @vlebourl, @tetienne, @nyroDev, @Tronix117, 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)

@Anlumet

This comment was marked as off-topic.

@Anlumet

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants