Home Assistant Companion for Android 1.6 and 1.7

Blog
13

always acted like that, same behaviour as html5 notifications
so still using pushover for notifications :frowning:

14

What device do you have? Does it run a stock ROM or something else?

15

yes, stock rom, a Oneplus 6T

16

Very weird. One of the developers working on the app also has a OP6T and hasn’t experienced any delays…

17

verry easy to reproduce here :slight_smile:
whats also funny, if i know a notification should come, and it doesnt when it sleeps
if i then send a pushover message, at that point also the other notification from the ha client comes trough at the same time

18

Can you set TTL to 0 and priority to high in your notifications and see if that changes anything? For example:

title: 'Title Text'
message: 'Body Text'
data:
  ttl: 0
  priority: 'high'
19

ok, will try that next time

20

This is insane guys! Thanks for this, no more panic 30 seconds trying to disarm the alarm

21

I had the same experience as @pergola.fabio and i’m using a OnePlus 7, so maybe it’s OnePlus related, i don’t know.
But i tried the TTL / prio solution at it works for me :ok_hand: :metal:
So thank you for pointing at a possible solution :muscle:

data:
  actions:
    - action: close_garage
      title: Close Garage Door
  priority: high
  ttl: 0
message: Message to display
title: Message Title
22

That’s verry good to hear

23

still not working for me either, tested below script, maybe its the image? but what i noticed, the message didnt come, i had to wake up phone, and even i had to open the “home assistant” app , the the push message arrived

aa_test:
  alias: Doorbell notification
  sequence:
  - service: !secret notify_ha_fabio
    data:
      title: "Alert"
      message: "Someone at the door"
      data:
        # actions:
          # - action: "close_garage" # The key you are sending for the event
            # title: "Close Garage Door" # The button title 
        image: "https://i.pinimg.com/originals/0f/7b/fa/0f7bfa4e6775b5977694a6036fc85b48.png"  
        priority: high
        ttl: 0
24

Can you test without the image to see if it works better? in all my testing today I have yet to see a delayed notification.

25

Yes, let’s continue the discussion and results on the GitHub thread

26

one feature i miss for notifications is to be able to select a sound
based on script/message i want to have another notification sound
is that already possible and not documented? to use somekind of internal sound name?

https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidNotification

27

sound is not supported yet but there is an existing feature request for it via notification channels

28

ah cool thnx for info

29

Since the 1.6 release i get a huge delay for the notifications… What i was getting at the set hour now i get the notification with a 6-7 minutes delay… Is someone else having the same issue?

30

Is this still an issue in 1.7? Did you try to set ttl: 0 and priority: high?

31

Another OnePlus user here (OnePlus 6) confirming that notifications work much better when priority: high and ttl: 0 are set.

Loving the new update and just modified a bunch of my automations to include actionable notifications!

32

I have followed the example for the formatting of the actionable notifications, which at first seemed to be working find, but i’ve noticed that multiple actions are being triggered when clicking on the notification button, even though i’m only expecting one to run