This has been a long sought for ability and requested many times in the past. It would work as the variable time context works only include a date along with time. It would be set with global variables. I think a new context would be better then updating the existing time or date contexts.
To clarify a bit more..
I could set --
The forum discussion can be found here..
https://groups.google.com/forum/m/#!topic/tasker/UbcFQndcoaM
Rich, you know this already works? If you put %Start_Epoch_context into the first box on the time context screen, your profile will activate at the roughly the intended time. I say roughly because I've had some issues with it, sometimes it will activate up to a few minutes early so I use a wait action at the start of tasks I run like this if I need their start time to be precise.
I've not tested using an end time set this way.
But the date part is ignored so the context would activate every day at the time portion of the variable which is the reason why this feature is needed.
Arrrg.... A year later and only 5 votes... :(
This issue has been recently highlighted again in this reddit post
https://www.reddit.com/r/tasker/comments/egpyz0/time_context_is_giving_me_headache/
Hopefully we can get get some more attention to this issue.
In addition to respecting the date part of epoch time I believe a total make over (new context) of the variable time context would be a great addition to the now incredibly robust tasker arsenal. If we could get a '%Variable' capability for the "every" portion of the context as well as have it include seconds into time part of the context this would then be a very versatile context.
I couldn't agree more. Time contexts need to be brought into 2020 in Tasker ;)
