Luminance Level as Condition for Sensor Lights

[123 (Taras)]

@c0ntax

both true again

Make the modification I suggested in my previous post. We need to see the actual value of sensor.kitchen_light_level in the trace so we can understand why the automation’s Template Condition considers it to be less than 6.

BTW, you overlooked to post a screenshot of sensor.kitchen_light_level that I had requested (the one you posted doesn’t show the entity’s entity_id only its friendly name) so I am assuming it is the correct name of an existing entity in your system. Because if it’s misspelled (i.e. doesn’t exist) then that would explain why the Template Condition always reports true.

[c0ntax (Martin)]

@123

  - variables:
      light_level: "{{ states('sensor.kitchen_light_level') }}"
  - service: script.kitchen_bright

Got this:

[123 (Taras)]

Step forward to the next node in the flowchart (because the one in the screenshot isn’t showing the variables we want).

[c0ntax (Martin)]

@123

BTW, you overlooked to post a screenshot of sensor.kitchen_light_level that I had requested (the one you posted doesn’t show the entity’s entity_id only its friendly name) so I am assuming it is the correct name of an existing entity in your system. Because if it’s misspelled (i.e. doesn’t exist) then that would explain why the Template Condition always reports true.

You may have hit the nail on the head here. I’ve misnamed my sensor entity in the automation. It should be sensor.kitchen_sensor_light_level (sorry, can’t figure out how to add code quotes on the iPad as it doesn’t have back quotes)

I’ll make the changes and retest.

[123 (Taras)]

@c0ntax

I’ve misnamed my sensor entity in the automation

As I explained above, that’s one of the reasons that can cause the Template Condition to report true.

If sensor.misspelled doesn’t exist:
states('sensor.misspelled') reports unknown
states('sensor.misspelled') | float(0) reports 0
states('sensor.misspelled') | float(0) < 6 reports true

[c0ntax (Martin)]

I’ve made the amendments and the variable, after 3 tests each time is showing light_level: unknown:

[123 (Taras)]

Post the automation’s YAML code.

In addition, post a screenshot of the sensor entity as it appears in Developer Tools > States like this:

[c0ntax (Martin)]

I hadn’t renamed the entity in the state variable template but done that now and instead of ‘unknown’ it’s showing 0, so…progress.

It just triggered as expected, with a light level of 3, however, I’m finding it difficult to test now with no daylight. I will retest tomorrow and see how it goes.

Thank you for your help and time. I’ve definitely learned a lot tonight so hopefully this will work tomorrow.

[123 (Taras)]

@c0ntax

I hadn’t renamed the entity in the state variable template but done that now

I suspected that but didn’t want to second guess you (again) because earlier you said:

I’ve made the amendments and the variable

Anyway, the main mistake was supplying the template with a non-existent entity (like I explained several posts ago: “… or the specified sensor entity doesn’t exist”). The addition of the variable was just to confirm it and now it’s no longer needed given that the correct entity_id has been specified. I’m confident it will work properly tomorrow when you test it during daylight hours.

[c0ntax (Martin)]

So, I’ve had chance to play about testing now that there is natural light going into the room and have managed to successfully get the automation working in various rooms.

Thank you for your help and time, it’s much appreciated.

One last question though, can the below be put in template form? If so what would the template format be?

    - condition: time
      after: '23:00:00'
      before: '06:00:00'

[123 (Taras)]

@c0ntax

Thank you for your help and time,

You’re welcome!

Before you go, please consider marking my post above with the Solution tag. It will automatically place a check-mark next to the topic’s title which signals to other users that this topic has been resolved. This helps users find answers to similar questions.
For more information, refer to guideline 21 in the FAQ.

---

@c0ntax

can the below be put in template form?

Like this:

    - condition: template 
      value_template: "{{ now().hour < 6 or now().hour == 23 }}"

Or in shorthand notation:

    - "{{ now().hour < 6 or now().hour == 23 }}"

Yet another way:

    - "{{ now().hour in [0, 1, 2, 3, 4, 5, 23] }}"

---

EDIT

Correction. The before: '06:00:00' option means the current hour must be 5 or less, not 6. I have corrected the suggested templates.

[c0ntax (Martin)]

@123

- "{{ now().hour <= 6 or now().hour == 23 }}"

That’s great, I’ll use that. Again, thank you.

[c0ntax (Martin)]

@123

Correction. The before: '06:00:00' option means the current hour must be 5 or less, not 6. I have corrected the suggested templates.

Thanks. Can I just confirm, the or in the template below is correct as opposed to and?

- "{{ now().hour < 6 or now().hour == 23 }}"

[123 (Taras)]

The or is correct. The template is checking if the current hour is less than 6 or equal to 23. The value cannot be a number less than 6 and equal to 23.