2023.2: How can I Assist?

I took the plunge and updated but I only have a v small db. Upgrade was smooth. No issues so far

Hi,

Has anyone experienced issues with icon colours with the stock Light Card with 2023.2.x?

Specifically, I have a Hue group and Tuya lights not showing the icon colours they previously did with respect to the lights on/off/brightness.

This is an example from 2023.1.7

image

And this is the same from 2023.2.x

image

both are using the default HA theme.

Kitchen - Dining is a Hue group and in 2023.1.x works as expected, but in the second screenshot it is black (in dark mode it is grey)
Lounge & Porch - Wall Lights is a tuya light
And interestingly Lounge & Porch - Chair is a hue single bulb which behaves as expected!

Using an Entities card or a Button card the entitiesā€™ icons behave as expected i.e as per the 2023.1.x screenshot.
Thanks

BTW the sink, oven, fireplace, island are all Magic Home LED strips which work as expected.

1 Like

Yes I see that too. Black is the new yellow :slightly_smiling_face: Shrug.

Just a short question. How long does the database migration of 2023.2 take?
I recently upgraded and did a reboot while migrating and i think my database was corrupted.
Now i will wait some more but i dont know if i get a succesful message or something like that.

Any way to identify the finished state? This is the only thing i see in logs: Database is about to upgrade from schema version: 30 to: 33

Also RAM usage is pretty high with 90-95% on my VM.

Same here. Iā€™m stuck with MariaDB version provided by Synology. Iā€™m afraid that issues would happen and so , Iā€™ve removed the recorder DB from MariaDb and Iā€™m back to the HA disk :frowning: .
If this is a wait until Synology updates the packege, Im afraid it will take time ā€¦

Seems like something worth revising in the release notes, eh?

And yes when I first read it I wondered how it would effect last_changed and last_updated, and if there would be less database entries if many small changes were less than the rounded precision.

If you use a custom theme (or card) then it needs updating.

If you use the default theme and a core card and this is happening then it is a frontend bug. Please report it.

Isnā€™t it in the esphome doco what to change to

The repair popup links to the documents just as you did.
Canā€™t see anything wrong with this.

For me it exchanged the encryption key by itself.
Perhaps that is because I had to upgrade my node also?

I too was really looking forward to the precision updateā€¦

Thought I would be able to lose about 80-100 template sensors that round and truncate decimals on so many sensors (which I primarily implemented to reduce database writes and size to about 15% of the original writes/size)

1 Like

No.

It doesnā€™t explain what to remove or replace, only what is now required.

The forum article I linked to explains the process succinctly, the API documentation does not.

Hmm to me it was pretty clear

  • password (Optional, Deprecated, string): The password to protect the API Server with. Defaults to no password. It is recommended to use the encryption ā†’ key above instead of the the password.

remove password, replace with the encryption key

Hi

Apparently someone beat me to it.

Light card not showing correct color when light is on Ā· Issue #15319 Ā· home-assistant/frontend (github.com)

2 Likes

With regard to the upgrade of the database for MariaDB users: How will I know it has finished? Will I get a persistant notification? Can I tell in some other way?

I suspect it has finished but Iā€™m not sure.

Check the log. And your cpu use.

Thanks @tom_l

My CPU did spike for a minute. My log book is updating okay. Iā€™ll assume Iā€™m done. Maybe the i3 processor made it super quick.

Sorry, I mean there should be a message in the log (not logbook) that the migration is done.

This looks like a GREAT release, thanks HA folks!

2 Likes

Hi @tom_l

I have the following in the log but nothing that specifically tells me itā€™s done.

Logger: homeassistant.components.recorder.migration
Source: components/recorder/migration.py:138
Integration: Recorder (documentation, issues)
First occurred: 10:13:25 (1 occurrences)
Last logged: 10:13:25

Database is about to upgrade from schema version: 30 to: 33
Logger: homeassistant.components.recorder.migration
Source: components/recorder/migration.py:154
Integration: Recorder (documentation, issues)
First occurred: 10:13:25 (6 occurrences)
Last logged: 10:13:30

Adding columns last_updated_ts, last_changed_ts to table states. Note: this can take several minutes on large databases and slow computers. Please be patient!
Adding index `ix_events_time_fired_ts` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!
Adding index `ix_events_event_type_time_fired_ts` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!
Adding index `ix_states_entity_id_last_updated_ts` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!
Adding index `ix_states_last_updated_ts` to database. Note: this can take several minutes on large databases and slow computers. Please be patient!*emphasized text*

For me, in the Android app, when I select by entity nothing gets added to the card. So, add by entity is broken for me.