#Dreame Integration Notifications

1 messages · Page 1 of 1 (latest)

frozen cloak
#

I'm using Tasshacks Dreame integration trying to create an automation based off vacuum cleaning and it's like ha does not see any of the states of the entity when using state trigger.

Does anyone have a dreame and successfully managed to find a way to get this working?

stoic sentinel
#

Mine having no problem, are you connecting thru dreamhome account? I found there was problem in using xiaomi home account for authentication in the last month.

frozen cloak
# stoic sentinel

I should rephrase, i have the vacuum completely installed, and i see all it's entities. My issue is i'm trying to create an automation off it's state attributes but it seems HA ignores everything or the vacuum is not showing the same attributes.

#

`alias: Vacuum
description: ""
triggers:

  • trigger: state
    entity_id:
    • vacuum.l10s_ultra
      to: returning
      from: cleaning
      conditions: []
      actions:
  • data:
    message: Jack got off his ass and decided to clean
    title: Vacuuming Complete
    data:
    ttl: 0
    priority: high
    image: /local/tmp/Designer.png
    notification_icon: mdi:cctv
    channel: Motion
    actions:
    - action: URI
    title: Show Vacuum
    uri: /lovelace/vacuum
    action: notify.mobile_app_galaxy_flip_6
    mode: single`
frozen cloak
#

Finally figured it out!

#

`alias: Vacuum
description: ""
triggers:

  • trigger: event
    event_type: dreame_vacuum_task_status
    event_data:
    entity_id: vacuum.l10s_ultra_2
    completed: true
    conditions: []
    actions:
  • data:
    message: "{{ trigger.event.data.status }}"
    title: Vacuuming Complete
    data:
    ttl: 0
    priority: high
    image: /local/tmp/Designer.png
    notification_icon: mdi:cctv
    channel: Motion
    actions:
    - action: URI
    title: Show Vacuum
    uri: /lovelace/vacuum
    action: notify.mobile_app_galaxy_flip_6
    enabled: true
    mode: single`
#

i put dreame_vacuum_task_status in events under developer tools and listened for the exact attributes the persistant notifications throw off