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

Cover not fully opening (DRBL) #1552

Closed
7 of 12 tasks
JonasWirz opened this issue May 10, 2024 · 8 comments
Closed
7 of 12 tasks

Cover not fully opening (DRBL) #1552

JonasWirz opened this issue May 10, 2024 · 8 comments

Comments

@JonasWirz
Copy link

I agree to the following

  • I have read the documentation right now
  • I have read the FAQs right now
  • I am aware of the latest release notes
  • I am aware that an integration that was installed via HACS also needs to be updated via HACS
  • The Backend (CCU/Homegear/...) is working as expected, devices are taught in and are controllable by its own UI.
  • I am running the latest version of the custom_component (and Home Assistant)

The problem

After updating to 1.6.1.0, my covers are only opening up to 99% when opening them via HomeAssistant Dashboard.
They first fully open to 100%. After a few seconds, they are moving again and stop at 99%.

Before updating, everything worked fine.

What version of HomematicIP (local) has the issue?

1.6.1.0

What was the last working version of HomematicIP (local)?

No response

What type of installation are you running?

Home Assistant OS

What type of installation are you running for your homematic backend?

CCU3

Which version of your homematic backend are you running?

No response

What hardware are you running for your system?

No response

Which config details do you use

  • TLS
  • callback data (see)

Which interfaces do you use?

  • Homematic IP
  • Homematic (Bidcos-RF)
  • Groups (Heating-Group)
  • BidCos-Wired (HM-Wired)

Diagnostics information (no logs here)

No response

Log file extract. Anything in the logs that might be useful for us? The log (Setting/System/Logs -> load full log) is the best source to support trouble shooting!

No response

Additional information

No response

@SukramJ
Copy link
Owner

SukramJ commented May 10, 2024

We only send one command for covers, so why do you think it’s an issue of this integration.
Or are you using blinds?

@JonasWirz
Copy link
Author

JonasWirz commented May 10, 2024

Sorry. I am using blinds ;).
I think it has something to do with the "slap position" as well. After opening the blind via HA, the blind has a slat position of 50% configured in HomeMatic.
When I open the blind directly in HomeMatic, the slat position is 100%.

@SukramJ
Copy link
Owner

SukramJ commented May 10, 2024

That is menitioned in the release notes of 1.60.0:

Set open tilt level to 50%

@JonasWirz
Copy link
Author

I saw the release notes of 1.60.0.
But this causes problems in my case. If I press "open" in Homeassistant, the blind opens (I think it receives the command 100% open). Afterwards, it receives the command for 50% slat position and goes to position 99% and 50% slat position, because I think that 100% open at 50% slat position is an invalid state (if the blind is fully open, it can not have a slat position).
Why was an open tilt level of 50% chosen?

@SukramJ
Copy link
Owner

SukramJ commented May 10, 2024

It was requested by blind users in the past.

@SukramJ
Copy link
Owner

SukramJ commented May 10, 2024

I think this is not an issue with this integration.
If you want to change the tilt default to a new value you should start a discussion in this repository.
I personally don‘t use blinds or covers.

@SukramJ SukramJ closed this as not planned Won't fix, can't repro, duplicate, stale May 10, 2024
@JonasWirz
Copy link
Author

Thank you!

I think the problem lies within the order of the commands as they are sent to the Homematic upon combined tilt/position command.
In cover.py starting from line 109, there is the service definition. First, the position command is sent. Afterwards, the tilt command is sent. This way, the position of 100% is overwritten by the HomeMatic system due to the wrong tilt value. However, if you press "open" in HomeAssistant, a position of 100% is sent, which is never reached because of the tilt value.

@SukramJ
Copy link
Owner

SukramJ commented May 10, 2024

No, if you use the service cover combined position, then only on combined parameter is send.
Same with the cover open/close command.

@github-actions github-actions bot locked and limited conversation to collaborators May 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants