atsio
5 November 2018 01:34
1
Brian, after upgrading to the last two WD builds (82 released at 01/04/2018 and the latest 83 at 04/11/2018), the yesterday’s temperature tags are replaced with dashes.
I rolled back to build 82 (released at 17/10/1918) and the problem is resolved!
Have a look at the attached image.
Thanos
http://www.meteothes.gr
windy2
5 November 2018 02:31
2
that was a bug I introduced, which I have fixed in build 83
(for the next daily reset it will fix it)
sorry about that
atsio
5 November 2018 05:16
3
Thanks Brian, I’ll check it tonight!
Thanos
atsio
6 November 2018 04:40
4
Ok Brian, it has been fixed in latest build 83!
After the midnight reset, the yesterday’s temp values came back to mormal.
Thanks,
Thanos
http://www.meteothes.gr
firewx
7 November 2018 14:15
5
For my setup the yesterdays high humidity and low barometer are still blank with the newest version after the midnight roll over.
gwwilk
7 November 2018 14:26
6
I’m back to ‘NaN’ for yesterday’s high and low, along with ‘NaN’ for Dewpoint High and Yesterday’s Wind Chill.
(Removed ‘Resolved’ from the title of my post!)
I will restore a b82 known fully functional version of WD until these errors get sorted out…,
windy2
8 November 2018 00:19
7
I am not seeing a problem myself here with build 83
maybe try downloading it again?
dan43
8 November 2018 03:13
8
I’m using 10.37S B83, and I still have this issue. How can it be fixed?
windy2
8 November 2018 03:21
9
what do you see when you go to view, daily hi/low data, in WD
(and by doing that, does that fix the issue on the web page)
dan43
8 November 2018 06:41
10
I see the “Extra Daily High/Low Weather Parameters” page, and all of the values for Yesterday are filled in. The values on my main page have been filled in! Thank you for this!
Point of note, the Daily Low Barometer value and time fields are blank.
windy2
8 November 2018 06:55
11
I see what the issue is then
use a new WD update to fix
dan43
9 November 2018 00:40
12
Thanks Brian. Are you releasing B84 to address this issue? I’m not sure I fully understand your statement above, “use a new WD update to fix”.
gwwilk
9 November 2018 00:59
13
B83 2018 Nov 8 addresses the issue nicely.
Thanks, Brian!