feature request - delay start/stop (compute the percentages separately for 3 zones)

[nagyrobi]

feature request - delay start/stop (compute the percentages separately for 3 zones)

[nagyrobi]

Fully agree with you.

Unfortunately it's not me who wrote the timing part of the component, and as far as I understand, it's relying on other (knx) components built-in Home Assistant.

Maybe somebody can take the time to rewrite that part.

[JeroLajHub]

Firstly thanks for the superb custom component.

I was about to pull a similar request so I support this one above.

To be sure it is the same, let me explain my purpose :

• I have roller shutters.
• When the bottom-slat of it just reaches the bottom of the windows while closing, there is still gaps between the slats letting the light enter through the shutter ; the motor continues to roll down 2 sec more until all the gaps are closed and the slats reach their lower positions.
• Reversely, when opening is asked from the totally closed shutter, 2 sec are needed to opening the gaps between slats, and only after the shutter (the bottom-slat) begins to move up.
• Taking into account such a non-linear move would be a very refined improvement of the custom component !

I guess I can do it without asking you anything.

• I should be able to make it outside of the component with an automation to monitor the move when reaching the below, with your "set_known_position" option for adjustment, but it would be heavy and inelegant, wouldn' it ?
• May be I could do it at the scrypt.yaml level but I have no guess how to do it right now.

That would me so much more elegant and beneficial to everybody if done inside your custom component.

As I may not be aware of the constraints in the code of such a great custom component, I think of several different ways to implement it, should one skirt the constraints :

• as a first option, I thought of a non-linear implementation as @Flopescu has suggested... but your reply tells us it is outside your reach (xknx) - I stilll wonder if an intermediate non-linear function would do the trick (between position shown to end-user and position for xknx move).
• As a second option, I wonder if you would be able to implement a negative position in your CC but only show from 0 to 100 positions : with adding a parameter such as "no_move_delay" of eg. 3 sec while "traveling_time_up" of eg. 30 sec, positions would go from -10 to 100 in 33 sec but you would enter xknx only after 3s and with 0 position (compliant with xknx ?).
• As a third option, I noticed that may be 0 and 100 position were special because asking to go respectively down and up with no stop command at an assumed time needed for reaching the position (the shutter stops itself at the end) ; may be you can implement that opening during the first 3 sec "set_know_position" to 1 ; "traveling_time_up" and "traveling_time_down" would be the delays used between 1 and 99 in the coding.

I am trying to help but I am only at the conceptual level. I will be pleased to help anyhow... but I have never coded. One time or another I should have a look at your code files to dig deeper about it.

[nagyrobi]

Nice concepts.

[JeroLajHub]

Nice concepts.

Thanks, I would be happy to let you find a way 😃

[nagyrobi]

Me too, be my guest. ;)

[JeroLajHub]

Me too, be my guest. ;)

I may try looking at your code the next week-end. It would be a first for me !