4.5.0 not showing actual binary_sensor value anymore but on|off instead

[bcutter]

Entity:

YAML:

      - type: custom:multiple-entity-row
        entity: update.deconz_update
        name: deCONZ
        toggle: false
        state_color: true
        show_state: false
        secondary_info: null
        style: |
          :host .entities-row {
            justify-content: flex-start;
            align-items: unset;
          }
          :host .entities-row div.entity:nth-child(1)  {
            {% if states('sensor.deconz_cpu_percent') | float(0) > 5 %}
              color: orange;
            {% endif %}
            {% if is_state('sensor.deconz_cpu_percent','unavailable') %}
              color: red;
            {% endif %}
          }
          :host .entities-row div.entity:nth-child(2)  {
            {% if states('sensor.deconz_memory_percent') | float(0) > 5 %}
              color: orange;
            {% endif %}
            {% if is_state('sensor.deconz_memory_percent','unavailable') %}
              color: red;
            {% endif %}
          }
          :host .entities-row div.entity:nth-child(3)  {
            {% if states('binary_sensor.deconz_running') == "on" %}
              color: green;
            {% endif %}
            {% if states('binary_sensor.deconz_running') == "off" %}
              color: red;
            {% endif %}
          }
        entities:
          - entity: sensor.deconz_cpu_percent
            name: CPU
          - entity: sensor.deconz_memory_percent
            name: RAM
          - entity: binary_sensor.deconz_running
            name: Status
        state_header: ''
        column: false

4.4.1 ✔:

4.5.0 ❌:

---

What's the issue here?

• Do I need to change something?
• Or is it a newly introduced bug in 4.5.0?

---

And I could not find anything related to this small note in the release description:

Sounds a bit like a "I did not test it with an older version" excuse :-)

[nilsreiter]

I think it‘s the same issue as in #292, which was thought of as fixed, but isn‘t. I‘m seeing the same thing as @bcutter.

[bcutter]

So how to make any progress here? @benct

I prefer to not escape to a forked version like people in the other issue 😃

[nilsreiter]

Actually, my problem went away after emptying the cache. Did you do that @bcutter?

[bcutter]

Yes of course. Multiple times on various devices/browsers/apps.

The bug is in this piece of software.

And there's still not a single word (explanation) on this:

So I bet you're on HA Core >= 2023.4.x where frontend cache deletion seems to fix this. If people are not, it doesn't. Current theory.

[bcutter]

After updating HA Core to 2023.4.x and updating multiple-entity-row again to 4.5.0, the status shown was fixed. So to sum up:

• HA Core < 2023.4 + multiple-entity-row < 4.5.0: ✅
• HA Core >= 2023.4 + multiple-entity-row < 4.5.0: ❌
• HA Core < 2023.4 + multiple-entity-row >= 4.5.0: ❌
• HA Core > 2023.4 + multiple-entity-row >= 4.5.0: ✅

So it's definitely not a "might require". You should also use the dependency function in HACS so the 4.5.0 update would not be offered to installations nut fulfilling the requirements (HA Core 2023.4.x).

So: it's fixed for me but I would really like to see a statement of @benct here. Hopefully such situations will therefore be avoided in future.