13d6ebaabf
Avoid delaying automation/script startup to check if the blueprint folder exists automations and script both populate sample blueprints if none exist The check to see if the blueprint folder exists always had to create an executor job which would delay startup a bit if the executor was busy. Since we do not need the sample blueprints to be populated until the start event, we can run this in a task. |
||
|---|---|---|
| .. | ||
| blueprints | ||
| __init__.py | ||
| config.py | ||
| const.py | ||
| helpers.py | ||
| icons.json | ||
| logbook.py | ||
| manifest.json | ||
| reproduce_state.py | ||
| services.yaml | ||
| strings.json | ||
| trace.py | ||