hanwg
hanwg
@c0ffeeca7 can you assist to get this merged? Thanks!
These doc changes are applicable since 2025.7.0.
> Wouldn't a separate entity service be more suitable? There is a select for the config entry, but the notify entities could correspond to different config entries. That is imho...
> I'd like to see a motivation to why we want to extend the legacy services instead of adding entity service(s) as done for ntfy in #143560 I initially did...
One of the early suggestion was to remove the existing `config_entry_id` and `target` parameters and to add the new `notify_target` parameter for the existing actions. This would have been a...
I had intended the legacy style (`config_entry_id` with `target`) to be used for sending/receiving to arbitrary chat_ids (see: https://github.com/home-assistant/core/pull/149924).
PR is ready for review, if anyone wants to be an early tester, I would greatly appreciate it.
It's only for `send_message` for now. The some of the other actions have some special handling so it's probably better to do them in a separate PR.
Yes, you understood it correctly. Shouldn't the display show only 1? i.e. count only entities whose `config_subentry_id` matches the row's subentry.
The config flow could have been more user friendly.  I think it will be better to split the flow into 3 steps: - choose authentication type step - this...