2024.10: Heading in the right direction

[parautenbach (Pieter Rautenbach)]

I don’t know how the new colour palettes got determined, but this isn’t ideal. Grey isn’t the best choice for a weather condition. It intuitively looks like something’s off (pun intended).

(Yes, I know there are various ways to customise this. This isn’t a good default, in my view.)

[meni123 (Meni)]

I have the same problem, too.
All the integrations from HACS that take data from the Internet do not work,

[parautenbach (Pieter Rautenbach)]

I’ve hacked together a replacement that displays my ping sensors how I want it. Unfortunately, the entities aren’t clickable (I could’ve used the custom button card if I wanted that, but decided to just leave it, since I already have graphs on my dashboard view). This replacement uses the built-in markdown card and card-mod.

This:

      - type: entities
        show_header_toggle: false
        entities:
          - entity: sensor.internet_round_trip_time_avg
            name: Mean Ping Time
          - entity: sensor.internet_round_trip_time_mdev
            name: Mean Ping Deviation
          - entity: sensor.internet_packet_loss
            name: Packet Loss

Becomes:

      - type: markdown
        content: >
          |   |   |   |
           | :--- | :--- | ---: |
           | <ha-icon icon="{{ state_attr('sensor.internet_round_trip_time_avg', 'icon') }}"></ha-icon> | Mean Ping Time | {{ states('sensor.internet_round_trip_time_avg', rounded=True, with_unit=True) }} |
           | <ha-icon icon="{{ state_attr('sensor.internet_round_trip_time_mdev', 'icon') }}"></ha-icon> | Mean Ping Deviation | {{ states('sensor.internet_round_trip_time_mdev', rounded=True, with_unit=True) }} |
           | <ha-icon icon="{{ state_attr('sensor.internet_packet_loss', 'icon') }}"></ha-icon> | Packet Loss | {{ states('sensor.internet_packet_loss', rounded=True, with_unit=True) }} |
        card_mod:
          style:
            ha-markdown:
              $:
                ha-markdown-element: |
                  table {
                    border-spacing: 0;
                    width: 100%;
                  }
                  th {
                    display: none;
                  }
                  td {
                    padding-bottom: 1em !important;
                  }
                  td:nth-child(1) {
                    width: 45px;
                    padding-left: 8px;
                  }
                  td:nth-child(2), td:nth-child(3) {
                    color: var(--primary-text-color);
                  }
                  ha-icon {
                    padding: 0px;
                    color: var(--paper-item-icon-color);
                  }

You can also use the friendly name of your sensors.

[Mariusthvdb (Marius)]

not sure of your specific needs, but did you try the custom template-entity-row card? it allows you to configure any of the entity’s properties inside an entities card, and keeps clickability and prevents the Markdown complexities

[parautenbach (Pieter Rautenbach)]

I like that. It’s not a “card” I’ve used. I’ll give that a go too. It should be a bit cleaner.

I did numerous searches to see if there was an entities card replacement and this didn’t come up.

[chairstacker]

Same here, but adding the following into my configuration.yaml seems to fix it:

homeassistant:
  customize:
    sensor.emoncms_node_XXXXXXX_w:
      unit_of_measurement: 'W'
      device_class: power

[Drealine]

Hi
We have some news entity regarding Aqara U200. Voltage of battery and identify. But no state when lock/unlock failed aka Jamed state. Any news about that ?

[GeoRW (JRobW81)]

Seems like the new version broke parameter settings for Z-Wave devices. The “Configure” device screen has changed a bit showing default value now, but changing the value does nothing. So, reverted back to 2024.9.3

[parautenbach (Pieter Rautenbach)]

Much cleaner – and I have my tap actions too. Thanks!

      - type: entities
        show_header_toggle: false
        entities:
          - type: custom:template-entity-row
            entity: sensor.internet_round_trip_time_avg
            icon: "{{ state_attr('sensor.internet_round_trip_time_avg', 'icon') }}"
            name: Mean Ping Time
            state: "{{ states('sensor.internet_round_trip_time_avg', rounded=True, with_unit=True) }}"
            tap_action:
              action: "more-info"
          - type: custom:template-entity-row
            entity: sensor.internet_round_trip_time_mdev
            icon: "{{ state_attr('sensor.internet_round_trip_time_mdev', 'icon') }}"
            name: Mean Ping Deviation
            state: "{{ states('sensor.internet_round_trip_time_mdev', rounded=True, with_unit=True) }}"
            tap_action:
              action: "more-info"
          - type: custom:template-entity-row
            entity: sensor.internet_packet_loss
            icon: "{{ state_attr('sensor.internet_packet_loss', 'icon') }}"
            name: Packet Loss
            state: "{{ states('sensor.internet_packet_loss', rounded=True, with_unit=True) }}"
            tap_action:
              action: "more-info"

[Mariusthvdb (Marius)]

I do believe more-info is default on sensors, so you can leave that out iirc
And do use things like {{states(config.entity)|int(0)}} to avoid repeating the entity in all templates

[Ildar_Gabdullin]

2024.10.2 brought a new surprise in Dev tools → Statistics:
there are “INFO” issues:

which were in fact “fixed” a month ago - I choose to delete old LTS.
Now after pressing the “INFO” button the same popup is shown as it was displayed for the old “FIX” issue:

And ofc a bunch of there repairs displayed - AGAIN:

A bit tired of these “Devtools-Stats / Repairs” changes.
What is a meaning of showing “INFO” issue which allows to perform same actions like the traditional “FIX” issue?
(not to mention that these statistics issues popup again & again after “fixing”)

Issue for this INFO things
Update: PR is made

[tom_l]

Anyone else having trouble with the Daikin integration after this update?

Daikin integration resets Zena wifi adaptor

[Duke_box]

Anyone having trouble with the Squeezebox integration (Lyrion Music Server)?

Since 2024.10.x I get this in the logs:

Logger: homeassistant
Source: components/squeezebox/media_player.py:224
First occurred: 21:45:16 (2 occurrences)
Last logged: 21:45:16

Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/squeezebox/media_player.py", line 141, in _discovered_player
    entity = SqueezeBoxEntity(player, lms)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/squeezebox/media_player.py", line 224, in __init__
    if player.model == "SqueezeLite" or "SqueezePlay" in player.model:
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable

And none of my players work.
I deleted the integration and re-installed and now I have the server with 10 sensors (which I didn’t have before) and NO devices.
So unable to use it.

Any ideas?

Edit: it works fine in 2024.9.3

[nickrout]

No such problem here, on 2024.10.2

[Duke_box]

Thanks for your response.
I’m on 2024.10.2 on a pi using HAOS v13.2
My working version is 2024.9.3 on a generic x86 HAOS v13.1
I don’t think the HAOS version is relevant as I was getting the errors in the logs before updating HAOS just now.

In my working instance I don’t have the server and its sensors. In the non working instance I only have the server and its sensors, no devices / media players

[Duke_box]

I looked more closely at the log.

Are you using SqueezeLite or SqueezePlay by any chance? I don’t have them as media players on the SqueezeBox server.

[nickrout]

Some run squeezelite, some are native logitech devices. Thay all appear in LMS and in the HA Integration for LMS.

[reste_narquois (Chris Warne)]

All working fine here (HA 2024.10.2). No Squeezelite or Squeezeplay players in my system, all original Squeezeboxes.

By the way, the sensors you are seeing were added in 2024.10.0, so their existence is to be expected (if your non-existent players are not to be expected of course).

Do the stat sensors you are seeing in the non-working updated version tally with the server in the working version (number of tracks and so on)? You haven’t got two LMS servers running by any chance?

[nickrout]

Or running Music Assistant?

[Duke_box]

@nickrout - not running Music Assistant.

@reste_narquois - yes the stat sensors tally with the LMS server. But since I don’t have the service in 2024.9.3 I can’t see those sensors for the LMS server in my working instance. And no I don’t have 2 LMS servers running.

It seems to me to be something with the update from 2024.9.3 to 2024.10.x as the integration was noted in the release notes as an “improvement to existing integration”