2024.8: Beautiful badges!

You can use a grid card to get three columns. Just place that inside your card, but I get that it would be nice to have this as an option for the sections layout natively.

  1. You donā€™t have to update.
  2. If you want a consumer-grade home automation, then go to Home Depot and buy a Lutron system.

I look forward to updates. There are almost always new features and integrations or improved components, and yes, sometimes we get a breaking change. That is the price of being on the bleeding edge of IOT. These breaking changes are often necessary to add new features or to add conformity at the developer level. (I do usually wait for the .1 release).

Using Home Assistant allows the user to automate just about anything, mostly limited only by your imagination. (And budget). You will never get that flexibility from an ā€œOff the Shelf Home Automationā€ system. (Of course, you will probably never have to update an OTS system).

4 Likes

Actually this has been one of the worst updates Iā€™ve applied in years.

Busted two major core integrations I use a lot and a couple of custom cards.

Is the the end of the world?

No.

Is it frustrating?

Heck yes.

Progress is being made on fixing the integrations. And it is partly my fault for not participating in the beta as I usually do. If the issues were noted in the beta they may have been fixed before release or held back from release until they were fixed.

3 Likes

Wait. What? Please elaborate. I thought history was history.

More or less nothing to elaborate, as it is as it is: LTS are kept forever no matter what purge days setting you have

5 Minute max, min, average, (or total) LTS data is kept until your purge keep days. After that time it is down-sampled to hourly data and kept until your database dies without a backup :slight_smile:

LTS data is only kept for sensors with a valid state_class.

1 Like

Guys, new icons are great!
But what have real working WLED devices done to you? Why doesnā€™t the new update allow me to use my lamp that I spent a lot of time and effort creating? I have a couple of lamps on the ESP8266 with a microphone for color music. And the latest version of the SoundReactive firmware is 0.12.0. And you demand a minimum version of 0.14.0!
But such a version does not exist for the ESP8266! What should I do? Disassemble the sealed glass structure and completely remake it for a different controller? Where did the flexibility of the home assistant go? Are beautiful icons really worth breaking devices that have been working for years?

2 Likes

I had the same experience when I suggested an update to the bluetooth tracker docs that a warning that the classic BT tracker didnā€™t work anymore after the upgrade of python would be beneficial to the community - but no that was an ā€œissueā€ so not appropriate for the docs!!!

6 Likes

Sound reactive is a wled fork. It is an archived repo on GitHub. You canā€™t expect the HA devs to keep supporting an out of date repo.

But you might have luck with the moon modules fork. It supports esp8266

1 Like

In my case, it was about the wake on LAN integration to wake a device on network and return whether it is on or off. Frenck argued that it is a technology outside HA and that HA documentation does not need to mention, which port I have to use. So I spent a whole day figuring out why it does not work because the documentation DID !!! not mention the port.

I just checked it, the documentation is wholly rewritten, the port is mentioned even in the flow during adding the integration and our discussion on the GitHub is not there. We wouldnā€™t be where we are without the amazing passion of Frenck but this is really unnecessarily childish.

1 Like

I have a request. Without the icon text displayed it is hard to know the badge is about.
Could we show the Icon Text when hovering over the badge, like a tooltip?

Hi all,

Not sure this is correct thread but my issue started after upgrade to 2024.8.1. I canā€™t connect from outside anymore despite my still valid Letā€™s Encrypt certificate. Also, certificate expiry addon says about refused connection. If i restore 2024.7.4, all works again. I know there are several moving parts in the problem, e.g. haos upgrade to 13, few bumps of Letā€™s Encryptā€¦ 2024.8.2 hasnā€™t fixed anything.

Sorry if this is in wrong place. Maybe someone could advice where I should start looking from.

Cheers.

EDIT: seems some problem with all those updates. Restored to 2024.8.0, applied all updates one by one, everything was on HAOS 13. The last thing to apply was 2024.8.2 - all works ok :confused:

Hello.
Is it possible to resize the section width?

After I updated to 2024.8.2, from 2024.8.1, I get ā€œDatabase upgrade in progressā€ AGAINā€¦ amazing, not!

Soā€¦ This could be a new thing with every update?! Thereā€™s nothing about this, written in the change logā€¦

That is my configuration.yaml

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:

themes: !include_dir_merge_named themes
 
automation: !include automations.yaml
 
script: !include scripts.yaml
 
scene: !include scenes.yaml

scripts.yaml, scenes.yaml are empty.

I donā€™t know anything about that themes: And there are some blueprints probably made by system for motion sensors, motion_light.yaml, notify_leaving_zone.yaml and confirmable_notification.yaml

automations.yaml

- id: '1722448417755'
  alias: chodba_pohyb
  description: ''
  trigger:
  - type: motion
    platform: device
    device_id: 3a97b2732d5965cb4bf351df0372eabc
    entity_id: 8847dbccc7403ed3a0c1d4fa2023422a
    domain: binary_sensor
  condition: []
  action:
  - type: turn_on
    device_id: da6da9f2045475a3e2dba68479a4a3d9
    entity_id: 180223f81e622000f0bd8f560fb2b687
    domain: light
  mode: single
- id: '1722448464485'
  alias: chodba_klid
  description: ''
  trigger:
  - type: no_motion
    platform: device
    device_id: 3a97b2732d5965cb4bf351df0372eabc
    entity_id: 8847dbccc7403ed3a0c1d4fa2023422a
    domain: binary_sensor
  condition: []
  action:
  - type: turn_off
    device_id: da6da9f2045475a3e2dba68479a4a3d9
    entity_id: 180223f81e622000f0bd8f560fb2b687
    domain: light
  mode: single
- id: '1722448851917'
  alias: kuchyn_pohyb
  description: ''
  trigger:
  - type: motion
    platform: device
    device_id: 6c00a55febfd4921150b6fb8bd6bd9f1
    entity_id: f10942b408e5112d917fb75b440aab94
    domain: binary_sensor
  condition: []
  action:
  - choose:
    - conditions:
      - type: is_illuminance
        condition: device
        device_id: 0728a8c881b106ef8d1d90d8f01688f2
        entity_id: 602735c498ecb9b628052e32c657c7e9
        domain: sensor
        below: 50
      sequence:
      - type: turn_on
        device_id: e26fa02bd1e64642b61a387fedabdd6c
        entity_id: 6804232ac54fddd31b9df02cacf08b03
        domain: light
      - type: turn_on
        device_id: cf4caea58aefc6827a186c74d643f318
        entity_id: 2d5e4260e6d9249a388be7685da20b97
        domain: light
    - conditions:
      - type: is_illuminance
        condition: device
        device_id: 0728a8c881b106ef8d1d90d8f01688f2
        entity_id: 602735c498ecb9b628052e32c657c7e9
        domain: sensor
        above: 50
      sequence:
      - type: turn_on
        device_id: e26fa02bd1e64642b61a387fedabdd6c
        entity_id: 6804232ac54fddd31b9df02cacf08b03
        domain: light
  mode: single
- id: '1722448889373'
  alias: kuchyn_klid
  description: ''
  trigger:
  - type: no_motion
    platform: device
    device_id: 6c00a55febfd4921150b6fb8bd6bd9f1
    entity_id: f10942b408e5112d917fb75b440aab94
    domain: binary_sensor
  condition: []
  action:
  - type: turn_off
    device_id: cf4caea58aefc6827a186c74d643f318
    entity_id: 2d5e4260e6d9249a388be7685da20b97
    domain: light
  - type: turn_off
    device_id: e26fa02bd1e64642b61a387fedabdd6c
    entity_id: 6804232ac54fddd31b9df02cacf08b03
    domain: light
  mode: single
- id: '1722450530275'
  alias: otevrene_dvere
  description: ''
  trigger:
  - type: opened
    platform: device
    device_id: 90bff7249fce900fc7dd0d101c7947f7
    entity_id: 1e0c86f1b8313741a9ca7f6608ede109
    domain: binary_sensor
  condition: []
  action:
  - service: notify.notify
    metadata: {}
    data:
      title: OtevřenĆ© dveře
      message: Někdo otevřel dveře
  mode: single
- id: '1722464218947'
  alias: loznice_svetlo
  description: ''
  trigger:
  - platform: event
    event_type: ios.action_fired
    event_data:
      actionID: FF876831-3BB0-41C9-8D5C-BA21E0B13F1D
  condition: []
  action:
  - service: light.turn_on
    metadata: {}
    data:
      brightness_pct: 1
      transition: 1
    target:
      device_id:
      - 0457f989248c900c1582958742e57f78
      - 01a21c218f0026d3ce6bf2fd1e303d59
  - delay:
      hours: 1
      minutes: 0
      seconds: 0
      milliseconds: 0
  - service: light.turn_off
    metadata: {}
    data: {}
    target:
      device_id:
      - 0457f989248c900c1582958742e57f78
      - 01a21c218f0026d3ce6bf2fd1e303d59
  mode: single
- id: '1722787881374'
  alias: vypadek_proudu
  description: ''
  trigger:
  - platform: homeassistant
    event: start
  condition: []
  action:
  - service: light.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: light.svetla
  - service: switch.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: switch.zasuvky
  - service: notify.mobile_app_telefon
    metadata: {}
    data:
      message: HA zapnuto
      title: Reset
  mode: single
- id: '1722812276975'
  alias: konec_prani
  description: ''
  trigger:
  - type: no_vibration
    platform: device
    device_id: 6297bf3787ab4b307ab542214a51b347
    entity_id: ead0b61a73e760b54aa61b3735dfc1bf
    domain: binary_sensor
    for:
      hours: 0
      minutes: 20
      seconds: 0
  condition: []
  action:
  - service: notify.notify
    metadata: {}
    data:
      message: Pračka doprala
      title: Pračka
  mode: single
- id: '1722954538293'
  alias: vypnout_svetla
  description: ''
  trigger:
  - platform: zone
    entity_id: person.ja
    zone: zone.home
    event: leave
  condition: []
  action:
  - service: light.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: light.svetla
  - service: switch.turn_off
    metadata: {}
    data: {}
    target:
      entity_id: switch.zasuvky
  mode: single
- id: '1722968693641'
  alias: stetka_dock
  description: ''
  trigger:
  - platform: device
    device_id: 3966060ba97a2c91f48b67d969b78446
    domain: vacuum
    entity_id: dded4482a2b7d8ff2b5f785d1bf572c5
    type: docked
  condition: []
  action:
  - if:
    - type: is_on
      condition: device
      device_id: 3966060ba97a2c91f48b67d969b78446
      entity_id: 18b67ecd2af357226a86d806fc9e342c
      domain: binary_sensor
    then:
    - service: notify.mobile_app_telefon
      metadata: {}
      data:
        message: Å tětka uklidila, vysyp jĆ­ koÅ”
        title: Å tětka uklidila a mĆ” plnej koÅ”
    else:
    - service: notify.mobile_app_telefon
      metadata: {}
      data:
        message: Štětka uklidila
        title: Štětka uklidila
  - service: light.turn_off
    target:
      entity_id:
      - light.svetlo_chodba_dvere_light
      - light.svetlo_kuchyn_strop_linka_light
      - light.svetlo_loznice_strop_light
      - light.svetlo_obyvak_strop_dvere_light
      - light.svetlo_obyvak_strop_okno_light
      - light.svetlo_pracovna_light
    data: {}
  mode: single
- id: '1722970841325'
  alias: stetka_uklid
  description: ''
  trigger:
  - platform: state
    entity_id:
    - vacuum.stetka
    from: docked
    to: cleaning
  condition: []
  action:
  - service: light.turn_on
    metadata: {}
    data: {}
    target:
      entity_id:
      - light.svetlo_pracovna_light
      - light.svetlo_chodba_dvere_light
      - light.svetlo_kuchyn_strop_linka_light
      - light.svetlo_loznice_strop_light
      - light.svetlo_obyvak_strop_dvere_light
      - light.svetlo_obyvak_strop_okno_light
  mode: single
- id: '1723065785465'
  alias: loznice_strop
  description: ''
  trigger:
  - platform: event
    event_data:
      actionID: 5935C980-8E8E-463A-9E7E-EC34A5B0CE52
    event_type: ios.action_fired
  condition: []
  action:
  - type: turn_off
    device_id: 0457f989248c900c1582958742e57f78
    entity_id: 80d258d1c63b354ca2471f015968da58
    domain: light
  - type: turn_off
    device_id: 01a21c218f0026d3ce6bf2fd1e303d59
    entity_id: 33d6d2d3707f75239d12e4bf8748e3d6
    domain: light
  - type: turn_on
    device_id: 3863caa0ea78ee789dde217b8ae7a64e
    entity_id: 3120ebcac3b9a5a91f19cf340a29e13b
    domain: light
  - delay:
      hours: 1
      minutes: 0
      seconds: 0
      milliseconds: 0
  - type: turn_off
    device_id: 3863caa0ea78ee789dde217b8ae7a64e
    entity_id: 3120ebcac3b9a5a91f19cf340a29e13b
    domain: light
  mode: single
- id: '1723285949714'
  alias: stetka_zacit_vysavat
  description: ''
  trigger:
  - platform: device
    device_id: c4b153833e4b4e258ca72b4df1f33017
    domain: device_tracker
    entity_id: 2c9bfd59ac0eba08d54505d519036d0b
    type: leaves
    zone: zone.home
  condition: []
  action:
  - service: vacuum.start
    metadata: {}
    data: {}
    target:
      device_id: 3966060ba97a2c91f48b67d969b78446
  mode: single

This is an interesting message:

The unit of this entity changed to 'ERR' which can't be converted to the previously stored unit, 'Wh'.
If the historic statistic values have a wrong unit, you can update the units of the old values. The values will not be updated.
Otherwise you can choose to delete all historic statistic values, and start over.

I found it in the developer tools / statistics when searching for the reason for the error in the homeassistant log.

Logger: homeassistant.components.min_max.sensor
Source: components/min_max/sensor.py:319
integration: Combine the state of several sensors (documentation, issues)
First occurred: 10:20:58 PM (4 occurrences)
Last logged: 10:22:13 PM
Units of measurement do not match for entity sensor.solarproduktion_gesamt

To fix the issue there are two options, I donā€™t like any of them:
Update the unit of the historic statistic values from ā€˜Whā€™ to ā€˜ERRā€™, without converting.
Delete all old statistic data for this entity

Since the historic data is about the energy produced by my solar panels and I might need it for the government, I neither want to delete it nor to convert it to unit ERR, energy deserves the unit kWh

Any idea how to fix?

No, only when required and yes it is in the release notes.

https://www.home-assistant.io/blog/2024/08/07/release-20248/#202482---august-16

This one should be a lot quicker. It took 6 seconds for me.

With regards new KNX feature, what about the entities already configured using yaml? I noted that they are not loaded into the ā€œentity pageā€ of the gui. Is it normal? @farmio
May I have some conficts adding new entities by GUI if I have already a lot of entities configured by yaml (splitted config)?

I got a failed database upgrade and a lot of errors.

Hi :wave:!
Yes, thatā€™s expected. See Manually created entities not shown in KNX-Frontend Ā· Issue #140 Ā· XKNX/knx-frontend Ā· GitHub
There shouldnā€™t raise any conflicts using both, UI and YAML.

1 Like