0.105: Safe mode, Headers & Footers, New Zones Editor, Garmin, Sighthound

Thank you Taras for taking the time to help me out, I have used the first solution with success.

1 Like

So this doesn’t work:

      - type: vertical-stack
        cards:
          - type: entities
            title: Security & Home
            show_header_toggle: false
            card:
              state_color: true
            entities:
              - entity: input_boolean.alarmgaragedoor
                secondary_info: last-changed
              - entity: switch.sonoff51083
                secondary_info: last-changed
              - entity: switch.sonoff63719
                secondary_info: last-changed

But this does:

      - type: vertical-stack
        cards:
          - type: entities
            title: Security & Home
            show_header_toggle: false
            entities:
              - entity: input_boolean.alarmgaragedoor
                secondary_info: last-changed
                state_color: true
              - entity: switch.sonoff51083
                secondary_info: last-changed
                state_color: true
              - entity: switch.sonoff63719
                secondary_info: last-changed
                state_color: true
1 Like

I didn’t try the combination shown in your first example (using both an entity-wide option, state_color, and entity-specific options, secondary_info). Perhaps once you define an entity-specific option you are no longer permitted to define entity-wide options? Or it’s a bug. :man_shrugging:

1 Like

I always assume I’m missing/not understanding something rather than a bug.

I just have a bunch of binary sensors (ping sensors in this case, just to see if anything is down on my network. I display them in an entities card.

entities:
  - entity: binary_sensor.media_server
  - entity: binary_sensor.pi_hole
  - entity: binary_sensor.foyer_light_1
  - entity: binary_sensor.foyer_light_2
  - entity: binary_sensor.upstairs_hallway_light_1
  - entity: binary_sensor.upstairs_hallway_light_2
  - entity: binary_sensor.hd_homerun
  - entity: binary_sensor.philips_hue_hub
  - entity: binary_sensor.printer_study
  - entity: binary_sensor.weather_server
  - entity: binary_sensor.test32_status
  - entity: binary_sensor.kitchen_status
show_header_toggle: false
title: Hosts Up
type: entities
card:
  state_color: true

doesn’t work, it does with individual ones:

entities:
  - entity: binary_sensor.media_server
    state_color: true # and it works for each one I add this to
  - entity: binary_sensor.pi_hole
  - entity: binary_sensor.foyer_light_1
  - entity: binary_sensor.foyer_light_2
  - entity: binary_sensor.upstairs_hallway_light_1
  - entity: binary_sensor.upstairs_hallway_light_2
  - entity: binary_sensor.hd_homerun
  - entity: binary_sensor.philips_hue_hub
  - entity: binary_sensor.printer_study
  - entity: binary_sensor.weather_server
  - entity: binary_sensor.test32_status
  - entity: binary_sensor.kitchen_status
show_header_toggle: false
title: Hosts Up
type: entities

It doesn’t get nested under card: like you had it, that’s just for entity-filter card. For the standard Entities card it’s a top-level option just like show_header_toggle: and title etc.

Try this:

      - type: vertical-stack
        cards:
          - type: entities
            title: Security & Home
            show_header_toggle: false
            state_color: true
            entities:
              - entity: input_boolean.alarmgaragedoor
                secondary_info: last-changed
              - entity: switch.sonoff51083
                secondary_info: last-changed
              - entity: switch.sonoff63719
                secondary_info: last-changed

and for @nickrout same thing for yours.

entities:
  - entity: binary_sensor.media_server
  - entity: binary_sensor.pi_hole
  - entity: binary_sensor.foyer_light_1
  - entity: binary_sensor.foyer_light_2
  - entity: binary_sensor.upstairs_hallway_light_1
  - entity: binary_sensor.upstairs_hallway_light_2
  - entity: binary_sensor.hd_homerun
  - entity: binary_sensor.philips_hue_hub
  - entity: binary_sensor.printer_study
  - entity: binary_sensor.weather_server
  - entity: binary_sensor.test32_status
  - entity: binary_sensor.kitchen_status
state_color: true
show_header_toggle: false
title: Hosts Up
type: entities
5 Likes

Thanks Sean… one of your earlier examples threw me off… I thought I tried that before but apparently not as yours is working for me now. Cheers.

Thank you too @SeanM. As usual PEBKAC.

2 Likes

I upgraded to 0.105.2 and HassOS 3.9 today. The upgrade itself seemed to work great, but lots of things broke afterward.
ESPHome can no longer do OTA updates, Node-Red stop functioning altogether (redoing that installation).
I did 0.105.2 first then the OS, did I do the wrong order. Should I have expected so many issues with this update? All my components were up to their latest and greatest version before upgrading (jus to make sure).

1 Like

Why is there still no warning like “Do not install 105.2 it still not reliable with Z-wave…” or other things…
One solution would be to FORCE new version program to check if Check Home Assistant Configuration was run before. It would avoid bad surprises…

WTF? esphome is a completely separate application. How can updating home assistant or hassos affect it?

? This is not very adequate…

What? Inadequate because you don’t understand what it means?

I do not Z-Wave or Zigbee. All of my devices are strictly wired or WiFi.
I wanted to mention what the state of HA was following the update. Trying to figure out if it’s the update that caused the issues, or something else and the update simply brought it to the surface.

did you run the Check Configuration Tool? For me it gives errors and rolled back in 104.3

Doing full restore to pre-upgrade. I cannot get Node-Red working. ESPHome is one thing, and I can live with that short term. Node-Red, however, is critical. Will do full restore, then test upgrade with my config on dev HA (been thinking about setting that back up anyway).

The addon check config? No, because that stopped working properly after version 0.96 for me. Took long time and didn’t provide a final status

yes. But there is a problem with 105.x, you can have a look there: Can't update hassio to 0.105.x - #43 by hfeenstra

Once again, you can flag again my answer, but this is a fact, you’re really aggressive with people who simply ask or report things, sorry for you if my english is so bad, maybe it’s due to the fact that i do not speak ONLY english…

5 Likes

Critiquing someone else’s style isn’t very helpful to anyone is it. If you don’t like a reply, ignore it and move on.