My HA installtion chrached when installing 2024.1? Gets this error messege,
ERROR (MainThread) [supervisor.docker.interface] Can’t install ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2024.1.1: 404 Client Error for http+docker://localhost/v1.43/images/ghcr.io/home-assistant/raspberrypi4-64-homeassistant:2024.1.1/json: Not Found (“No such image: Package raspberrypi4-64-homeassistant · GitHub”)
Any ideas how to recover this?
I would like to recommend the solution from github.
" use the editor of your choice to add , "gen": 1…
Thanks to all developer and maintainer!
1.1 broke shelly 1 20230913-112003/v1.14.0-gcb84623 varning stay with 1.0
Downgraded to the 1.0 from a backup
Thank you. I have downgraded to 2024.1.0 (IMO not having this version before) using this instruction: https://www.youtube.com/watch?v=iigi1ZgUSMo
The downgrade resolved the issue.
Shelly works fine again. I recommend this solution rather than deleting the integration and adding it back.
It would be reasonable to post a warning for this update or withdraw its availability until 2024.1.2 is released.
Don’t make inappropriate comments. If you make comments that violate the coc, they will be removed. You could have made your comments without the swearing and blaming and it would have been fine, just like everyone else.
Secondly, the OS updates are not related to this release which is what broke z2m on your system, so all these “catch in beta” complaints you have are unrelated to this release and its beta.
All my automations with STATE changing to … no longer work. The value of the STATE that i choose has dissappeared and i don’t seem to be able to add a value.
Anyone else experienced this??
Go to the developer tools → states page and look at your entities, you’ll see they still have states. Otherwise, please use different words to explain your issue.
yes, that works nicely, and yet it is odd, because all of my Shelly devices were up to date to 1.14, and of my 5 gen 1 devices, only 1 missed the gen property.
They were added to my system in 1 go, so this could not explain that as far as I can see.
the fix does fix it so yes, no need to wait for 2024.1.2 
Agree 1000%
The When\And If\Then Do is fine and probably easier for the new user. But OMG burrying everything within sub menu’s is excrutiatingly painful. And finding things… near impossible. I’ve resorted to just using the search field because I know exactly what I’m looking for. But a new user will be searching around in those menus for a while trying to figure out what they’re looking to do. Sub menus IMO are a big step backwards in ease of use.
I had the same issue with System Monitor, also caused by an issue with a mounted drive (mounted via SMB). In my case, changing the mount in fstab to add vers=2.0 to the options allowed it to work.
Actually, new users were involved in the process for making this new organization. They found it to be much easier to understand. You can get all the gritty details in this months release party video which extensively covers the UI automation changes. They were designed with the assistance of new users, it was not based on assumptions like your comments.
Yikes. Well for an existing user that knows what they’re looking for… It feels like a pretty big step backwards. And “building blocks” (odd name) as a separate menu? That just makes it worse. Soooo many buttons on the page now. Feels very messy. This is feedback, not assumptions.
use the search. Type the service call and it will find it. You can always go to the full list and search there as well, which is the exact same number of clicks.
Again, this was all vetted by a large focus group. Sorry that you don’t like it.
The post was made out of frustration with all the issues amounted in general with this release which broke my entire setup, not just with Z2M. I don’t recall swearing, but if I did I’ll happily apologies again for my rant.
I love and appreciate the hard work HA devs and community do, so the last thing I want to do is bring bad vibes. I’ve already given a slap on my face, and hope to leave it as that.
Happy 2024 everyone! 
Well done to the developers who solved the problem with the 2024.1.2 update 
Hello, since upgrade to 2024.1.0 - 2024.1.2 after every HA restart my SynologyNAS-mounted “Backup” folder needs manual repair. Anything I can do to prevent this?
Manual repair always works but it’s inconvenient… Thanks
Maybe it’s HassOS related, upgraded both the same time.
Like somebody said: there’s nothing wrong with being a little technical and use good German words like Auslöser, Bedingung and Aktion. No reason to use inferior language when there are simple, proper words to describe the subject.
Same for English: Trigger, Condition and Action are precise and not complex.
If somebody is into home automation, he will understand these three words in any language.
I think its actually the other way around: people would be more confused when they read the fuzzy headings “If”, “And if” and “Do”. That’s toddler language and we’re all grown up. No reason to fall back to kindergarten times.
You’re fine.
Interesting for this discussion might be that with 43k HA installations running in Germany, it is 2nd place behind US (52k) [source]. These two countries have by far the most HA installations.
Which source file contains the GUI automation editor translations to German?
