Happy to help, but it’s sure not an easy thing to share concisely. Have you reviewed the post Using Tasker with HA? Please follow that guide’s steps 1-3 to get Tasker set up for an HA connection. You will import an HA-call-service template as a new TASK you will configure as described in step 4. (There is an alternative method to install a free HA Tasker plugin from Google Play that you can use instead of this template, but I didn’t find it necessary or all that much simpler).
You first need to set up a Tasker profile to react to SmartHome App alert notifications. From the Tasker profile tab main menu, tap + to select Event , then UI, then Notification. Tap Owner Application and select Amcrest SmartHome. Then in the Title field, enter Someone*. This will trigger when the doorbell button is pressed and the notification says “Someone is at your <name of doorbell>”.
Now tap the back < icon to exit this menu and you then select the HA call-service task that was previously imported. Now tap on this task name from the profile menu to configure this task.
In the Parameter 1 field, enter: input_boolean.turn_on
In the Parameter 2 field, enter: {“entity_id”: “input_boolean.amcrest_doorbell_button”}
That’s it! press the back <- arrow, and then the check mark at the top to save. You can also long press on each name to edit and rename both the event and newly configured task to your liking.
Now you can either reset the boolean switch in your automation, or you can have Tasker immediately turn it off by repeating the above process to assign an additional HA-call service task to the button press event. Just define parameter 1 in the second task as input_boolean.turn_off with the same entity_id value in parameter 2.
Repeat the above to create a second event trigger, but in the Title field, enter Motion* to perform a new task to recognize “Motion detected at your …”
Here is how I configured HA switches and event triggers…
configuration.yaml:
input_boolean:
amcrest_doorbell_button:
initial: off
name: "Front Doorbell Button Pressed"
amcrest_doorbell_motion:
initial: off
name: "Front Doorbell Motion Detected"
automation.yaml:
trigger: # These events are triggered by Tasker/Smarthome app notifications
platform: state
entity_id:
- input_boolean.amcrest_doorbell_button
- input_boolean.amcrest_doorbell_motion
to: 'on'
I’ll also include some screen captures here to help clarify the Tasker configuration. Below is the home screen from an old Android phone dedicated to running Tasker and SmartHome. Here it is showing the two SmartHome alerts Tasker will recognize. (Ignore the “No active profiles” Tasker message, that is normal).
Below is the main menu from Tasker where both doorbell button press and motion SmartHome notifications are triggered. I have renamed them from the default names. (Ignore the Skybell info, that is what I had before replacing it with the AD110).
This is all that is needed to recognize a doorbell press notification “Someone is at your …”
And here is the action taken to signal HA via an input_boolean switch…
The first task is to turn on the boolean switch, then the second it to turn it off.
