2024.2: More voice, more icons, more integrations, more... everything!

I have tried updating from 2024.1.6 to 2024.2.0 and it fails each time. I use the UK Met Office, I tried disabling this, but still the update fails.

All these updates are quite tedious, what we need is a long-term suported version that just works with new released properly tested before release.

2 Likes

This ZHA ziggbe automatic update seems like a future Iā€™m searched for long time but I have a few question

You could already edit the configuration yaml to add auto update is this the same? Or what about this futures

Where will the zha download firmware from?

Same issue here updating from 2024.1.6

It took me less than 15 minutes to update, including a backup of the previous version. You should look at your logs to see what is going wrong.

But what is the point of removing a working sensor that is in use and carries zero load in the system, especially for those who do not use it? To add load to the templates?

1 Like

Another Tapo custom component what you need for that!

I donā€™t know, I was not involved in the decision making here.
I just wanted to provide an alternative for after it is removed.

3 Likes

You could have a look at the HACS integration Places ā€” it does lookups based on gps cords and returns very precise address data from OpenStreetMap. You could then filter by postal code, building names or whatever to define zones.

1 Like

I understand, but this is a very strange solution, if there were problems with this sensor, it would depend on other libraries that are outdated, but here is banal mathematics that only works for those who have it in the configuration.

1 Like

guess you can read the discussion on that in the PR Deprecate legacy Proximity entity by mib1185 Ā· Pull Request #108730 Ā· home-assistant/core Ā· GitHub

what I did, and it works perfectly, is create a new template for the former proximity entities (I also liked to have those grouped attributes on a Zone centered entity)

template:

  - sensor:

      - unique_id: proximity_sensor_thuis
#         name: Proximity Thuis
        state: >
          {{states('sensor.thuis_nearest_distance')}}
        picture: /local/family/family_thuis.jpg
        device_class: distance
        unit_of_measurement: km
        attributes:
          direction: >
            {{states('sensor.thuis_nearest_direction_of_travel')}}
          nearest: >
            {{states('sensor.thuis_nearest_device')}}

I only need these 3 sensors per zone, and not all of the individual sensors for each tracker on that zone, so disable those.

There is noting in the log that relates to the update. Previously I saw script errors, so it does look like a faulty update script.

Home Assistant Core
CEMI Frame failed to parse: <CouldNotParseCEMI description="APDU LEN should be 225 but is 1 from 15.15.249 in CEMI: bce0fff91909e10000" />
08:30:51 ā€“ (WARNING) runner.py - message first occurred at 08:25:22 and shows up 110 times
Error: KNX bus did not respond in time (2.0 secs) to GroupValueRead request for: 2/6/1
08:30:51 ā€“ (WARNING) runner.py - message first occurred at 08:25:23 and shows up 217 times
Error fetching tesla_custom data: Error communicating with API:
08:28:17 ā€“ (ERROR) Tesla Custom Integration (custom integration)
The unit of sensor.smart_meter_electricity_lqi (%) cannot be converted to the unit of previously compiled statistics (). Generation of long term statistics will be suppressed unless the unit changes back to or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this
08:27:21 ā€“ (WARNING) Sensor - message first occurred at 08:27:21 and shows up 2 times
Waiting on integrations to complete setup: hikvision_next, velux
08:27:12 ā€“ (WARNING) bootstrap.py - message first occurred at 08:26:11 and shows up 2 times
Entity sensor.smart_meter_electricity_lqi (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement '%' which is not a valid unit for the device class ('signal_strength') it is using; expected one of ['dBm', 'dB']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
08:25:32 ā€“ (WARNING) Sensor
Platform knx does not generate unique IDs. ID 2/2/1_2 already exists - ignoring scene.tv_viewing
08:25:22 ā€“ (ERROR) Scenes - message first occurred at 08:25:22 and shows up 5 times
Entity sensor.smart_meter_electricity_import_unit_rate (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22
08:25:21 ā€“ (WARNING) Sensor - message first occurred at 08:25:21 and shows up 2 times

Top right corner, dropdown, Supervisor. Select that and see if any obvious in that log.

Overall much faster - at least right now it feels a lot faster and more responsive
Mel Cloud is working again - I hope my Mel App will also work too.

Great progress after
I had first figured out how to reconfigure the tuya authentification

Thanks

Thanks for the help BTW! The only salient lines are:

24-02-08 08:24:54 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
24-02-08 08:24:54 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!

The entire log is:

e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/systeme[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/coree[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/systeme[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_servere[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addone[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.check] System checks completee[0m
e[32m24-02-08 06:08:15 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m24-02-08 06:08:16 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m24-02-08 06:08:16 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state runninge[0m
e[32m24-02-08 06:08:16 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[32m24-02-08 06:10:13 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repositorye[0m
e[32m24-02-08 06:10:13 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repositorye[0m
e[32m24-02-08 06:10:13 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repositorye[0m
e[32m24-02-08 06:10:16 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 removee[0m
e[32m24-02-08 06:10:16 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 removee[0m
e[32m24-02-08 06:10:20 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m24-02-08 06:40:20 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state runninge[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/systeme[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisore[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/systeme[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_servere[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/systeme[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/systeme[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/coree[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/systeme[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_servere[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addone[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.check] System checks completee[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state runninge[0m
e[32m24-02-08 07:08:16 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[32m24-02-08 07:10:09 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.jsone[0m
e[32m24-02-08 07:10:21 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m24-02-08 07:40:22 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m24-02-08 07:43:34 INFO (MainThread) [supervisor.host.info] Updating local host informatione[0m
e[32m24-02-08 07:43:35 INFO (MainThread) [supervisor.host.services] Updating service informatione[0m
e[32m24-02-08 07:43:35 INFO (MainThread) [supervisor.host.network] Updating local network informatione[0m
e[32m24-02-08 07:43:35 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio informatione[0m
e[32m24-02-08 07:43:35 INFO (MainThread) [supervisor.host.manager] Host information reload completede[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state runninge[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for docker_config/systeme[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for trust/supervisore[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for no_current_backup/systeme[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_ipv6_error/dns_servere[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for free_space/systeme[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for ipv4_connection_problem/systeme[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for security/coree[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for multiple_data_disks/systeme[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for dns_server_failed/dns_servere[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for pwned/addone[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.check] System checks completee[0m
e[32m24-02-08 08:08:16 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m24-02-08 08:08:17 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m24-02-08 08:08:17 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state runninge[0m
e[32m24-02-08 08:08:17 INFO (MainThread) [supervisor.resolution.fixup] System autofix completee[0m
e[32m24-02-08 08:10:23 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API tokene[0m
e[32m24-02-08 08:19:58 INFO (MainThread) [supervisor.backups.manager] Backup ac3498cf starting stage addon_repositoriese[0m
e[32m24-02-08 08:19:58 INFO (MainThread) [supervisor.backups.manager] Backup ac3498cf starting stage docker_confige[0m
e[32m24-02-08 08:19:58 INFO (MainThread) [supervisor.backups.manager] Creating new partial backup with slug ac3498cfe[0m
e[32m24-02-08 08:19:58 INFO (MainThread) [supervisor.backups.manager] Backup ac3498cf starting stage home_assistante[0m
e[32m24-02-08 08:19:58 INFO (MainThread) [supervisor.homeassistant.module] Backing up Home Assistant Core config foldere[0m
e[32m24-02-08 08:20:11 INFO (MainThread) [supervisor.homeassistant.module] Backup Home Assistant Core config folder donee[0m
e[32m24-02-08 08:20:11 INFO (MainThread) [supervisor.backups.manager] Backup ac3498cf starting stage finishing_filee[0m
e[32m24-02-08 08:20:12 INFO (MainThread) [supervisor.backups.manager] Creating partial backup with slug ac3498cf completede[0m
e[32m24-02-08 08:20:12 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.2.0e[0m
e[32m24-02-08 08:20:12 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.1.6 to ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.2.0e[0m
e[32m24-02-08 08:20:12 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/generic-x86-64-homeassistant with tag 2024.2.0.e[0m
e[32m24-02-08 08:24:33 INFO (SyncWorker_1) [supervisor.docker.manager] Stopping homeassistant applicatione[0m
e[33m24-02-08 08:24:33 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closede[0m
e[32m24-02-08 08:24:43 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning homeassistant applicatione[0m
e[32m24-02-08 08:24:43 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulsee[0m
e[32m24-02-08 08:24:44 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/generic-x86-64-homeassistant with version 2024.2.0e[0m
e[32m24-02-08 08:24:44 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is readye[0m
e[31m24-02-08 08:24:54 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!e[0m
e[31m24-02-08 08:24:54 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!e[0m
e[32m24-02-08 08:24:54 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.loge[0m
e[32m24-02-08 08:24:54 INFO (MainThread) [supervisor.homeassistant.core] Updating Home Assistant to version 2024.1.6e[0m
e[32m24-02-08 08:24:54 INFO (MainThread) [supervisor.docker.interface] Updating image ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.2.0 to ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.1.6e[0m
e[32m24-02-08 08:24:54 INFO (MainThread) [supervisor.docker.interface] Downloading docker image ghcr.io/home-assistant/generic-x86-64-homeassistant with tag 2024.1.6.e[0m
e[32m24-02-08 08:24:55 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning homeassistant applicatione[0m
e[32m24-02-08 08:24:55 INFO (MainThread) [supervisor.homeassistant.module] Update pulse/client.config: /data/tmp/homeassistant_pulsee[0m
e[32m24-02-08 08:24:55 INFO (MainThread) [supervisor.docker.homeassistant] Starting Home Assistant ghcr.io/home-assistant/generic-x86-64-homeassistant with version 2024.1.6e[0m
e[32m24-02-08 08:24:55 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is readye[0m
e[32m24-02-08 08:25:03 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state runninge[0m
e[32m24-02-08 08:25:04 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation completee[0m
e[32m24-02-08 08:25:10 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to NOT_RUNNINGe[0m
e[32m24-02-08 08:25:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repositorye[0m
e[32m24-02-08 08:25:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repositorye[0m
e[32m24-02-08 08:25:10 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repositorye[0m
e[32m24-02-08 08:25:10 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.jsone[0m
e[32m24-02-08 08:25:13 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 removee[0m
e[32m24-02-08 08:25:13 INFO (MainThread) [supervisor.store] Loading add-ons from store: 77 all - 0 new - 0 removee[0m
e[32m24-02-08 08:25:15 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mosquito'e[0m
e[32m24-02-08 08:25:15 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cachee[0m
e[32m24-02-08 08:27:19 INFO (MainThread) [supervisor.homeassistant.core] Home Assistant Core state changed to RUNNINGe[0m
e[32m24-02-08 08:27:19 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instancee[0m
e[32m24-02-08 08:27:19 INFO (MainThread) [supervisor.homeassistant.core] Successfully started Home Assistant 2024.1.6e[0m
e[32m24-02-08 08:27:19 INFO (SyncWorker_2) [supervisor.docker.manager] Cleanup images: ['ghcr.io/home-assistant/generic-x86-64-homeassistant:2024.2.0']e[0m

This is understandable, but it is not clear why this was done. Those. we remove one entity, add at least 5, then hide the unnecessary ones and create a template.
Why do we increase entropy?

yah, I hear you.
but, this was a move from yaml to UI, and those integrations have to conform to the Architecture decisions, and one of those is to create individual entities for former attributes.

It is considered to be better for DB, and better for users (simpler).

3 Likes

For Deprecate ā€˜beatā€™ display option in Time & Date i open discussion: Deprecate `beat` display option in Time & Date Ā· home-assistant/architecture Ā· Discussion #1037 Ā· GitHub

I understand that this is a transition to the GUI, I also understand that this is an attempt to get rid of attributes, but in this case this attempt is not successful, we are changing one entity with 3 more or less static attributes to 5 entities that still have attributes. As a result, this is a large load on the database, there is no ease of use and there are no normal settings in the GUI (not creating separate entities for devices, for example).

1 Like

You should check homeassistant/home-assistant.log.1 through File Editor, if you have that addon.

That should be the log for the crashed 2024.2. (The log from the previous start.)

in my case, I dont have them recorded at all, so no DB issues.

but, if you wanted, you could now only record one of those new entities, where before you had to record the complete proximity entityā€¦

tbh, I do believe this UI is much ā€˜easierā€™ than the yaml config before.

define ā€˜normalā€™ settingsā€¦