[Feature request] Add consumable status notifications

[vordenken]

Hi @mundschenk-at,

first of all thanks for the nice blueprint. I created notifications manually before - using the blueprint is so much better.

That being said, would it be possible to add notifications for consumables to the blueprint? As far as I know their status gets pushed via mqtt as well, so this should be possible.

If you have the time and want to explore this, let me know if you need help testing or something :)

Best regards,
VD

[mundschenk-at]

Hi @vordenken, yes, this is is something I have been thinking about, but it hasn't bothered me enough so far to actually sit down and design an automation for it. (Another thing is that continuable tasks should not trigger the notification for finished tasks, or at least only optionally.)

[catduckgnaf]

@vordenken I am testing your fork, so far so good.
Are you planning to add consumable notifications, have you made any progress?

[vordenken]

@catduckgnaf never thought anyone would notice my fork lol 👍🏼
The things I changed so far are way easier to do (for me at least) than something like the consumable notifications but I still would love to have them - I will take another look at it :)

So I tried putting something together with the help of chatgpt but I cannot get to work - even manually setting the sensor to a value of 0 (below 1) it doesn't get triggered. Maybe someone smarter than me can fix this:

blueprint:
  name: Valetudo Staubsauger Consumables Wartungsbenachrichtigung für mehrere Sensoren
  description: Sendet eine Benachrichtigung an dein Mobilgerät, wenn eines der Verbrauchsmaterialien des Staubsaugerroboters gewartet werden muss, einschließlich des Mops.
  domain: automation
  input:
    filter_sensor:
      name: Filter Sensor Entity
      description: Entity des Sensors für den Filter.
      selector:
        entity:
          domain: sensor
          integration: mqtt
    main_brush_sensor:
      name: Hauptbürsten Sensor Entity
      description: Entity des Sensors für die Hauptbürste.
      selector:
        entity:
          domain: sensor
          integration: mqtt
    right_brush_sensor:
      name: Seitenbürsten Sensor Entity
      description: Entity des Sensors für die Seitenbürste.
      selector:
        entity:
          domain: sensor
          integration: mqtt
    sensors_sensor:
      name: Sensoren Sensor Entity
      description: Entity des Sensors für die Sensoren.
      selector:
        entity:
          domain: sensor
          integration: mqtt
    mop_sensor:
      name: Mop Sensor Entity
      description: Entity des Sensors für den Mop.
      selector:
        entity:
          domain: sensor
          integration: mqtt
    notify_target:
      name: Zielgerät für Benachrichtigungen
      description: Wähle das Mobilgerät aus, das benachrichtigt werden soll.
      selector:
        device:
          integration: mobile_app
          multiple: true

trigger:
  - platform: numeric_state
    entity_id: !input filter_sensor
    below: 1
    id: filter_sensor
  - platform: numeric_state
    entity_id: !input main_brush_sensor
    below: 1
    id: main_brush_sensor
  - platform: numeric_state
    entity_id: !input right_brush_sensor
    below: 1
    id: right_brush_sensor
  - platform: numeric_state
    entity_id: !input sensors_sensor
    below: 1
    id: sensors_sensor
  - platform: numeric_state
    entity_id: !input mop_sensor
    below: 1
    id: mop_sensor

action:
  - choose:
      - conditions:
          - condition: trigger
            id: filter_sensor
        sequence:
          - service: notify.notify
            target:
              device_id: !input notify_target
            data:
              message: "Dein Staubsaugerroboter benötigt eine Filterwartung."
              title: "Filterwartung benötigt"
      - conditions:
          - condition: trigger
            id: main_brush_sensor
        sequence:
          - service: notify.notify
            target:
              device_id: !input notify_target
            data:
              message: "Dein Staubsaugerroboter benötigt eine Hauptbürstenwartung."
              title: "Hauptbürstenwartung benötigt"
      - conditions:
          - condition: trigger
            id: right_brush_sensor
        sequence:
          - service: notify.notify
            target:
              device_id: !input notify_target
            data:
              message: "Dein Staubsaugerroboter benötigt eine Seitenbürstenwartung."
              title: "Seitenbürstenwartung benötigt"
      - conditions:
          - condition: trigger
            id: sensors_sensor
        sequence:
          - service: notify.notify
            target:
              device_id: !input notify_target
            data:
              message: "Dein Staubsaugerroboter benötigt eine Sensorenwartung."
              title: "Sensorenwartung benötigt"
      - conditions:
          - condition: trigger
            id: mop_sensor
        sequence:
          - service: notify.notify
            target:
              device_id: !input notify_target
            data:
              message: "Dein Staubsaugerroboter benötigt eine Mop-Wartung."
              title: "Mop-Wartung benötigt"

mode: single

[mundschenk-at]

I'd rather parse the sensor.valetudo_<robot>_events data for a generic solution.

[vordenken]

I only get a 0 or a 1 back from the events sensor so I thought it would be something useless...

[mundschenk-at]

The interesting data is in the attributes, not in the state.

[vordenken]

Thanks for letting me know!
Shouldn't I see something here then?

[mundschenk-at]

Only if there are any pending events. The state is 0, so there are none. (The state indicates the number of events.)

[RafaelSchridi]

I've been trying to setup something similar but the events are weirdly formatted, instead of an array you have to know what each event is called.

But I guess you can look for consumable_*?