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’.
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? 
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.
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).
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.
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.
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.
If you are running the DEV/HACS version, make sure you are running the latest version. I also ran into issue but when I redownloaded to force an update to v0.0.10 it worked
Don’t get me wrong, all the updates and work you’re putting into Home Assistant is great, but can you please do something about the Overview? We have been waiting for a working version of grid view for 3 years now but are still stuck with those up and down buttons…
Not exactly. Yes, this could be way more intuitive and easier, but we are not stuck.
With stacks you can place everything exactly, where you want and it wont move.
But still, a rework of the whole dashboard design UI stay very high even on my wish-list… 
Some nice features,
but google home missing all its entities / needing remap is just a hastle (160+ enitities) tripple the amount of clicks, and it was not mentioned in the release notes I think…
while the new menu adds extra functionality for ha’s ow assistant, it does make the integration far more bulky
Awesome update with great potential!
With the addition of VoIP into Home assistant would it finally be possible to built a VoIP intercom to allow broadcasts (Room1 to all) as well as directed room1 to room2 2-way audio via home assistant or does the VoIP component only speak to HA?
Thanks!
Sure, follow this guide: Controlling Google Home With Home Assistant! - YouTube
After that you have a service in home assistant to send natural language commands to your google assistant. If you has integrated roborock to your google assistant you can create a button that sends e.g. “Clean the livingroom”.