2022.7: A stunning performance

Blog
61

Thanks for the tip!!

2 Likes
62

Why are the entity names in the history panel all in lower case?

Also, the name of entities other than sensors have been truncated on mobile for a while.

IMG_A338A232E626-1
IMG_A338A232E626-11125Ɨ2436 121 KB

63

I am also having this error. Iā€™m a bit reluctant to upgrade for now.

64

Its a real shame about the Bluetooth integrations. I LOVE and rely on my MiFloraā€™s to help me with my plant integrations.

I hope there is a way around this sometime soon. If anyone can give me some pointers on how I can upgrade but continue to make these work I would be REALLY grateful.

65

You could make an ESPHome BLE receiver

1 Like
66

My update from 2022.6.x to 2022.7 was absolutely smooth. Kudos to the developers.

1 Like
67

I can confirm. Haveibeenpwnd does not work anymore. No real useful debug info.

2 Likes
68

opencv is busted, unable to import cv2 for a custom component using opencv-python-headless 4.6.0.66 and numpy 1.23.0

69

Seems great. Unfortunately I have to hold off upgrading because my bluetooth tracker integration will stop working. Sadly BLE isnā€™t an option for me because Iā€™m tracking mobile phones and BLE apps randomise macs.

70

I tried to run a core config check before updating, I got this:

[07:11:30] INFO: Don't worry, this temporary installation is not overwriting your current one.
[07:11:30] INFO: Installing Home Assistant: stable...
[07:11:30] INFO: Please be patient, this might take a few minutes...
[07:13:21] INFO: Installed Home Assistant 2022.7.0
[07:13:21] INFO: Making a copy of your configuration for checking...
[07:15:09] INFO: Checking your configuration against this version...
[07:26:10] ERROR: The configuration check did not pass!
[07:26:10] ERROR: See the output below for more details.
Testing configuration at /tmp/config
INFO:homeassistant.helpers.storage:Migrating core.entity_registry storage from 1.6 to 1.7
  
  Ɨ Building wheel for numpy (pyproject.toml) did not run successfully.
  ā”‚ exit code: 1
  ā•°ā”€> [258 lines of output]
      Running from numpy source directory.
      setup.py:86: DeprecationWarning:
      
        `numpy.distutils` is deprecated since NumPy 1.23.0, as a result
        of the deprecation of `distutils` itself. It will be removed for
        Python >= 3.12. For older Python versions it will remain present.
        It is recommended to use `setuptools < 60.0` for those Python versions.
        For more details, see:
          https://numpy.org/devdocs/reference/distutils_status_migration.html
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping

Anyone know what this means?

71

It happens to me too. I am looking for a solution.

72

Same for me here ā€¦

73

My backups look fine. I just made a new full backup of 2022.6.7, checked it and then re-updated to 2022.7.0 and all seems okay nowā€¦

74

having the same problem here. Using HA in a container and MySQL as a normal system service

in configuration.yaml I have

recorder: 
  db_url: !secret recorder_url

and the relevant line in secrets.yaml looks like this:

recorder_url: mysql://user:password@host/homeassistant?unix_socket=/mysqld.sock&charset=utf8mb4
1 Like
75

After update to version 2022.7.0 i have a problem with not showing sensor rain and gas sensor from my SATEL Alarm by ETHM-1 Plus.
On version 2022.6.7 all works ok. Please help meā€¦

1 Like
76

I have the same issue, unfortunately

77

Also for alarm from this integrationā€¦ panels alarma also not showing. But connection with alarm works ok.All sensors from integration SATEL not workingā€¦

78

Lots of great stuff here. Giant kudos to everyone who made this awesome update happen! Lots of things to be excited about in the Open Home Newsletter too. :clap: :clap: :clap:

However, I am disappointed (and I raised this during beta) in the changes to History. I used history as a glance panel, where I had filtered in Recorder just things for which I wanted history kept, and when I looked at the History page I could, with a glance at the colors, tell if things were working or if there were problems (e.g., I have many sensor/switches that come on and go off in a regular pattern, which was EASY to see previously across the entire range of devices/entities). Having to choose devices or entities makes History pretty much useless to me atm. There is NO easy way using the filtering options currently provided to do what I did before, so this is a regression to me.

I understand that with increases in DB efficiency and with many new users, filtering your DB is no longer that much of an issue to some. To me, thatā€™s not the point. Itā€™s about usability. If I wanted to see the history of a single entity previously, I clicked on the entity and viewed it there.

Perhaps we could include an EVERYTHING option, which would show everything in the DB (filtered by Recorder, if it exists) giving us what we had before (for those of us who liked it that way). That should be an easy add, since it was what it did before, right?

Am I the only one who misses that?

Also, Iā€™ve experienced no issues with the release to date, and LOVE that the Logs have been consolidated (and added to).

15 Likes
79

Or you could make your own dashboard of history graphs.

2 Likes
80

Exactly the same here ā€¦