This time of year is dark, at least in my part of the world. The sun heads out the door at about 15:00, making it seem like it’s the middle of the night by the time a lot of people finish work. My Outside Tasker profile therefore needed an upgrade to handle this time of year, allowing it to intelligently set the brightness depending on whether or not it’s dark outside or not, rather than just blasting it up to max like it did during the summer months.
I didn’t make much out of it this time, going for a simple manually changed time-based solution. My Outside profile now has the section you see in the screenshot, where it checks to see if %TIME is above a certain value (15 in my case) and act accordingly. If it is, it’s dark outside, and it sets the brightness to about 40%. If it’s not, it sets it to max. Since the Outside profile only triggers when I’m outside, other scenarios aren’t part of this specific task.
You can however make much more out of this than I did. Perhaps the most natural thing to do would be to create a profile that checks sunset/sunrise data online, and act accordingly. That is quite simple to do using standard variable data processing techniques. I’ll probably do that too soon, as the current system needs to be manually changed as the sunset time changes. All you really need to do is get sunset data, and do an if condition to see if %TIME is larger- assuming you use 24 hour format for time, AM/PM is more complicated. You could also make it weather-dependent, setting the brightness lower on a cloudy day, or you could make it more dynamic, using different brightness values depending on how long it’s been since the sun set.
I don’t know if it’s just me, but the automatic brightness on all my devices is very far off from what I would consider decent brightness in any given situation. As such, I prefer to handle it myself using Tasker.