For those of us on the other side of the world, having the azimuth sensor jump from 0 to 360 in the middle of the day means that using something like a threshold helper doesn’t work (higher than 290 and lower than 50 never triggers).
I propose to have a sensor that goes between -180 and 180 so that the southerners can use some of the built in functions a bit more easily.
I figure having a second sensor would be easier to develop and more backwards compatible, but having a toggle within the existing or even have it automatically switch based on latitude may be neater.
Now for the defence:
Yes you can write your own sensors to factor in the reset, and this will give you more control over it too, but some people simply rather staying away from code or aren’t familiar with yaml syntax and want to just get something working without having to half learn yet another language
You could make your own azimuth sensor for your location, which is what I have done (see below for snippet) and use that instead.
You could also just poke your head out of the door and do away with the automation… 
… but that’s no fun
For anyone who would benefit from this, here is the details of the sensor I created to do this:
Vote for this feature
New Helper>Template>Sensor
Name: Sun Solar Azimuth Southern
State Template:
{% if states('sensor.sun_solar_azimuth') | float > 180 %}
{{ (states('sensor.sun_solar_azimuth') | float) -360 }}
{% else %}
{{ (states('sensor.sun_solar_azimuth') | float) }}
{% endif %}
Unit of Measure: degree symbol (alt+ 0176)
Device: Sun
Save
For good measure change the icon to mdi:sun-angle