Upgrade was smooth and quick as normal.
As a long-time user of Mushrooms I love the direction we are going, but i have to admit the change in colours did catch me out and took a while to fix. Detailing the exact css that needed modified would have been helpful, having the colour configurable on the frontend would have been better! 
Great release again! 
Is it possible to edit an event in the calendar?
As far as I can see it’s only possible to delete the event…
any chance we could up the granularity on the battery colors? experience shows that many batteries remain in the green zone for a long time, and only after lowering into the mid 50% or so, start accelerating downwards. Having more than 3 colors for high, medium and low is a ‘nice to have’
think:
icon_color: >
if (['unavailable','unknown'].includes(state)) return 'steelblue';
if (state > 75) return 'green';
if (state > 50) return 'gold';
if (state > 25) return 'orange';
if (state > 10) return 'brown';
return 'red';
btw, this image is now obsolete Binary Sensor - Home Assistant
any chance the Frontend team could update that, its not something we end-users can easily do.
This is the climate entity - in Idle (heat) mode.
This is the climate entity - in Heating (heat) mode.
Can you see the problem?
Previously it went yellow when it was actually heating, now I can’t tell at a glance if the heating is actually on or not.
Pretty sure you don’t need a FR for this as it’s already planned and coming.
And I’m sure even more people didn’t.
This is a very disruptive change.
My dashboards look like they were designed for a toddler now.
That is excellent news 
I might have overlooked device_class: heat? was thrown off by the ‘off’ icon to be thermometer. So I didnt associate that with a heating device. Made a PR to change that to flame-off
Adding re-occuring events, with an On end-date does not bring any dialogue to enter the end date, it deems to defail to 3 months
Post your errors, It’s working for me. FYI reporting issues like this usually require all information, not abridged versions from the user. I.e. Post fully un-paraphrased errors accompanied with a description of what’s not working.
Known bug, that is already fixed in dev via Fix hidden/broken input_datetime date selector by spacegaier · Pull Request #14623 · home-assistant/frontend · GitHub
Other questions about UX -
- datetime: '2022-12-08T00:00:00+00:00'
conditions: Snow Likely
condition: snowy
temperature: 1
templow: -2
precipitation: 1
precipitation_probability: 50
precip_icon: chance-snow
precip_type: snow
wind_speed: 9.76
wind_bearing: 315
wind_direction_cardinal: NW
- datetime: '2022-12-09T00:00:00+00:00'
conditions: Snow Possible
condition: snowy
temperature: 2
templow: -2
precipitation: 1
precipitation_probability: 30
precip_icon: chance-snow
precip_type: snow
wind_speed: 8.82
wind_bearing: 295
wind_direction_cardinal: WNW
Given that this snippet of weather data clearly says conditions - snowy.
and the forecast in the more-info box clearly shows snow:
Why do the forecast icons show rain?
is that supposed to be snow?
Why this error since update?
Source: components/hassio/http.py:111
First occurred: 07:32:58 (3 occurrences)
Last logged: 08:25:05
Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py”, line 433, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 81, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 236, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 136, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/hassio/http.py”, line 75, in _handle
return await self._command_proxy(path, request)
File “/usr/src/homeassistant/homeassistant/components/hassio/http.py”, line 111, in _command_proxy
await response.prepare(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 421, in prepare
return await self._start(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 429, in _start
await self._write_headers()
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_response.py”, line 502, in _write_headers
await writer.write_headers(status_line, self._headers)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 131, in write_headers
self._write(buf)
File “/usr/local/lib/python3.10/site-packages/aiohttp/http_writer.py”, line 76, in _write
raise ConnectionResetError(“Cannot write to closing transport”)
Hi! I’ve updated to 2022.12 to enjoy new tile card features, but it seems it doesn’t work.
Am I doing something wrong? 
Thanks
Be happy it’s not raining red 
Really Accessibility UnFriendly update.
No idea where to change it and I will not build theme for scratch because some mad scientist came with bright idea of his own hardcoded colors not reachable in File Editor in HA
Using the Local calendar - is there a way to use the event title as a trigger? Like I have a vacuum cleaning scheduled to start at 12 o’clock and a heater at 11 PM. From what I see I can only create two separate calendars to distinguish the trigger? Also is there an option to edit an event? Like I want to start the cleaning at 7PM from now on.
Sounds like a bug. Please raise a frontend ticket and copy in the complete entity state there so we can try to reproduce it.
The YAML looks good to me. So my guess would be that this light entity is not able to set the brightness (or at least HA thinks it is not).
Do you see those sliders when using other cards or when you go to the more-info dialog of the light?
The trigger variable contains information about the Calendar Trigger. You can reference trigger.calendar_event.summary in a template and determine if its value refers to the vacuum or the heater.
In addition, you can put information in the Calendar event’s description and reference it using:
trigger.calendar_event.description
