@SteveDinn and @Gluwc and @jcollie The issue regarding sensor generic names will be fixed in 0.106. Keep in mind this will not impact any sensors already registered with HA. You can easily rename them in the UI and you can find them via the integrations panel as they are attached to your device.
1 Like
The actionable notifications are fantastic!
I find that clicking on an action properly triggers the event; however it doesn’t dismiss the notification (Android, Pixel 4). Do I have to listen for the event and send a clear_notification? Or am I missing a setting?
do you by chance have sticky: true defined? If so change it to false or remove it.
It’s there a way to use actions with a notify group? I would love to be able to send ‘Garage left open’ to a notify group and then clear it from that same group when anybody takes action on it.
I tried to do this but it seems to disallow the extra parameters when calling the notify group.
Unfortunately the ‘sticky’ value has no impact, and selecting an action won’t dismiss the notification. In fact, setting ‘sticky’ to true, false, or leaving it out completely has no effect regardless of having ‘actions’ or not (I can always swipe right to dismiss the notification).
Here’s an example message. Tapping “One” or “Two” will trigger the callback in Home Assistant, but keep the notification displaying on my phone (Pixel 4).
{
"message": "Test",
"data": {
"tag": "notify_test",
"sticky": "false",
"actions": [
{
"action": "1",
"title": "One"
},
{
"action": "2",
"title": "Two"
}
]
}
}
what about the other new notification options like color or tag? I have a feeling you may want to try and start fresh with the android app to see if it resolves teh issue:
does your group contain only android devices? if so it should work as the service data is the same.
Yeah, the group contained two devices, both of which are Android companion app notifiers
I also tried it with just one item in the group, and no dice.
what did your service data look like? did you get any errors in the HA logs?
Yeah, there were errors describing exactly the problem. The notify.group service can’t handle the extra parameters. I can reproduce it and get the exact text if you want.
What does the service data look like that you used?
I can use the following and it works fine:
- service: notify.android
data_template:
message: "test message"
title: "test title"
data:
image: !secret url
priority: high
ttl: 0
notify.android goes to 2 android devices and the image loads properly, notice how the entire service data is under data_template or alternatively it could be data
I think I have to take that back. I also had a notify.file notifier in that group. In any case, it’s a shame that the group just can’t ignore parameters for notifiers that don’t support them.
Edit: Apparently, I’m completely crazy. I just tried it with the file notifier back in the group, and everything is working exactly how I expect it to. I must have had a brain fart.
1 Like
Hey guys. I’ve searched around for this and tested it in developer tools, but are Icons and Badges supported through the Android Home Assistant Companion app yet? I suspect not based on my searches so far. Thanks.
Badges appear to me. My entire HA front-end seems to be replicated.
Same.
Looks identical whether in app or browser
If you mean by additional notification parameters then not yet.
Hi I am having a issue with notifications. I can send with a image ok but when i use a URL with a username and password it will not send the image to android. It works five with IOS. e.g. below.
Works:
message: “TEST”
data:
android:
image: http://YOURIP:PORT/jpg/image.jpg
Not working:
message: “TEST”
data:
android:
image: http://username:secret!@YOURIP:PORT/jpg/image.jpg
Anyone else had the issue or worked out a solution?
If you are attaching a snapshot why not just use the API call instead of wanting to send your credentials like that? See the link below on how to send a snapshot from the camera with auth already taken care of
1 Like
Maybe he has enabled authentication on the /jpg directory?
1 Like
Thanks guys your advise really helped! Went with the API method.
I think I’m making a basic error here - I get an error Invalid config for [automation]: [state_topic] is an invalid option for [automation]. Check: automation->trigger->0->state_topic. .
Can anyone please advise. Here’s my entry.
> - alias: Notify apps when the garage door opens
> trigger:
> platform: mqtt
> state_topic: "RFBridge/tele/RESULT"
> name: 'garage_door1'
> from: 'closed'
> to: 'open'
> for: ‘0:5:00’
> action:
> service: notify.mobile_app_device_tracker.gm1913
> data:
> message: "The garage has been left open"
> data:
> image: https://www.home-assistant.io/images/merchandise/shirt-frontpage.png
> actions:
> - action: "switch.garageopener" # The key you are sending for the event
> title: "Close Garage Door" # The button title
>
> - alias: Close the garage when notification action is tapped
> trigger:
> platform: event
> event_type: mobile_app_notification_action
> event_data:
> action: close_garage
> action:
> service: switch.turn_on
> entity_id: switch.garageopener