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

Overkiz Core integration doesn't work as good as a custom component #66258

Closed
RafaZafra opened this issue Feb 10, 2022 · 10 comments
Closed

Overkiz Core integration doesn't work as good as a custom component #66258

RafaZafra opened this issue Feb 10, 2022 · 10 comments

Comments

@RafaZafra
Copy link

The problem

Overkiz Core Integration misses entities like "low speed" on shutters.

Rolling back to use Overkiz as a custom components, everything works fine.

What version of Home Assistant Core has the issue?

core-2022.2.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

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@mvdwetering
Copy link
Contributor

Not everything from the custom component version has been moved over to core yet. They are keeping track of the todo list in this ticket iMicknl/ha-tahoma#697

@probot-home-assistant
Copy link

overkiz documentation
overkiz source
(message by IssueLinks)

@probot-home-assistant
Copy link

Hey there @iMicknl, @vlebourl, @tetienne, 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!
(message by CodeOwnersMention)

@tetienne
Copy link
Contributor

tetienne commented Feb 12, 2022

Hi, we have not yet backport all the custom component. It's a work in progress.
See iMicknl/ha-tahoma#697
Meanwhile you can still use the custom component.

@tetienne
Copy link
Contributor

FYI I plan to change how we handle the low speed feature: iMicknl/ha-tahoma#763

@RafaZafra
Copy link
Author

Thank you all. You are doing an amazing work! @iMicknl @tetienne

@iMicknl
Copy link
Contributor

iMicknl commented Feb 24, 2022

@RafaZafra if you want to try this, you can test the beta of 2022.3.0. This will add your low speed cover again.

Could you try this and close this issue if it works?

@RafaZafra
Copy link
Author

Hi @iMicknl it works perfect, just as the custom component. Thank you! (beta core-2022.3.0b0)

Just for looping the loop (I don't really know if that expression exists in English too ;))... the low speed switch sets how the open/close action must be done, from start to end.
Meanwhile in my Somfy remote control, when I'm opening if I switch the low speed mode it applies inmediately to the current transition so I can vary the speed of the blind while it keeps moving.

Thanks again and let me know if you need me to test anything else,
Rafa

@iMicknl
Copy link
Contributor

iMicknl commented Feb 24, 2022

@RafaZafra I don't think we can implement that behavior, looking at the commands they expose. My belief would be that the remote will cancel the current execution and create a new execution using the low speed mode (and vice versa).

Can you close this issue? :). Feel free to create a new issue if other issues arise.

@RafaZafra
Copy link
Author

RafaZafra commented Feb 24, 2022

@iMicknl perfect!

I just commented in case you didn't know that functionality.

Thank you ever!

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

No branches or pull requests

5 participants