The reason I'm asking this is because I am using the ha_washdata integration.
In the setting there's an option to select notify targets to receive a message for when the washing machine starts/finishes/changes phase.
The dropdown looks like this:
However, I want to send the notification via telegram.
The telegram_bot integration however, only creates notify targets, and I can't figure out how to use them in the ha_washdata notification system.
Is there any way, to get notification targets / action - I would appreciate input on the nomenclature here because at this point I'm hella confused - for telegram targets?
Or is there any suitable other workaround, maybe a way to manually create actions for telegram targets similar to the device actions?
Thanks in advance.
-morgan
Ok I just saw that the ha_washdata integration fire events itself for cycle start and end so I guess I can create y own automations for sending the TG messages - however I would still appreciate feedback on the confusion about the notify actions and target entities. thank 
We're kind of in the Wild West when it comes to notifications right now... older notifiers create unique actions under the notify domain. Newer notifiers that only need basic notifications are supplying notify entities. Newer or updated notifier integrations (like Telegram Bot) are both providing notify entities and providing actions under custom domains. And then there's the Mobile App integration, that provides both notify entities and individual actions under the notify domain.
The Telegram Bot integration provides a notify entity that can be used with the notify.send_message action. This should be usable with HA Wash Data. More complex notifications through Telegram Bot use the telegram_bot domain and are not currently compatible with HA Wash Data.
Haha ok so it's not just me being extremely dumb. I was getting worried because everything is pretty confusing.
The Telegram Bot integration provides a notify entity that can be used with the notify.send_message action. This should be usable with HA Wash Data.
That's the problem, I don't see how. I will probably have to ask the dev of the integration but if I select notify.send_message in the dropdown above, it just selects that action and does not give me an option to select an additional notify entity.
Do you think it would be reasonable to feature request separate notify actions (like the apps get them) to be created directly by the telegram_bot integration for the registered chat ids?
In the notification section of your WashData click "Add action" then type "send message" into the search bar then scroll down to the one that is named "Send a notification message"... that is the notify.send_message action:
No, I don't think that would ever be approved.
Do you mean here?
I didn't understand when these actions are triggered because I want to trigger only on Cycle Finish, not have a Notification for every state change... But maybe I'm misunderstanding the Notification Actions purpose.
Yes, that was what I was talking about, but I think that will send all the messages... the integration docs are pretty light on explanation for all the notification options.
And, I see what you mean about trying to do it with only selected message types. It looks like you'll have to use the Events until/unless those options are updated to use full Action selectors instead of the service list they are currently using.
For anyone stumbling across this, I now used the events.
Here's the yaml of my automation:
alias: Washdata Cycle End
description: ""
triggers:
- trigger: event
event_type: ha_washdata_cycle_ended
event_data: {}
enabled: true
conditions: []
actions:
- action: notify.send_message
metadata: {}
target:
entity_id:
- notify.home_assistant_telegram
data:
message: |-
{% set seconds = trigger.event.data.cycle_data.duration | int %}
{% set h = seconds // 3600 %}
{% set m = (seconds % 3600) // 60 %}
{% set s = seconds % 60 %}
{{ trigger.event.data.device_name }} semms to be finished!
Cycle duration: {{
(h ~ 'h ' if h else '') ~
(m ~ 'm' if m or h else s ~ 's')
}}
mode: single
Feedback if this can be improved always welcome
2 Likes
Thx for the feedback, I will work on the docs because I understand that some features might be confusing. Especially multiple ways of sending notification.
