Thank you for the release. Again and again impressive and excited to see changes.
The hacs history-explorer-card is also working in this version 
The thermostat can still be used via the 3 dots but not from the UI directly. Little change will come for corrections (supposed)
I was patientā¦ Iām not dumb. I have waited 30 minutes. Then I checked my HA and saw that it says itās still starting. 90% of the entities on my dashboard said HA is still starting, 10% were grayed out. I found this a bit weird and have checked the logs. Full of errors. Not infos, errors. I have checked CPU usage: 2%. MariaDB usage: almost 0%. I let it sit for 5 more minutes but nothing had happened. Then I tried restarting HA, which it refused to do. Then I tried restarting the host which booted in emergency mode. At the end I had to restore a full backup.
File "/usr/local/lib/python3.10/site-packages/MySQLdb/connections.py", line 254, in query
_mysql.connection.query(self, query)
MySQLdb.OperationalError: (1054, "Unknown column 'statistics.start_ts' in 'field list'")
Great! love the sensor precision, was just looking for this!
I got also lot of sql error just after the upgrade, (sqlite3.OperationalError) no such column: statistics.start_ts
Then I decide to restart the host with the new UI
No issue after restarted came about sql except recorder saying this:
The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
I canāt set anymore RGBW light to mode: white, only 255,255,255 (cold white via rgb) is possible. on versions before 2023.3 there was 2 options: color and white. Am I doing anything wrong?
After the update i cannot change the temperature of a climate device through the thermostat card anymore, I have to click on the three dots and then adjust it. Is that on purpose?
No itās a bug and it will be fixed in the next patch.
Good morning,
I am pleased with the new version of HomeAssistant. The update went smoothly without any problems. However, it saddens me to see the repetition of old mistakes.
Once again, the developers seem to have forgotten about accessibility. I like the new window for turning on the lights, changing colors, etc. The concept is good. Unfortunately, the execution could be better.
It is very weak that the on/off button for the light does not have a descriptive label for screen readers to inform about the current state. Additionally, the nice vertical brightness or white light color level bar cannot be controlled with Google TalkBack. There is information about the set light level, but it cannot be changed. There are problems with these control bars in HomeAssistant in many places, and itās getting worse from version to version. Unfortunately, worse. Please pay more attention to accessibility. In HA, there are areas where accessibility is exemplary (for example, automation creation screens), and itās great. On the other hand, no one with a screen reader can control the setting bars, regardless of whether they are vertical or horizontal. No one can set a schedule with a screen reader. No one with a screen reader can read statistics or charts. These things ask for greater care.
I hope these issues will be addressed. The best building automation system cannot have such shortcomings; it must comply with WCAG guidelines. Different people with different needs and limitations use the system. Please remember this and do not repeat past mistakes in new HomeAssistant updates.
Agree, hopefully all controls will be on the same page.
probably your computer clock is going wrongā¦
Hello 
Thank you for your feedback.
We built the new slider according to slider pattern from WCAG guidelines by adding keyboard interaction, aria roles, states, and properties. Iām surprised and disappointed that it doesnāt work with Google TalkBack 
For the color wheel, we re-used the old one which is not accessible at all but we plan to improve it in future release.
According to the documentation, it seems that all assistive technologies doesnāt support these specs :
Some users of touch-based assistive technologies may experience difficulty utilizing widgets that implement this slider pattern because the gestures their assistive technology provides for operating sliders may not yet generate the necessary output. To change the slider value, touch-based assistive technologies need to respond to user gestures for increasing and decreasing the value by synthesizing key events. This is a new convention that may not be fully implemented by some assistive technologies. Authors should fully test slider widgets using assistive technologies on devices where touch is a primary input mechanism before considering incorporation into production systems.
We need to go back to an old <input type="range" /> but there is a lot of issues for safari touch interactionā¦ (thatās one of the reasons we moved for input type range to aria role slider).
I have the same problem with the thermostat card
There is a workaround. You can set the target temperature in the dialog that comes up by clicking on the three dots top right.
[edit]
By the way, I noticed that the draggable dot can be easily inadvertently moved when scrolling on mobile, so I first thought it was a feature, not a bugā¦
When it comes to accessible tools never assume it will just work you have to do manual testing with each supported tool as they all behave differently with varying navigation structure. The only truly āsafeā tool is Voice Over but even that has itās own quirks which should be tested in real world situations.
Till the update it was correct. Rpi4 + hassos
whatās the problemā¦ That tells us nothing other than showing us the time. What should it be?
Iām pretty sure, that this is not related to the update itself.
{{ now() }} is just working fine on my machine and providing the correct timestamp.
Also, the update itself should not change in this directioin, since itās just using the python function to get the devices clocksā¦ and the only reason I can see for this to display the wrong information should be a wrong computer clockā¦
You should check the computer clock of your system - since I donāt know if you are using HASS-OS or anything else, it is hard to provide further help at that time.
Itās not even displaying wrong, nothing in his post indicates a problem unless he is expecting a different time.
Look at the date.
