Upgrade to 2024.1.1 has wiped my automations

I upgraded to 2024.1.1 from 2023.12.? (I believe it was the latest .12 release) and the automatons are no longer there. I don’t have a yaml configuration of them they were all done in the UI. Are they lost? I see that 2024.1.2 is available, would that fix it?

I’m seeing the: Start automating screen and no entries.

Settings → Devices & Services → Entities → in search field type automation - are they listed there? They should also be in the automations.yaml file regardless of how you made them.

@fleskefjes yes, they do seem to exist as entities.
They are however not triggering. That’s how I noticed they were gone. I also was using a bluerpint “medication reminder” that the entity has gone dark.

Try reloading automations from the developer tools.

Tried, no go.
One thing I noticed, the entities are all status = “restored”.

Can you check automations.yaml to see if there are entries there?

No, doesn’t seem like there is a automation.yaml file … I do have my backup and it does exist in the homeassistant.tar.gz file.

Try restoring it.

I put the automatons.yaml in /config and restarted. Seems to have fixed the problem. The templates came back and the entity status now show as normal. tyvm.

1 Like

my HA was on Qnap NAS container station (docker). After upgraded from 2023.12 to 2024.1.3. Qnap container station won’t help to copy old config folder to new docker. I lost all settings, HACS and etc. Stop new HA 2024.1.3 and manually copied config folder over. all yaml files are there. However, it still won’t get all working. Endup I have to reconfig all devices. Correct automation jobs. Now, 2024.2 available. I tried today. It has same issue. Any solutions? I do have backup file. However, in Docker version, no restore feature.

You should keep the config outside the container, then you won’t have the need to copy anything. Just map your container to the folder like this:


    volumes:
      - share/path-to-your-ha-folder-outside-the-container:/config

This isn’t docker, it’s HASS OS

Huh? He clearly states that he uses docker: “Qnap NAS container station (docker)”

I see the confusion. @newstartech added to an existing thread with a different architecture. He should have started a new thread. You didn’t quote him or @ so hence the confusion.

Sure, but I replied to his post though :slight_smile:

Thanks. I will try to figure out how to do so in docker. I am new to docker and linux.

sorry to create confusion

Problem temp solved by ensure all hidden folders of existing config folder copied over to new HA.