The Seasons skin has an automatic provisioning feature where it will display and plot data which is non-null in your database.
For whatever reason, both extraHumid1 and UV are not null. For example, look at this packet in your log:
Dec 16 19:59:50 solar weewx[522] DEBUG user.interceptor: mapped packet: {'dateTime': 1671181189, 'usUnits': 1, 'pressure': 29.92, 'outHumidity': 61.0, 'inHumidity': 51.0, 'outTemp': 62.96, 'inTemp': 71.42, 'windSpeed': 2.91, 'windGust': 6.93, 'windDir': 188.0, 'radiation': 2.45, 'rain': 0.0, 'rainRate': 0.0, 'UV': 0.0, 'extraTemp1': 62.96, 'extraHumid1': 61.0, 'soilMoist1': 48.0, 'soilMoist2': 57.0, 'soilMoist3': 41.0}
Perhaps you have sensors you didn't know you had, or perhaps you are picking up a neighbor's sensors, or perhaps your sensor mappings are incorrect. You'll have to sort that out.
If you don't believe these numbers and want to suppress them, you have two options:
Option 1. Remove them from your sensor mappings. This will cause them to become null values in your database. Seasons looks back 30 days to decide whether a sensor has non-null values. So, after a month, it will self-correct. If you don't want to wait a month, you can modify the database and set the values to null yourself.
Option 2. Suppress the values from being displayed and plotted. They'll still be in the database, but they won't get displayed. Go into the Seasons configuration file Seasons/skin.conf and remove 'extraHumid1' and 'UV' from options 'observations_stats' and 'plot_groups'.
-tk