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

Few suggestions #4

Open
KernSani opened this issue Jun 27, 2024 · 0 comments
Open

Few suggestions #4

KernSani opened this issue Jun 27, 2024 · 0 comments

Comments

@KernSani
Copy link

Hi,
Thanks for your great work! I'm pretty new to home assistant (currently migrating from FHEM) and this integration is (almost) exactly what I was looking for to control my blinds. I just have a few points:

  1. I already have "cover" entities set up (through another integration) which support open/close/stop service, I just need the custom component for the traveltime calculation. Although I'm new to Python I was able to adjust your code to my needs, but probably that might be an interesting option for others as well (i.e. in the configuration flow you could ask for the type ("cover" or "boolean") and depending on that call different services.
  2. I have a few blinds which are inverted (i.e. up-command moves them down and vice versa), thus I added an "inverted" flag to the configuration flow to invert the commands sent to the cover entity
  3. The time my blinds travel through the visible area of the window differ from the total travel time. If they are open, they take approx. 2 seconds until they become visible, then they travel for e.g. 16 seconds and then the window is fully covered, however they continue for another 4 seconds until they are fully closed. So what I would need are attributes for top and bottom time. If a blind is fully open or closed it would first travel that time until the calculated time starts (i.e. if it's open and target is 50% it would first travel 2 seconds top time and then start the calculated time of 16 seconds * 50% = 8 seconds. I wasn't able to add that to the component myself...
  4. The select option for (up/down/tilt) entities in the configuration flow is basically unusable, if you have 1000s of entities. I restricted it to entities of type "cover", that makes it much easier, I have no idea if a "searchable" select box could be added there...

Thanks a lot,

Oli

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

No branches or pull requests

1 participant