I'm hoping to use Tasker on my android tablet to change the screensaver based on time of day, OR more related to this for us to use a light switch status in hubitat.
This light switch status is the bit I'm unsure of the best way to do. I'm confident on the other direction of an android tablet triggering hubitat to do something (maker API)
I know I could probably use the maker API to expose the light switch. Then from the android tablet use Tasker to periodically do a http get (or oost I can't recall) to check the status. But this would require polling..
I'm thinking that I could create a rule in hubitat that is triggered by the light switch status, that would then do an action of "something" that the tablet would detect in near real time...
Other than using push notifications in a rule from hubitat hub to the tablet, and then intercept that using auto notification (add-on for tasker) on the tablet, are there any other reliable and relatively easy ways for Android to detect in real time of something happening in hubitat? I looked at Join on android (made by the current developer of tasker) but didn't do it for some reason. Maybe extra costs.
If I understand you correctly, you may want to look at HD+ Android Dashboard. You can visually monitor light switch status and use your tablet to control that device.
I'm not sure about changing screensaver though. I'm just not that familiar with Tasker.
I'm more wanting to monitor the status of a switch, and then act on that in android. Rather than control it from android, which that looks more like unless I am mistaken?
I have the screensaver change (amongst other things) working on the tablet.
Tasker can do a http get and likely monitor for the switch status, but I'd have to keep polling. I guess every minute would be ok...
Other option I thought was hubitat send the notification to the tablet running hubitat app. Then I know tasker can monitor for specific notifications and act on that...
I just feel there are more efficient ways to do it.
Over a (very) long time I have been developing an integration using Tasker, which I have still been toiling away on in recent months... I wouldn't want to commit to when I might release it...
But if you want something simple I could likely help you out with something bespoke for the time being. Actually, there's every chance what I made available back then could do what you need....
I guess I do not understand exactly what you are wanting. I monitor the status of multiple devices with my phone and my pads using HD+. I can monitor/change/update multiple devices from anywhere. If I need background monitoring/updates/changes to any of my devices, then I use webcore/Rule Machine/Basic Rules, etc.
More recent versions of Tasker introduced the feature of HTTP endpoints able to be configured in Tasker. I have used this within my project to allow commands to be sent from HE to Tasker. You could use something like RM to detect the appropriate trigger within HE and then send a HTTP request to Tasker, with Tasker setup to do whatever it is you want, including (I expect) displaying the screensaver. You could also setup a time-based profile in Tasker to display the screensaver, or control that via HE as well, if you prefer.
The monitoring and triggering of "something" based on a light switch already in the HE system, yes, that is something we have all enjoyed since the beginning of (HE) time...
My understanding would be that Peter is unsure how to best trigger the change in the display on the Android tablet in response to this event on HE. HD+ may be an existing option, I have not actively used it myself.
My experience has been in setting up Profiles in Tasker that can be configured to respond to HTTP requests and do whatever you can do in response within Tasker actions.
Yes maybe I'm a little lost here too.... So thanks to you both for responding. I may need a sleep myself.... End of day in Oz.
I've used the maker API to have android tablets control devices in HE... Also my windows PC with Blue iris to trigger a HE rule based on motion.. I've obviously used a dashboard to turn a light on and off. Which I can visually monitor if the light is off or on on my android devices.
What I haven't done is have android monitor for a change in a switch status in HE.
I was originally thinking of http request from tasker to HE, and read the response. That would require polling..
Seems as @sburke781 mentioned I can use HE rule machine to send the http request to my tablet, then have tasker on my android tablet receive that and act.
Seems using rule machine in HE to send a http request to my tablet is the better option as it's near real time and no frequent http requests this way.
I already have the tasker "task" that changes the screensaver from a slideshow to a clock, puts the tablet in do not disturb, turns any media off, puts the tablet it dark mode.
I have setup a trigger based off time only at the moment (first day on this project). So hoping I can also trigger it based off status of switches.. there's potentially more but that's as far I have thought so far.
It's for my son's bed clock. It also used for music and controlling AC plus lights in his room thus why I went to this level of tech
What Android OS version is the tablet running? (you can answer this stuff tomorrow... AutoRemote would be another option... likely regardless of the OS version... Starting up my old phone to get some screenshots of my dev Tasker project with examples of what I was describing earlier)
Yeah, likely it will, but could be a couple of awkward points where it could be hard for me to make it generic enough for what I want to develop, vs what you and others are likely wanting. Probably hard to explain simply at this time of night for us...
Let me give you (and others) some screenshots of what I have been describing...
Here's the setup of a "App Launch" profile I have in my project that is based on a HTTP Request... The name / context, i.e. the App Launch part, is not something to get too worried about... The important parts are that I have a profile setup to use a HTTP Request as the trigger, nominating a port and path, which are completely up to you to choose. The response is also not necessary, particularly if you choose to go the RM route.
From there I chose to turn the screen on and then launch the app based on the body of the request received, which is more to do with my "Mobile Controller" app and what I want to achieve.... not necessarily something to be concerned about for the use case in this topic...
I think his suggestion will do exactly what you want. The relatively new option for Tasker to receive HTTP requests and then act on them is great. I created a Find My Phone virtual momentary switch on Hubitat. Then I have a rule when that switch is turned on to send an HTTP request to a specific URL on phone. Next, Tasker Event is created for when it receives a request to that URL to make my phone ring loudly until I make it stop. Any kind of polling would be less than ideal.
This only works when your phone is local and you need to make sure your phone has a reserved IP address on your home network. If you want it to work no matter where you are, you're going to have to use the more complicated Join option in Tasker probably.
If you are at home and need to find your phone that is not also at home then no alarm or sound is going to help you.... Sadly... Might alert potential thieves to a free phone... but won't help you....
All in jest... AutoRemote could also be another option, which includes local control.... I only recommend because I haven't used Join in a meaningful way...
I used to use Join but for things when my phone might be away from home network. However, I have since installed a VPN so my phone is never "away" from my home network and is not needed anymore. When I did rely on it, it was definitely reliable.
EDIT: I lied. I still use Join to send a message to my phone that both my wife and I are reporting Away and that triggers my phone using Tasker to ask me if I want to arm home alarm. When connected to VPN, my IP address is different so the Join option is preferred.
You could also have a rule monitor the switch and send a notification to the device. Tasker can read the notifications on the device and use them as triggers. This might get around the home lan vs. outside on the wan use case. (Note: if it is a Samsung Device, Bixby routines can do this as well, but you are more limited on what actions you can take)
Might alert potential thieves to a free phone... but won't help you....
