2023.3: Dialogs!

greybags · March 3, 2023, 3:11am

Possibly a topic for it’s own thread, but since it was mentioned in the main post… I have an old Hue bridge (v2) that sits in a drawer since I changed everything to ZHA on a Sonoff dongle. Is there any benefit to be gained by setting up the hue bridge again now it can be used as a matter bridge?

fversteegen · March 3, 2023, 4:38am

Did you wait until the database upgrade was completed? I had the same issue, but simply let it run for the night and in the morning it was all migrated.

Mathegeek · March 3, 2023, 7:40am

Hi,

The solution I found there works for me : Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6']. · Issue #37 · meichthys/uptime_kuma · GitHub

You just need to type “pip3 install pyuptimekuma==0.0.6” in the command shell of your HA container and Uptime Kuma will be fix after reboot.

o0larry0o · March 3, 2023, 7:42am

I have the same issue since the update,
I can’t adjust he thermostat temp from the UI

MagicCosmicParticle · March 3, 2023, 7:49am

Dears,

This is all wonderful. For me biggest question is when you will get rid of AM/PM time presentation, since it is used only in USA, and show the proper 24h time, also for the dates, similar thing, to give people option to choose date format, from usual European (and world wide) dd-mm-yyyy, to coders friendly as well yyyy-mm-dd . I am not lonely in this request I am quite sure that more than 80% of HA users will be happy with this tiny but also so major improvement.

Thank you
Andjela

CChris · March 3, 2023, 8:17am

at least, you can already set the time in 24hr format in the user settings
(localization)
grafik

Regarding the date format, there’s already a Feature Request:

Kaaf · March 3, 2023, 9:04am

Since the upgrade (at least one) automation was missing. Ver 2023.3.1 didn’t resolve this issue. I had to go back to the backup of 2023.2.5 which made it available again. Strange.

update: apparently the specific automation contained something illegal which was not bothered in v2023.2 but in 2023.3 it did. I deleted the automation and rebuild it → now it works again.
Error in log was: extra keys not allowed @ data[‘action’][0][‘choose’][1][‘sequence’][3][‘delay’][‘sequence’]. Got None

nickrout · March 3, 2023, 9:06am

No logs, no issue.

jpg1961 · March 3, 2023, 9:11am

Hi,
You’re running HA from a docker container, so I assume it has python.
The installed syno packages are not used by the docker container.

Rgds,

Mariusthvdb · March 3, 2023, 9:15am

hehe, I dont use those that much, so hadn’t noticed either.

so glad we can still use an entities card with a plain toggle. Or just have our own custom:button-card designs that dont get touched upon these modernizations in the core HA Frontend.

looking at these, makes me wonder why there is that slider/switch in the first place, as it has become ‘just a big slider switch’ panel, instead of a ‘more-info’ view panel we expect.

I mean, on a light more-info that makes sense, but on a switch? on/off, what’s more to mimic there? I must be missing the obvious for this improvement

There’s also a bug probably, as this switch (which is turned into a fan in the UI), doesnt show the new slider switch, but still uses the toggle we saw before.

clicking that option in the settings reveals another bug:

arganto · March 3, 2023, 9:42am

But has been exactly mentioned from several users in the beta already. To click on a switch to see only a big switch and no direct history anymore …

Unfortunately nothing changed.

Mariusthvdb · March 3, 2023, 9:47am

yeah, sorry I missed that aspect in the beta,
(I did manage to PR the fan icon though )

really odd, now I recheck the same entity , I get a cut off dialogue in English…

seems really unstable currently, not sure what is happening

zigomatic · March 3, 2023, 9:55am

Question about sensor display precision (may be question for @emontnemery)
My water is displayed like this

But I don’t see how to modify the precision. Is it not available for an input number ?

Seems different as another sensor like:

I would like same kind of approach but for conversion for instance:
daily unit meter is in minute but if I display this for a month, it would be nice to have a kind of max treshold (if it’s more than 60mins, display in hour,min)

boheme61 · March 3, 2023, 10:58am

ok, i have for quite awhile used /Developer/—restart— . if that was my purpose, i.e update - HACS(custom) component, but Reboot and the others, that comes with this “package” was spread out, to me it makes sense to "collect this in a menu, i know it “cost” 1 click more for the “restart”, but gains in a functional/logic, i guess we all “develop” various routines

boheme61 · March 3, 2023, 11:09am

Have you tried with HHH, instead of hhh ?

Bepp · March 3, 2023, 11:32am

I was, I got the error “Database Migration failed” two times (.0 and .1). Waiting for 0.2 then I’ll try again.
After reading this I made a full backup before, so only an hour or so is missing.

KennethLavrsen · March 3, 2023, 11:55am

Still problems with precision feature in 2023.3.1

I post it here in case you are hit by it.

github.com/home-assistant/frontend

New precision feature still has problems with number format None

opened 11:38AM - 03 Mar 23 UTC

KennethLavrsen

### 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 With the update to 2023.2.1 the precision feature with Number format set to None changed but still not working I have 3 sensors. All are sensors that should report a price in DKK/kWh with two decimals Here is how it looks like with Number format set to my system (English UK). Here it looks right. ![image](https://user-images.githubusercontent.com/8373419/222705720-a1dcf896-a29e-4099-a3dc-af5a8dfb863a.png) And here with None. Why is the first number shows with 3 decimals? It does not matter what precision I choose. It is 3 decimals. And the unit it gone. Same for Nordpool. The unit is DKK/kWh. It is not shown. Why? These are the same electricity price but from 3 different integrations because they are often not updated correctly and I see the problem and can act when they are not the same. ![image](https://user-images.githubusercontent.com/8373419/222705316-a8f4a453-21f7-429e-9085-11143b428ded.png) The actual values without rounding off are The Electricity Price (EDS) is 1.81386011609675 The Electricity Price Kamstrup is 1.81 - yes rounded by the template sensor to be displayed with 2 decimals The Nordpool Electricity Price is 1.814 - it has 3 decimals from the source Note the units. When the number format is none - the units are gone. But only for some of the numbers. The unit handling in HA lately has become a mess and all the integrations do it differently. I just want the numbers show in the units_of The EDS has unit_of_measurement: DKK/kWh device_class: monetary The Kamstrup only has unit_of_measurement: DKK/kWh The Nordpool has unit_of_measurement: DKK/kWh device_class: monetary I have another one. I have a sensor that shows a cost in DKK in very small numbers where I need all the decimals to see what is going on The actual value is 0.018139 and the unit is DKK unit_of_measurement: DKK device_class: monetary Here is the sensor displayed with Number format not set to None and I have chosen to see 6 decimals. I get 3 decimals. No matter what precision I select I get 3 decimals. And the unit it gone. ![image](https://user-images.githubusercontent.com/8373419/222709865-98740a9c-15ea-4a77-bb3d-70213ba2e4e5.png) And now I set the Number format to my system. I get 2 decimals. No matter what precision I set. I cannot use that. I need to see this particular value with its precision. In fact I want all decimals. I have a unit. It is in the front of the value. I guess this makes sense in English for things with money and I can live with that. ![image](https://user-images.githubusercontent.com/8373419/222709392-b0b7aa44-fb0a-4485-8b8d-319a1491cb13.png) ### Describe the behavior you expected I expect - no matter what Number Format I have To see the number of decimals that I choose No matter what number format No matter what unit of measurement it is No matter what device class it is If I ask for 2 decimals I expect 2 decimals. If I ask for 4 decimals I expect 4 padded with 0's if needed If I choose default - then I am I expect something intelligent and that may not fit my need. But that it OK as long as I can set the precision. And if a unit_of_measurement is defined I expect it displayed. Always Also if it is bananas/lightyears ### Steps to reproduce the issue See above ### What version of Home Assistant Core has the issue? core-2023.3.1 ### What was the last working version of Home Assistant Core? New feature ### In which browser are you experiencing the issue with? Multiple browsers ### Which operating system are you using to run this browser? Multiple OS Linux, Windows and iPad ### 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_

It seems the safest Number format right now is fixed 1,234,567.89 or 1.234.567,89 and not None, or system based or browser based.

bronek · March 3, 2023, 12:15pm

Hello! I have just created new venv with python 3.11.2, however I can’t install pybluez=0.22:
With python 3.10.9 I had no issue at all (previous, currently running venv).
Could anyone suggest me how to solve it? (I couldn’t find solution with google)

 gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fno-semantic-interposition -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free -ljemalloc -DTHREAD_STACK_SIZE=0x100000 -fPIC -I./port3 -I/srv/homeassistant_3.11.2/include -I/usr/local/include/python3.11 -c bluez/btmodule.c -o build/temp.linux-armv7l-cpython-311/bluez/btmodule.o
      bluez/btmodule.c: In function ‘PyInit__bluetooth’:
      bluez/btmodule.c:2837:22: error: lvalue required as left operand of assignment
       2837 |  Py_TYPE(&sock_type) = &PyType_Type;
            |                      ^
      bluez/btmodule.c:2838:29: error: lvalue required as left operand of assignment
       2838 |  Py_TYPE(&sdp_session_type) = &PyType_Type;
            |                             ^
      error: command '/usr/bin/gcc' failed with exit code 1
      [end of output]

Ildar_Gabdullin · March 3, 2023, 12:22pm

Sorry, I disagree.
Same as - since blind users are a MINORITY, we anyway MUST allow them to use HA.

kompre · March 3, 2023, 1:01pm

Not really sure. When I noticed the missing data, a couple of hours were already passed since installation. Since I read here to expect a 15 minutes to rebuild, I’ve assumed something was wrong and I’ve restored the backup.

I haven’t seen any indication that the database would be rebuild, or something was in progress. I didn’t check very thoroughly tough. (backup are so easy to restore that I didn’t fret too much)