Using an extra channel as outside tempurature and humidity with my WMR968

[John Trostel]

I have an add-on Thermo-Hydro sensor being used for my outside Temp and Dewpoint sensor.  Weewx shows my indorr temperature fine, but seems to be having trouble displaying the outside temeprature/humidity.  I can set the sensor to channel 1, 2 or 3.  Is there somewhere in the driver I need to make a change for this to show up?

[mwall]

On Sunday, November 16, 2014 4:06:27 PM UTC-5, John Trostel wrote:

I have an add-on Thermo-Hydro sensor being used for my outside Temp and Dewpoint sensor.  Weewx shows my indorr temperature fine, but seems to be having trouble displaying the outside temeprature/humidity.  I can set the sensor to channel 1, 2 or 3.  Is there somewhere in the driver I need to make a change for this to show up?

hi john,

what do you mean by 'having trouble displaying the outside temeprature/humidity'?

data from the remote sensors should show up as extraTemp1, extraHumid1, extraTemp2, extraHumid2, or extraTemp3, extraHumid3

run weewx directly:

sudo /home/weewx/bin/weewxd /home/weewx/weewx.conf

do you see the extra*N values in the LOOP data?  in the archive data?

m

[John Trostel]

I'm seeing the outside data when I run weewx directly as extraHumid1 and extraTemp1.  Is there a place to make that display on the local webpage?

LOOP:   2014-11-22 18:22:34 UTC (1416680554) {'batteryStatusTH1': False, 'dateTime': 1416680554, 'dewpoint1': -1.045350405615825, 'extraHumid1': 35, 'usUnits': 1, 'extraTemp1': 57.56}

LOOP:   2014-11-22 18:22:39 UTC (1416680559) {'barometer': 30.398700531600706, 'dateTime': 1416680559, 'pressure': 29.149438865918487, 'inHumidity': 32, 'inTemp': 68.72, 'inTempBatteryStatus': False, 'altimeter': 30.31673419174993, 'usUnits': 1, 'inDewpoint': 3}

LOOP:   2014-11-22 18:23:11 UTC (1416680591) {'totalRain': 2.34251968265, 'rain': 0.0, 'dateTime': 1416680591, 'rainBatteryStatus': False, 'dayRain': 0.0, 'rainRate': 0.0, 'usUnits': 1}

LOOP:   2014-11-22 18:23:18 UTC (1416680598) {'batteryStatusTH1': False, 'dateTime': 1416680598, 'dewpoint1': -1.440166392771242, 'extraHumid1': 34, 'usUnits': 1, 'extraTemp1': 57.56}

LOOP:   2014-11-22 18:23:21 UTC (1416680601) {'barometer': 30.398700531600706, 'dateTime': 1416680601, 'pressure': 29.149438865918487, 'inHumidity': 32, 'inTemp': 68.72, 'inTempBatteryStatus': False, 'altimeter': 30.31673419174993, 'usUnits': 1, 'inDewpoint': 3}

John Trostel

jtro...@gmail.com

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/WxuyI4DoakM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mwall]

On Saturday, November 22, 2014 1:26:23 PM UTC-5, John Trostel wrote:

I'm seeing the outside data when I run weewx directly as extraHumid1 and extraTemp1.  Is there a place to make that display on the local webpage?

you must modify the skin to display additional observations.

as an example, consider the Standard skin.  in skins/Standard/skin.conf you tell weewx to include extraTemp1 and extraHumid1 in plots.  for example, if you want extraTemp1 in the same plot as outTemp and dewpoint, then change this:

        [[[daytempdew]]]
            [[[[outTemp]]]]
            [[[[dewpoint]]]]

to this:

        [[[daytempdew]]]
            [[[[outTemp]]]]
            [[[[extraTemp1]]]]
            [[[[dewpoint]]]]

similarly for humidity.

to display current readings, modify skins/Standard/index.html.tmpl.  for example, change this:

              <tr>
                <td class="stats_label">Outside Temperature</td>
                <td class="stats_data">$current.outTemp</td>
              </tr>

to this:

              <tr>
                <td class="stats_label">Outside Temperature</td>
                <td class="stats_data">$current.outTemp</td>
              </tr>
              <tr>
                <td class="stats_label">Extra Temperature</td>
                <td class="stats_data">$current.extraTemp1</td>
              </tr>

see the Labels section in skin.conf to assign a label to extraTemp1.  the customizing guide describes these things in much greater detail.

m

[John Trostel]

Hacking about with the skins has let me show the outside temperature...  Any idea how to send it correctly to Wunderground?

John Trostel

jtro...@gmail.com

--

[Stephen Emert]

Wow, I am reviving an old one but I face the same issue. My original Channel 1 humidity sensor died and there are no reliable replacements to be found. So I purchased an add-on outdoor temp & humidity sensor. So I need channel 2 to be the default to send data to Weather Underground. I am also making the move from Cumulus on a Windows Home Server V1 to weewx on a Raspberry PI, so I am a bit in the weeds. Looks like it is just a matter to modify the driver file to change the mappings for the channels. John, did you solve this problem by chance?

[Stephen Emert]

For prosperity.

This was actually very easy to fix.

I found the definition of the driver here:

https://github.com/weewx/weewx/blob/master/bin/weewx/drivers/wmr9x8.py

So I just changed my default mappings on lines 148 & 149 and 158 & 159 so that the extra sensors wrote to the default slots in weewx and the default sensors wrote to the extra slots.

[gjr80]

Hi,

Modifying a .py can be a risky business, at the very least you open your self up to losing your changes in the future during an upgrade. Sensor maps are typically able to be controlled from a config file. Looking at the WMR9x8 driver you should be able to set the sensor map by using a sensor_map stanza under [WMR9x8] in weewx.conf. Something like (untested):

# This section is for the Oregon Scientific WMR918/968

[WMR9x8]
    ....
    [[sensor_map]]
        outTemp = temperature_1
        outHumidity = humidity_1

would remap temperature_1 and humidity_1 to WeeWX fields outTemp and outHumidity respectively. When starting WeeWX the sensor map is logged by the driver so changes can be verified by referring to the log (and of course by what data goes in what fields in your archive!).

Gary'

[Stephen Emert]

Thanks Gary!

Now that you told me about this, I was able to find the documentation that talks about it! lol

I was worried about updating and solving that was my next project, now i do not have to!!

Much obliged, Stephen