Missing sensors on seasons skin

[Doug Couper]

Using a gw2000 with the gw1000 gate driver version 0.5.0

I have 8 soil moisture sensors and 2 air quality sensors

After much searching and trailing different configurations I cannot get four of the  soil moisture sensors and one of the air quality sensors to display information on the web page 

The driver output is displaying the data for all the sensors, I just cannot get the additional data to display on the seasons skin.

Looking at the Hilo.inc sensors.inc skin.conf does not present any clue as to why these are not displaying 

Any assistance would be appreciated 

Doug

https://baldivisweather.ddns.net

[gjr80]

The first point of call when customising what sensors are displayed by the Seasons skin v4.7.0 or later is the [DisplayOptions] section of the Seasons skin config file, skin.conf. Sensor data display in earlier versions of the Seasons skin relied on the content of the relevant Seasons skin template files and the content of skin.conf, in v4.7.0 much of this was parameterised making it much easier for users to customise the skin. For v4.7.0 or later you really don't want start digging in the templates unless you are doing some hardcore customisation.

In your case work through the various settings under [DisplayOptions], the comments should guide you and most are fairly self explanatory. In general, the order of items in lists determines the order of display. One thing to remember, in order to plot any sensor data you need to be saving that sensor data to database; so you may need to add a few columns to your database. The utility wee_database is your friend and the process is covered here in the Customization Guide.

Once you have your skin settings down pat you may wish to include them as skin overrides in weewx.conf, but that is another story.

Gary

[Tom Keffer]

The Seasons skin uses a limited list of observation types in deciding whether to display something. If a type is not in the list, it won't get displayed unless you add it.

Look in skin.conf, for section [DisplayOptions]. The list of which types to display under "Current Conditions" is option "observation_current". For "Statistics", it's "observation_stats". And so on. Just add your types to the appropriate list. If a type is already in the list but not displaying, then something else is going on.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9b431446-5a89-4cb4-87d3-6806e1665782n%40googlegroups.com.

[Doug Couper]

Thanks for the information Gary and Tom

I know have all the sensor data displaying, looks like the lines for the sensors was missing in the database.

Now another issue has cropped up and again probably a very simple fix, the original soil moisture sensors display cb as the unit and the new ones display a percentage which I would consider correct, how do I change the unit for the old ones??

That said the data from the second air quality though correct from what I can see is showing as a number with 6 decimal places and no unit, how can this be fixed??

Doug

https://baldivisweather.ddns.net

[gjr80]

First pm25_2. You typically see WeeWX displaying a numeric field with many decimal places when WeeWX either (1) does not know what unit group a particular observation belongs to (in other words WeeWX does not know if this is a temperature or a speed etc so it just displays the data as stored internally and with no unit label) or (2) does not know how to format the field. In this case I am betting the former, since earlier we were talking about adding new fields to the database. There is another step - telling WeeWX what unit group the new field belongs to - I should have mentioned this in my earlier post. The relevant part of the Customisation Guide is the section Assigning a unit group. In this case the pm25 fields belong to the group_concentration unit group (refer to the Unit groups, members and options table). To assign pm25_2 to the group_concentration unit group you need to edit extensions.py (it will be in either /home/weewx/bin/user/ or /usr/share/weewx/user/ depending on your WeeWX install) and add the following lines:

import weewx.units
weewx.units.obs_group_dict['pm25_2'] = 'group_concentration'

Save extensions.py and restart WeeWX. On the next report cycle you should now see pm25_2 being formatted as per the default concentration formats.

On to soil moisture. The default units used by WeeWX for soil moisture is the centibar, due largely to this being the units used by Davis station for soil moisture. Ecowitt on the other hand reports soil moisture as a percent. Both centibar and percent use a range of 0 (or 1) to 100, though I understand there is no direct correlation between the two. In any case, the numbers are fine but the displayed units are not. In your case you have a couple of options:

1. you can change the unit group for the soil moisture fields of interest from group_moisture to group_percent 

2. you can change the unit label for centibar from cb to %

I favour the former as that way you are only changing the sensor data for the sensors of interest. If you choose the latter you are effectively changing the units for all soil moisture sensors including any you might add in the future. Plus with (2) WeeWX still considers soil moisture to be in centibars (even though it is not for your sensors) it is just displaying a different unit label.

To change unit groups for your sensors you need to add a few more lines to extensions.py (just like for pm25_2), something like the highlighted lines:

import weewx.units
weewx.units.obs_group_dict['pm25_2'] = 'group_concentration'

weewx.units.obs_group_dict['soilMoist1'] = 'group_percent'

weewx.units.obs_group_dict['soilMoist2'] = 'group_percent'

weewx.units.obs_group_dict['soilMoist3'] = 'group_percent'

weewx.units.obs_group_dict['soilMoist4'] = 'group_percent'

Again a change to extensions.py will require a WeeWX restart to take effect and the change should be evident on the next report cycle.

[Doug Couper]

Thanks again Gary

Yes some of the sensors where commented out fixed that, and fixed the fat fingered problem with the air quality sensor

All working correctly 

Doug