I only just saw this question: you should not have to re-add any LIFX device for the new entities to be created. It should just happen automagically when Home Assistant starts up. If this is not happening, please open a GitHub issue and include the new diagnostics output from the LIFX device page (which is also new but not mentioned!)
First, I’d like to say that I’m a fan of the new dashboard style, and prefer it over the old one. (Although with anything in design, any change tends to seem better just because it’s “newer” than what came before 
).
However, this release comes with another change that is a lot less about looks and a lot more about functionality. After using HA with the new statistics graph in the entity popup for a while now, I’m convinced that it was a bad idea to change the way that history is displayed.
Let me explain: I almost never have Min, Max and Avarage values selected on a Statistics line graph card because it looks messy and provides little-to-no extra information. But this is what you’re stuck with in the new entity popup.
I recently added a new Bluetooth temperature sensor, which was painless thanks to all the great work that’s been done on that front recently. Next, I open up the entity popup, only to be greeted by a message that says that no statistics are available (there’s a 5-minute delay). Then, when I want to check how the sensor is warming up to room temperature, I have to open up the History page just to get any form of useful data.
Later on, I want to test the range of the sensor, to see if the sensor value continues to update as I move it around. The new sensor popup is once again useless for this purpose, as clear, discreet lines have been replaced with uncertain curves. Last month, I’d have easily been able to see the gaps caused by signal dropouts; this month, they’re hidden.
I trust that the HA developers will understand the issue and make amends next release.
10 Likes
I have posted a solution for the graphs twice, read the thread 
The existence of an imperfect workaround using third party code doesn’t mitigate the inanity of the decision requiring the workaound.
8 Likes
Very true.
Automations that you trigger while you brush your teeth I guess, e.g. a counter for children to do it for a certain amount of time.
Is it me or are the preview pop-up for camera feeds way smaller now?
I have a cam feed on my dashboard. Normal card. One MPEG feed and one Amcrest Feed. Previously I would tap one and it would display a popup with a much larger video preview and then the playback controls, volume, etc. This was probably 2-3 times bigger than the usual card. Now - the pop-up is roughly the same size as the original card. Is this normal? How can I change?
I’m real hesitant to enjoy these display and UI tweaks. They aren’t voted on by the community and they seem to cause more trouble than usefulness. Especially since there are a lot of UI bugs that should probably be fixed before theming and such. Like after many releases - the date pickers are still messed up. If I click the ‘ending’ date - it forces me to select the whole range again. Can’t even enter a date manually. So if it were me i would be fixing those things before thinking, hey we need a border around the elements now.
4 Likes
I just tried to retart today and get the same warning, after searching I found your post as well as the github issue.
Package rest setup failed. Component rest cannot be merged. Expected a dict.
But… what is the final resolution. What do I need to fix.
Thanks to everyone for all the hard work.
We need to wait for the fix to be merged. Or dl the fix from epenet s repo and install it as Custom component ( I did that, and it works as before)
Not familiar with this.
Would you mind providing a link.
Thank you
I guess you best wait for the fix, I should think it will be published in a hot fix soon
The link btw is in that issue I posted earlier
I noticed my popup is smaller now as well after upgrading. My fallback for now is to go fullscreen on the popup
This doesn’t work for ssdp all of the time…
The Gas section of the energy dashboard contains a bug. It is not possible to add new (-additional) gas entities. They are not showing up, even with the right class.
You have to configure them to show up in the energy dashboard, are you doing that as well?
Any ETA on patch 3?
Anxiosly awaiting the RESTful integration patch 
2 Likes
I am trying to update Core to 2022.11.2 from 2022.10.4, but it endlessly loops and never finishes. I am using HAOS in VirtualBox. If I reboot the supervisor it shows it is still on 10.4. Same thing happens if I try to update the Supervisor from 2022.11.0 to 2022.11.1. Is it just me?
PS. I am now unable to take backups from the interface as it keeps complaining it is in startup state
“Creating a backup is not possible right now because the system is in startup state.”
Thank you!