10MEngThesis

1

colourcycletimed

Open your Home Assistant instance and show the blueprint import dialog with a specific blueprint pre-filled.


blueprint:
  name: Light Schedule, Every 15 minutes
  description: 'Turns light on for 15m, off for 15m, indefinately' 
  domain: automation
  input: 
    cl_light:
      name: Colour Loop Light
      description: 'Choose Light entity to Schedule'
      selector:
        target:
          entity:
            domain: light

variables:
  colors: |-
    {{ [[0.217,0.077], [0.157,0.05], [0.136,0.04], [0.137,0.065],
        [0.141,0.137], [0.146,0.238], [0.151,0.343], [0.157,0.457],
        [0.164,0.591], [0.17,0.703], [0.172,0.747], [0.199,0.724],
        [0.269,0.665], [0.36,0.588], [0.444,0.517], [0.527,0.447],
        [0.612,0.374], [0.677,0.319], [0.701,0.299], [0.667,0.284],
        [0.581,0.245], [0.477,0.196], [0.385,0.155], [0.301,0.116], 
        [0.217,0.077]] }}

trigger:
  - platform: time_pattern
    hours: '*'
    minutes: '*'
    seconds: '/5'

condition:
  condition: state
  entity: 
  state: "on"

action:
  - service: light.turn_on
    data_template:
      xy_color: '{{ colors[(now().second/2.5)|round(0)] }}'
      transition: 1
    target: !input cl_light

mode: single
2

Did you mean to post this publically?

3

Oh no, apologies, I’m using HA within my thesis and trying to test blueprints. Is it possible to post them privately, to ensure they work before posting publically? I’m new to home assistant and trying to keep up with the very steep learning curve!

4

No worries, you’re not the only one dealing with the learning curve!

you could send a direct message to yourself, or if you have a lot of code to keep track of, it might be worth creating a private GitHub repository and storing it there.

1 Like