Update notifications for Home Assistant

Blueprints Exchange
, ,
21

Thanks for the feedback, sure, this is something doable.

However, I made some changes to the blueprint which change its behaviour in this scenario.

With the old blueprint you needed to manually enter the entities you wanted to be notified immediately, while others relied on the reminder.
Who wants to manually configure them? So I removed this feature, and rely entirely on the reminder. Easier, just set and forget.

I can implement your functionality to get a weekly reminder, but I can't easily get new updates to be notified immediately - at least, not in an automatic way.

Would you be fine with just one weekly reminder?

22

Hi @auanasgheps

Got you, personally i dont need immediately reminders.
Would be really nice if you implement an weekly reminder and an None setting to the intervall.

Thanks a lot

1 Like
23

Here we go!

Version 2.2

New Features

  • Lazy mode: A new mode in the Schedule section. When enabled, the Reminder interval is ignored and a single reminder is sent once per week on a configured weekday and time. Ideal if you prefer to handle updates on your own schedule without repeated reminders.
    • Note: the Notify after / Notify before time window still applies.
  • Disabled option for Reminder interval: The "None" interval has been re-introduced. When selected, no hourly reminders are sent. Intended for use together with Lazy mode.
    • Note: if both are off, no notifications will be sent.

Upgrade note
Use Re-Import Blueprint button to update to 2.2.

1 Like
24

Nive Blueprint.
Can you add the option "Update with Backup" to the Logik?

25

Can you explain what you mean? Backup option is already available for supported entities

1 Like
26

@auanasgheps Thanks a lot for implementing lazy mode with weekly reminders.
I have ditched the old, not maintained one and setup your new v2.2.

Next reminder should be today 14:00, i will check if it works and report here.

again: thanks a lot!

1 Like
27

Hi @auanasgheps,

Initially, I had a config issue with the before/after time window, so no notifications were sent to my phone at 14:00 (yeah, my fault!).

After fixing that, I set a test time a few minutes in the future, but still, no notifications were sent to my phone. I did another test a few minutes later, and suddenly the notifications came through.

I compared the old blueprint I used with yours and noticed a key difference:

Your blueprint is missing the priority and ttl parameters in the notification payload. Because of this, notifications (especially scheduled reminders) are often delayed or completely dropped on modern Android devices when the phone is in deep sleep (Doze mode). I’ve verified via HA traces that the automation triggered perfectly on both of my tests, but Android’s aggressive battery management suppresses the standard push notification if the phone isn’t actively used at that exact moment.

Maybe the solution:
Adding priority: "high" and ttl: 0 to the notification data payload solves this reliably. These parameters tell Firebase Cloud Messaging (FCM) to deliver the message immediately and wake up the device if necessary.

Could you consider adding these two parameters to the base_data dictionary for non-Apple devices in the blueprint?

base_data: {
  "tag": "{{ cl_tag_id }}",
  "channel": "{{ notification_channel }}",
  # ... other existing data ...
  "ttl": 0,
  "priority": "high"
}

Thanks for your great work on this blueprint!

1 Like
28

Hi, thanks for the feedback!
Indeed notifications can be delayed, based on the phone status. I usually see no delay to a maximum of 15 minutes, which never bothered me.

I had a look at the options you mentioned, I found them here.

I’ve implemented the change and I will test during these days. It only touches the Reminders part, because Install/Skip/Changelog/Updating notifications are interactive so Doze mode doesn’t apply.

Stay tuned for an update!

2 Likes
29

@auanasgheps thanks for you making the blueprint better and better.

Just ping me if you need testers.

30

New Version available: 2.2.1 :rocket:

Bug Fixes

  • Fixed: Android notifications may be delayed due to sleep inactivity (Doze) The blueprint now uses high priority settings to allow consistent and on-time delivery on Android. This replicates what the original v1 blueprint did.

Upgrade note
Use Re-Import Blueprint button to update to 2.2.1

2 Likes
31

Hey there, @auanasgheps! I saw that you were now maintaining this blueprint! I hadn’t actually used the blueprint in so long, that I didn’t realize that it had a different maintainer now! I am posting this here, in case you didn’t already see it.

32

@auanasgheps thx a lot for the update.
Rocking it now and will report back if there any other issues.