Notify.send_message in 2024.6

Biscuit · December 21, 2024, 4:03pm

Yes the change happened six months ago, so the deprecated but allowed configuration.yaml settings have finally been removed for good.

Just remember, the ‘team’ are striving to make Home Assistant open and easy to use for those of us without a double Masters Degree in Computer Science and Information Technology (not that, in this particular case, you would notice). You can complete the new customer satisfaction survey here…

Biscuit:

The new ‘file notification’ integration now supersedes any notify.yaml to file configuration.

The old yaml setup still works, but will generate a warning message saying it is obsolete.

The new ‘file integration’ works, but needs

the file-path directory added to the allowlist_external_dirs (for each directory used by all file writes)

the file integration added (once) and a new target entity added (for each individual file you want to write to) Set this up as a notification, with the full file path-name, and optionally ‘use timestamp’

then use the new ‘file notification’ entity in your automations as the target

File notification is now done using the service call ‘notify.send-message’, and
to a target (the entity created under file notification)
service: notify.send_message
target:
  entity_id: notify.file_battery_event
data:
  message: Battery Full (at least 1 hour)
The target entity created as a new entry under the file integration [notify.file_battery_event in my case] now holds the platform (file) and the file pathname in its definition

{and if this all makes sense to anyone, would you be so kind as to explain it back to me so I can understand it myself. Thanks}

It is certainly worth adding the file directory access permission first, and also going back and renaming each file-notification-entity, otherwise you have no idea from the name which is which.