Any way to use HA for notifications when a vent looses connectivity?

[ptr727]

I rarely look at the Flair mobile app, but I do see there are some alerts about vents that lost connectivity.
I use HA alerts for most other of importance things, is there a way to get offline notifications from the integration to use in an automation, e.g. connectivity state, or something like that?

[RobertD502]

Yes, I programmed the cover entity for a vent to become unavailable if the Flair API reports a vent as being offline. In Home Assistant, you can use if a vent cover entity has a state of unavailable as the trigger for your notification automation.

Note: In addition to the cover entity being unavailable when Flair reports the vent as being offline, Home Assistant, on its own, will set EVERY entity for the Flair integration to unavailable if polling the API fails to return any data (which is bound to happen from time to time when dealing with a cloud-based API). So, I highly recommend you add a condition in your automation that will only fire off the notification if the state of the fan's cover entity has remained unavailable for an extended period of time (e.g., 4 min). This way you aren't sending a notification when there is a one-off hiccup in the API / every time the vent goes offline for a few seconds - I myself didn't have a check and got constant notifications until I added the condition. You aren't aware of how frequently a vent may go offline and quickly back online if you are using the Flair app for notifications since they also seem to use a time condition before they consider sending a push notification from the app.

[ptr727]

Reason I considered a blueprint is so I do not need to "add each one" that is cumbersome, I'd like to get notified if "any flair vent" is offline, similar to how e.g. low battery blueprints works, any device, with a battery, that reports low, in this case I'd like any flair vent that is disconnected.

[RobertD502]

Ah I see. Sorry, I tend to use node red for my automations, so I didn't grasp what you were trying to achieve.

[RobertD502]

@ptr727

I see that the low battery blueprint automation is executed on a time basis (seems that this is the workaround since the Home Assistant trigger entity_id field doesn't accept templating).

So, if you go down this route, you can set a timed automation with the following template variable (named offline_flair_vents, for example):

{% set flair_list = integration_entities("flair") | list %}
{% set conn_entities = namespace(entities=[]) %}
{% set vent_conn_list = namespace(entities=[]) %}
{% set offline_vents = namespace(entities=[]) %}
{% for entity in flair_list %}
  {% if is_state_attr(entity, "device_class", "connectivity") %}
    {% set conn_entities.entities = conn_entities.entities + [entity] %}
  {% endif %}
{% endfor %}
{% for entity in conn_entities.entities %}
  {% if is_device_attr(device_id(entity), "model", "Vent") %}
    {% set vent_conn_list.entities = vent_conn_list.entities + [entity] %}
  {% endif %}
{% endfor %}
{% for vent in vent_conn_list.entities %}
  {% if is_state(vent, "off") %}
    {% set offline_vents.entities = offline_vents.entities + [device_attr(vent, "name")] %}
  {% endif %}
{% endfor %}
{{ offline_vents.entities | join(', ') | replace(', ', '\n') }}

The template above looks at any Vent device in the Flair integration and adds the name of the Vent to the offline_flair_vents variable if the associated connection status binary sensor is off.

Then you add a template condition to the notification action that checks to make sure the offline_flair_vents variable isn't empty (only send a notification if there is one or more vents offline):

{{ offline_flair_vents != '' }}

And construct a message of:

'Offline Flair Vents: {{ offline_flair_vents }}`

[ptr727]

I created a variant that alerts on the condition being met vs. on a timer, but I can use your code to adapt.

Low battery:

blueprint:
  name: Battery low alert
  description: Send a notification when a battery low condition triggers
  domain: automation
  input:
    exclude:
      name: Excluded sensors
      description: Sensors to exclude
      default:
        entity_id: []
      selector:
        target:
          entity:
            device_class: battery
    actions:
      name: Actions to take
      description: E.g. Battery low reported by {{ trigger.event.data.new_state.attributes.friendly_name }}
      selector:
        action: null
trigger:
- event_data: {}
  event_type: state_changed
  platform: event
condition:
- condition: template
  value_template: '{{ trigger.event.data.new_state.attributes.device_class == "battery" }}'
- condition: template
  value_template: '{{ trigger.event.data.new_state.state == "on" }}'
action:
- choose: []
  default: !input 'actions'
mode: single

Leak detected:

blueprint:
  name: Leak sensor alert
  description: Send a notification when a leak sensor triggers
  domain: automation
  input:
    exclude:
      name: Excluded leak sensors
      description: Leak sensors to exclude
      default:
        entity_id: []
      selector:
        target:
          entity:
            device_class: moisture
    actions:
      name: Actions to take
      description: E.g. Leak reported by {{ trigger.event.data.new_state.attributes.friendly_name }}
      selector:
        action: null
trigger:
- event_data: {}
  event_type: state_changed
  platform: event
condition:
- condition: template
  value_template: '{{ trigger.event.data.new_state.attributes.device_class == "moisture" }}'
- condition: template
  value_template: '{{ trigger.event.data.new_state.state == "on" }}'
action:
- choose: []
  default: !input 'actions'
mode: single

[RobertD502]

Didn't think about using the event trigger! Guess you can set multiple conditions of: the entity integration having to be "flair", the entity having a device class of connectivity, having a state of off, and the entity's associated device having a model of "Vent".

• The device model condition is there so you aren't sending a puck or bridge in the vents offline notification since pucks and bridges also have the connection status binary sensor.

Then create the variable using my code above to construct the offline vents to be used in the notification message.