2023.4: Custom template macros, and many more new entity dialogs!

[nickrout]

Yes it is frustrating that custom card developers do not keep up and fix their cards. It happens release after release. Goddamn slackers.

[diplix (felix schwenzel)]

there is a regression in command line sensors and also a quick fix suggested:

Fix value_template not being used if json_attributes set

the fix works for me (command line sensor states are generated again and not unknown) but the PR was rejected (or rather a completly different implementation was suggested).

i worked around this by copying homeassistant/components/command_line to custom_components and changing line 141 in sensor.py as suggested until there is a fix.

[njs75 (Nathan)]

Thanks for the reply-- but in what context? I am running HA in docker-compose… Wouldn’t this just be included in the image?

[bdraco (J. Nick Koston)]

Yes it should be, but you might have a custom component that is pinning it to an older version

[njs75 (Nathan)]

Ah ok. Any idea what I might look for to identify the offending custom component? I’m a Java developer-- my python-foo is weak

[SteveDinn]

It seems like it’s consistently “migrating states context_ids” and “migrating entity_ids”

Is this behaviour to be expected in a normal database upgrade?

app_1  | 2023-04-05 22:24:14.475 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: StatesContextIDMigrationTask()
app_1  | 2023-04-05 22:24:14.475 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating states context_ids to binary format
app_1  | 2023-04-05 22:24:14.922 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating states context_ids to binary format: done=False
app_1  | 2023-04-05 22:24:14.922 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EntityIDMigrationTask()
app_1  | 2023-04-05 22:24:14.923 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating entity_ids
app_1  | 2023-04-05 22:24:15.383 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating entity_ids done=False
app_1  | 2023-04-05 22:24:15.383 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: StatesContextIDMigrationTask()
app_1  | 2023-04-05 22:24:15.383 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating states context_ids to binary format
app_1  | 2023-04-05 22:24:15.800 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating states context_ids to binary format: done=False
app_1  | 2023-04-05 22:24:15.801 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: EntityIDMigrationTask()
app_1  | 2023-04-05 22:24:15.801 DEBUG (Recorder) [homeassistant.components.recorder.migration] Migrating entity_ids

[bdraco (J. Nick Koston)]

@SteveDinn

app_1  | 2023-04-05 22:24:14.475 DEBUG (Recorder) [homeassistant.components.recorder.core] Processing task: StatesContextIDMigrationTask()

@SteveDinn

Is this behaviour to be expected in a normal database upgrade?

Yes its doing them in batches to avoid overloading the system. Its slower but it allows for online migration. I expect you have a very large database (or slow disk). I’d let it run overnight and check it in the morning.

[donaldtrump]

Tile card feature development is agonizingly slow. The front end needs to mature way faster in general. The fact that I need custom button card and card mod for most UI tweaks is crazy. Why can’t I have a tile card that slides vertically? The popup UI has it, so wth? Why can’t I just not have an icon in tile card? Why can’t I change the width of sliders with a simple parameter change vs card mod? Why can’t I just…use the slider UI without all the extras, for that matter?

[formatBCE (Andrii)]

So all in all, how to hide top bar on both web and Android companion app? I used to use minimalist-mobile theme, but today it broke, which is even worse for my LG clock 2 devices, where top bar eats 20% of space.

Looks like no one of HA devs uses any mods at all.

[SteveDinn]

Yeah, my database is about 11Gb. Since the migration notification went away, I thought I could have expected that it would be completely finished. I guess I’ll just wait and see.

[markfrancisonly]

The update appears to have broken the mobile left-edge swipe-in gesture for expanding collapsed sidebar nav menu. Super hoping this is a temporary feature loss with the complete removal of polymer?

The HA header is hidden on all of our mobile phones (along with sidebar expand menu button in the header). Since there is no happy medium between the mutually exclusive choice of a dashboard view title or icon button, and anyway the hass-swipe-navigation is so much better for phones.

[sparkydave (🇦🇺 Dave)]

2023.4: Custom template macros, and many more new entity dialogs!

It seems that swiping the sidebar open no longer works in Android companion app?

2023.4: Custom template macros, and many more new entity dialogs!

From what I understand, It will be back at a later date. It only works for closing the sidebar at the moment.

[francisp (Francis)]

Nice release. Upgrading from the beta now.

[Proche72 (Jiri Pragr)]

Same here. Mine is also now covering rest of the cards

[formatBCE (Andrii)]

What do you use to hide top bar?

I use mushroom menu chip to open menu BTW.

[Eoin]

Thank you team for another great update! I was affected by the Kiosk Mode custom component but luckily that was a 1min fix, other than that flawless!

[Masteroshi]

I have around 20% memory usage drop on RPI3 with this release, thank you!

[kaizersoje]

Same here.

[kaizersoje]

Can the macros defined in the custom_templates folder be used in the yaml files as well or just only in the Template section of Developer Tools?