Weekday condition - Error message when variably declaring array

Configuration Blueprints
, ,
1

I’m trying to include a textfield in a blueprint that parses the input text to an array of days on which the blueprint should run.
The if loop in the below statement is throwing an error: Incorrect type: expected ‘array’

blueprint:
  input:
    schedule_days:
      name: Run on these days
      description: >
        Days on which the automation will run.
        Write days in short form (mon, tue, wed, thu, fri, sat, sun).
        Seperate days by comma's or spaces.
      selector:
        text:

variables:  
  days: !input schedule_days

condition:
  - condition: time
    after: !input schedule_start
    before: !input schedule_stop
    weekday: >
      {% if 'mon' in states(days) %}
        - mon
      {% endif %}

I’ve also tried it as follows, but the same error is thrown.

weekday: >
  {% set day_array = namespace(daylist=[]) %}
  {% if 'mon' in states(days) %}
    {% set day_array.daylist = day_array.daylist + [mon] %}
  {% endif %}
  {{ day_array.daylist }}
2

You should consider using split() to convert the comma-separated string to a list.

You supply split() with the delimiter to use for splitting the string. For example, this will use a comma as the delimiter split(',') and this uses a comma followed by a space split(', ').

Copy-paste this into the Template Editor and experiment with it:

{% set x = 'mon, wed, fri' %}
{{ x.split(', ') }}

Screenshot_20220321-095652~2
Screenshot_20220321-095652~21098×347 33.2 KB

The challenge you will face is that you have offered the user a choice of delimeters (commas or spaces) and split() doesn’t support multiple choices. Faced with this situation, you will have to use replace to normalize the string (such as replace spaces with commas and the replace double commas with a single comma) before splitting it.

3

… and replace double spaces with single spaces before the other replaces.
User inputs is horrible, the more options you give them the more creative they will be.

4

To simplify things, I suggest restricting the delimiter to a space character. It’s the default delimiter used by split() and it ignores consecutive space characters.

Screenshot_20220321-100403~2
Screenshot_20220321-100403~21137×344 33.4 KB

It’s fine for this application because each item (abbreviated day name) doesn’t contain a space.

5

ooohhhh… thats a nice feature

6

While this looks correct, and it beautifully simplifies the solution, it still throws the error:

Schermafbeelding 2022-03-21 om 15.11.34
Schermafbeelding 2022-03-21 om 15.11.34852×162 17.7 KB

It does so with and without parentheses, btw.
P.S.: variable ‘days’ was already declared earlier as seen in the original post.

7

The weekday option of a Time Condition doesn’t support a template.

1 Like
8

I don’t see that mentioned anywhere in the documentation though.

9

The documentation usually documents only what is possible (rarely what is not possible).

At this point, you will need to re-design it. Consider using a Template Condition to handle the weekdays.

1 Like
10

I still find it weird that it’s possible to use templating with other variables and not here, but anyway.
i’ve given up on this and have created a Template Condition that gives a rather elegant solution to the problem.

It solves the issue of the different separators as well. users can now use practically any combination of punctuation marks and spaces to separate the short form days.
It’s also very easily copied over to other blueprints, so I’ve created another post for the script.

User friendly way of adding a start & end time and weekdays to a blueprint

11

For future reference, you can’t use templates for entity_id in a State Trigger nor for above and below in a Numeric State Trigger.

1 Like
12

I’l keep that in mind, thanks!