2023.3: Dialogs!

CChris · March 10, 2023, 10:57pm

just found an issue with the Unit_convertion when a Utility_meter (helper) is using the entity as source…

Create Utility_meter helpers (weekly, monthly, etc.)
Link your Energy sensor as source (unit_of_measurement == kWh)
Utility_meters are showing 0.00 kWh

Then:
Change the unit of measurement to MWh…
Change the precision (?)
Change the unit of measurement back to kWh…
Change the precision (?)

the Utility_meters are showing some values they should not have:

I don’t know if the change of precision is really required… but it is the only explanation I do have at the moment why the utility meters are not showing the exact same value as the source sensor…

Github issue:

github.com/home-assistant/core

changing the unit_of_measurement is causing the Utility_meter helper to get crap data

opened 10:52PM - 10 Mar 23 UTC

ChristophCaina

### The problem Today I've installed a new device to read out my utility meter …from the provider. I've created additional helpers to get measurements on a weekly, monthly, quarterly and yearly basis... So far, this is working as expected... BUT: I did a test and changet the Unit_of_measurement for the sensor / entity from kWh to MWh.... and then back to kWh... After that, I've noticed, that all utility-meters I've created had strange values... ![image](https://user-images.githubusercontent.com/26391061/224442662-493d693c-69b0-45c1-be1d-a783ddf9832f.png) It seems, that changing the Unit_of_measurement does affect the Utility_meters which have the specific sensor as source. Yet, I cannot explain where the measurements are comming from. They DO NOT show the same value as the source sensor... Maybe, this is a result of precision, too...? ### What version of Home Assistant Core has the issue? core-2023.3.3 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant OS ### Integration causing the issue helpers, unit_of_measurement conversation ### 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_

CChris · March 11, 2023, 8:45am

found another issue with the unit conversation in the statistics graph… :-/
The value will be recalculated, but the unit of measurement will remain the same.

Github issue:

github.com/home-assistant/core

unit convertion does create issues in the statistik graph

opened 08:43AM - 11 Mar 23 UTC

ChristophCaina

### The problem I've impmemented a device that is reading the meter values from… our energy meter. It had a value of 21,992 kWh with the first reading, increasing the value to 21,993 kWh later on. ![grafik](https://user-images.githubusercontent.com/26391061/224474426-27b3fd20-6ed5-4b5a-b52a-6f9b6fdedede.png) ![grafik](https://user-images.githubusercontent.com/26391061/224474438-a7f2fdce-4c5e-4333-bd85-5db8106d2cbb.png) I've tested the unit conversation from kWh to MWh - and switched back and also adjusted the precision during this part. In the Statistics, you can see, that the Unit is now showing as it should be -> 21.99 (MWh) -> but still with the kWh unit. This is causing a drop in the statistics graph, because the value does change, the unit itself not. ![grafik](https://user-images.githubusercontent.com/26391061/224474553-b7952d8d-843c-4658-b37a-d49e9cab6a43.png) Switching back the Unit of Measurement to kWh - has resolved the issue. ### What version of Home Assistant Core has the issue? core-2023.3.3 ### What was the last working version of Home Assistant Core? _No response_ ### 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_

Joao-Sousa-71 · March 11, 2023, 10:50pm

What type of Bluetooth devices did you have? I’ve the update and would like to use the Shelly Gen2 as well. If you can detail your config that would be awesome. Thanks.

kave · March 12, 2023, 6:53am

Since I had other integrations that broke I reverted from a backup really quick. When I updated to a later release the bluetooth integration worked, was a bit slow to start and see my devices. The Shelly Bluetooth bridge works fine with my thermo pro devices.

Nabs · March 13, 2023, 5:11pm

Apologies if this has been mentioned yet, I did look through this thread and didn’t see it. It’s also nothing major…

When I go to logbook or history, and tap on Start Date or End Date to change the date/hours, the month of February shows in the date picker.

Previously, it would show the current month, and the current date selected in blue. So today it would show the month of March, but instead it’s showing February.

The current March date is selected, so it has the correct date selected, but the date picker itself shows February.

As I said, nothing major.

I’m on 2023.3.3, on a raspberry pi. A restart didn’t fix it.

tom_l · March 13, 2023, 5:18pm

There is an issue open for this and a fix has been merged for a future release.

github.com/home-assistant/frontend

Extended history graph does not offer actual month in date select

opened 11:46AM - 12 Mar 23 UTC

PetrMa

### Checklist - [X] I have updated to the latest available Home Assistant versi…on. - [X] I have cleared the cache of my browser. - [X] I have tried a different browser to see if it is related to my browser. ### Describe the issue you are experiencing Hello, if I click in history graph to the month field, the system offered me by default February instead of March which is the current month. Why? ### Describe the behavior you expected I expected that the system offer actual month in the date select field. ### Steps to reproduce the issue 1. click to some entity 2. on History graph click show more 3. click to file for date select 4. there is showed February insted of March ... ### What version of Home Assistant Core has the issue? 2023.3.3 ### What was the last working version of Home Assistant Core? _No response_ ### In which browser are you experiencing the issue with? _No response_ ### Which operating system are you using to run this browser? _No response_ ### State of relevant entities _No response_ ### Problem-relevant frontend configuration _No response_ ### Javascript errors shown in your browser console/inspector _No response_ ### Additional information _No response_

CChris · March 14, 2023, 7:23am

this really confused me
Was not sure, if I have changes something unintensionally that caused this behave ^^

Thanks for confirming this as an issue

petitpiton · March 15, 2023, 7:33pm

I have an issue with the change to ONVIF providing the switch control for ir cut filter (infrared light). My IP Cameras support this feature and so I got new switches for the IR for each camera. The ONVIF standard allows 3 states for the ir cut filter control - on/off/auto. However, with the switch you can only set on or off.
Have I missed how you set the camera back to auto operation?
Currently the ir cut filter only stays in the state dictated by the switch. I need auto mode back somehow.
Thanks.

azaka · March 16, 2023, 4:03pm

Is there anyway we could get a feature flag or something to turn off the new dialogs? I honestly hate them. They look nice sure, but 98% of the time I’m clicking/tapping into a light or switch, it’s because I’m looking for the history. And the other 2% of the time, it’s to change the color or temperature of the light. So now instead of this all being 1 click/tap into the light and I can do or see anything I need, I have to click around multiple times.

kevincw01 · March 17, 2023, 3:22pm

This is not true at all. Happy to test upgrades with non-production systems but I don’t install any updates unless they haven’t had minor version updates for at least 1 month.

Pocky0013 · March 17, 2023, 3:56pm

I can’t get room temperature information with assist.
I have correctly assigned a temperature sensor to a room. The sentence is correctly transcited and corresponds to what the script expects. But it is as if the link between the areas and the measurement is not made. Is there something more to do?

Mariusthvdb · March 17, 2023, 8:40pm

But then we’re already on the next monthly update…catch22 then?

Ildar_Gabdullin · March 18, 2023, 12:26am

Although it turned out that users’ complains are simply ignored (check new PRs, currently more domains getting these shiny & more-or-less useless more-info windows), I will post this anyway.
Check this more-info window for a “restored” entity - now the “Delete” button is hidden, a challenge for beginners:

Since this cannot be considered as a bug, created a post in Discussions.

Akinetopsia · March 19, 2023, 8:29pm

HA crashed while doing the most recent xx.5 update and now won’t start.

Halp!!

~~I had the Create Backup option ticked. Is there any way to roll back from the console ?~~

Ok i managed. Command was

ha backups restore [slugname]

I thankfully had a full backup from early febuary and am working my way restoring the partials backups i have until core_2023.3.3 – which i’ll stick to.

Still I lost a bunch of customization i spent hours creating. Moral of the story: Don’t upgrade.

crzynik · March 19, 2023, 9:33pm

Not really, if anything just do a backup before upgrading. But many users upgrade smoothly and never have issues like you experienced.

Akinetopsia · March 19, 2023, 9:38pm

I did.

I thought the “create backup” option created, well, a usable backup – but turns out it’s only a partial backup that can’t be restored as is - at least it didn’t allow me to. So i had to rollback even further to a full backup i thankfully did 6 weeks ago, but that one has overwritten all my configs and customizations i made since.

HA was working fine, i didn’t need to upgrade and now i regret that i did.

nickrout · March 20, 2023, 3:42am

There are plenty of people on 2023.3.5 who’s updates went smooth, so stop spreading FUD.

Your system had an error, but that doesn’t make it universal.

sparkydave · March 20, 2023, 3:53am

I fixed your mistake above.

Akinetopsia · March 20, 2023, 5:48pm

HA is free software built for free by volunteers and I get that. I love it and really and i’m super grateful for a self-hosted IOT system.

It’s a bit quirky tho. I’ve only been using HA for two months. Perhaps those quirks are common knowledge for experienced users – and i did read the strong suggestions to create a backup before updating which, again, I thought i was doing. Given that the option is located in the core update confirmation dialog, one could reasonably expect that it will, in fact, backup the system.

Can we agree that this option is misleading ? It lulled me into a false sense of security when in reality it is *not* a full backup.

And yes i am aware this is not the current version but the dialog is the same. i picked a screenshot online as HA is somehow updated to 2023.3.5 now while i left it at 2023.3.3 which at this point i’m just not going to question how

I am not using hyperbole when i say i lost a lot of time – most of my customizations i did after that full backup i manually triggered early on. I was happy with my setup, but now i have to basically start over so apologies for the frustration in my previous posts.

lordwizzard · March 20, 2023, 5:58pm

You do know that it only backs up what it is updating only, right? Otherwise go into settings and do the backup there