Please downgrade bundled frontend version to 20221108.0 until they fixed it

[prof7bit]

The problem

Frontend is currently in an unworkable inconsistent state because they accidentally merged incomplete code into their release branch. At the moment they seem to try their best to sort it out and get it back into a consistent state, but it can be extrapolated that this will take a few more weeks.

To relief some pressure from the frontend team, to enable to fix this without permanent pressure from affected users, core should therefore bundle the latest known working frontend code, the one from the last November release (afaik this was 20221108.0), until the issue is fixed and frontend can provide a functioning and consistent release again.

What version of Home Assistant Core has the issue?

2022.12.4

What was the last working version of Home Assistant Core?

2022.11.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[frenck]

Frontend is currently in an unworkable inconsistent state because they accidentally merged incomplete code into their release branch.

Please be more specific, as this is a general statement that I can't use to decide or act on.

Core should therefore bundle the latest known working frontend code, the one from the last November release (afaik this was 20221108.0), until the issue is fixed and frontend can provide a functioning and consistent release again.

That sounds pretty much impossible, as that version won't be compatible in many ways.

It would help if you where explicit in the issues you are referring too. "the issue" is hard to pin-point. The project over 2.5K issues and requests open the whole org.

../Frenck

[prof7bit]

They attempted a major rewrite of the color theming of entity state on the lovelace cards and on the history-card, but for some reason it ended up in some half finished and completely untested state that got released with 2022.12.0 and since the last 4 core versions they are trying to fix it under great pressure from hundreds of upset users, committing dozens of fixes per day directly into the release branch thereby introducing even more mistakes, for example currently all binary sensors show the same color for off and on, this happened this morning in an attempt to fix the on color, which was almost the same shade of blue as the off color.

They seem to be under immense pressure at the moment, there is a huge outrage in the forum, many users are really upset, and IMHO the best idea would be to revert to something that was known to work and then let the frontend guys try to sort it out without pressure of permanent new releases, until they have gained back control over the situation.

[mmashnev]

It seems that the frontend version 20221208.0 bundled with core 2022.12.1 had fewer visible problems on the surface, such as the new color theming being much more consistent than in the current version. So I'd propose considering it as a downgrade option.

[frenck]

They attempted a major rewrite of the color theming of entity state on the lovelace cards and on the history-card, but for some reason it ended up in some half finished and completely untested state that got released with 2022.12.0

There are issues open, that is for sure. However, your statement on untested is incorrect and (IMHO) blown out of proportion. Besides nightly testing and dev use, those changes have gone through beta testing as well (including our user base that joins the beta).

Yet, things happen. We are all humans :)

they are trying to fix it under great pressure from hundreds of upset users

I'm not aware of anybody feeling to be "under great pressure", nor did anyone express that as such. That said, false expressions or questionable expressions (as you made in this issue for example), does make it feel like there is. Please don't do that.

They seem to be under immense pressure at the moment, there is a huge outrage in the forum, many users are really upset, and IMHO the best idea would be to revert to something that was known to work and then let the frontend guys try to sort it out without pressure of permanent new releases, until they have gained back control over the situation.

There is no way to revert at this point, especially not the revert suggested. Reverting also causes issues for people that have adopted, thus creating a breaking change as well.

Let's figure out how to move forward. If you find a frontend issue, please be sure to report it in the appropriate issue tracker. If you don't want to be on this path, we recommend you restore a backup to a previous Home Assistant version that does fit your needs for now.

Closing this issue on this end, as from the Core repository, there is no possible action to take with this issue.

../Frenck