Author Topic: rtldavis below zero temperatures  (Read 895 times)

0 Members and 1 Guest are viewing this topic.

Offline RunnerDan

  • Member
  • *
  • Posts: 2
rtldavis below zero temperatures
« on: December 22, 2022, 12:06:16 PM »

If this has already been answered, I apologize ahead of time, but I haven't been able to find a clear answer by searching.

I'm running weewx v.4.9.1 on a Raspberry Pi 4B, reading data from my Davis wireless VP2 via rtldavis v.0.15.

Everything had been working fine for the past month or so until yesterday evening when the outside temperature dropped below zero.  I see that some time ago this issue was recognized (, so I think I must not be using the best version of rtldavis.  But I'm having trouble determining which one I should be using.  I see the github lheijst / rtldavis version (which I think is what I have) with lots of forks and a lheijst / weewx-rtldavis version...

If I could get some direction on what would be the best one I should be using that would be awesome!

- Dan

Offline vinceskahan

  • Senior Contributor
  • ****
  • Posts: 155
    • home site
Re: rtldavis below zero temperatures
« Reply #1 on: December 22, 2022, 06:12:55 PM »
Another good question for the weewx-user google group.... (
WeeWX sites:
  Davis VP2+DFARS to a pi4
  EcoWitt GW1000, WH32 outdoor T+H, multiple WH31 indoor T+H, WH51 soilMoisture (docker)
  Davis AirLink (inside)
  PurpleAir (outside)
Home site:
Wunderground: KWAFEDER15
PWS:                KWFEDER15
CWOP:              CW6881

Offline bahuga

  • Member
  • *
  • Posts: 10
    • Meteo-Sciez
Re: rtldavis below zero temperatures
« Reply #2 on: December 25, 2022, 06:47:52 AM »
You may have a look at the following issue, listed in rtldavis GitHub issues section :    , and try the proposed code modifications .
Davis Vantage Pro 2

Offline RunnerDan

  • Member
  • *
  • Posts: 2
Re: rtldavis below zero temperatures
« Reply #3 on: December 25, 2022, 10:09:55 AM »
Awesome!  Thanks!  I'll take a look at that.  I wonder what it takes to get this rolled out into the regular github package.  I saw that this issue was identified by Luc about 3 years ago, but it still seems to be a problem in the normal package...