I have the problem that I like to build a binary_sensor which checks an upcoming event (tomorrow) of a CalDAV calendar. To do so I created the following sensor: urlaub_marco_tomorrow: friendly_name: "Urlaub Marco (morgen)" value_template: >- {% if now().timestamp() >= as_tim…

If you’re just trying to get back to the way it used to be, just add the zero. If you want to catch them, then add the if statements

The error explains how to fix it. You can read this thread for details about using default. [image] Updating Templates with the new default values in 2021.10.x Configuration I keep seeing the same question about the new default argument for the templating. T…

It seems I am to stupid to understand this. I really can’t find a way to solve my problem by reading your solution. Just to clarify: I am sure there is the solution. My problem is that I am really new in coding and right know I am searching for examples which could help me because the article itsel…

there’s examples in the article. Read it from top to bottom. Don’t skim.

[image] petro: Don’t skim. I did not. Am I blind?

OK, now I tried the following in template tool: {{ as_timestamp(state_attr('calendar.gemeinsam_urlaub_marco', 'start_time'), 0) }} As a result I get 0. Would it be an idea to use the value 0 in an elif clause?

One final question :wink: My “final solution” for my sensor is at follows: urlaub_marco_tomorrow: friendly_name: "Urlaub Marco (morgen)" value_template: >- {{ now().timestamp() >= as_timestamp(state_attr('calendar.gemeinsam_urlaub_marco', 'start_time'), now().timestamp() +…

Problems with a value template in a binary_sensor for future events

Configuration

petro (Petro) January 18, 2022, 4:19pm 2

The error explains how to fix it. You can read this thread for details about using default.