Sep-05-2020, 01:14 AM
It has occurred to me that this is a long roundabout way of dissecting and reassembling a URL. Since I am not actually passing a variable to Tasker (such as a numeric value of temperature), I am simply relaying a state change (greater or less than a temperature). I could be just as easily creating a URL that has the "alert" populated at the end of the "base" for each possible condition. Since Tasker/Join/AutoRemote triggers on specific (sometimes case specific) keywords, it would be best if I only had it trigger on a few keywords.
Thank you to those who took the time to respond to this. While it is possible for this to work, it is waaaaay too much work on the other end to capture and react to the spectrum of the possible values returned as the "alert" variable. I shall be content with just having the pi react to threshold breaches and reporting them to the Android ecosystem that is my interface.
Thank you to those who took the time to respond to this. While it is possible for this to work, it is waaaaay too much work on the other end to capture and react to the spectrum of the possible values returned as the "alert" variable. I shall be content with just having the pi react to threshold breaches and reporting them to the Android ecosystem that is my interface.