jeffdeal
(Jeff Deal)
March 1, 2023, 9:44pm
21
When I use the HA observer my instance is showing as “unsupported” and “unhealthy” with the following error in the supervisor log:
ERROR (MainThread) [supervisor.api.middleware.security] Invalid token for access /supervisor/info
This popped up in the last version, the update has not changed it. The upgrade to 2023.3.0 seemed to go fine, and everything seems to be working.
conorlap
(Conor)
March 1, 2023, 9:46pm
22
Seems to have broken ljmerza/light-entity-card: Control any light or switch entity (github.com) for me. The color wheel no longer appears on that card
I’ve submitted an issue with the dev but just thought I’d give a heads up in here!
1 Like
you can trigger assist from the dashboard by using a navigation tap action to /lovelace/home?conversation=1
just replace home
with the current dashboard you are adding it to so you don’t actually navigate to another dashboard
This is also how you can add it to your android home screen using the android app shortcut feature
2 Likes
flobalzer
(Flobalzer)
March 1, 2023, 9:50pm
25
Thanks for the advice, but how i can delete the zigbee.db?
I think a link in the sidebar would be nice, but thanks for this tip,I’ll create my own link and put it there
1 Like
Connect with SMB or use the addon FileEditor.
Is it just me or did this update break the Thermostat card? I can’t set the desired temperature anymore
Same problem with the Lights card
8 Likes
CChris
(Christoph)
March 1, 2023, 9:53pm
29
Great release again
Many nice, little changes that adds to the UI … I like it!
BUT:
I do have sensors reporting “W” - which I cannot change to kW… ?
Does anyone might have an Idea why this might happen?
big-ted
(Big-Ted)
March 1, 2023, 10:02pm
30
I have the same problem, there is an open issue on github
nickrout
(Nick Rout)
March 1, 2023, 10:10pm
31
In which you say it is fixed in 2023.2.5
confused
JDv1
(Jd)
March 1, 2023, 10:12pm
32
I have the same issue. I use mariaDB as well. After upgrade. no database anymore. Also in the file editor all my files are not visible. Had to downgrade again. Hope someone finds a solution for this
JDv1
(Jd)
March 1, 2023, 10:15pm
33
I tried the update for a couple of times. every time the database upgrade fails for my MariaDB on my Synology
I’m on MySQL and after the upgrade, based on the table changes, my Energy dashboard looks faulty. For example, negative gas usage values. I created an issue for is, as early as during the beta phase of 2023.3 but I think it was not noticed.
So I grabbed a backup from the database and rolled back to 2023.2.5. The issue on GitHub contains the screenshots and some of the SQL data. For now I’m stuck on 2023.2.5.
I was getting this error on my Home Assistant Core w/venv:
"Error importing platform config_flow from integration zha to set up zha configuration entry: No module named 'psutil_home_assistant'"
I fixed it by running “pip install psutil-home-assistant
” in the python venv and reloading the integration.
3 Likes
nickrout
(Nick Rout)
March 1, 2023, 10:34pm
38
Three people describe same problem.
Three people show no logs.
sheesh
2 Likes
right, that’s wrong dont know how we missed that… maybe it slipped in on the last beta and we didnt set the temp…
anyways, here’s the link to the issue: Lost draggable dot on thermostats · Issue #15662 · home-assistant/frontend · GitHub so we can track it
1 Like
List of precision options seems to be not very rich :
opened 10:42PM - 01 Mar 23 UTC
### 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
The new precision feature is great and it also seems to work
But the UI has a small problem
If the value of a sensor happen to be a round number - the UI is not very user friendly in showing the choices in the pull down
See pictures below. Price is close to 2 and rounded off the first 2 decimals are zeros
### Describe the behavior you expected
The UI should show the zeros after the decimal
Like
2
2.0
2.00
and not
2
2
2
### Steps to reproduce the issue
Have a sensor with a value that is with zeros like 2.000 or 1.99998
This will show
2
2
2
2
2
1.99998
Should be
2
2.0
2.00
2.000
2.0000
1.99998
Here is an actual example
![image](https://user-images.githubusercontent.com/8373419/222281921-6dd4aa65-8e03-4de6-adb2-94f0c6f46f6e.png)
I even had a sensor where the choices were
2
2
2
2
2
2
### What version of Home Assistant Core has the issue?
core-2023.3.0
### What was the last working version of Home Assistant Core?
new feature
### In which browser are you experiencing the issue with?
Google Chrome
### Which operating system are you using to run this browser?
Windows
### 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_
2 Likes
I raised a bug report for this.
But even when you guess the UI - and you have a sensor with 4 decimals - and you choose any number - it shows 4 decimals. The feature does NOTHING.
1 Like