Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Mwall,

Thanks so much! Seems to be displaying now! I'll test and let you know.

Thanks again

Sam

On Tuesday, March 6, 2018 at 4:45:03 PM UTC+11, mwall wrote:
>
> i thought this smelled familiar.  i think this problem was fixed at commit 
> 9164c08 on 24 dec 2017.
>
> please replace your wxservices.py with the latest:
>
>
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxservices.py
>
> then restart weewx.
>
> m
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

i thought this smelled familiar.  i think this problem was fixed at commit 
9164c08 on 24 dec 2017.

please replace your wxservices.py with the latest:

https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxservices.py

then restart weewx.

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Graphs not always visible, skips archive interval, no data loss

[Andrew Milner]

I'd blame Trump and his attempts at stopping net equality for all!!  Could 
be the beginnings of multi-tiered internet!!  They have to introduce 
'issues' to persuade the populace to cough up readies for 'better' = what 
we should have = service .



On Tuesday, 6 March 2018 06:57:04 UTC+2, gjr80 wrote:

> Andrew is right, the logs are your friend. you might find it useful to run 
> with debug=1 so you get a bit more details about what (well how many) files 
> are being generated. Are you ftp'ing or rsync'ing to a remote web server or 
> hosting locally, if remote it might be worth seeing what is being 
> ftp'd/rsync'd. If it happens relatively frequently you might need to spend 
> a bith of time in front of a terminal listing the contents of public_html 
> (or wherever) on your weeWX machine to see what is being generated after 
> each cycle.
>
> Unless you are pushing the bounds and your reports are taking nearly as 
> long to process as your archive period it is unlikely the length of your 
> archive period is the issue. Perusing your logs and looking at the typical 
> time taken to generate (and ftp/rsync) all reports/images will give you a 
> feel for whether this may be a problem.
>
> Be interesting if it is a browser caching issue, seems odd though, as 
> there appears to have been a number of these issues recently.
>
> Gary
>
> On Tuesday, 6 March 2018 13:43:24 UTC+10, Steve2Q wrote:
>>
>> Hi: in the last few days I noticed that some charts are not always 
>> visible, but this is seemingly random; sometimes they are all there then 
>> there may be one or more missing with just the names showing (see picture). 
>> I have a 2 minute archive interval, and sometimes one or more intervals may 
>> go by before the web page updates. However no data appears to be 
>> lost..there are no gaps in the charts. Where would be a good starting point 
>> to start troubleshooting?
>>
>> Thanks, Steve
>>
>>
>>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

On Monday, March 5, 2018 at 11:49:37 PM UTC-5, Sam Walton wrote:
>
> Let try again! The logs look like it's put the debug info in this time.
>
>
yay!  now we know that the hardware and driver are behaving as expected.

now for the next level.  set debug=3 instead of debug=2.  restart weewx, 
then post the log again.

that will tell us exacty what is happening with the rapidfire cache.

m 

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Graphs not always visible, skips archive interval, no data loss

[gjr80]

Andrew is right, the logs are your friend. you might find it useful to run 
with debug=1 so you get a bit more details about what (well how many) files 
are being generated. Are you ftp'ing or rsync'ing to a remote web server or 
hosting locally, if remote it might be worth seeing what is being 
ftp'd/rsync'd. If it happens relatively frequently you might need to spend 
a bith of time in front of a terminal listing the contents of public_html 
(or wherever) on your weeWX machine to see what is being generated after 
each cycle.

Unless you are pushing the bounds and your reports are taking nearly as 
long to process as your archive period it is unlikely the length of your 
archive period is the issue. Perusing your logs and looking at the typical 
time taken to generate (and ftp/rsync) all reports/images will give you a 
feel for whether this may be a problem.

Be interesting if it is a browser caching issue, seems odd though, as there 
appears to have been a number of these issues recently.

Gary

On Tuesday, 6 March 2018 13:43:24 UTC+10, Steve2Q wrote:
>
> Hi: in the last few days I noticed that some charts are not always 
> visible, but this is seemingly random; sometimes they are all there then 
> there may be one or more missing with just the names showing (see picture). 
> I have a 2 minute archive interval, and sometimes one or more intervals may 
> go by before the web page updates. However no data appears to be 
> lost..there are no gaps in the charts. Where would be a good starting point 
> to start troubleshooting?
>
> Thanks, Steve
>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Atlas

[mwall]

On Monday, March 5, 2018 at 11:25:56 PM UTC-5, Paul Grunwald wrote:
>
> My current WS2080 is on the last legs.
>
> I noticed that the Acurite Atlas is sorta mentioned in the hardware list.  
> Postings here indicate an imminent release: 
> http://www.wxforum.net/index.php?topic=33456.50.
>
> Questions:  Will this be supported by Weewx on release?
>

not unless someone has an atlas we can plan with!

as i understand it, the atlas uploads data using the acurite access (which 
is the successor to the smartHUB, which is just the acurite bridge with a 
new name and forced firmware update).

since the acurite access sends data to weather underground, you can capture 
it using the weewx-interceptor driver.

the acurite access sends a richer data set to the acurite servers, but you 
cannot capture that because acurite encrypts it.  the only way to get your 
data is if someone writes a driver that polls the acurite servers (like the 
weewx-netatmo driver does for the netatmo servers).  (btw, polling those 
servers is not reliable, and you only get data aggregated to 5 minute 
intervals, even though the sensors are spitting it out much more often)

no definite word yet as to whether the elite will send data directly or use 
the acurite access as well.

we have most of the issues resolved in the wmr300 driver.  oregon 
scientific made a few design decisions on that one that make you go "huh?". 
 for example, why would anyone make a rain counter that does not wrap 
around, provide a USB interface, but not provide a way to reset the rain 
counter via software?

imho, davis is still top of the class for reliability and support, although 
they have issues too.  i just installed a brand new vantage pro2 and the 
logger keeps going into a state where it won't respond to TEST - power 
cycling the console is the only fix.  belfry boy to the rescue!

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: How to use the .years iterator

[gjr80]

Good that it works as it should.

Just one thing to add, iterating over all years and then all months in a 
database can be (processor) time consuming - try deleting all of your NOAA 
reports sometime and see how long they take to regenerate. There are no 
hard and fast rules here, the time taken to generate such a report will 
depend on how many years of data are in the database and how complex the 
report is. Also, how often you run the report and the number of other skins 
you use will also contribute to overall processor load. The key measure is 
having a look at your logs and seeing how long a report cycle takes 
compared to your archive period. This is best done over a number of cyles 
not just one. If the report cycle typically finishes within a few seconds 
of the (next) archive cycle starting you could be on thin ice. The good 
thing is such reports use the daily summaries rather than the archive and 
you can often use options such as stale_age and report_timing to limit how 
often such reports are run.

Gary 

On Tuesday, 6 March 2018 10:33:49 UTC+10, Louis De Lange wrote:
>
> Gary,
>
> I just want to confirm that you suggested approach with alltime works, and 
> further I can iterate a *year.months* loop within an *alltime.years* loop.
>
> For the benefit of anyone else, the code to print the avg temperature for 
> every month in the database is as follows:
>
>   #for $year in $alltime.years
> #for $mth in $year.months
>   #if $mth.outTemp.count.raw
>   $mth.dateTime.format("%Y 
> %m")$mth.outTemp.avg
>   #end if
> #end for
>   #end for
>
>   Thank you for your help
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx_wd

[gjr80]

Hallo,

Das war mein plan, du bist testkandidat nummer eins. Wir haben ein paar 
tage regenprognose, also hoffentlich etwas Zeit für mich, daran zu arbeiten.

That was my plan, you are number 1 test candidate. We have a few days of 
rain forecast so hopefully some time for me to work on this.
Gary

On Tuesday, 6 March 2018 03:24:57 UTC+10, k-l...@gmx.de wrote:
>
> Hallo
> wenn du die neue Version fertig hast, könnte ich die dann mal Testen.
>
>
> Am Donnerstag, 22. Februar 2018 22:07:13 UTC+1 schrieb k-l...@gmx.de:
>>
>> hallo
>>
>> ich benutze WD-Live 
>> da wird aber leider die Mondphase nicht angezeigt. 
>> muss da noch was eingesellt werden.
>>
>>
>>
>> Hello
>>
>> I use WD-Live
>> but unfortunately the moon phase is not displayed.
>> there must be something else set up.
>>
>> cu. Kalli
>>
>>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

sam,

you are still not getting the debug_decode information in the log.

please verify that debug_decode has been set to 1

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Thanks for the response. I noticed that too, It's weird when i was running 
Weewx on Raspbian i had no issues with rapid fire on. 

Happy to turn off and test!

Sam

On Tuesday, March 6, 2018 at 3:26:14 PM UTC+11, Andrew Milner wrote:
>
> From the logs the wind direction appears to be being uploaded when it is 
> available.  I know the wmr300 produces partial packets which do not always 
> seem to work well with rapid fire at WU.  I also see that you are giving 
> rapid fire updates at 1 second (or even less) intervals - yet the upload 
> says the interval is 2.5 seconds - this could be causing issues at the WU 
> end, and resulting in lost data (just a theory, since it does not take much 
> for WU to lose/drop data).
>
> Does it work OK if you turn rapid fire off and go to a 5 minute archive 
> interval??
>
> I'll leave this to Matthew as he knows FAR FAR more than me!!
>
>
>
> On Tuesday, 6 March 2018 06:13:39 UTC+2, Sam Walton wrote:
>
>> Attached are hopefully the correct logs!
>>
>> Thanks
>>
>> Sam
>>
>> On Tue, Mar 6, 2018 at 2:43 PM, Sam Walton  wrote:
>>
>>> My bad! I read the error again and noticed line 1 had the fault (must of 
>>> deleted the #) It is running now!
>>>
>>> I'll upload the logs asap
>>>
>>> Sam
>>>
>>>
>>> On Tuesday, March 6, 2018 at 2:40:24 PM UTC+11, Sam Walton wrote:

 Hi Andrew,

 I searched for debug_decode and could not find it. I added it to the 
 section WMR300 and now when i start the service i get the error

 swalton@weather-station:~$ sudo /etc/init.d/weewx start
 [ ok ] Starting weewx (via systemctl): weewx.service.
 swalton@weather-station:~$ sudo /etc/init.d/weewx status
 ● weewx.service - LSB: weewx weather system
Loaded: loaded (/etc/init.d/weewx; bad; vendor preset: enabled)
Active: active (exited) since Tue 2018-03-06 14:32:00 AEDT; 2s ago
  Docs: man:systemd-sysv-generator(8)
   Process: 2465 ExecStop=/etc/init.d/weewx stop (code=exited, 
 status=0/SUCCESS)
   Process: 2522 ExecStart=/etc/init.d/weewx start (code=exited, 
 status=0/SUCCESS)

 Mar 06 14:32:00 weather-station weewx[2522]:  * Starting weewx weather 
 system weewx
 Mar 06 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
 version 3.8.0
 Mar 06 14:32:00 weather-station weewx[2534]: engine: Using Python 
 2.7.12 (default, Dec  4 2017, 14:50:18)
  [GCC 5.4.0 20160609]
 Mar 06 14:32:00 weather-station weewx[2534]: engine: Platform 
 Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
 Mar 06 14:32:00 weather-station weewx[2534]: engine: Locale is 
 'en_AU.UTF-8'
 Mar 06 14:32:00 weather-station weewx[2534]: engine: pid file is 
 /var/run/weewx.pid
 Mar 06 14:32:00 weather-station weewx[2538]: engine: Error while 
 parsing configuration file /etc/weewx/w...conf
 Mar 06 14:32:00 weather-station weewx[2538]: Reason: 'Invalid 
 line (' WEEWX CONFIGURATION FILE')... 1.'
 Mar 06 14:32:00 weather-station weewx[2522]:...done.
 Mar 06 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
 system.
 Hint: Some lines were ellipsized, use -l to show in full.
 swalton@weather-station:~$ sudo tail -f /var/log/syslog
 Mar  6 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
 version 3.8.0
 Mar  6 14:32:00 weather-station weewx[2534]: engine: Using Python 
 2.7.12 (default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
 Mar  6 14:32:00 weather-station weewx[2534]: engine: Platform 
 Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
 Mar  6 14:32:00 weather-station weewx[2534]: engine: Locale is 
 'en_AU.UTF-8'
 Mar  6 14:32:00 weather-station weewx[2534]: engine: pid file is 
 /var/run/weewx.pid
 Mar  6 14:32:00 weather-station weewx[2538]: engine: Error while 
 parsing configuration file /etc/weewx/weewx.conf
 Mar  6 14:32:00 weather-station weewx[2538]: Reason: 'Invalid 
 line (' WEEWX CONFIGURATION FILE') (matched as neither section nor 
 keyword) 
 at line 1.'
 Mar  6 14:32:00 weather-station weewx[2522]:...done.
 Mar  6 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
 system.
 Mar  6 14:33:44 weather-station rsyslogd-2007: action 'action 10' 
 suspended, next retry is Tue Mar  6 14:34:14 2018 [v8.16.0 try 
 http://www.rsyslog.com/e/2007 ]


 Here is the snippet from the config


 ##

 # This section is for general configuration information.

 # Set to 1 for extra debug info, otherwise comment it out or set to zero
 debug = 2

 # Root directory of the weewx data file hierarchy for this station
 WEEWX_ROOT = /

 # How long to wait before timing out a socket (FTP, HTTP) connection
 socket_timeou

Re: [weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Andrew Milner]

>From the logs the wind direction appears to be being uploaded when it is 
available.  I know the wmr300 produces partial packets which do not always 
seem to work well with rapid fire at WU.  I also see that you are giving 
rapid fire updates at 1 second (or even less) intervals - yet the upload 
says the interval is 2.5 seconds - this could be causing issues at the WU 
end, and resulting in lost data (just a theory, since it does not take much 
for WU to lose/drop data).

Does it work OK if you turn rapid fire off and go to a 5 minute archive 
interval??

I'll leave this to Matthew as he knows FAR FAR more than me!!



On Tuesday, 6 March 2018 06:13:39 UTC+2, Sam Walton wrote:

> Attached are hopefully the correct logs!
>
> Thanks
>
> Sam
>
> On Tue, Mar 6, 2018 at 2:43 PM, Sam Walton  > wrote:
>
>> My bad! I read the error again and noticed line 1 had the fault (must of 
>> deleted the #) It is running now!
>>
>> I'll upload the logs asap
>>
>> Sam
>>
>>
>> On Tuesday, March 6, 2018 at 2:40:24 PM UTC+11, Sam Walton wrote:
>>>
>>> Hi Andrew,
>>>
>>> I searched for debug_decode and could not find it. I added it to the 
>>> section WMR300 and now when i start the service i get the error
>>>
>>> swalton@weather-station:~$ sudo /etc/init.d/weewx start
>>> [ ok ] Starting weewx (via systemctl): weewx.service.
>>> swalton@weather-station:~$ sudo /etc/init.d/weewx status
>>> ● weewx.service - LSB: weewx weather system
>>>Loaded: loaded (/etc/init.d/weewx; bad; vendor preset: enabled)
>>>Active: active (exited) since Tue 2018-03-06 14:32:00 AEDT; 2s ago
>>>  Docs: man:systemd-sysv-generator(8)
>>>   Process: 2465 ExecStop=/etc/init.d/weewx stop (code=exited, 
>>> status=0/SUCCESS)
>>>   Process: 2522 ExecStart=/etc/init.d/weewx start (code=exited, 
>>> status=0/SUCCESS)
>>>
>>> Mar 06 14:32:00 weather-station weewx[2522]:  * Starting weewx weather 
>>> system weewx
>>> Mar 06 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
>>> version 3.8.0
>>> Mar 06 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
>>> (default, Dec  4 2017, 14:50:18)
>>>  [GCC 5.4.0 20160609]
>>> Mar 06 14:32:00 weather-station weewx[2534]: engine: Platform 
>>> Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
>>> Mar 06 14:32:00 weather-station weewx[2534]: engine: Locale is 
>>> 'en_AU.UTF-8'
>>> Mar 06 14:32:00 weather-station weewx[2534]: engine: pid file is 
>>> /var/run/weewx.pid
>>> Mar 06 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
>>> configuration file /etc/weewx/w...conf
>>> Mar 06 14:32:00 weather-station weewx[2538]: Reason: 'Invalid 
>>> line (' WEEWX CONFIGURATION FILE')... 1.'
>>> Mar 06 14:32:00 weather-station weewx[2522]:...done.
>>> Mar 06 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Hint: Some lines were ellipsized, use -l to show in full.
>>> swalton@weather-station:~$ sudo tail -f /var/log/syslog
>>> Mar  6 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
>>> version 3.8.0
>>> Mar  6 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
>>> (default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
>>> Mar  6 14:32:00 weather-station weewx[2534]: engine: Platform 
>>> Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
>>> Mar  6 14:32:00 weather-station weewx[2534]: engine: Locale is 
>>> 'en_AU.UTF-8'
>>> Mar  6 14:32:00 weather-station weewx[2534]: engine: pid file is 
>>> /var/run/weewx.pid
>>> Mar  6 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
>>> configuration file /etc/weewx/weewx.conf
>>> Mar  6 14:32:00 weather-station weewx[2538]: Reason: 'Invalid 
>>> line (' WEEWX CONFIGURATION FILE') (matched as neither section nor keyword) 
>>> at line 1.'
>>> Mar  6 14:32:00 weather-station weewx[2522]:...done.
>>> Mar  6 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Mar  6 14:33:44 weather-station rsyslogd-2007: action 'action 10' 
>>> suspended, next retry is Tue Mar  6 14:34:14 2018 [v8.16.0 try 
>>> http://www.rsyslog.com/e/2007 ]
>>>
>>>
>>> Here is the snippet from the config
>>>
>>>
>>> ##
>>>
>>> # This section is for general configuration information.
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>>> debug = 2
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # How long to wait before timing out a socket (FTP, HTTP) connection
>>> socket_timeout = 20
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 3.8.0
>>>
>>>
>>> ##
>>>
>>>
>>> ##
>>>
>>> [WMR300]
>>> # This section is for WMR300 weather stations.
>>>
>

[weewx-user] Atlas

[Paul Grunwald]

My current WS2080 is on the last legs.

I noticed that the Acurite Atlas is sorta mentioned in the hardware list.  
Postings here indicate an 
imminent release: http://www.wxforum.net/index.php?topic=33456.50.

Questions:  Will this be supported by Weewx on release?

Is it worth waiting for?   I'm considering a VantageVue, WMR300A as well.

Thanks,
Paul 

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Graphs not always visible, skips archive interval, no data loss

[Andrew Milner]

A good place to start is by looking at the log!!

Depending on the pc/cpu you are using it is possible the report interval is 
too short, and needs to be increased to say 5 minutes.

You could always just try and refresh the page when the plot is 'missing' - 
it could just be a delay in your server delivering the image to the browser



On Tuesday, 6 March 2018 05:43:24 UTC+2, Steve2Q wrote:

> Hi: in the last few days I noticed that some charts are not always 
> visible, but this is seemingly random; sometimes they are all there then 
> there may be one or more missing with just the names showing (see picture). 
> I have a 2 minute archive interval, and sometimes one or more intervals may 
> go by before the web page updates. However no data appears to be 
> lost..there are no gaps in the charts. Where would be a good starting point 
> to start troubleshooting?
>
> Thanks, Steve
>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

My bad! I read the error again and noticed line 1 had the fault (must of 
deleted the #) It is running now!

I'll upload the logs asap

Sam

On Tuesday, March 6, 2018 at 2:40:24 PM UTC+11, Sam Walton wrote:
>
> Hi Andrew,
>
> I searched for debug_decode and could not find it. I added it to the 
> section WMR300 and now when i start the service i get the error
>
> swalton@weather-station:~$ sudo /etc/init.d/weewx start
> [ ok ] Starting weewx (via systemctl): weewx.service.
> swalton@weather-station:~$ sudo /etc/init.d/weewx status
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; bad; vendor preset: enabled)
>Active: active (exited) since Tue 2018-03-06 14:32:00 AEDT; 2s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 2465 ExecStop=/etc/init.d/weewx stop (code=exited, 
> status=0/SUCCESS)
>   Process: 2522 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>
> Mar 06 14:32:00 weather-station weewx[2522]:  * Starting weewx weather 
> system weewx
> Mar 06 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
> version 3.8.0
> Mar 06 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
> (default, Dec  4 2017, 14:50:18)
>  [GCC 5.4.0 20160609]
> Mar 06 14:32:00 weather-station weewx[2534]: engine: Platform 
> Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
> Mar 06 14:32:00 weather-station weewx[2534]: engine: Locale is 
> 'en_AU.UTF-8'
> Mar 06 14:32:00 weather-station weewx[2534]: engine: pid file is 
> /var/run/weewx.pid
> Mar 06 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
> configuration file /etc/weewx/w...conf
> Mar 06 14:32:00 weather-station weewx[2538]: Reason: 'Invalid line 
> (' WEEWX CONFIGURATION FILE')... 1.'
> Mar 06 14:32:00 weather-station weewx[2522]:...done.
> Mar 06 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
> system.
> Hint: Some lines were ellipsized, use -l to show in full.
> swalton@weather-station:~$ sudo tail -f /var/log/syslog
> Mar  6 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
> version 3.8.0
> Mar  6 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
> (default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
> Mar  6 14:32:00 weather-station weewx[2534]: engine: Platform 
> Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
> Mar  6 14:32:00 weather-station weewx[2534]: engine: Locale is 
> 'en_AU.UTF-8'
> Mar  6 14:32:00 weather-station weewx[2534]: engine: pid file is 
> /var/run/weewx.pid
> Mar  6 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
> configuration file /etc/weewx/weewx.conf
> Mar  6 14:32:00 weather-station weewx[2538]: Reason: 'Invalid line 
> (' WEEWX CONFIGURATION FILE') (matched as neither section nor keyword) at 
> line 1.'
> Mar  6 14:32:00 weather-station weewx[2522]:...done.
> Mar  6 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
> system.
> Mar  6 14:33:44 weather-station rsyslogd-2007: action 'action 10' 
> suspended, next retry is Tue Mar  6 14:34:14 2018 [v8.16.0 try 
> http://www.rsyslog.com/e/2007 ]
>
>
> Here is the snippet from the config
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 2
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 3.8.0
>
>
> ##
>
>
> ##
>
> [WMR300]
> # This section is for WMR300 weather stations.
>
> # The station model, e.g., WMR300A
> model = WMR300
>
> # The driver to use:
> driver = weewx.drivers.wmr300
>
> debug_decode = 1
>
> ##
>
> Sorry i'm quite new to Weewx!
>
> Sam
>
>
> On Tuesday, March 6, 2018 at 2:02:28 PM UTC+11, Andrew Milner wrote:
>>
>> Sam - I think Matthew is saying that:
>> a)  The main weewx.conf debug statement near the start of weewx.conf 
>> should say debug = 2 to invoke more detailed weewx logging
>> AND
>> b) There should be a line within the WMR300 section - add it if necessary 
>> - saying debug_decode = 1 to force more detailed logging from the driver 
>> itself
>>
>>
>> On Tuesday, 6 March 2018 03:47:48 UTC+2, Sam Walton wrote:
>>
>>> Hi Mwall,
>>>
>>> I don't have the line in the config file for "debug_decode" do i add it 
>>> in? I tried to add the line into the config under the driver section but 
>>> the service fails to start.
>>>
>>> Sam
>>>
>>> On Tuesday, March 

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Hi Andrew,

I searched for debug_decode and could not find it. I added it to the 
section WMR300 and now when i start the service i get the error

swalton@weather-station:~$ sudo /etc/init.d/weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
swalton@weather-station:~$ sudo /etc/init.d/weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; bad; vendor preset: enabled)
   Active: active (exited) since Tue 2018-03-06 14:32:00 AEDT; 2s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2465 ExecStop=/etc/init.d/weewx stop (code=exited, 
status=0/SUCCESS)
  Process: 2522 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Mar 06 14:32:00 weather-station weewx[2522]:  * Starting weewx weather 
system weewx
Mar 06 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
version 3.8.0
Mar 06 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
(default, Dec  4 2017, 14:50:18)
 [GCC 5.4.0 20160609]
Mar 06 14:32:00 weather-station weewx[2534]: engine: Platform 
Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
Mar 06 14:32:00 weather-station weewx[2534]: engine: Locale is 'en_AU.UTF-8'
Mar 06 14:32:00 weather-station weewx[2534]: engine: pid file is 
/var/run/weewx.pid
Mar 06 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
configuration file /etc/weewx/w...conf
Mar 06 14:32:00 weather-station weewx[2538]: Reason: 'Invalid line 
(' WEEWX CONFIGURATION FILE')... 1.'
Mar 06 14:32:00 weather-station weewx[2522]:...done.
Mar 06 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
system.
Hint: Some lines were ellipsized, use -l to show in full.
swalton@weather-station:~$ sudo tail -f /var/log/syslog
Mar  6 14:32:00 weather-station weewx[2534]: engine: Initializing weewx 
version 3.8.0
Mar  6 14:32:00 weather-station weewx[2534]: engine: Using Python 2.7.12 
(default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
Mar  6 14:32:00 weather-station weewx[2534]: engine: Platform 
Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
Mar  6 14:32:00 weather-station weewx[2534]: engine: Locale is 'en_AU.UTF-8'
Mar  6 14:32:00 weather-station weewx[2534]: engine: pid file is 
/var/run/weewx.pid
Mar  6 14:32:00 weather-station weewx[2538]: engine: Error while parsing 
configuration file /etc/weewx/weewx.conf
Mar  6 14:32:00 weather-station weewx[2538]: Reason: 'Invalid line 
(' WEEWX CONFIGURATION FILE') (matched as neither section nor keyword) at 
line 1.'
Mar  6 14:32:00 weather-station weewx[2522]:...done.
Mar  6 14:32:00 weather-station systemd[1]: Started LSB: weewx weather 
system.
Mar  6 14:33:44 weather-station rsyslogd-2007: action 'action 10' 
suspended, next retry is Tue Mar  6 14:34:14 2018 [v8.16.0 try 
http://www.rsyslog.com/e/2007 ]


Here is the snippet from the config

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 2

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.8.0

##

##

[WMR300]
# This section is for WMR300 weather stations.

# The station model, e.g., WMR300A
model = WMR300

# The driver to use:
driver = weewx.drivers.wmr300

debug_decode = 1
##

Sorry i'm quite new to Weewx!

Sam


On Tuesday, March 6, 2018 at 2:02:28 PM UTC+11, Andrew Milner wrote:
>
> Sam - I think Matthew is saying that:
> a)  The main weewx.conf debug statement near the start of weewx.conf 
> should say debug = 2 to invoke more detailed weewx logging
> AND
> b) There should be a line within the WMR300 section - add it if necessary 
> - saying debug_decode = 1 to force more detailed logging from the driver 
> itself
>
>
> On Tuesday, 6 March 2018 03:47:48 UTC+2, Sam Walton wrote:
>
>> Hi Mwall,
>>
>> I don't have the line in the config file for "debug_decode" do i add it 
>> in? I tried to add the line into the config under the driver section but 
>> the service fails to start.
>>
>> Sam
>>
>> On Tuesday, March 6, 2018 at 12:32:59 PM UTC+11, mwall wrote:
>>>
>>>
>>>
>>> On Monday, March 5, 2018 at 8:46:45 AM UTC-5, Sam Walton wrote:

 Hi Mwall,

 I've set the config to debug_decode = 1 Attached is the putty dump. 
 I've also attached a screen shot of the Weewx local site.

 Sam 

>>>
>>> sam,
>>>
>>> i am confused.  
>>>
>>> that does not look like the previous log output - there are no messages

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Andrew Milner]

Sam - I think Matthew is saying that:
a)  The main weewx.conf debug statement near the start of weewx.conf should 
say debug = 2 to invoke more detailed weewx logging
AND
b) There should be a line within the WMR300 section - add it if necessary - 
saying debug_decode = 1 to force more detailed logging from the driver 
itself


On Tuesday, 6 March 2018 03:47:48 UTC+2, Sam Walton wrote:

> Hi Mwall,
>
> I don't have the line in the config file for "debug_decode" do i add it 
> in? I tried to add the line into the config under the driver section but 
> the service fails to start.
>
> Sam
>
> On Tuesday, March 6, 2018 at 12:32:59 PM UTC+11, mwall wrote:
>>
>>
>>
>> On Monday, March 5, 2018 at 8:46:45 AM UTC-5, Sam Walton wrote:
>>>
>>> Hi Mwall,
>>>
>>> I've set the config to debug_decode = 1 Attached is the putty dump. I've 
>>> also attached a screen shot of the Weewx local site.
>>>
>>> Sam 
>>>
>>
>> sam,
>>
>> i am confused.  
>>
>> that does not look like the previous log output - there are no messages 
>> about wu uploads, and there are no messages from the wmr300 driver.
>>
>> your weewx.conf should have the following in it:
>>
>> debug = 2
>> ...
>> [WMR300]
>> ...
>> debug_decode = 1
>>
>> m
>>  
>>
>>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Hi Mwall,

I don't have the line in the config file for "debug_decode" do i add it in? 
I tried to add the line into the config under the driver section but the 
service fails to start.

Sam

On Tuesday, March 6, 2018 at 12:32:59 PM UTC+11, mwall wrote:
>
>
>
> On Monday, March 5, 2018 at 8:46:45 AM UTC-5, Sam Walton wrote:
>>
>> Hi Mwall,
>>
>> I've set the config to debug_decode = 1 Attached is the putty dump. I've 
>> also attached a screen shot of the Weewx local site.
>>
>> Sam 
>>
>
> sam,
>
> i am confused.  
>
> that does not look like the previous log output - there are no messages 
> about wu uploads, and there are no messages from the wmr300 driver.
>
> your weewx.conf should have the following in it:
>
> debug = 2
> ...
> [WMR300]
> ...
> debug_decode = 1
>
> m
>  
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

On Monday, March 5, 2018 at 8:46:45 AM UTC-5, Sam Walton wrote:
>
> Hi Mwall,
>
> I've set the config to debug_decode = 1 Attached is the putty dump. I've 
> also attached a screen shot of the Weewx local site.
>
> Sam 
>

sam,

i am confused.  

that does not look like the previous log output - there are no messages 
about wu uploads, and there are no messages from the wmr300 driver.

your weewx.conf should have the following in it:

debug = 2
...
[WMR300]
...
debug_decode = 1

m
 

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: How to use the .years iterator

[Louis De Lange]

Gary,

I just want to confirm that you suggested approach with alltime works, and 
further I can iterate a *year.months* loop within an *alltime.years* loop.

For the benefit of anyone else, the code to print the avg temperature for 
every month in the database is as follows:

  #for $year in $alltime.years
#for $mth in $year.months
  #if $mth.outTemp.count.raw
  $mth.dateTime.format("%Y 
%m")$mth.outTemp.avg
  #end if
#end for
  #end for

  Thank you for your help

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Potential bug in template iterator

[Louis De Lange]

Gary how did you know that ?! - It works !  Thank you.

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Potential bug in template iterator

[gjr80]

Hi,

Definitely not a feature, probably not a bug as it's just how cheetah/python 
handle variable lookups, so maybe its 'something else'.

Try changing $month in the for loop (and subsequent iteration tags) to 
something else, say $mth. Then try using $month after the #end for.

Gary

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Potential bug in template iterator

[Louis De Lange]

I have created my own html template and I am playing around with adding 
some stuff that require the use of the template iterator - I asked a 
related but different question about that yesterday.

I just noticed that calling any $month tag before I invoke *#for month in 
year.months* iterator the the *$month* tag get filled as expected.  If  I 
invoke the iterator first then any following *$month* tags are returned as 
empty or N/A.

Example

  

  Avg Temp This 
Month:$month.outTemp.avg
  #for $month in $year.months
#if $month.outTemp.count.raw
$month.dateTime.format("%Y 
%m")$month.outTemp.avg
#end if
  #end for

  

Produces the following output



If I change it to 
  

  Avg Temp This 
Month:$month.outTemp.avg
  #for $month in $year.months
#if $month.outTemp.count.raw
$month.dateTime.format("%Y 
%m")$month.outTemp.avg
#end if
  #end for
  Avg Temp This 
Month:$month.outTemp.avg

  

I get the following result



Is this a bug, a feature or something else?

Thanks in advance

Louis


-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Adding archive data to daily report

[Chris Alemany]

The history cards are totally cool! Would love to see how you made them. 
Thanks for this!

On Monday, March 5, 2018 at 8:15:43 AM UTC-8, Thomas Carlin wrote:
>
> Hi Chris!
>
> Thank you for the kind words.  I did not make this available anywhere, but 
> I would be happy to post it here if you are interested.  Keep in mind that 
> I am not a programer by any stretch, but I haven't had any issues with it.  
> The really cool extension on the history tab I didn't write, but I 
> extensively modified it to auto-define the color scheme, and color the 
> fonts accurately so they don't get lost on the background.  The original 
> unmodified version is available here:  
> https://github.com/brewster76/fuzzy-archer/blob/master/bin/user/historygenerator.py,
>  
> and I am less confident in the modifications I made to it than the 
> historical summary cards, but I have debated submitting it to the author 
> for review anyway.  
>
> Let me know if you would like the History Cards, and I'll post some code.
>
>
> On Sunday, March 4, 2018 at 3:53:05 PM UTC-7, Chris Alemany wrote:
>>
>> Hi Thomas! 
>>
>> This is a great addition, love how you presented it on your website too.
>>
>> Do you have the extensions you made available to download anywhere?
>>
>> Thanks!
>> Chris
>>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx_wd

[K-Lutz]

Hallo
wenn du die neue Version fertig hast, könnte ich die dann mal Testen.


Am Donnerstag, 22. Februar 2018 22:07:13 UTC+1 schrieb k-l...@gmx.de:
>
> hallo
>
> ich benutze WD-Live 
> da wird aber leider die Mondphase nicht angezeigt. 
> muss da noch was eingesellt werden.
>
>
>
> Hello
>
> I use WD-Live
> but unfortunately the moon phase is not displayed.
> there must be something else set up.
>
> cu. Kalli
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Adding archive data to daily report

[Thomas Carlin]

Hi Chris!

Thank you for the kind words.  I did not make this available anywhere, but 
I would be happy to post it here if you are interested.  Keep in mind that 
I am not a programer by any stretch, but I haven't had any issues with it.  
The really cool extension on the history tab I didn't write, but I 
extensively modified it to auto-define the color scheme, and color the 
fonts accurately so they don't get lost on the background.  The original 
unmodified version is available here:  
https://github.com/brewster76/fuzzy-archer/blob/master/bin/user/historygenerator.py,
 
and I am less confident in the modifications I made to it than the 
historical summary cards, but I have debated submitting it to the author 
for review anyway.  

Let me know if you would like the History Cards, and I'll post some code.


On Sunday, March 4, 2018 at 3:53:05 PM UTC-7, Chris Alemany wrote:
>
> Hi Thomas! 
>
> This is a great addition, love how you presented it on your website too.
>
> Do you have the extensions you made available to download anywhere?
>
> Thanks!
> Chris
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[Sam Walton]

Hi Mwall,

I've set the config to debug_decode = 1 Attached is the putty dump. I've 
also attached a screen shot of the Weewx local site.

Sam 

On Monday, March 5, 2018 at 11:37:00 PM UTC+11, mwall wrote:
>
> sam,
>
> in weewx.conf, enable debug_decode like this:
>
> [WMR300]
> debug_decode = 1
>
> then restart weewx and post about 10 minutes of the resulting log.
>
> it is odd that winddir would be reported for regular weewx reports but not 
> for wu, so lets find out exactly what the driver is sending out.
>
> m
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.03.06 00:32:39 =~=~=~=~=~=~=~=~=~=~=~=
login as: swalton
swalton@192.168.1.3's password: 
Welcome to Ubuntu 16.04.4 LTS (GNU/Linux 4.4.38-v7+ armv7l)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

34 packages can be updated.
2 updates are security updates.

Last login: Tue Mar  6 00:10:19 2018 from 192.168.1.8

]0;swalton@weather-station: ~swalton@weather-station:~$ 
]0;swalton@weather-station: ~swalton@weather-station:~$ 
]0;swalton@weather-station: ~swalton@weather-station:~$ 
]0;swalton@weather-station: ~swalton@weather-station:~$ sudo nano 
/etc/weewx/weewx.conf/etc/init.d/weewx 
stoptail -f /var/log/syslog 
[sudo] password for swalton: 
Mar  6 00:31:19 weather-station weewx[3350]: wmr300: rain=0.254 rain_total=8.89 
last_rain=8.636
Mar  6 00:31:19 weather-station rsyslogd-2007: action 'action 10' suspended, 
next retry is Tue Mar  6 00:32:49 2018 [v8.16.0 try 
http://www.rsyslog.com/e/2007 ]
Mar  6 00:31:54 weather-station systemd[1]: Stopping LSB: weewx weather 
system...
Mar  6 00:31:54 weather-station weewx[3401]:  * Stopping weewx weather system 
weewx
Mar  6 00:31:54 weather-station weewx[3350]: engine: Shutting down StdReport 
thread
Mar  6 00:31:54 weather-station weewx[3350]: engine: Terminating weewx version 
3.8.0
Mar  6 00:31:59 weather-station weewx[3401]: .   ...done.
Mar  6 00:31:59 weather-station systemd[1]: Stopped LSB: weewx weather system.
Mar  6 00:32:46 weather-station systemd[1]: Started Session c5 of user swalton.
Mar  6 00:33:23 weather-station rsyslogd-2007: action 'action 10' suspended, 
next retry is Tue Mar  6 00:34:53 2018 [v8.16.0 try 
http://www.rsyslog.com/e/2007 ]
Mar  6 00:33:30 weather-station systemd[1]: Starting LSB: weewx weather 
system...
Mar  6 00:33:30 weather-station weewx[3534]:  * Starting weewx weather system 
weewx
Mar  6 00:33:30 weather-station weewx[3546]: engine: Initializing weewx version 
3.8.0
Mar  6 00:33:30 weather-station weewx[3546]: engine: Using Python 2.7.12 
(default, Dec  4 2017, 14:50:18) #012[GCC 5.4.0 20160609]
Mar  6 00:33:30 weather-station weewx[3546]: engine: Platform 
Linux-4.4.38-v7+-armv7l-with-Ubuntu-16.04-xenial
Mar  6 00:33:30 weather-station weewx[3546]: engine: Locale is 'en_AU.UTF-8'
Mar  6 00:33:30 weather-station weewx[3546]: engine: pid file is 
/var/run/weewx.pid
Mar  6 00:33:30 weather-station weewx[3550]: engine: Using configuration file 
/etc/weewx/weewx.conf
Mar  6 00:33:30 weather-station weewx[3550]: engine: debug is 1
Mar  6 00:33:30 weather-station weewx[3550]: engine: Initializing engine
Mar  6 00:33:30 weather-station weewx[3550]: engine: Loading station type 
WMR300 (weewx.drivers.wmr300)
Mar  6 00:33:30 weather-station weewx[3534]:...done.
Mar  6 00:33:30 weather-station systemd[1]: Started LSB: weewx weather system.
Mar  6 00:33:30 weather-station weewx[3550]: wmr300: driver version is 0.19rc5
Mar  6 00:33:30 weather-station weewx[3550]: wmr300: usb info: 
pyusb_version=1.0.0b2
Mar  6 00:33:30 weather-station weewx[3550]: wmr300: sensor map is 
{'outHumidity': 'humidity_1', 'extraDewpoint6': 'dewpoint_7', 'windchill': 
'windchill', 'extraDewpoint4': 'dewpoint_5', 'rainRate': 'rain_rate', 
'heatindex': 'heatindex_1', 'inTemp': 'temperature_0', 'windGustDir': 
'wind_gust_dir', 'extraDewpoint2': 'dewpoint_3', 'extraDewpoint3': 
'dewpoint_4', 'extraDewpoint1': 'dewpoint_2', 'barometer': 'barometer', 
'extraDewpoint7': 'dewpoint_8', 'dewpoint': 'dewpoint_1', 'extraDewpoint5': 
'dewpoint_6', 'extraHumid6': 'humidity_7', 'pressure': 'pressure', 
'extraHumid4': 'humidity_5', 'extraHumid5': 'humidity_6', 'extraHumid2': 
'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid1': 'humidity_2', 
'extraTemp6': 'temperature_7', 'extraTemp7': 'temperature_8', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp2': 'temperature_3', 
'extraTemp3': 'temperature_4', 'extraTemp1': 'temperature_2', 
'extraHeatindex3': 'heatindex_4', 'extraHeatindex2': 'heatindex_3', 
'extraHeatindex1': 'heatindex_2', 'extraHeatindex

Re: [weewx-user] VantagePro 2 + WeeWX Sensor Data?

[Paul Miller]

I'm currently using WeeWX to digest the data and serve it as JSON so we can
hook it into an existing GUI.. as for making your own, WeeWX should suffice
with it's template system. It's very good.

weewxd /etc/weewx/weewx.conf

Look up running WeeWX directly. The hardware guide has all the specific
details about what's provided by what.

On Mar 5, 2018 4:56 AM, "Joush"  wrote:

> Hello, Keffer
>
> Is there any way to use weewx in another script?
> I want to create a GUI and display current data from Davis Vantage Pro 2.
>
>
> On Saturday, 24 February 2018 03:17:48 UTC+7, Tom Keffer wrote:
>>
>> Yes. Every type emitted in both LOOP packets and archive records is
>> included, so running WeeWX from the command line will print out the whole
>> lot.
>>
>> The types are also listed in the Hardware Guide
>> .
>>
>> -tk
>>
>> On Fri, Feb 23, 2018 at 11:22 AM, Paul Miller  wrote:
>>
>>> Hello,
>>>
>>> Is there a way to see a full list of data that the Vantage Pro2 ( cabled
>>> ) provides to WeeWX?
>>>
>>> Thanks!
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/TwqRjEYPcXg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Maplins N23DQ Weather Station

[mwall]

On Sunday, March 4, 2018 at 2:37:38 PM UTC-5, Season Ticket wrote:
>
>
> Any ideas on why the weatherstation doesn't seen to even connect to the 
> webserver?
>

can you do packet capture at the edge of your network (i.e., on the 
router)?  see exactly what the weather station is sending, and where it is 
sending it.  it is possible that the console configuration did not 'stick', 
or that there is a bug in the firmware, or you mistyped the address when 
configuring the console.

try using an ip address in the console, not a hostname

if you have control of your router, change the dns entry for 
www.wunderground.com (or whatever hostname the console is using to contact 
weather underground - i am pretty sure it is not www.wunderground.com), 
preferably just for the console.

if your network configuration supports it (mirrored port on a switch or 
ethernet hub), put the weewx-interceptor into sniff mode instead of listen 
mode, and have it capture whatever traffic the console is sending.

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR300 - Ubuntu Weather Undergroud wind direction

[mwall]

sam,

in weewx.conf, enable debug_decode like this:

[WMR300]
debug_decode = 1

then restart weewx and post about 10 minutes of the resulting log.

it is odd that winddir would be reported for regular weewx reports but not 
for wu, so lets find out exactly what the driver is sending out.

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Get instant data only once

[mwall]

On Wednesday, February 28, 2018 at 4:34:16 PM UTC-5, Rodrigo Scuissiato 
wrote:
>
> Hi, Is there a way to run weewx only one time and get a instant data from 
> the station?
> Im using the simulator and running weewx directly, but it keeps on a loop, 
> and i jut want one read
>

it depends on the hardware, but most drivers support this:

wee_device --current

to get the current conditions from the hardware.

generally speaking, weewx should be in control of the hardware.  some 
hardware has specific timing or protocol issues, and the weewx drivers are 
designed to get data robustly and reliably.

instead of running weewx periodically, you might want to run weewx 
continuously, then have your process query the weewx database using 
standard sql.  or use a service that emits data on every LOOP, and have 
your process read that.

m

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] VantagePro 2 + WeeWX Sensor Data?

[Joush]

Hello, Keffer

Is there any way to use weewx in another script?
I want to create a GUI and display current data from Davis Vantage Pro 2.


On Saturday, 24 February 2018 03:17:48 UTC+7, Tom Keffer wrote:
>
> Yes. Every type emitted in both LOOP packets and archive records is 
> included, so running WeeWX from the command line will print out the whole 
> lot.
>
> The types are also listed in the Hardware Guide 
> .
>
> -tk
>
> On Fri, Feb 23, 2018 at 11:22 AM, Paul Miller  > wrote:
>
>> Hello,
>>
>> Is there a way to see a full list of data that the Vantage Pro2 ( cabled 
>> ) provides to WeeWX?
>>
>> Thanks!
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] VantagePro 2 + WeeWX Sensor Data?

[Joush]

Hello, Paul

Can you tell me which command you used to get print out this.?

On Saturday, 24 February 2018 03:44:12 UTC+7, Paul Miller wrote:
>
> Mr. Keffer,
>
> Thanks for the timely reply! I did as you suggested as was able to get the 
> following to print out in terminal--
>
> 2018-02-23 14:50:21 EST (1519415421) 
>> altimeter: None,
>> appTemp: 71.666996991,
>> barometer: 30.315,
>> cloudbase: 4710.26217207,
>> consBatteryVoltage: 4.72,
>> dateTime: 1519415421,
>> dayET: 0.0,
>> dayRain: 0.0,
>> dewpoint: 50.6748464429,
>> extraAlarm1: 0,
>> extraAlarm2: 0,
>> extraAlarm3: 0,
>> extraAlarm4: 0,
>> extraAlarm5: 0,
>> extraAlarm6: 0,
>> extraAlarm7: 0,
>> extraAlarm8: 0,
>> forecastIcon: 6,
>> forecastRule: 12,
>> heatindex: 71.4,
>> humidex: 74.0160582445,
>> inDewpoint: 50.8498780575,
>> inHumidity: 41.0,
>> insideAlarm: 0,
>> inTemp: 76.3,
>> leafWet4: 0.0,
>> maxSolarRad: None,
>> monthET: 0.0,
>> monthRain: 0.0,
>> outHumidity: 48.0,
>> outsideAlarm1: 0,
>> outsideAlarm2: 0,
>> outTemp: 71.4,
>> pressure: None,
>> rain: None,
>> rainAlarm: 0,
>> rainRate: 0.0,
>> soilLeafAlarm1: 0,
>> soilLeafAlarm2: 0,
>> soilLeafAlarm3: 0,
>> soilLeafAlarm4: 0,
>> stormRain: 0.0,
>> sunrise: 1519386480,
>> sunset: 1519426560,
>> trendIcon: -20,
>> txBatteryStatus: 0,
>> usUnits: 1,
>> windchill: 71.4,
>> windDir: None,
>> windGust: 0.0,
>> windGustDir: None,
>> windSpeed: 0.0,
>> windSpeed10: 0.0,
>> yearET: 0.0,
>> yearRain: 0.0
>
>
> However, what this doesn't tell me is what WeeWX will calculate on the fly 
> using the data provided. Is there a way to ping WeeWX to provide the data 
> it calculates for specific hardware? I realize that this is a tall order, 
> however if it exists, this will save me hours of cross-referencing to see 
> what's being gathered and what's being calculated on the fly.
>
> Many thanks 
>
> On Fri, Feb 23, 2018 at 3:17 PM, Thomas Keffer  > wrote:
>
>> Yes. Every type emitted in both LOOP packets and archive records is 
>> included, so running WeeWX from the command line will print out the whole 
>> lot.
>>
>> The types are also listed in the Hardware Guide 
>> .
>>
>> -tk
>>
>> On Fri, Feb 23, 2018 at 11:22 AM, Paul Miller > > wrote:
>>
>>> Hello,
>>>
>>> Is there a way to see a full list of data that the Vantage Pro2 ( cabled 
>>> ) provides to WeeWX?
>>>
>>> Thanks!
>>>
>>> -- 
>>> 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 .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/TwqRjEYPcXg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.