mirror of
https://github.com/maziggy/bambuddy.git
synced 2026-10-04 13:11:35 +02:00
maziggy
49f9d7120d
When an HA notification provider targets a notify service (e.g. notify.mobile_app_myphone), a new optional Data (JSON) field is forwarded as the service call's nested "data" object - the same place HA automations put mobile push options like priority, ttl, channel, and group. ttl: 0 + priority: high make Android pushes arrive immediately; channel gives printer alerts their own sound. JSON rather than key=value lines so numbers stay numbers and nested options work. Validated on both ends: the UI rejects malformed JSON before saving, and the sender fails loudly instead of posting a half-built payload. Only included when configured - the default persistent_notification.create path is unchanged, as its schema rejects unknown keys.
