Push Notification instead of Persistent Notification

[badewanne1234]

I want to send a Push Notification instead of a Persistent Notification as soon as the sidebrush or mainbrush is blocked or if there is another error.

For that, I was thinking to listen to the event dreame_vacuum_error and its error message.
Upon that, I can then create a push notification for each individual error message.

Does anyone have the correct syntax including the error messages that are fired? It would prevent me of putting the dreame bot into that state by myself, like throwing a cable under the bot ;)

dreame_vacuum_error
    entity_id: Vacuum entity
    error: Error description
    code: Fault code of the error

Thank you!

[feerlessleadr]

Did you ever figure this out? I'm looking for an example of this myself.

[badewanne1234]

Yes I did.
Example:

platform: state
entity_id:
  - vacuum.yourvacuumname
attribute: error
to: Route

Error codes I figured out...:

• Route
• Drop
• Brush
• Side brush
• Forward suffocate

Drop means that the wheels are suspended.

Maybe there are more error codes but I did not figure out more so far...

[Tasshack]

https://github.com/Tasshack/dreame-vacuum/blob/master/custom_components/dreame_vacuum/dreame/types.py#L107
Error codes are there.

[badewanne1234]

Thats quite a lot of error codes 😁😁

[Tasshack]

Because of that you should use events for triggering automations.
https://github.com/Tasshack/dreame-vacuum/blob/master/docs/events.md#error

[badewanne1234]

Does listening to events use less resources compared to state changes or why would you rather listen to events instead of state changes?

[Tasshack]

https://community.home-assistant.io/t/send-web-ui-persistent-notifications-to-mobile-devices/274891