I use the time portion (has_time) of an input_datetime to input the desired delay between two events (sequentially heating parts of my cabin before arriving).
For a specific case, I’ve wanted to start heating one section of the cabin uncharacteristically early, so that the delay to the next step is more than 24 hours. It seems, however, that the has_time part of an input_datetime cannot hold a time exceeding 24 hours? I didn’t see anything about this in the documentation nor have I found any similar discussion here in the community.
Yeah, I get that time >24 hours could be seen as days, not time… It’s just that normally, the delays that I want are <24 hours, and then the has_time part of input_datetime is a very straight-forward way of implementing the input. So it’s just for this extraordinary case that I wanted >24 hours and ran into trouble. Just wanted to check that the 23:59 limit is in fact a limitation (and that it’s not just me fumbling it).
I’m using the input_datetime as input to a timer. The timer is started at each step. When the timer finishes, an automation is triggered to start the next step.
Yes, agreed, but I’m trying to make the input fool proof (since I’m the one operating the user interface, it’s needed…), so automatic validation is important. Without the validation, it’s just a matter of time before the cabin is cold on arrival, without the UI giving me a hint that that’s what’s going to happen…