2023.11 To-do: Add release title

[MDieperink]

Yes, for example. But 2023.11 also had a database upgrade. Which isn’t mentioned in the releasenotes. That’s why I’m asking.

[tom_l]

It wasn’t mentioned because it did not have one.

[MDieperink]

Why did my logs say “Database is about to upgrade from schema version: 41 to: 42” after upgrading from 2023.10 to 2023.11 then?

[tom_l]

Maybe because your stats migration failed previously and this is now caught and fixed:

Recover from previously failed statistics migrations

This is the only other db change I could find:

Increase max bind vars based on database version

[FredTheFrog (Keith)]

Updated to HA release 2023.11.3 this afternoon. Now it says I cannot use the weather information provided by the Ecobee integration as a platform for the weather: item in configuration.yaml. I’d guess this is somewhere in the ‘breaking changes’ area of a release notes page?

This post is mostly intended as FYI for other Ecobee users… I simply disabled the weather: item altogether. Can’t currently use the NWS integration because it’s not updating the sensor values, even though the Python component is parsing the JSON from NWS successfully.

[nickrout]

Yep, the 41 to 42 was committed on October 23

Recover from previously failed statistics migrations

[dicekillsyou161]

this must be something related to your config, my ecobee weather is still coming through without issue on 2023.11.3

edit: for clarity, I am using the ecobee integration, not the homekit integration.

I also have weather pulling from the Meteorologisk institutt (Met.no) integration so that I can also have an hourly forecast available in homeassistant, since the ecobee weather does not

[MDieperink]

It happened to me in the past that I tried to rollback just the HA container to a previous version, but then HA didn’t startup because the database schema version was newer than it expected. Because I didn’t rollback the database addon (I prefered to keep the data that was generated in the meantime).

So that’s why a little sentence in the releasenotes like 'this release has an upgrade to the database schema" would be real nice. So that people know they need to make sure to backup their database.

[tom_l]

Yes I understand why you want a warning in the notes and I agree it should be included when there is a schema update.

However as I said, this release did not actually include an update. It only included a fix in case you missed previous updates.

So most people who the update worked for in a previous release would not see an update this time.

Something went wrong with your install when it tried to update your install in a previous release or possibly because of this:

@MDieperink

I tried to rollback just the HA container to a previous version

Home Assistant now realises you are on the wrong DB version and updated it for you. This did not happen for everyone.

[VdR]

Had the same problem. That’s how I ended up here.

[image969 (James Scialdone)]

Hey this worked great for my media player. Only thing missing is when I click the handle its a diff color…

Is there a md-slider-ON-CLICK-handle-color: orange

[stamandr]

I can tell you for certain that my device ID’s changed. I did a comparison of an older core.device_registry to the one after the update. A big number of these changed…

The automations now have errors due to the ID’s changing.

[petro]

Please show the comparison then

[stamandr]

Here is an example…

Old: (2024.6.4)
{“area_id”:null,“config_entries”:[“c2cc4f4ef1e0bd78d35dd6921630d1c4”],“configuration_url”:null,“connections”:,“disabled_by”:null,“entry_type”:null,“hw_version”:null,“id”:“5ab4f196bb5cacaf1d03f64991ae80d4”,“identifiers”:[[“mobile_app”,“f0db0ce87b8ca83d”]],“labels”:,“manufacturer”:“samsung”,“model”:“SM-G991W”,“name_by_user”:null,“name”:“SM-G991W”,“serial_number”:null,“sw_version”:“34”,“via_device_id”:null},

New: (2024.7.1)
{“area_id”:null,“config_entries”:[“c2cc4f4ef1e0bd78d35dd6921630d1c4”],“configuration_url”:null,“connections”:,“disabled_by”:null,“entry_type”:null,“hw_version”:null,“id”:“15626cf34118514d603501c0b20f25ed”,“identifiers”:[[“mobile_app”,“f0db0ce87b8ca83d”]],“labels”:,“manufacturer”:“samsung”,“model”:“SM-G991W”,“name_by_user”:null,“name”:“SM-G991W”,“primary_config_entry”:“c2cc4f4ef1e0bd78d35dd6921630d1c4”,“serial_number”:null,“sw_version”:“34”,“via_device_id”:null},

[petro]

That would be a bug, I suggest you create an issue against the mobile app integration for Android.

Do you have other examples of “big” number of them changing?

[stamandr]

The biggest number of devices that changed were my Zigbee devices (ZHA). I had to redo all of my automations that had anything to do with ZHA. Unfortunately, I deleted the backups after sending you the example. This is the second time for me that this has happened in 2023.11 and 2024.7. I know others have reported this as well in the past.

[petro]

The point is, this should not happen. if/when it does happen, an issue should be written up against the offending integration. Your device IDs will not change. If they do, you encountered an issue.

[e-raser]

I noticed that after removing all TODO integrations (tested few locally), the sidebar icon redirecting to /todo still exits, showing nothing (empty page):

I expected that when the last todo.* entity has been removed, that item is also removed. Now the only (ugly as it needs to be done on every client) way to hide them (temporarily) is to use Manage sidebar/menu items (hide/add/move).

There’s also no config option at /config/lovelace/dashboards like for other dashboards (“show in sidebar” config option). Nothing

Has that been fixed in a later HA release maybe?

[petro]

Restart…

[e-raser]

Didn’t try yet
Good old Windows style right… haha