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

[makai]

Use VSCode and search for polymer in all files

[VDRainer]

@silfax

SQL sensors not working (again!):

Take a look here and change your sql queries.
The entity_id’s are no longer stored in the states table.

[Mariusthvdb (Marius)]

@Ildar_Gabdullin

Polymer

the average text editor will search your www folder and return something like this

Note decluttering is listed twice, because I have 2 different versions…

[JRO]

For those who don’t like breaking their beloved HA but can’t resist clicking on the update button, do like me:

• Create an automation, triggered by the HA components update action, who skip automatically the update until the right moment (here I avoid everything until we are the 15th of the month so that let’s the time to the others devs to update their own code like HACS).

alias: HomeAssistant - Skip early update of the current month
description: "Avoid showing update notification of Home Assistant before the 15th of the current month "
trigger:
  - platform: device
    type: turned_on
    device_id: <id>
    entity_id: update.home_assistant_supervisor_update
    domain: update
  - platform: device
    type: turned_on
    device_id: <id>
    entity_id: update.home_assistant_core_update
    domain: update
  - platform: device
    type: turned_on
    device_id: <id>
    entity_id: update.home_assistant_operating_system_update
    domain: update
condition:
  - condition: or
    conditions:
      - condition: template
        value_template: "{{ now().day < 15 }}"
action:
  - service: update.skip
    data: {}
    target:
      entity_id:
        - update.home_assistant_supervisor_update
        - update.home_assistant_core_update
        - update.home_assistant_operating_system_update
mode: single

• You could also add another automation to reveal the skipped patch the 15th but in reality, it’s not useful as the devs are quite motivated and deliver at least one additional patch before the end of the month.

Thanks HA team ! Love your free product.
PS: I can’t wait adding that in my car and display some traffic alert or reminders from HA

[Ildar_Gabdullin]

@Mariusthvdb

average text editor will search your www folder and return something like this

Thank you, will check it.

[silfax]

you’re the man! thanks a lot, that was it!

[HaEsphomeTstr]

I’m running Mariadb and Grafana in HA. This release recommends using HA SQL lite. Are there any guides for migrating from Mariadb back to HA SQL lite in Home Assistant?

[PGAA (Pierre GANANSIA)]

Thank you. It’s OK now.
Rgds

[PGAA (Pierre GANANSIA)]

@petro

lease update your custom cards.

Excuse me but what do you mean by “Please update your custom cards.”. You mean the HACS files (*.js)?

[silfax]

@silfax

1. Very high processor usage from HA core, some 3 hours after updating
   
   
2. SQL sensors not working (again!):
   
   

Any advice? Thanks!

Answering my own post, just in case someone encounters the same problem. The two issues were related, being actually caused by the outdated syntax of the SQL sensors I am using. The (never ending, it seems) changes to the database resulted in some incorrect queries, which, at their turn, were putting the CPU under a continuous heavy load. Solved by correcting the queries, with the invaluable help of @VDRainer.

[petro]

Decluttering card is a custom card, 2023.4 broke many custom cards. Many of those custom cards have new versions that work with 2023.4. Decluttering card is one of them. So, update your custom card (decluttering card) to the latest version.

[PGAA (Pierre GANANSIA)]

I already done it to version 1.0.0.
I am uding lovelace thriugh configuration.yaml.
May be there is something else to do?
Rgds

[petro]

Refresh your page. Keep in mind that updating decluttering card will only fix decluttering card. It will not fix other custom cards. You’ll have to apply updates for every broken custom card.

[jarekmor]

I have had problem with the Data Science for long time but decided to write about it now.
I have HA Supervised (healthy and supported). I do not remember exacly when it stopped working.
HASS-data-detective works and is connecting to the database (MariaDB). But there is the following error as in the attached picture.

I can work with engine = create_engine(db_url) but now there is the same error:

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
File <timed exec>:8

AttributeError: 'Engine' object has no attribute 'execute'

Hope you can advise me how to solve the problem.

[Mariusthvdb (Marius)]

decluttering is also mentioning the Polymer copyrights, so hope this will not break since again because of that.
There’s not a lot of evidence the card actually uses it besides the 26 mentions though.
so keeping fingers crossed

[yravoul]

After the update the (non-custom) button-card totaly breaks when the unit_of_measurement of the entity is ‘%’ and show_state is true. The card failes to render.

[Mariusthvdb (Marius)]

have to reiterate on that I am afraid…

I have disabled all of those cards in my config, (they are indeed actually no longer functional, and restarted nevertheless) and still see the warning. So there is more t that than simply text searching for Polymer

since this will happen next release, see Deprecating Polymer | Home Assistant Developer Docs maybe we can get some guidance in ‘loading Polymer ourselves’ by the dev frontend team?
maybe we can do so, for the time being, as a standalone custom resource?

given several of these cards have not been updated for a while now, it would keep many of us from breaking frontends.

[mamoel]

@HaEsphomeTstr

This release recommends using HA SQL lite

Where can I find this recommendation?

[petro]

There is no formal recommendation outside the livestream event.

[Mariusthvdb (Marius)]

there is this 2023.4: Custom template macros, and many more new entity dialogs! - #15 by bdraco
but who’s to tell if you config fits that description

sqlite is likely just fine for most use cases.