I have tried this using my Video Doorbell POE and it works PERFECTLY.
Thank you so much for the detailed explanation and everything.
I have tried this using my Video Doorbell POE and it works PERFECTLY.
Thank you so much for the detailed explanation and everything.
Also interested in iOS equivalent if anyone figures that out
This works great! Any chance you know how to launch the activity without requiring a click on the notification? I’ve tried @mbotje’s solution below but it doesn’t seem to work.
Had this working great with notification opening directly to the correct camera and then my note20 ultra updated to Android 13 and it stopped working. Anybody else have similar issues?
alias: Android Motion at frontdoor
description: ""
use_blueprint:
path: McDAlexander/actionable_notifications_for_android_with_cam.yaml
input:
notify_device: notify.mobile_app_sm_n986u
trigger_entity: binary_sensor.doorbell_camera_motion
doorbell_cam: camera.doorbell_camera_snapshots_fluent
notification_title: Motion at front door.
action_1_title: Open Reolink
action_1_uri: >-
intent:#Intent;launchFlags=0x14000000;component=com.mcu.reolink/com.android.bc.login.WelcomeActivity;S.UID=95270006AF348KN2;S.ALMTIME={{now().isoformat()}};S.ALMNAME=Detection;S.DEVNAME=DontCare;S.ALMTYPE=PEOPLE;S.ALMCHN=1;end
action_2_title: Ignore
second_action:
- service: persistent_notification.dismiss
metadata: {}
data: {}
third_action: []
persistent_notification: false
Edit: after some research it seems to be an issue with the way android 13 handles intent for an external app.
Before Android 13, if your app sent an
Intent
with a specific action to an external receiver (or to be more specific, to another app), no matter if the action was declared or not, the receiving side would process it.If your app tries to send an
Intent
to an external app targeting Android 13 and no<intent-filter>
matches the sent action, the request will get blocked.
Anybody know of a workaround? I just got this working weeks ago and I am pissed the update Samsung forced on me broke it. Thanks in advance.
Is this still working for you? Mine was for a while and stopped…
still works on my android 13 phone. it’s not a samsung, though.
I’ve just tested this, and it works for me. The notification opens up to a specific camera. Android 14.
I’m surprised nobody has been asking how to dynamically determine the camera channel. If you want to have a generic automation that sends notifications then the automation needs to know that a given camera is on a given channel. I don’t see that being discussed.
I did some poking around and I think I found a solution. I only have 3 cameras, so the fact that it works might be a coincidence. It’d be nice if others could test & confirm.
I’m using an NVR.
Using this template:
{{ device_attr(device_id('binary_sensor.SOME_SENSOR'), 'identifiers') }}
Returns something like:
{('reolink', 'UID_ch2')}
Where UID is the NVR UID. This is nice because the automation can parse this, and you don’t have to hardcode anything specific to your setup. It enables blueprints.
For channel, the channel in the identifier is 0-based whereas the app intents use 1-based.
So if the ID returns 0 then that’s camera 1. If it returns 1 then that’s camera 2, and so on. In my example “ch2” refers to camera 3.
Given the camera number, you can convert as per @olorinsledge 's post. So
1 = 1
2.= 2
3 = 4
etc.
In other words,
ch0 = 1
ch1 = 2
ch3 = 4
I leave the parsing up to the reader. My goal so far was just to figure out if I could dynamically get the correct parameters.
Sounds like we need a blueprint wizard in this thread to cook us up a blueprint. … also anyone know how to do it with iOS app?
Anyone figure out how to do deep linking with iOS?
How do I go abouts deep linking the 2way audio button in the Reolink android app?
I made progress for iOS. You can link to your local Shortcut!
I am using url: fb1675493782511558://1
which opens the camera directly in the app. But I only have 1 doorbell camera in the app.
So I don’t know if adding the 1 at the end changes something for you?
I have tried this and no matter what channel I use, it always opens channel 1 of my NVR…
intent:#Intent;launchFlags=0x14000000;component=com.mcu.reolink/com.android.bc.login.WelcomeActivity;S.UID=XXXYYZZ;S.ALMTIME={{now().isoformat()}};S.ALMNAME=Detection;S.DEVNAME=kurnik;S.ALMTYPE=PEOPLE;S.ALMCHN=1;end
Try set UID of your desire camera for specific camera stream open
I have a NVR and I have set the UID, but the first channel of the NVR is always opened, no matter what I input as channel…