Is this really the cleanest way to 'guard' an entity (Meteoalarm failing) in an entities card?

using Meteoalarm, we often find ourselves confronted with the binary_sensor not being created by the integration, for a multitude of reported issues… today the message frequently was WrongCountry… of course this is nonsense, but the source of the Meteoalarm servers apparently return us this error.

Listing it in the entities card as is, binary_sensor.meteoalarm_brabant causes the yellow line we all know.

because of that, I’ve made a binary_sensor

binary_sensor:

  - platform: template
    sensors:
      meteoalarm_brabant_online:
        friendly_name: Meteoalarm Brabant online
        value_template: >
          {{states.binary_sensor.meteoalarm_brabant is not none}}
        device_class: connectivity

to test for its existence and use that in a conditional card, which in itself is used as a row by using the custom hui-element card:

  - type: entities
    title: Alerts dashboard
    entities:
      - ####
      - ####
      - type: custom:hui-element
        card_type: conditional
        conditions:
          - entity: binary_sensor.meteoalarm_brabant_online
            state: 'on'
        card:
          type: entities
          style: |
            ha-card {
              box-shadow: none;
              margin: -16px -16px -16px -16px;
            }
          entities:
            - binary_sensor.meteoalarm_brabant
       - etc

this works alright, but it seems rather contrived… hence my question: can’t this be done in a cleaner way?

thanks for having a look.

1 post - 1 participant

Read full topic