KNX Integration - Cover: Is traveling_time_up/down really used?

[farmio (Matthias Alphart)]

@lutz85

Now it doesn’t need the travelling times anymore, right?

Your points 1 and 2 are correct. When you have a position address set up the times are still used to calculate intermediate positions.

Best practice is to configure everything you know about your cover. It may vary slightly on different manufacturers actuator implementations but generally it will try to do the right thing given any valid configuration.

[experience404]

Hi @farmio, hi @ll,

I’ve read the thread and it might be already solved for others. Its more like two short question to be sure (I have MDT as well):

→ travelling_time_up/down will be ignored or not used if actuator provides the values?

I have configured them in HA as test case with 5 seconds each, but HA still uses the 23 secs configured in MDT actuator. Playing around with different values for up/down doesn’t changed the behavior, only MDT actuator values in ETS had an effect. So I’ve removed them from yaml, might this result in problems?

→ does HA try to write the calculated “position value” to the position_address?

If yes, who will win? HA or MDT actuator who’s also using it? Or will it be ignored from HA, cause actuator is using it?

Imo I should just use the integration without the traveling times, cause it looks like they aren’t used. (Version of actuator, ETS, HA, etc. is latest possible).

Thx a lot for your help

[farmio (Matthias Alphart)]

@experience404

does HA try to write the calculated “position value” to the position_address?

No. It is only written when you set a different target value.

@experience404

Imo I should just use the integration without the traveling times, cause it looks like they aren’t used.

KNX Integration - Cover: Is traveling_time_up/down really used?

Great. Travel time is not “unused”. It will always fall back to a default of 25 if not configured.

[experience404]

If this would be correct with the 25 seconds, I would assume, that my 55 seconds KNX time for a specific cover should stop after 25 seconds, if travelling_time_ values aren’t configured, like they are at the moment (not configured).

But the cover closes as expected over HA without these values. Don’t get me wrong, I like it, but I wanna understand it.

If I tell HA to use it 5/5 seconds for up and down it ignores it. Only KNX values will be used. Is this correct or am I doing something “wrong”?

[farmio (Matthias Alphart)]

You said, you read the thread it is explained here.

KNX Integration - Cover: Is traveling_time_up/down really used?

Hi ! Yes, it’s really used for KNX. On movement the position is updated every second (I think) based on the configured time. However a received position state value has precedence and the calculation is restarted from that value. So when your actuators report wrong position states it will show wrongly in the HA entity too. HomeKit has nothing to do with it - this is just the forwarded HA entity you see there.

So whenever a new position state is received, time based calculations are discarded / reset.

[experience404]

How a tiny little word (precedence) can be overlooked more than once …

Thx for the quick response and explanation. It works as expected for me without the time lines in yaml. Still great to have them in case you don’t have an actuator with this feature.