Problems sending notifications to multiple entities

Configuration
21

And as a side comment. I recommend that you reach out to the custom integration and let them know that their notification service should swap to the proper domain. Your notify.notify would work had that been the case

22

I think this is the norm now for notifiers that require data… it’s what is being done with core notification integrations as well…

Mastodon and Matrix also do it.

23

But the above example only adds a device id, for all intents and purposees, this should use the notify.send_message service with notify entities, one for each device.

All the more reason to make a template notify. I have to put that PR through at some point

24

OP has only added a device ID, but the integration supports way more like text spacing, justification, alignment, duration, etc.

I agree the dev should add a notify entity so it’s inline with current expectation… and we could use Template notify to make the service/entity situation easier to work around.

25

Yeah, it was just a sketch. Here’s the final version, slightly updated, mostly to not use the name “notify” which seems like a namespace collision waiting to happen with the names used in the notification system:

# Forward a notification to multiple targets.  This takes a standard
# notification and farms it out to multiple targets, in this case the HA
# app on the phone and the Vestaboard.
#
# To test: Developer Tools | Actions | "Notification Forwarder", set
# Action Data = title: "Test" / message: "Test message", click Perform.

script:
  notification_forwarder:
    alias: "Notification Forwarder"
    description: "Forward a notification to multiple targets"
    fields:
      title:
        description: "Notification title"
      message:
        description: "Notification message body"
    sequence:
      - action: notify.send_message
        target:
          entity_id: notify.phone
        data:
          title: "{{ title }}"
          message: "{{ message }}"
      - action: vestaboard.message
        data:
          device_id: abcd1234
          message: "{{ message }}"
26

I’ve only just started playing with it, there’s actually a pile of interesting things you can do with it, one of which I’d like to achieve is have that cool ripple update that airport display boards used to do. I’m also still in the process of working my way through all the YAML that I’ve got to switch from notify.notify to the script for everything.

For the Vestaboard integration, it doesn’t tie into notifications AFAIK, there’s just some actions to display messages. This is why I was having trouble connecting the two up.