2023.5: Let's talk!

And I don’t like your haircut. So what? You don’t know me and I don’t know you. That’s fine by me, don’t make this personal.

I am frustrated by this updates because I have a lot of time to spent with totally senseless things now to get my system up and working again. Time I won’t get back. I do not have problems with the usual bugs that might come with an update but the last two updates of HA were just too much.

An update of a home automation should never ever break a running system the way todays update did. What I expected was a well tested and smooth update with little or even no manual work at all.

And yes, I have restarted HA already. Twice. No change.

7 Likes

And what you’re running into is a bug that no one found in beta. So relax and vent your frustrations elsewhere. Otherwise, join the beta so we can catch these issues before release.

11 Likes

don’t you?

Ok I didn’t mean to make it personal. I know stuff can be frustrating if it doesn’t work. however, keep in mind the hard work people put in to developing HA and deliver it to you for absolutely no cost at all.
You can of course ask questions, but bashing this work is not done for me.

if you have questions or problems, you can ask them nicely. And if you are depending on HA don’t update at the first day, but wait a couple and check the forum to see if there are any critical issues for you so you might can wait for a fix.

6 Likes

Please don’t continue the personal arguments. Thank you.

6 Likes

I’m using a custom skill (Hasska), and my Alexa YAML configuration seems to be working as it did previously, as it did throughout all 9 betas.

  • Included and excluded entities seem to be the same as always.
  • Routines linked to HA scripts are working normally.

Also, no issues with Alexa Media Player-derived entities or services.

1 Like

Did you already update debian?
There’s a bug in udev not creating /dev/serial/by-id/ symlinks.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035094

1 Like

As some others have mentioned, Alexa integrations were greyed out and unavailable in the Alexa app until I manually re-added them in Home Assistant.

Additionally, and maybe more painfully - I had some temperature sensors which were set up in my configuration.yaml file that are no longer able to be added to Alexa. I can expose it to Assist, but the option to expose to Alexa shows as ‘Unsupported’.

1 Like

Try to make a full system restart. I had same problem with missing espHome devices after restoring my backup.

I have updated Debian yes… and indeed the serial/by-id/ is not there anymore. Is there a workaround? :frowning:

can you explain more about the SDK?

Hope it is not broken (that early). As there is a tutorial, there must be some more experience with it.

Check this out:

Shouldn’t this release be pulled until this bug is fixed (presumably in 2023.5.1), or at least a big warning placed somewhere? This is a major problem for anyone that’s using Alexa or Google exposed entities, especially if you have hundreds of them. Even if rolling back to a backup, it creates a major headache reorganising everything into rooms inside the Alexa app afterwards.

8 Likes

thnx, but how to use it for room cleaning for example for an excisting vacuum entity?

2023.5.1 is already on its way and as far as I can tell, it contains a bug fix for that (2023.5.1 by balloob · Pull Request #92513 · home-assistant/core · GitHub).

1 Like

Not sure, maybe this one. Sorry in german.

What about everyone that’s still to install this before 2023.5.1 is released? It seems a crazy (to me) to leave this released and available to install with such a major bug, potentially causing hundreds/thousands (who knows how many) people a problem and potentially hours of work fixing things. There should at least be a prominent warning for people somewhere IMO.

13 Likes

I am using HA OS so thats a big difference

Never install .0 releases if you cannot handle bugs (this counts for almost all software), actually best is to wait at least to half the month is over before updating. Most of the bugs will have been squashed by then.

11 Likes

Take a look at the breaking changes on the release notes.

History

All YAML configuration options for the history integration have been removed as they were no longer used by the frontend.

Github:
Require a list of entity ids when fetching history