ws6in1 sensor mapping

67 views
Skip to first unread message

Steven Garré

unread,
Nov 18, 2020, 10:36:08 AM11/18/20
to weewx-user
Hello

My main unit from the Garni935pc gets too hot when the sun is all out. So i tried to make my second sensor in the Stevenson screen make the default sensor for reporting to website/WU/WOW but can't make it to work.

I tried the following:

[WS6in1]
    driver = user.ws6in1
    [[sensor_map]]
    outTemp =  extraTemp1
    outHumidity =  extraHumid1

But makes no difference. How do i make this work?

Kind regards
Steven


Bob Atchley

unread,
Nov 18, 2020, 12:30:26 PM11/18/20
to weewx-user
Hi Steven,

I'm afraid, put very simply, this is a driver option that I have not implemented in the WS6in1 driver.
As I now have an additional sensor this is something I could add ... I'll have a play this weekend.

Personally I have the identical Youshiko YC9388 and I find the temperature accuracy to be very good (compared to an old WS2300 - mounted in a stevenson screen ... sort of.  Also compared to other local weather stations)

I'd be interested to see the temperature differences you are getting between the main unit and your extra sensor (on a day with the sun out!)

Regards

Bob

Steven Garré

unread,
Nov 18, 2020, 1:02:06 PM11/18/20
to weewx-user
Hello Bob

Well, that would be really amazing if you can implement the driver.
 
i'm a bit disappointed in the Garni935 mean unit. Offcourse when it's cloudy or at night the unit is mostly spot on. But otherwise in full sun i'm getting readings with more than 1°C-1.5C difference with the closest Davis or more official stations. (and it's not even summer yet) As back up i'm using a TFA weatherhub sensor (and the second Garni sensor), wich never reads those temp differences, so it must be the unit sadly enough. 

Only other options left is tweaking the screen off the sensor mean unit, or placing the whole unit in the shade wich than renders the anemometer and UV-meter useless.

Regards
Steven

Op woensdag 18 november 2020 om 18:30:26 UTC+1 schreef Bob Atchley:

Jarda Uher

unread,
Nov 18, 2020, 3:56:43 PM11/18/20
to weewx-user
Hello Steven and Bob
I also use a garni 935 pc with one external sensor in the weewx 4.2.0 configuration, I use the ws6in1 driver version 0.8 and the Belchertown 1.2 skin. I didn't have to use sensor_map in weewx.conf, but just write the sequence to graps.conf.example in the skin. the temperature display will then appear on the graph page. Bob's driver works without problems and is able to load more sensors in the database.
[[chart1]]
        title = Teplota
        [[[outTemp]]]
            zIndex = 1
            name = Temperature
        [[[extraTemp1]]]
            name = Přízemní teplota
        [[[appTemp]]]
            name = pocitová teplota
            color = "#f7a35c"
        [[[dewpoint]]]
            color = purple

Best regards
Jarda
Dne středa 18. listopadu 2020 v 19:02:06 UTC+1 uživatel steven...@gmail.com napsal:

gjr80

unread,
Nov 18, 2020, 4:18:22 PM11/18/20
to weewx-user
Hi,

If a driver does not support sensor mapping you can in some cases use the StdCalibrate service to achieve a similar outcome. For example, to have your second sensor fill outTemp/outHumidity you could place something like the following under [StdCalibrate] in weewx.conf (untested):

[StdCalibrate]
    [[Corrections]]
        outTemp = extraTemp1
        outHumidity = extraHumid1

Of course this relies on the driver placing the data you seek in extraTemp1 and extraHumid1. This will result in your extraTemp1 value appearing in both outTemp and extraTemp1. You could use a further correction to set extraTemp1 to None, but that would interfere with archive records as corrections are applied to both loop packets and archive records. Likewise for extraHumid1.

If you did want to keep your original outTemp data you could first place it in another field, say extraTemp2 by including something like:

[StdCalibrate]
    [[Corrections]]
        extraTemp2 = outTemp
        outTemp = extraTemp1

If saving the original outTemp to database is not important you could instead save it to a new field, say outTemp_orig. This would make the current (original outTemp) data available in reports via the $current.outTemp_orig tag but it would not be saved to database. Againlikewise for outHumidity.

There are a couple of caveats though; first you need to be using WeeWX v4.2.0 or later. Second is that order matters with the lines under [[Corrections]], corrections are applied in the order they appear.

Gary

Steven Garré

unread,
Nov 18, 2020, 5:42:33 PM11/18/20
to weewx-user
Gary,

Thanks! Just tried this and works like a charm. Data from outTemp isn't needed because of the inaccurate readings, so i used the first option.
Really grateful for the help. 

Kind regards
Steven

Op woensdag 18 november 2020 om 22:18:22 UTC+1 schreef gjr80:
Reply all
Reply to author
Forward
0 new messages