weewx.4.6.0: no windrun calculation after update

132 views
Skip to first unread message

David Schulz

unread,
Feb 6, 2022, 3:58:28 AM2/6/22
to weewx-user
hi,

since the update to 4.6.0, i have no windrun calculation. it only outputs 0.

via $day.windrun.sum / $current.windrun there are no more values.

nothing changed on the weewx.conf and i see no errors in the syslog.

[StdWXCalculate]
[[Calculations]]   
windrun = prefer_hardware

David Schulz

unread,
Feb 6, 2022, 6:39:49 AM2/6/22
to weewx-user
problem occurs even with a completely new installation.

 echo "SELECT dateTime, windrun FROM archive" | sqlite3 weewx.sdb
1644146400|0.0
1644146700|0.0
1644147000|0.0
1644147300|0.0  

Karen K

unread,
Feb 6, 2022, 7:47:01 AM2/6/22
to weewx-user
First I would change prefer_hardware by software and hardware in turn and see what happens. Is there a difference in behavior?

Then you may want to set debug high enough to see the LOOP packets in syslog. What wind related values are there?


David Schulz

unread,
Feb 6, 2022, 8:49:57 AM2/6/22
to weewx-user
windrun = software

Solved the problem and the behavior looks the same.

echo "SELECT dateTime, windrun FROM archive WHERE dateTime > 1644154200" | sqlite3 weewx.sdb
1644154320|0.171428571428571
1644154440|0.227210884353742
1644154560|0.25578231292517
1644154680|0.199319727891156
1644154800|0.218421052631579
1644154920|0.250340136054422

thx.

Tom Keffer

unread,
Feb 6, 2022, 6:07:49 PM2/6/22
to weewx-user
Glad you found a workaround, but this is clearly not right. I've opened up issue #737 to track.

--
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/aca739ea-3030-4bd5-a505-96a7f286b951n%40googlegroups.com.

David Schulz

unread,
Feb 6, 2022, 6:11:35 PM2/6/22
to weewx-user
Thank you. I have already replied to this on Github. Same / similar problem exists with ET as well. I also had to change from prefer_hardware to software, otherwise a 0 or 0.0 is always written to the DB, even though I don't have the value in use.
Reply all
Reply to author
Forward
0 new messages