You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current notification for HA uses the service persistent_notification/create and works really well.
However within HA it is possible to create custom notifications that are sent to various devices e.g. TV, phone etc. as popups. This can be done using these devices services, and notifications groups.
it is simple to call these using for example curl with the long-lived token but calling a different url e.g.
This is so similar to the existing code, I thought it might be possible to add this in by allowing a custom path to be given in the configuration that would bypass the persistent_notification/create path.
I think it would be a great addition but appreciate you may not think so, but thanks for taking the time to read this.
if I can provide anything else to support this enhancement let me know.
🔨 Breaking Feature
The text was updated successfully, but these errors were encountered:
💡 The Idea
The current notification for HA uses the service persistent_notification/create and works really well.
However within HA it is possible to create custom notifications that are sent to various devices e.g. TV, phone etc. as popups. This can be done using these devices services, and notifications groups.
it is simple to call these using for example curl with the long-lived token but calling a different url e.g.
http://homeassistant.local:8123/api/services/notify/servicename
This is so similar to the existing code, I thought it might be possible to add this in by allowing a custom path to be given in the configuration that would bypass the persistent_notification/create path.
I think it would be a great addition but appreciate you may not think so, but thanks for taking the time to read this.
if I can provide anything else to support this enhancement let me know.
🔨 Breaking Feature
The text was updated successfully, but these errors were encountered: