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

Blog
127

Barely - no explanation of context, no logs, and no description of what you expected to see. If you provide that information, then I’m sure people will try to help

1 Like
129

Hi,
Decluttering-card seems to stop working with the nex version. Has someone the same problem?

130

The main MQTT information can only be integrated from the UI

If I remember correctly, your configuration was migrated to the UI, so all you need to do is remove broker: ip from your configuration.yaml and you should be good to go.

1 Like
131

Please update your custom cards.

132

Regarding this:

2023-04-06 13:52:18.037 WARNING (MainThread) [frontend.js.latest.202304050] WARNING: Polymer will be removed from window in Home Assistant 2023.5. More info: Deprecating Polymer | Home Assistant Developer Docs

Agree, this warning is not helpful, we cannot see which card causes this.

133

Replacing /config/www/community/kiosk-mode/kiosk-mode.js with the one here then restarting HA, clearing your browser caches works. No need to amend any lovelace references anywhere.

1 Like
134

See here

135

I’m fairly certain it’s not possible to see what’s using the the resource. All HA can see is that someone is loading it.

136

Use VSCode and search for polymer in all files

137

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

1 Like
138

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

Scherm­afbeelding 2023-04-06 om 13.49.40
Scherm­afbeelding 2023-04-06 om 13.49.40716×478 56.1 KB

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

5 Likes
139

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

4 Likes
140

Thank you, will check it.

141

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

1 Like
142

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?

143

Thank you. It’s OK now.
Rgds

144

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

145

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.

1 Like
146

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.

1 Like
147

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