Debian 10 Supervised install. MariaDB add-on.
No,problems. Db took 5 min to upgrade, then the msg went away.
Yup, it broke ALL my thermostat cards. I have like 10 of them.
Interestingly they work if you use the home assistant app (at least on iOS), but on Safari and Brave, the control dot is missingā¦
They wonāt. Lots of controversial UI changes lately, but none of them has ever been reversed. I personally find the new switch dialog quite ugly as well. I would say that we are witnessing a āmushroomizationā of the HA UI.
The HA container includes python so it will get upgraded when image will get it. It is a also mentioned in the release notes
If this is the entities card then I can observe the same behaviour.
Some positive feedback on UI
When I use a dashboard to interact with HA it is 99% of the time on my iPad
The old sliders for setting light intensity were fiddly. You often had to try twice before the finger caught the little dot on the slider. The new interface is so much easier to use. No matter where your finger goes on the slider you catch the control and can set the light intensity. Thank you Paul for that improvement.
And thanks for not messing with my colours in my picture-entities cards. What a relief this month
Note that a work around was posted. The bug with the precision is only happening when the Number Format for the user is set to None.
Click on your username in the bottom of the left menu and find the Number format field and set it to something else than None. It is a bug that Paul hopefully can fix now that we know how to reproduce it.
The None value makes numbers appear with dot as decimal seperator and without the 1000s seperator. The other formats adds 1000s seperators which not all wants. The most important for most of us is that you get the right decimal seperator for your language/locale and you can pick a format both for comma and dot that makes precision work.
I had the āUse system localeā format chosen, which uses comma. So now I have chosen the same format from the list but not as āUse system localeā and it works. Thanks
the sensor, where I can see the option to change the unit: yes. but for this one, changing the unit does not show any effect
The other ones unfortunately notā¦ thatās something I will raise with the devs of the component
Navigate or URL tap action? I canāt seem to get this work with āNavigateā. URL works but the screen reloads, and it opens safari on IOS.
I have to disagree. Even when setting number format to anything other than ānoneā the sensors on the dashboard is still unaffected, despite that I have changed the number of decimals.
After installing 2023.3.0 I noticed that all my data in the energy dashboard where gone (probably other stuff too but I hadnāt notice).
Reading this thread seems like something with the database has gone wrong, but I hadnāt notice any suspicious log message.
I have restored a full backup and the data returned. Iāll wait for a point release before upgrading
phuh, this update is going more haywire than expected, killed a couple of integrations (Tibber, solaredge). Rolling back.
Iām not sure Iām understanding the Thread part correctly, I get this:
But I canāt set the Apple TV as my favourite network?
Tibber integration broke, but was expected.
My Bluetooth devices from Theromo pro connected via the Shelly/Bluetooth bridge where lost as well.
You did the mandatory control F5 ( force browser to reload all cached elements of the page )?
Yes, thatās correct. Tried on my RPI4 in the kitchen as well. Updating does not help. I have tried every combination of number formats in user settings without success.
no you cant. I asked that in thread and jc2k replied:
thats not possible yet. you canāt connect to a homepod with the otbr protocol.
if someone builds the ios code to sync thread connection details into HA, it will become your āpreferredā network and that prompt for a url will disappear.
and if you do connect your homepod it will just cause suffering anyway, because we are still working on things like e.g. NetworkManager never releasing old routes, and that makes your devices unreachable.
I removed the integration and will probably revisit when of use in a later stage
I think itās worth it to create an issue/ticket as the cause might not always be the same? After the upgrade it takes some time to alter the database. During that time the Energy dashboard is empty.
With my instance it took about 15 minutes for the database upgrade to be completed and after that my Energy data was mangled.
So, I added the device_class power to the other sensors that did not yet have the correct Device_class setā¦ but, it seems that they also canāt be converted from W to kWā¦
I donāt know, why this happens - unfortunately, the log doesnāt show anything that could be related to thisā¦
could it be, because of the usage of "unit_of_measurementā rather than ānative_unit_of_measurementā ?