![]() ![]() ![]() You are done, and now you can control a device directly from a notification on your android device! There are other fun things you can do like cancel the notification once the door is locked. Put the Maker API or Local/Cloud Endpoint URL in the URL field. In the actions for this task, add Net > HTTP Request. Put the action name created above (lockfrontdoor) as the command filter. Make the trigger Event > Autonotification > Autonotification. I use "Lock" for this.Ĭreate another tasker profile called the action you want the button to perform. I use lockfrontdoor as the action for this. Make the button's action something aribtrary (this is a command that will be used later to perform an action). Go to the buttons menu (while still in the configuration screen from the above step) and configure button 1. If you haven't played around with Autonotification, you can customize a ton of things in the notification, icon, color, actions, buttons, etc. Do Plugin > Autonotification > Autonotification. Select the app (in my case, Pushover) and fill in the "Text Filter" to the message you had HE create, select Exact to make sure it doesn't pick up any other notifications.Ĭreate an action to send a notification from Tasker/Autonotification. Make the trigger Event > Plugin > Autonotification > Intercept. Notifying Tasker"Ĭreate tasker profile to intercept the HE notification. For my example I have HE send a notification to Pushover if the front door has been unlocked for 10 minutes that says "Front Door Lock unlocked for 10 minutes. It just needs something that won't be sent for other reasons. I like to add "Notifying Tasker" at the end of these (to be used later for more generalized notificaiton interception). Make the notification say something that is distinct. I use the Notification app and send to Pushover. I'm no expert, but it seemed more secure that way to me.Ĭreate a notification in HE. That way if for whatever reason someone gets ahold of your phone and finds their way into Tasker, they won't be able to compromise security by changing the 'lock' command in a Maker API http request to 'unlock'. In the case of devices that are critical to your home security, I would recommend executing this through a local or cloud endpoint that executes a rule. ![]() rule locks the door) and make the rule trigger a local or cloud endpoint, and get the url. If you want to execute a rule instead of control a device, create a rule (eg. Create a link to the device you want to control in Maker API and get the url of the command you are going to want to send directly from the notification.This is the method I use, but I'm sure the same thing could be accomplished in different ways. Keep in mind there are many different ways to skin a cat. A way to send notifications from HE (I use Pushover).Android device with Tasker + Autonotification.If I don't want the door to lock, I can ignore or dismiss the notification. Now I have a notification sent if the door has been unlocked for 10 minutes, and a button to lock the door directly from that notification. When I took the autolock off, I found people (including myself) were forgetting to lock the front door. I used to have it lock automatically after a set amount of time, but that gets annoying because sometimes I don't want it to lock. I use the same method (having tasker intercept a notification from HE) for a few different things, but the easiest to explain is the warning I have set up for my front door lock. This way when I get a warning, I don't have to open the hubitat app up, find the right dashboard, find the device, send the command, etc., etc. Wanted to share something cool I did, well I think it's cool at least.hopefully someone will find it useful.Ĭreates an 'actionable' notification that can be used to send a device command and/or execute a rule via Maker API or a local/cloud endpoint trigger, respectively. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |