My yaml blueprint remains not visible > path issue?

Configuration Blueprints
1

Hi,

I experiment with HA since about a year (considering myself newbie).
I get a Docker install of HA (Core 2024.4.4 | Frontend 20240404.2)

I created a ikea_e1744.yaml file located at
/home/[USER]/hass-config/blueprints/automation/homeassistant/
using

~$ sudo nano /home/[USER]/hass-config/blueprints/automation/homeassistant/ikea_e1744.yaml

and pasted there the some content.

I reloaded config using
Developper Tools > YAML > All Yaml Configuration
(Tried Developper Tools > YAML > Automations as well)

However the blueprint does not appear in the UI

I managed to import blueprints. They were visible in the UI but not at
~$ ls -l /home/[USER]/hass-config/blueprints/automation/homeassistant/

I suspect a linux path issue. How can I verify the default path for blueprints?

2

What install method are you using for HA. That’s not a path in the HAOS world.

3

Check the rights, and a restart of HA.

4

Hi @Sir_Goodenough

I have a Docker install more or less described here:

I am thinking of moving to HAOS as I did the Docker choice when I knew nothing about HA but I see now some drawbacks (Supervisor not available) > Do you know if I move to HAOS I can restore a backup from a Docker install without issue?

Your feedback will be much appreciated

5

Hi @francisp ,

I also think to look in this direction. But how can I check the rights of HA?
I looked everywhere into the UI.
Guessing this is a command line step?

Thanks for taking the time :pray:

6

Yes, you can

Yes

On HA OS, blueprints are stored in /config/blueprints/automation/homeassistant, where /config is the directory where configuration.yaml is.

7

I will definitely give it a try.

In the meantime, is there a way I can check the rights of this existing HA install through UI or command line?

8

sudo ls -l should do it

9

Here is what I get

~$ ls -l /home/[USER]/hass-config/blueprints/automation
total 4
drwxr-xr-x 2 root root 4096 May 19 16:46 homeassistant

~$ ls -l /home/[USER]/hass-config/blueprints/automation/homeassistant/
total 24
-rw-r--r-- 1 root root 15012 May 19 12:35 manual_ikea_e1744.yaml
-rw-r--r-- 1 root root  1442 Apr 12 13:25 motion_light.yaml
-rw-r--r-- 1 root root  1666 Apr 12 13:25 notify_leaving_zone.yaml

Does that explain the issue? (not really familiar with linux rights :pray:)

10

They are all owned by root, so OK. maybe try to restart HA.

11

Tried. Still manual_ikea_e1744 will not appear:

Screenshot 2024-05-20 at 09.16.37
Screenshot 2024-05-20 at 09.16.372320×756 48 KB

Another weird thing is that homeassistant/confirmable_notification.yaml is not found within the same path:

~$ ls -l /home/[USER]/hass-config/blueprints/automation/homeassistant/
total 24
-rw-r--r-- 1 root root 15012 May 19 12:35 manual_ikea_e1744.yaml
-rw-r--r-- 1 root root  1442 Apr 12 13:25 motion_light.yaml
-rw-r--r-- 1 root root  1666 Apr 12 13:25 notify_leaving_zone.yaml

EDIT: it’s findable under

~$ ls -l /home/[USER]/hass-config/blueprints/script/homeassistant/
total 4
-rw-r--r-- 1 root root 2595 Apr 12 13:25 confirmable_notification.yaml

So I don’t think there is a path install in my HA install…

12

No idea. Sir_Goodenough is the expert on blueprints. I don’t use them myself.

13

I don’t deal with docker. I don’t know what or if there is an external path where files live on the OS and get mirrored / symlinked into the container. I had Supervised for a while and it worked like that, but don’t know what you have there.

If you have some text outside the container, I would import a blueprint from somewhere. Change the name of the last level folder it creates. Delete the blueprint. Copy=paste the text of your blueprint into the editor. The editor would be something that runs in HA however you would do that with Docker.

Since you are relying on a Docker install to run you house, I assume you are good with Docker’s quirks so that you can maintain this thing. It is too annoying and complicated for me so I don’t use it.