> My version of ideal is ssh access only to the command line and no GUI
involved.
+1
And get a firewall and VPN in.
> On Dec 9, 2020, at 11:04 AM, Greg Troxel wrote:
>
>
> Sunray writes:
>
>> Sorry if this has been brought up already. I plan to install a Raspberry Pi
>> running Weewx at a r
I’ve been grappling with this. It is annoying. The “new site” is maddening to
interact with: https://radar.weather.gov/
There’s a FAQ about the change here:
https://www.weather.gov/radarfaq
The FAQ tells one where files can be downloaded. I’ve started to look at them
(they are gzipped), but,
about 30m old:
https://radar.weather.gov/ridge/lite/KMUX_1.gif
It’s not clear one could determine which file has the latest image. Maybe this
will improve over time and the _0.gif will have the latest gif (and/or the loop
will be updated regularly).
> On Dec 17, 2020, at 4:18 PM, John Kl
://radblast.wunderground.com/cgi-bin/radar/WUNIDS_map?station=OAX&brand=wui&num=18&delay=15&type=N0R&frame=0&scale=1.000&noclutter=0&showstorms=0&showlabels=1&severe=1&rainsnow=0&lightning=0&smooth=0
> On Dec 17, 2020, at 10:00 PM, John Kline wrote:
>
>
The loops in https://radar.weather.gov/ridge/lite/ seem to be up to date today.
For example:
https://radar.weather.gov/ridge/lite/KMUX_loop.gif
As such, that’s also an option, although these gifs are tough to get used to.
> On Dec 18, 2020, at 9:38 AM, John Kline wrote:
>
>
It looks like you are running python3. Try:
apt install python3-ephem
> On Dec 19, 2020, at 9:30 AM, Kevin Davis wrote:
>
>
> pi@smith:/var/www/html/weewx $ python
> Python 2.7.16 (default, Oct 10 2019, 22:02:15)
> [GCC 8.3.0] on linux2
> Type "help", "copyright", "credits" or "license" for
$current.windSpeed.format(add_label=False) is equivalent to
$current.windSpeed.formatted
The latter being a little shorter to type.
Instead of MPH, you could use $unit.label.windSpeed
> On Dec 20, 2020, at 4:01 PM, Rob Cranfill wrote:
>
> Thanks, all! Looks like there is more than one way to a
I'm pissed at WU, I'm going to use their gif while it's
>>>>> available.
>>>>>
>>>>>> On Sat, Dec 19, 2020 at 7:17 AM wfs...@gmail.com
>>>>>> wrote:
>>>>>> Yes John kind of crummy image
Only the IP data logger is discontinued:
https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/
The USB and serial loggers are still being sold by Davis:
https://www.davisinstruments.com/product/weatherlink-windows-usb/
https://www.davisinstruments.com/product/weatherlink-win
Station volts is not in the default map. It wouldn’t be hard to add.
I did the IP100 port to WeeWX 4 and fixed bugs in the driver (and bumped the
version to 0.5 in my fork). I’m presuming you are running it.
Although I’m not currently running the driver, I did run it for almost two
years and
You don’t to delete records. There isn’t really much to the rain calculation.
For all rain that occurred while WeeWX is up and running, the day_rain_total
will increment, the driver will calculate the delta and add it to the loop
record as ‘rain’. For the discrepancy to occur, 0.09 inches wou
The IP100 resets the day’s rain total at midnight (according to it’s clock).
It doesn’t really matter to the driver when that happens. The driver is simply
looking for a positive increment in day_rain_total. On a negative increment
(e.g., reset), the driver just saves the last value and repor
> Once I sort this possible discrepancy, I'd like to pick your brain on adding
> the Station Volts.
I added it at head. Station volts will now show up as supplyVoltage.
> On Jan 4, 2021, at 7:44 PM, John Kline wrote:
>
>
> The IP100 resets the day’s rain total at
; On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>> > Once I sort this possible discrepancy, I'd like to pick your brain on
>> > adding the Station Volts.
>>
>> I added it at head. Station volts will now show up as supplyVoltage.
&g
ctly find the inclusion of the
>>> station volts you noted in your last comm (btw Thanks for addressing).
>>>
>>> On Monday, January 4, 2021 at 9:58:26 PM UTC-8 jo...@johnkline.com wrote:
>>>> > Once I sort this possible discrepancy, I'd like to
;>>>
>>>>> Hi John,
>>>>>
>>>>> After leaving the server run uninterrupted, all of the data being
>>>>> displayed on weewx is ticking to the ip-100 console.
>>>>>
>>>>> Apologies for my ignorance, where ca
gt;
>>>>>> Then:
>>>>>>
>>>>>> sudo wee_extension --install master.zip
>>>>>>
>>>>>>
>>>>>>>> On Jan 6, 2021, at 8:54 AM, tim lambert wrote:
>>>>>>>>
>>
ine.com
>>>>>>> wrote:
>>>>>>>>> where can I exactly find the inclusion of the station volts
>>>>>>>>
>>>>>>>>
>>>>>>>> Download this file:
>>>>>>>> https://gi
Use the instructions in the second link Gary provided.
wee_extension --install weewx-forecast-3.4.0b11.zip
> On Jan 15, 2021, at 7:46 PM, Kevin Davis wrote:
>
>
> I'm working off the branch you sent, but the one I initially was working off
> does ref the tgz not zip
>
> 1) run the installe
ster.zip not weewx-forecast-3.4.0b11.zip
>>
>> What am I missing?
>>
>>> On Fri, Jan 15, 2021 at 8:26 PM John Kline wrote:
>>> Use the instructions in the second link Gary provided.
>>>
>>> wee_extension --install weewx-forecast-3.4.0b11.zip
cast-master.zip from there, it is the latest release,
> which in this case IS 3.4.0b11.
>
> Had I needed a specific release, I can go to the Release link on the right
> side.
>
> Sorry it took me a bit to get spun up.
>
>
>
>
>
>
>> On Sat, Jan 1
See the 4.3 change log here:
https://github.com/weewx/weewx/releases
The WMR200 driver is no longer supported. An unsupported version can be found
at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and
Oregon WMR300 will continue.
> On Jan 20, 2021, at 1:46 PM, Invisible Man
I don’t recommend reverting to 4.2 as it has some issues.
The problem you are describing now is do to some issues in your db;
specifically, intervals of 0 (4.3 is less forgiving). I found a thread to
address it from Jan 6. I’ve pasted Tom’s response below. Rather than deleting
records, if yo
I don’t use this driver, but looking at the driver code, it looks like you
would see the following message *fragment* in the log when it finishes
processing the missed archive records:
genStartup() phase exiting since looks like all
As I don’t have experience with this driver, you are better o
I had a look. This does not mean the database is bad. The code needs a small
fix as it’s using a variable that isn’t set if there are no records in the
database.
> On Jan 21, 2021, at 12:37 PM, S R wrote:
>
>
> if i run wee_database -- check on the sdb that was installed during the
> inst
:42 PM, John Kline wrote:
>
>
> I had a look. This does not mean the database is bad. The code needs a
> small fix as it’s using a variable that isn’t set if there are no records in
> the database.
>
>>> On Jan 21, 2021, at 12:37 PM, S R wrote:
>>>
&g
Damn, that’s funny.
I was giving you a partial line, that is what I was calling a fragment.
grep for “ genStartup() phase exiting since looks like all”
> On Jan 21, 2021, at 12:43 PM, Invisible Man wrote:
>
> >it looks like you would see the following message *fragment* in the log
>
> I hav
As such, I don’t *think* your problem is that it’s still processing old archive
records.
Others will have to help you with FTP. It’s probably not the driver and
perhaps not related to 4.3. You might need debug = 2 to see FTP progress in
more detail in the log. I don’t use FTP in weewx (I use
I don’t know that it is your problem, but does your hardware provide windchill,
heatindex and rainRate? I would change those entries back to prefer_hardware
in weewx.conf.
> On Jan 22, 2021, at 6:42 AM, Invisible Man wrote:
>
>
> Up :)
>
> Please assist. It's really an issue, because my we
I’m not sure why you keep mentioning simulator (as in extension/simulator).
Do you have the following line in your weewx.conf?
driver = simulator
If so, it should not be there.
> On Jan 23, 2021, at 8:49 AM, Invisible Man wrote:
>
>
> Hello,
>
> My outside temperature, my barometer, my dew
I meant to say station_type.
You do not want:
station_type = Simulator
You are seeing dummy data from the simulator.
> On Jan 23, 2021, at 9:43 AM, Invisible Man wrote:
>
>
> > sudo wee_config --reconfigure --driver=user.wmr200 --no-prompt
>
> I have to do it after an apt upgrade weewx ?
>
> I really fail to understand why the doc says to do that...
When freshly installing weewx, it is not possible to choose a driver UNLESS it
comes with weewx. But you need to pick something, so the doc says to pick
simulator. Once you install the wmr200 driver, you want to switch to using the
> File "/home/weewx/bin/user/rtgd.py", line 1007
It looks like you need to update real time gauge data:
https://github.com/gjr80/weewx-realtime_gauge-data
> On Jan 24, 2021, at 7:41 AM, WxManAJB wrote:
>
> Thanks Vince. I upgraded the forecast extension to 3.4.0b11 and am still
> getting an er
What versions of the forecast and steel series extensions are you using?
> On Jan 24, 2021, at 8:12 AM, sbar...@gmail.com wrote:
>
> Hello,
>
> I have been struggling a bit with my update to 4.3. So I ended uninstalling
> everything,
> upgrading to raspbian 10, and reinstall from setup.py wi
As for the forecast extension, please install:
https://github.com/chaunceygardiner/weewx-forecast/releases/tag/v3.4.0b11
> On Jan 24, 2021, at 11:26 AM, gjr80 wrote:
>
> On Monday, 25 January 2021 at 02:12:46 UTC+10 sbar...@gmail.com wrote:
>>
>> - SS skin seem to reference an older version o
It seems weewx-simple does not (yet) support Python 3.
> On Jan 24, 2021, at 12:46 PM, sc.lep...@gmail.com
> wrote:
>
> Hello
>
> I used the simple template from https://github.com/matthewwall/weewx-simple
>
> My platform
> Debian10 / Python 3 /last Weewx (4.3.0)
>
> When I activate simp
> but data refresh every 5 minutes, with the rest skins of weewx
Exactly what data are you talking about that refreshes every five minutes?
> On Jan 26, 2021, at 6:02 AM, Δημήτρης Βήχος wrote:
>
> i was easily installed the loop-data extension yesterday. i use weewx 4.3
> with wh1080 weather
How often does your driver write loop records?
Would you please check the actual loop-data.txt file, rather than the skin’s
report, to see if that file is being updated on every loop record?
> On Jan 26, 2021, at 7:15 AM, Δημήτρης Βήχος wrote:
>
> the loop-data.txt
>
> https://kairos.moudani
Again, how often does your driver write loop records?
loop-data.txt is not written in reporting cycles. I am asking you to look at
the actual loop-data.txt file that is written to the .../loopdata directory.
How often does the contents of that file change.
Also, please show what entries you a
OK, the behavior we are seeing leads me to believe your web server is on a
remote machine; i.e., not on the same machine as weewx. Is that correct? If
so, you’ll need to use rsync by filling out and enabling it under:
[LoopData]
[[RsyncSpec]]
> On Jan 26, 2021, at 7:57 AM, Δημήτρης Βήχος
As the README states:
If you need the loop-data.txt file pushed to a remote webserver, you will also
need to fill in the RsyncSpec fields; but one can fill that in later, after
LoopData is up and running.
It appears loopdata is up and running and working on the local machine. Have
you set up r
> remote_server = ftpupload.net
I would expect the remote server to be kairos.moudania.com
It looks like you are trying to use an ftp server. If so, that simply won’t
work.
If you don’t have ssh access to your server, such that you can get rsync to
work, you will not be able to use the loopdata
Are you using python3? What version of WeeWX?
Have you tried re-downloading the loopdata release?
> On Feb 3, 2021, at 5:07 PM, Michael Boccabella wrote:
>
> Hi All,
>
> I am new to this group, and weewx in general. I just installed weewx about 4
> weeks ago and am still playing around with
Thanks, Tom. I did not notice that.
> On Feb 3, 2021, at 5:41 PM, Tom Keffer wrote:
>
>
> You almost have the syntax right, but you're missing the --install option.
> You want
>
> sudo wee_extension --install=/var/tmp/weewx-loopdata-2.7.2.zip
>
>
>> On Wed, Feb 3, 2021 at 5:07 PM Michael
Hardcoding a timestamp makes it not a timestamp and will accomplish nothing.
Try this:
#import time
#set $cachebuster = time.time
> On Feb 6, 2021, at 6:22 AM, ginfo...@gmail.com wrote:
>
>
> No way:
> I added the timestamp to the images but it doesn't work!
>
> "daytempdew.png? v =
The two lines you are asking about should be entered exactly one time in each
template where you are adding a ?$cachebuster to an image URL. It should be
entered above the first time you use it.
> On Feb 6, 2021, at 8:53 AM, ginfo...@gmail.com wrote:
>
>
> It works !!!
>
> You are a genius
It’s intentional. Midnight is considered part of the previous day. If you
think about it, the midnight archive period is for the period from
minutes before midnight (often 23:55) through to midnight.
It belongs in the previous day.
> On Feb 15, 2021, at 4:41 PM, Dan Ciarniello wrote:
>
>
It’s the key, listed under my devices on WU, for that particular station.
> On Feb 21, 2021, at 6:21 AM, Timothy Butcher
> wrote:
>
> When setting up for Weather Underground, is the password to be the account
> password or the Key in system device. I have everything seeming to be
> working
> I have been trying to boot from RPI4 for 3 days now without success. I will
> keep trying.
I went through some drives and enclosures until I found some that work. I’m
running 1TB drives on three RPi 4s and 500GB drives on three other RPi 4s.
This enclosure (for NVMe SSDs) works:
https://smi
Try “http:” (rather than “https:”).
> On Mar 6, 2021, at 10:43 AM, michael.k...@gmx.at
> wrote:
>
> Is there something wrong with https://weewx.com/stations.html?
>
> I don't get a map shown...
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" g
If you installed the latest release, the command is:
wee_extension --install weewx-weatherlink-live-v1.0.5.tar.xz
If you cloned the git repository into, for example,
/home/foo/bar/weewx-weatherlink-live, use the command:
wee_extension --install /home/foo/bar/weewx-weatherlink-live
or cd to /home/
Did you miss the period at the end of the line? It is required.
> On Mar 11, 2021, at 3:40 PM, troutwitted wrote:
>
> actually, I spoke too soon because when I tried to list extensions, nothing
> appeared and I just realized I got this error:
> wee_extension: error: --install option requires
For forecast in WeeWX 4.x, you should have better luck installing:
https://github.com/chaunceygardiner/weewx-forecast
> On Mar 22, 2021, at 1:18 PM, craig@gmail.com
> wrote:
>
>
> I have two problems that I may have caused myself (noob). I have had weewx
> running fine on my raspberry pi
I don’t see W2IRT listed here:
http://www.wxqa.com/members.txt
I’m not sure; but perhaps it is no longer registered? A better place to ask
that question (is it registered), is here:
https://www.wxforum.net/index.php?board=15.0
> On Mar 22, 2021, at 3:38 PM, Peter Dougherty wrote:
>
> It occ
Well, I am seeing the data coming in here (W2IRT == E0732):
https://weather.gladstonefamily.net/site/E0732
> On Mar 22, 2021, at 4:00 PM, John Kline wrote:
>
>
> I don’t see W2IRT listed here:
> http://www.wxqa.com/members.txt
>
> I’m not sure; but perhaps it is no
It looks like every 5 minutes to me, no?
http://www.findu.com/cgi-bin/raw.cgi?call=W2IRT
> On Mar 22, 2021, at 7:03 PM, Peter Dougherty wrote:
>
>
> Sorry to be so daft, but I honestly could not understand this. I’m a
> “set-it-and-forget-it” user so I’m not up on all the terminology, I’m a
Hi,
These are calculations based on the pm2_5_cf_1, pm2_5_cf_1_b, current_humidity
and current_temp_f values returned from calling http:///json
Specifically, method is in the code here:
@staticmethod
def compute_pm2_5_us_epa_correction(pm2_5_cf_1: float, pm2_5_cf_1_b: float,
current_hu
> If you don't save the purpleair temperature and humidity with the particle
> concentration then you must be using the current temperature to calculate the
> AQI during the graph generation. Is this the correct assumption?
That is not correct. I do use the purpleair temperature and the purple
I have seen an issue when weewx calls set_time within the hour after falling
back to standard time (because there is no way in the command to state the time
is in DST and the console assumes standard time). I got around this issue by
forking the driver and adding code such that set_time does no
> heck, i have never had to clear logger memory
ditto
> On Mar 28, 2021, at 7:04 AM, Graham Eddy wrote:
>
>
> i have never seen this problem viz having to clear logger memory to fix DST
> transition. heck, i have never had to clear logger memory
>
>> On 29 Mar 20
one hour off.
Having said that, I believe this is a bit off topic as this issue doesn’t
result in memory having to be cleared; and the issue being reported in this
thread seems to require clearing memory.
> On Mar 28, 2021, at 7:11 AM, Greg Troxel wrote:
>
>
> John Kline writes:
&g
Hi Greg,
It’s why I asked if they have the DST set correctly in the console.
> On Mar 28, 2021, at 7:14 AM, Greg Troxel wrote:
>
>
> I wonder if the people who are having trouble are in a situation where
>
> the console's firmware idea of DST
>
> and
>
> their computer's idea of DST
>
>
h to 2040 and drivers that ignore
set_time around those transitions.
> On Mar 28, 2021, at 7:23 AM, Greg Troxel wrote:
>
>
> John Kline writes:
>
>> You have to be unlucky to see the issue. If WeeWX decided to set the
>> time on the console within the hour of set
Greg, that would be a problem. For firmware that doesn’t recognized current
DST rules, setting the times manually would be required. I think the console
(at least with current firmware) allows this.
> On Mar 28, 2021, at 7:30 AM, Greg Troxel wrote:
>
>
> John Kline writes:
&g
Please run:
sudo apt update
sudo apt full-upgrade
Then try your install.
> On Mar 29, 2021, at 4:52 PM, colin@gmail.com
> wrote:
>
> Hi Team
>
> I'm attempting to upgrade from 4.0.0 to the latest version via Deb. Did a
> sudo apt-get update, then sudo apt-get install weewx as per the gu
I had a user of my website report the same thing not so long ago. It had me
doing a double take.
> On Mar 30, 2021, at 2:01 PM, Matt Hannan wrote:
>
>
> Never mind. I am a dope. It is mm/dd, not mm/yy. And it may have felt like
> I've been trapped in the house for 20 years, but I really hav
I you are running an up to date RPi OS Buster (the latest version), you should
have Python 3.7 installed.
What do you get when you run the following 3 commands (my example bellows shows
what you should get)?
jkline@judy:~ $ which python3
/usr/bin/python3
jkline@judy:~ $ python3 --version
Python
Buster has python2 and python3 installed out of the box.
On buster, if you execute python, you will get python2.
You must execute python3 to get python3.
You did not need to install yet another version of python3 and I would not
recommend it (although I’m not sure if you actually did).
I would a
WRT:
N: This must be accepted explicitly before updates for this repository can be
applied. See apt-secure(8) manpage for details.
You can’t explicitly accept with apt-get. You have to use apt.
Please run:
apt update
apt full-upgrade
> On Apr 4, 2021, at 12:51 PM, Phil Green wrote:
>
> List
That’s not an envoy driver exception. Rather, it’s a forecast extension
exception.
Try installing this:
https://github.com/chaunceygardiner/weewx-forecast
> On Apr 6, 2021, at 2:18 PM, weather list wrote:
>
> Working on getting Matthew Wall’s weewx-envoy driver running under Python3.
> I’m
genLoopPackets():
> File "/home/weewx/bin/user/envoy.py", line 203, in genLoopPackets
> packet = self.envoy.get_data()
> File "/home/weewx/bin/user/envoy.py", line 259, in get_data
> resp = urllib.urlopen(self.url)
> AttributeError: module 'urllib' has no
https://www.ncei.noaa.gov/access/metadata/landing-page/bin/iso?id=gov.noaa.ncdc:C00040
https://www1.ncdc.noaa.gov/pub/data/cdo/documentation/ANNUAL_documentation.pdf
> On Jun 3, 2021, at 8:03 AM, Karen K wrote:
>
> gjr80 schrieb am Mittwoch, 2. Juni 2021 um 22:21:18 UTC+2:
>> I’ve wondered thi
I assume you are running Python 3 (from the error).
What version of forecast are you running? Exactly where did you get it from?
> On Jun 20, 2021, at 9:17 AM, Mark Fraser wrote:
>
>
> Encountered this error this afternoon, the only extension I had installed
> previous to this was forecast.
Cheers,
John
> On Jun 20, 2021, at 10:55 AM, Mark Fraser wrote:
>
> On 20/06/2021 18:18, John Kline wrote:
>> I assume you are running Python 3 (from the error).
>> What version of forecast are you running? Exactly where did you get it from?
>>>> On Jun 20, 202
It looks like you have both the weewx-purple and the weewx-purpleair extensions
installed. You probably should pick one.
As for the errors from weewx-purple (ERROR user.purple), the purpleair device
(purpleair-8ac1) is not responding, so yes, that is a problem.
If you decide to keep weewx-purp
Got it. Besides that issue, you really should have only one of weewx-purple or
weewx-purpleair installed. Pick one and uninstall the other.
> On Aug 26, 2021, at 12:50 PM, rons...@gmail.com wrote:
>
>
> So it looks like my purple air keeps going off line. The WiFi is connected
> but the de
He doesn’t have the purple extension configured in weewx.conf, so he’ll get
that message since no sources are configured.
To get rid of that message change the following:
data_services = user.purple.Purple,
to
data_services = ,
A proper uninstall would have removed it.
As for the PurpleAirMonit
You can wait for a report cycle to happen (prob on the 5 minute boundary) or
run wee_reports:
/etc/weewx/bin/wee_reports
Having said that, another reason for the change not to “take effect” is an
error in the template. If that happens, you’ll still see the old report (i.e.,
html file). Have
The forecast extension has not been updated to use WU’s new API.
If you navigate your browser to the URL you have in your log snippet:
> http://api.wunderground.com/api
You will get:
Service Unavailable
> On Aug 3, 2020, at 1:06 PM, voyagesdedavid wrote:
>
>
> Hello,
> Can anyone offer help
>> download forecast: HTTP Error 503: Service Unavailable
>> Aug 3 21:28:15 weather weewxd: forecast: WUThread: WU: failed to download
>> forecast
>> Aug 3 21:28:15 weather weewxd: forecast: WUThread: WU: no forecast data for
>> XX from http://api.wunderground.com/ap
The chaunceygardiner fork is mine. I originally modified the extension to get
it working for me as I was running the WeeWX 4.x beta. Others asked for it, so
I made it available. I tested everything *except* WU and got it working. This
fork is intended as an interim solution while waiting for
> i think you have the wrong end of the stick there:
Yep, he did change the subject on us.
I just double checked. I still have OWM running and my fork is *fetching*
forecasts just fine.
> On Aug 4, 2020, at 7:57 AM, Graham Eddy wrote:
>
>
> i think you have the wrong end of the stick there
Don’t change ‘wu_strip’ to ‘owm_strip’. It is a referring to an element on the
page that has an id of wu_strip. Perhaps that’s not the greatest id, but it is
what it is.
So, that should read:
populate_strip(‘wu_strip’, ‘OWM’);
In addition, you need to change $strip_source in forecast_strip.in
See bin/weewx/engine.py:
class StdConvert(StdService):
"""Service for performing unit conversions.
This service acts as a filter. Whatever packets and records come in are
converted to a target unit system.
If the driver is incorrectly setting usUnits to ‘US’, one would see this
behavior. What driver are you using? Perhaps you are missing a setting in
weewx.conf to tell the driver the station is sending metric data. BTW, do you
know for sure if the data coming from the weather station is metric?
While you’re waiting for Tom:
The “count operation” just needs the word “select” in front of it. It was a
typo. If you want, you could try again with select prepended.
Did you delete the NOAA report files? When you say the records are still
there, do you mean in the NOAA reports that you may
When does your week start?
You should see something like this is weewx.conf:
# Start of week (0=Monday, 6=Sunday)
week_start = 6
What value do you have for week_start?
> On Aug 11, 2020, at 3:20 AM, geni08...@gmail.com
> wrote:
>
> I found a syntax.
> Question: for example "Hi Out Te
OK, before we look at the daily summaries in your database, please install
loopdata at head. I’ve added logging for week_start and rainyear_start at
startup. Let’s make sure that the extension thinks week_start is 0. Install
the the extension. Restart weewx and then paste in the lines from th
test or elsewhere.
> On Aug 11, 2020, at 9:11 AM, John Kline wrote:
>
>
> OK, before we look at the daily summaries in your database, please install
> loopdata at head. I’ve added logging for week_start and rainyear_start at
> startup. Let’s make sure that the extension thin
t; 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: day_obstypes
> : ['windGust', 'wind', 'windSpeed', 'windDir', 'windGustDir', 'rain',
> 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi w
. Please give it a try.
>> On Aug 11, 2020, at 9:41 AM, John Kline wrote:
>
> It does not look like you have installed from head on github.
>
> Go to this page:
>
> https://github.com/chaunceygardiner/weewx-loopdata
>
> Click “Code” and then click downlo
ns:
> Where can I find a description of what a "Rain Year" is?
> Where and how can I set that $wind.rms.formatted and $windGust.max.formatted
> also have a decimal place at km / h?
> Current Livelink
>
> Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
>>
; meter_per_second2 = %.1f
> mile_per_hour = %.0f
> mile_per_hour2 = %.1f
>
> I have now redefined target_report = LoopDataReport, now it works as desired
>
> Am Mittwoch, 12. August 2020 14:56:16 UTC+2 schrieb John Kline:
>>
>&
I promised I would take a look at supporting the new WU API.
I’ve done that.
See:
https://github.com/chaunceygardiner/weewx-forecast/releases/tag/v3.4.0b6
> On Aug 12, 2020, at 12:21 PM, Vetti52 wrote:
>
>
> Same question to me!
>
> Although, I think, that the forecast extension from
> h
The bug wasn’t a b5 bug, per se. It’s carried over from
matthewwall/weewx-forecast. I’m sure there are plenty more. Never-the-less,
these were easy changes. I’ve submitted them.
I don’t believe the extension has been abandoned. It is my understanding that
Matthew is busy at the moment; but
As your incorporating this into your Seasons skin, it makes sense to remove
(from the .inc files) the data that is not provided by WU (e.g., dew point).
You should have a look at what’s coming back from WU by using the following URL
(assuming you are using the default–station’s lat/long–for the
> 3 : "Showers possible in the afternoon. Highs in the low 70s and lows in
> the upper 50s."
> 4 : "Light rain and windy. Highs in the upper 60s and lows in the mid
> 50s."
> 5 : "Partly cloudy. Highs in the upper 60s and lows in the low 50s.&qu
> 1 ""
> 2 ""
> 3 ""
> 4 ""
> 5 ""
> 6 ""
> 7 ""
> 8 ""
> 9 ""
> 10""
> 11""
>
> So, there is an issue
uot;Showers"
>>>
>>> when language is set to "de-DE", I get
>>>
>>> wxPhraseLong
>>> 0 "Nachm. Schauer"
>>> 1 "Später Schauer"
>>> 2 "Regen"
>>> 3 "Wolkig"
&
t; 19:00
> 10 13
> 20:21:12
>
> 20%
>
>
> Fr
> 28 Aug
> 19
> 1013-16 06:20:05
> 20:18:49 18:18:50
> 00:32:33 76% 60%
> 6,10
>
>
> WU forecast for geocode=54.09,10.26 issued on 23-Aug-2020 21:1
1 - 100 of 482 matches
Mail list logo
