Automation created using a blueprint not showing up in UI after creating

thewellington · September 2, 2021, 8:55pm

Oh… look at this:

Logger: homeassistant.components.automation
Source: components/automation/__init__.py:632 
Integration: Automation (documentation, issues) 
First occurred: 10:55:02 AM (20 occurrences) 
Last logged: 1:12:29 PM

Blueprint Lava Lamp Timer generated invalid automation with inputs OrderedDict([('target_light', OrderedDict([('entity_id', 'light.lava_lamps')]))]): not a valid value for dictionary value @ data['action'][0]['entity_id']. Got None

Now to figure out what valid dictionary it wants

skepticAut0netic · March 12, 2022, 3:12pm

I too have the same issue with Home Assistant core-2022.3.3, supervisor-2022.03.3, HA OS 7.4

If the blueprint based automation is saved from the web form based UI it doesn’t show up in the automatons UI but if the automation is saved from the edit in YAML UI it shows up in automation UI.

In both case it gets saved in the automations.yaml file but in the former case it gets saved with the default title as the blueprint itself.

Does these file permissions look right for blueprints?