[weewx-user] Re: Live Update don't work anymore

[Dirk]

Thank you for your help,
mqtt send now the barometer in hPa
on my phone (Android) the icon gets green
but on pc is the same error
my website is www.schieber-com.de/wetter

Am Sonntag, 11. August 2019 02:55:48 UTC+2 schrieb Pat:
>
> Try this. If this doesn't work please provide a link to your website
>
> [[MQTT]]
> server_url = mqtt://broker.hivemq.com:1883/
> topic = wetter/ficht
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> [[[inputs]]]
> barometer
> name = barometer_hPa
> units = hPa
>
>
> On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:
>>
>> Hi,
>> The live update of my Website worked the whole day, but now it has 
>> stopped working, i changed nothing.
>> When i use Mqtt.fx on my laptop i see the Data, but on the Website i got 
>> an error.
>>
>> Chrome Console say
>>
>> 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal 
>> error. Error Message: Cannot read property 'barometer' of undefined, Stack 
>> trace: TypeError: Cannot read property 'barometer' of undefined
>>
>> I tried to change the units in weewx.conf mqtt but that don't work
>>
>> here the weewx.conf
>>
>> [[MQTT]]
>> server_url = mqtt://broker.hivemq.com:1883/
>> topic = wetter/ficht
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> [[[inputs]]]
>> barometer
>> units = hPa
>>
>> anyone an idea
>>
>> Dirk 
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/29f18fec-437a-4d20-983c-6eacab0803a3%40googlegroups.com.

Re: [weewx-user] Re: Live Update don't work anymore

[steeple ian]

Have you tried clearing your pc’s browser cache?

On Sun, 11 Aug 2019 at 08:09, Dirk  wrote:

> Thank you for your help,
> mqtt send now the barometer in hPa
> on my phone (Android) the icon gets green
> but on pc is the same error
> my website is www.schieber-com.de/wetter
>
> Am Sonntag, 11. August 2019 02:55:48 UTC+2 schrieb Pat:
>>
>> Try this. If this doesn't work please provide a link to your website
>>
>> [[MQTT]]
>> server_url = mqtt://broker.hivemq.com:1883/
>> topic = wetter/ficht
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> [[[inputs]]]
>> barometer
>> name = barometer_hPa
>> units = hPa
>>
>>
>> On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:
>>>
>>> Hi,
>>> The live update of my Website worked the whole day, but now it has
>>> stopped working, i changed nothing.
>>> When i use Mqtt.fx on my laptop i see the Data, but on the Website i got
>>> an error.
>>>
>>> Chrome Console say
>>>
>>> 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal
>>> error. Error Message: Cannot read property 'barometer' of undefined, Stack
>>> trace: TypeError: Cannot read property 'barometer' of undefined
>>>
>>> I tried to change the units in weewx.conf mqtt but that don't work
>>>
>>> here the weewx.conf
>>>
>>> [[MQTT]]
>>> server_url = mqtt://broker.hivemq.com:1883/
>>> topic = wetter/ficht
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> [[[inputs]]]
>>> barometer
>>> units = hPa
>>>
>>> anyone an idea
>>>
>>> Dirk
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/29f18fec-437a-4d20-983c-6eacab0803a3%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaTqWA7exuuz2T9hZxMtS6Onb3%2Bt1G57A5kaMJn5vDfpCg%40mail.gmail.com.

Re: [weewx-user] Re: Live Update don't work anymore

[Andrew Milner]

updating ok on my pc using edge browser with barometer in HPa

seems fine to me



On Sunday, 11 August 2019 10:27:21 UTC+3, steeple ian wrote:
>
> Have you tried clearing your pc’s browser cache?
>
> On Sun, 11 Aug 2019 at 08:09, Dirk > 
> wrote:
>
>> Thank you for your help,
>> mqtt send now the barometer in hPa
>> on my phone (Android) the icon gets green
>> but on pc is the same error
>> my website is www.schieber-com.de/wetter
>>
>> Am Sonntag, 11. August 2019 02:55:48 UTC+2 schrieb Pat:
>>>
>>> Try this. If this doesn't work please provide a link to your website
>>>
>>> [[MQTT]]
>>> server_url = mqtt://broker.hivemq.com:1883/
>>> topic = wetter/ficht
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> [[[inputs]]]
>>> barometer
>>> name = barometer_hPa
>>> units = hPa
>>>
>>>
>>> On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:

 Hi,
 The live update of my Website worked the whole day, but now it has 
 stopped working, i changed nothing.
 When i use Mqtt.fx on my laptop i see the Data, but on the Website i 
 got an error.

 Chrome Console say

 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal 
 error. Error Message: Cannot read property 'barometer' of undefined, Stack 
 trace: TypeError: Cannot read property 'barometer' of undefined

 I tried to change the units in weewx.conf mqtt but that don't work

 here the weewx.conf

 [[MQTT]]
 server_url = mqtt://broker.hivemq.com:1883/
 topic = wetter/ficht
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate
 [[[inputs]]]
 barometer
 units = hPa

 anyone an idea

 Dirk 

>>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/29f18fec-437a-4d20-983c-6eacab0803a3%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f3804d61-ae30-4d9b-bd6d-b24fc08e2eca%40googlegroups.com.

Re: [weewx-user] Re: Live Update don't work anymore

[steeple ian]

Yes I have also checked with various browsers so I suspect a cache problem
on Dirk’s PC

On Sun, 11 Aug 2019 at 08:41, Andrew Milner 
wrote:

> updating ok on my pc using edge browser with barometer in HPa
>
> seems fine to me
>
>
>
> On Sunday, 11 August 2019 10:27:21 UTC+3, steeple ian wrote:
>>
>> Have you tried clearing your pc’s browser cache?
>>
>> On Sun, 11 Aug 2019 at 08:09, Dirk  wrote:
>>
> Thank you for your help,
>>> mqtt send now the barometer in hPa
>>> on my phone (Android) the icon gets green
>>> but on pc is the same error
>>> my website is www.schieber-com.de/wetter
>>>
>>> Am Sonntag, 11. August 2019 02:55:48 UTC+2 schrieb Pat:

 Try this. If this doesn't work please provide a link to your website

 [[MQTT]]
 server_url = mqtt://broker.hivemq.com:1883/
 topic = wetter/ficht
 unit_system = METRIC
 binding = archive, loop
 aggregation = aggregate
 [[[inputs]]]
 barometer
 name = barometer_hPa
 units = hPa


 On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:
>
> Hi,
> The live update of my Website worked the whole day, but now it has
> stopped working, i changed nothing.
> When i use Mqtt.fx on my laptop i see the Data, but on the Website i
> got an error.
>
> Chrome Console say
>
> 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal
> error. Error Message: Cannot read property 'barometer' of undefined, Stack
> trace: TypeError: Cannot read property 'barometer' of undefined
>
> I tried to change the units in weewx.conf mqtt but that don't work
>
> here the weewx.conf
>
> [[MQTT]]
> server_url = mqtt://broker.hivemq.com:1883/
> topic = wetter/ficht
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> [[[inputs]]]
> barometer
> units = hPa
>
> anyone an idea
>
> Dirk
>
 --
>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/29f18fec-437a-4d20-983c-6eacab0803a3%40googlegroups.com
>>> 
>>> .
>>>
>> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/f3804d61-ae30-4d9b-bd6d-b24fc08e2eca%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CADASSaTb1Wmq1f5V0Law9mMX5OC6ENCwPiiXYah7Pk_cPOG9vQ%40mail.gmail.com.

[weewx-user] Re: Live Update don't work anymore

[Manfred Maier]

Hi Dirk,
I had the same issue a couple of days ago.

In my case the website didn't connect to the MQTT broker when I typed the 
website URL as "domain.de". It only worked with "www.domain.de".
Could that be the issue in your case, too?

Manfred 


Am Sonntag, 11. August 2019 09:09:15 UTC+2 schrieb Dirk:
>
> Thank you for your help,
> mqtt send now the barometer in hPa
> on my phone (Android) the icon gets green
> but on pc is the same error
> my website is www.schieber-com.de/wetter
>
> Am Sonntag, 11. August 2019 02:55:48 UTC+2 schrieb Pat:
>>
>> Try this. If this doesn't work please provide a link to your website
>>
>> [[MQTT]]
>> server_url = mqtt://broker.hivemq.com:1883/
>> topic = wetter/ficht
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> [[[inputs]]]
>> barometer
>> name = barometer_hPa
>> units = hPa
>>
>>
>> On Saturday, August 10, 2019 at 3:30:12 PM UTC-4, Dirk wrote:
>>>
>>> Hi,
>>> The live update of my Website worked the whole day, but now it has 
>>> stopped working, i changed nothing.
>>> When i use Mqtt.fx on my laptop i see the Data, but on the Website i got 
>>> an error.
>>>
>>> Chrome Console say
>>>
>>> 10. August 2019, 21:16:22: mqtt Connection Lost: AMQJS0005E Internal 
>>> error. Error Message: Cannot read property 'barometer' of undefined, Stack 
>>> trace: TypeError: Cannot read property 'barometer' of undefined
>>>
>>> I tried to change the units in weewx.conf mqtt but that don't work
>>>
>>> here the weewx.conf
>>>
>>> [[MQTT]]
>>> server_url = mqtt://broker.hivemq.com:1883/
>>> topic = wetter/ficht
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> [[[inputs]]]
>>> barometer
>>> units = hPa
>>>
>>> anyone an idea
>>>
>>> Dirk 
>>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f84e0403-6350-4559-92c3-166076ab7988%40googlegroups.com.

Re: [weewx-user] Potential memory issue

[Gordie Stirling]

On Saturday, 10 August 2019 14:01:11 UTC+1, Leon Shaner wrote:
>
> It isn't the weewx version, it's the pi kernel / usb module version.  The 
> usb stack hangs.  I wrote a watchdog to detect it and reboot the pi, 
> because so far there has been no fix to the issue.  I am not able to 
> correlate this to a memory leak.  What are you seeing re: memory? 
>
> Regards, 
> \Leon 
> -- 
> Leon Shaner :: Dearborn, Michigan (iPhone) 
>
> Hi Leon,

The reason I suspected an issue with the memory was a line in 
/var/log/syslog

Aug 11 1:31:04 wstation weewx[15295]: fousb: unstable read: blocks differ 
for ptr 0x0001000

I will revert back to Jessie and see if that fixes the issue.  My station 
pushes updates to Wunderground, but sits in its own DMZ, so I dont mind 
running slightly older code.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5023863c-1a28-450b-af1f-d6c71a72363a%40googlegroups.com.

[weewx-user] Re: Live Update don't work anymore

[Dirk]

Hi,
yes you have right, when i add the www before the url the connection work 
on every browser, pc ore mobile.
Thank you for this tipp
and thanks to everybody for your help.

Dirk

Am Sonntag, 11. August 2019 11:11:32 UTC+2 schrieb Manfred Maier:
>
> Hi Dirk,
> I had the same issue a couple of days ago.
>
> In my case the website didn't connect to the MQTT broker when I typed the 
> website URL as "domain.de". It only worked with "www.domain.de".
> Could that be the issue in your case, too?
>
> Manfred 
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/020436f1-9709-41f7-b11f-b884e1f9d605%40googlegroups.com.

[weewx-user] Re: Live Update don't work anymore

[Manfred Maier]

You're welcome! 

I guess you know how to fix this via a .htaccess file?


Am Sonntag, 11. August 2019 12:46:55 UTC+2 schrieb Dirk:
>
> Hi,
> yes you have right, when i add the www before the url the connection work 
> on every browser, pc ore mobile.
> Thank you for this tipp
> and thanks to everybody for your help.
>
> Dirk
>
>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/87f22269-46cd-4915-829f-e0726aef8dc2%40googlegroups.com.

[weewx-user] NeoWX skin problems

[Michael Stuhldreier]

Hello guys,
i installed neowx and the directory is okay.



But after restarting the weewx service and restart my raspberry pi, it dont 
works, here the status message:


I also edited my weewx.conf with the vi editor, because with winscp, i do 
not have permissions to edit this weewx.conf file :(



so what could be the problem here? 

My website do have the old skin with the last update from 1h ago :( so it 
is not working...or is there another url, now?

BR
Michael

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0ec1c19c-b51f-4dec-8cc3-5ea31d6717be%40googlegroups.com.

[weewx-user] Re: NeoWX skin problems

[Michael Stuhldreier]

Hey, 

after a few minutes, i got the new skin :-) 

But there are no data like day time (6:00 , 12:00 etc.) in the graphs :( 

should i wait and they come automatically after a few hours? Or is there a 
mistake?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5efa6e81-8fef-4f23-b63d-39b6d913d97a%40googlegroups.com.

[weewx-user] Neowx skin problem

[Michael Stuhldreier]

Hello again,
i have problems after updating my weewx skin from standard to neowx. 

The installataion was successful, i become a website with correct data, but 
there are no timestamps in the graphs (no clock or temperature o.ä) :( :( :(

What is the problem here?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4908f7e0-5dfa-4896-9851-ca48a3c9a544%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Manfred Maier]

Thanks Pat! It works.

Yet, my website coding skills are unfortunately not the best. 
How does your code look like, where you translate the 
$current.txBatteryStatus into a green 'OK' (on your about-page)?
I've tried all different kinds of if-statements but none worked.



Am Sonntag, 11. August 2019 04:16:34 UTC+2 schrieb Pat:
>
> Is your station or driver tracking the rxCheckPercent? (check your 
> database to see if its populated). If so then try $current.rxCheckPercent 
> for the text representation. 
>
> To graph it add this to your graphs.conf
>
> [about]
> show_button = false
> time_length = 172800 # 48 hours in seconds
> aggregate_type = last
> aggregate_interval = 300 # 5 min
> gapsize = 30 # 5 min
> 
> [[rxchart]]
> title = ISS Receive Stats
> yaxis_max = 100
> [[[rxCheckPercent]]]
> color = "#268bd2"
> 
> [[rxchartyear]]
> title = ISS Receive Stats Average
> yaxis_max = 100
> xaxis_groupby = month
> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul'
> , 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
> time_length = year
> [[[rxCheckPercent]]]
> aggregate_type = avg
> color = "#268bd2"
>
>
>
> Then at the top of your about.inc add this line which initializes 
> Highcharts for the [about] graph group
>
> showChart("about");
>
>
> Then inside your about.inc where you want the graph to actually appear add 
> this:
>
> 
> 
>
>
> Basically the top of the about.inc will initialize the Highcharts [about] 
> code, and the 's tell it where to put those charts. You can see that 
> the  is the same name as the chart name inside the [about] graph 
> group. 
>
> With this simple logic in mind, you can put any chart on any page you 
> want. 
>
>
> On Saturday, August 10, 2019 at 5:13:31 PM UTC-4, Manfred Maier wrote:
>>
>> Hi Pat,
>> a quick question: 
>> How do I get the Signal Quality / ISS Receive Stats onto the About page? 
>> I've tried $station.rxCheckPercent, but that triggered an error.
>>
>> Is the about.inc of your page somewhere available?
>>
>> Thanks!
>> Manfred. 
>>
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5688f2e9-d520-4bd8-b03b-ff703878ae97%40googlegroups.com.

[weewx-user] Re: Backupsystem

[Ton Karsten]

The Weewx software is installed on a Raspberry Pi with IP address 
192.168.178.11. The version that I use is 3.9.1. The Popcorn Hour (NMT) has 
IP address 192.168.178.19. Now I try to build an FTP connection to the NMT 
with various settings. With Filezilla and WinSCP I can log in to the NMT. 
But whatever I try with various settings always gets an error message. I do 
not know anymore. See LOG file.

Op donderdag 8 augustus 2019 10:54:35 UTC+2 schreef Ton Karsten:
>
> Can a NetworkMediaTank (NMT) such as a Popcorn Hour A400 be used as a 
> backup system?
> It can handle the FTP protocol.
> The NMT is in the same network.
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3b265cf2-8176-4e06-88db-8480662be01c%40googlegroups.com.
ug 11 06:25:22 raspberrypi weewx[5523]: ftpupload: Unable to connect or log 
into server : [Errno -2] Name or service not known
Aug 11 06:25:22 raspberrypi weewx[5523]: ftpupload: Unable to connect or log 
into server : [Errno -2] Name or service not known
Aug 11 06:25:22 raspberrypi weewx[5523]: ftpupload: Unable to connect or log 
into server : [Errno -2] Name or service not known
Aug 11 06:25:22 raspberrypi weewx[5523]: ftpupload: Attempted 3 times to 
connect to server /192.168.178.19. Giving up.
Aug 11 06:25:22 raspberrypi weewx[5523]: ftpgenerator: ftp'd 0 files in 0.14 
seconds

Re: [weewx-user] Re: Backupsystem

[Greg Troxel]

Ton Karsten  writes:

> The Weewx software is installed on a Raspberry Pi with IP address 
> 192.168.178.11. The version that I use is 3.9.1. The Popcorn Hour (NMT) has 
> IP address 192.168.178.19. Now I try to build an FTP connection to the NMT 
> with various settings. With Filezilla and WinSCP I can log in to the NMT. 
> But whatever I try with various settings always gets an error message. I do 
> not know anymore. See LOG file.

I am having trouble understanding what you are trying to do.

"backup" usually means to make copies of all files of importance on a
given system, and to put those copies someplace else.   I do this
outside of weewx.  Important files to back up are the weewx
configuration files (which would be annoying to recreate) and especially
the weewx database (which I can't recreate).

I use bup, and store the bits on multiple other disks.  My backup
mechanism has really nothing to do with weewx other than that I am
backing up files that weewx uses.

One could use tar, or dump, or bup, or various other mechanisms, and
then use ftp to store files.  I would be using the command-line ftp
client that I expect is part of the base OS, rather than something
complicated.

With weewx's ftpuploader, I would expect that to be used to transmit
constructed web pages to someplace else (to a web server, usually).  I
don't see that being super useful for backup as I would expect you want
to preserve weewx.sdb.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmipnlbpv4n.fsf%40s1.lexort.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pepe]

Hi

I am triying to draw a climate graph but I want to put in yAxis doble 
values than xAxis. For example if I got 20 in the left must be 40 in the 
right, that is to say, the rainfall scale must always be twice that of 
temperature. Attached the graph I get with precipitation scale column wrong.
Any idea?

El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8e0a80d6-4652-424a-8a10-f61680901950%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pepe]

Correction: In red what I meant

*Hi*

*I am triying to draw a climate graph but I want to put doble values in the 
right than left . For example if I got 20 in the left must be 40 in the 
right, that is to say, the rainfall scale must always be twice that of 
temperature. Attached the graph I get with precipitation scale column 
wrong.*

*Any idea?*




El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>
> Belchertown skin 1.0 is released!
>
> This update contains a lot of updates and changes including *an entire 
> rewrite of the Highcharts system* which allows you to make almost any 
> graph you want for almost any time span you want. You can see some examples 
> of the charts you can make on the BelchertownWeather.com website graphs 
> page .
>
> You can add/remove/change/reorder any chart, change colors, add 
> observation plots, categorize for all time. Almost anything you want to do 
> is available! The skin comes with the standard 4 charts ready to go, but 
> there's extensive Belchertown Charts Documentation 
> 
>  
> which can help you get started. 
>
> In addition to the Charts there's now a dark mode (which has an 
> auto-switching mode based on sunset/sunrise), more flexibility for 
> translations, user customized station observation table which is updated in 
> real time if the MQTT Websockets are enabled, and a lot more. Check the 
> release notes for all the details! 
>
> You can download the latest release here 
> ,
>  
> and read all of the details on the changes here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
> uninstall everything and reinstall new. This is due to the Chart system 
> being fully rewritten and the potential for conflicts. Please read this 
> upgrade guide if you are upgrading from an older version of Belchertown skin 
> 
> . 
>
> Thanks to all the beta testers and translators over the last couple of 
> months help me iron out all the kinks and shape the skin in a way that can 
> be translated a little easier! 
>
> Attached are some examples of the charts that can be made. If you find any 
> issues, you can reply here or open an issue on the Belchertown skin 
> GitHub page . 
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9d4694a4-55a2-474c-808e-26ba4f2d7530%40googlegroups.com.

Re: [weewx-user] Potential memory issue

[Thomas Keffer]

If memory increases every couple of seconds, which suggests that the leak
is in the part of device driver that deals with LOOP packets. But, you're
on an WMR300, right? As I recall, their LOOP packets are more like 10-20
seconds apart --- too long to correlate with what you're seeing. Or, are
you on something like a Vantage with a shorter LOOP packet interval?

I've noticed memory leaks in other instances, such as my own site
http://www.threefools.org/weewx. In my case, I spent a couple of weeks
trying to chase it down, and concluded the problem was somewhere in the
sqlite database driver, but couldn't put my finger on it conclusively.

Then, magically, Debian did an update and the problem (nearly) went away.
Memory leak dropped from 5 MB/day, to almost nothing (maybe a megabyte or
two over a week). Again, it suggests the problem was (is) in a device
driver somewhere.

-tk

On Sun, Aug 11, 2019 at 8:55 AM Leon Shaner  wrote:

> TK, you may want to know...
> There definitely is a memory leak in weewxd.
> It grows by 1 KiB about every 2 seconds.
>
> I haven't yet correlated whether weewxd can grow to a point where other
> things start dying, and whether that has any impact on the USB stack.
>
> What tipped me off was I just got a warning from sar/sa1 stating it
> couldn't do it's job due to "resource unavailable," so I went and had a
> peek.
>
> This RPI is a Zero W(H), so it has only 1 GB of RAM.
> It's full enough on memory that it's using some swap.
>
> Here is just one snapshot.  That RES (RZ) value for weewxd goes up by one
> digit every 2 seconds.
> I gleaned that is 1 KiB, but I am not 100% certain. It might only be 1
> byte every 2 seconds -- whatever the actual unit it goes up by one every 2
> seconds.  I've never seen it come down.
>
> I may enhance my watchdog to check the weewxd memory size and restart it
> after a limit, then see if that has any positive impact on avoiding the USB
> stack going south.  Yeah, I guess I'll work on that this week.   I'll put
> some logging in so anyone who wants to keep an eye on it can know whether
> their setup is memory leaking also.  =D
>
> I have the WMR300 driver, in case the leak could be specific to that
> driver.  :-/
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/D7820F76-CC3A-4CC2-B359-4AF967A32638%40isylum.org
> .
>
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> > On Aug 10, 2019, at 9:01 AM, Leon Shaner  wrote:
> >
> > It isn't the weewx version, it's the pi kernel / usb module version.
> The usb stack hangs.  I wrote a watchdog to detect it and reboot the pi,
> because so far there has been no fix to the issue.  I am not able to
> correlate this to a memory leak.  What are you seeing re: memory?
> >
> > Regards,
> > \Leon
> > --
> > Leon Shaner :: Dearborn, Michigan (iPhone)
> >
> >> On Aug 10, 2019, at 4:29 AM, Gordie Stirling  wrote:
> >>
> >> Hi all,
> >>
> >> I have been runnin Weewx on a Raspberry Pi (model a) for a couple of
> years with a Maplin NG96Y, without any issues.
> >>
> >> I recently upgraded to a Pi3, running Stetch, and Lighttpd.  the old Pi
> was starting to struggle and sat at 100% cpu for most of the time.
> >>
> >> All worked well for a month or so, the the station locked up.  After a
> reset(batteries out, usb disconnected) it works for an hour or so, then
> locks the connection again. the base station still continues to function.
> >>
> >> Error in syslog is Aug 10 09:17:28 raspberrypi weewx[10377]: fousb:
> get_records failed: [Errno 110] Operation timed out.
> >>
> >> so far, other than rebooting, i have used Easy Weather to clear tge
> memory, but alas had no effect, 85 mins later, timeouts start again.
> >>
> >> I am thunking of downgrading the Pi to Jessie, and using reverting to
> Weewx 3.9.1, but wondered if anyone has had this problem and managed to fix
> rather than rebuild.
> >>
> >> TIA
> >>
> >> G
> >>
> >> --
> >> 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.
> >> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/afbf7556-425f-4eca-8088-caaf96c06805%40googlegroups.com
> .
> >
> > --
> > 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.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/315802A3-3CD7-4206-B22B-77A377B0F5A7%40isylum.org
> .
>
> --
> You received this message because you are s

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

For the observation which you have specified yaxis = 1, you also should 
specify the yaxis_tickinterval 

 
if you want more ticks on the yaxis. 

On Sunday, August 11, 2019 at 11:52:33 AM UTC-4, Pepe wrote:
>
> Correction: In red what I meant
>
> *Hi*
>
> *I am triying to draw a climate graph but I want to put doble values in 
> the right than left . For example if I got 20 in the left must be 40 in the 
> right, that is to say, the rainfall scale must always be twice that of 
> temperature. Attached the graph I get with precipitation scale column 
> wrong.*
>
> *Any idea?*
>
>
>
>
> El sábado, 1 de junio de 2019, 18:57:56 (UTC+2), Pat escribió:
>>
>> Belchertown skin 1.0 is released!
>>
>> This update contains a lot of updates and changes including *an entire 
>> rewrite of the Highcharts system* which allows you to make almost any 
>> graph you want for almost any time span you want. You can see some examples 
>> of the charts you can make on the BelchertownWeather.com website graphs 
>> page .
>>
>> You can add/remove/change/reorder any chart, change colors, add 
>> observation plots, categorize for all time. Almost anything you want to do 
>> is available! The skin comes with the standard 4 charts ready to go, but 
>> there's extensive Belchertown Charts Documentation 
>> 
>>  
>> which can help you get started. 
>>
>> In addition to the Charts there's now a dark mode (which has an 
>> auto-switching mode based on sunset/sunrise), more flexibility for 
>> translations, user customized station observation table which is updated in 
>> real time if the MQTT Websockets are enabled, and a lot more. Check the 
>> release notes for all the details! 
>>
>> You can download the latest release here 
>> ,
>>  
>> and read all of the details on the changes here: 
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>> *Note: You cannot upgrade from Belchertown 0.9 and older*. You must 
>> uninstall everything and reinstall new. This is due to the Chart system 
>> being fully rewritten and the potential for conflicts. Please read this 
>> upgrade guide if you are upgrading from an older version of Belchertown skin 
>> 
>> . 
>>
>> Thanks to all the beta testers and translators over the last couple of 
>> months help me iron out all the kinks and shape the skin in a way that can 
>> be translated a little easier! 
>>
>> Attached are some examples of the charts that can be made. If you find 
>> any issues, you can reply here or open an issue on the Belchertown skin 
>> GitHub page . 
>>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4ae62220-d2dd-45f1-9eeb-7f236e22e06a%40googlegroups.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Pat]

Hi Manfred, I took this one right from the Season's skin, but modified it 
slightly to include the CSS color so it was inline. Give this a try (remove 
it from the table's tr's and td's if you're not using a table)

#if $day.txBatteryStatus.has_data

  
Transmitter Battery
  
#if $current.txBatteryStatus.raw == 0
OK
#else
LOW
#end if
  

#end if


On Sunday, August 11, 2019 at 9:44:24 AM UTC-4, Manfred Maier wrote:
>
> Thanks Pat! It works.
>
> Yet, my website coding skills are unfortunately not the best. 
> How does your code look like, where you translate the 
> $current.txBatteryStatus into a green 'OK' (on your about-page)?
> I've tried all different kinds of if-statements but none worked.
>
>
>
> Am Sonntag, 11. August 2019 04:16:34 UTC+2 schrieb Pat:
>>
>> Is your station or driver tracking the rxCheckPercent? (check your 
>> database to see if its populated). If so then try $current.rxCheckPercent 
>> for the text representation. 
>>
>> To graph it add this to your graphs.conf
>>
>> [about]
>> show_button = false
>> time_length = 172800 # 48 hours in seconds
>> aggregate_type = last
>> aggregate_interval = 300 # 5 min
>> gapsize = 30 # 5 min
>> 
>> [[rxchart]]
>> title = ISS Receive Stats
>> yaxis_max = 100
>> [[[rxCheckPercent]]]
>> color = "#268bd2"
>> 
>> [[rxchartyear]]
>> title = ISS Receive Stats Average
>> yaxis_max = 100
>> xaxis_groupby = month
>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>> time_length = year
>> [[[rxCheckPercent]]]
>> aggregate_type = avg
>> color = "#268bd2"
>>
>>
>>
>> Then at the top of your about.inc add this line which initializes 
>> Highcharts for the [about] graph group
>>
>> showChart("about");
>>
>>
>> Then inside your about.inc where you want the graph to actually appear 
>> add this:
>>
>> 
>> 
>>
>>
>> Basically the top of the about.inc will initialize the Highcharts [about] 
>> code, and the 's tell it where to put those charts. You can see that 
>> the  is the same name as the chart name inside the [about] graph 
>> group. 
>>
>> With this simple logic in mind, you can put any chart on any page you 
>> want. 
>>
>>
>> On Saturday, August 10, 2019 at 5:13:31 PM UTC-4, Manfred Maier wrote:
>>>
>>> Hi Pat,
>>> a quick question: 
>>> How do I get the Signal Quality / ISS Receive Stats onto the About page? 
>>> I've tried $station.rxCheckPercent, but that triggered an error.
>>>
>>> Is the about.inc of your page somewhere available?
>>>
>>> Thanks!
>>> Manfred. 
>>>
>>>
>>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/102f61d4-b97d-420f-9976-4d4e8e5450d4%40googlegroups.com.

[weewx-user] Re: OurWeather by SwitchDoc

[Chester L. Garrett IV]

I have attached the info on how the REST works. It depends on how often you 
want to pull the data. It updates underground weather every 5 mins. But if you 
do it locally it depends on how often you want to pull the data.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c318e873-a9ac-4fb2-957d-4b2ebf2e69d2%40googlegroups.com.

[weewx-user] Re: Live Update don't work anymore

[Dirk]

i don't know this before, now I unloaded this access file and it works

thank you again

Dirk

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c31b4705-7b43-4ec5-bc56-0fb07afbb653%40googlegroups.com.

[weewx-user] Recovering Data from a broken RPI installation

[Paul Lacatus (Gmail)]

Hi,

My long running installation of weewx on a RPI 3b+ with WMR300 is 
broken. Does not boot anymore. I am able to see the rpi partition 
mounted from SD card on my macBook  . I am thinking of reinstalling from 
scratch with the new raspbian that is running also on RPI4 but I want to 
recover my two years data base . Some hints please? What should I 
recover from old SD ?  I just saved /etc/weewx .



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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/255382b1-4b1e-f2bb-1a37-3c6e376f49e3%40gmail.com.

Re: [weewx-user] Recovering Data from a broken RPI installation

[Greg Troxel]

If you used sqlite, look for archive/weewx.sdb in your weewx install
path.

On my system, that's /usr/weewx/archive/weewx.sdb from a manual install.

If you used a package, you need to figure out where it put it.

For the next round, figure out how to save a copy of weewx.sdb at least
weekly.





-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmid0hbpmfy.fsf%40s1.lexort.com.

Re: [weewx-user] Recovering Data from a broken RPI installation

[Paul Lacatus (Gmail)]

After recovering the procedure is to reinstall Weewx and after to copy 
the saved database over the new one ?

Any known issues with weewx on rasbian buster ?



On 11-Aug-19 21:49, Greg Troxel wrote:

If you used sqlite, look for archive/weewx.sdb in your weewx install
path.

On my system, that's /usr/weewx/archive/weewx.sdb from a manual install.

If you used a package, you need to figure out where it put it.

For the next round, figure out how to save a copy of weewx.sdb at least
weekly.







--
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/90ce9882-3526-dfc9-1933-57dea0f5c13b%40gmail.com.

Re: [weewx-user] Recovering Data from a broken RPI installation

[rich T]

You could overwrite the new dB with the original dB.  Then rebuild the 
daily. 
 
On Sunday, August 11, 2019 at 2:53:57 PM UTC-4, Paul Lacatus (Gmail) wrote:
>
> After recovering the procedure is to reinstall Weewx and after to copy 
> the saved database over the new one ? 
> Any known issues with weewx on rasbian buster ? 
>
>
>
> On 11-Aug-19 21:49, Greg Troxel wrote: 
> > If you used sqlite, look for archive/weewx.sdb in your weewx install 
> > path. 
> > 
> > On my system, that's /usr/weewx/archive/weewx.sdb from a manual install. 
> > 
> > If you used a package, you need to figure out where it put it. 
> > 
> > For the next round, figure out how to save a copy of weewx.sdb at least 
> > weekly. 
> > 
> > 
> > 
> > 
> > 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/259afc1c-fc57-4975-948b-fd79d75e89a4%40googlegroups.com.

Re: [weewx-user] Recovering Data from a broken RPI installation

[p q]

You might want to copy the skin conf if you've done any customization.
You'll want /etc/weewx/weewx.conf and /etc/weewx/skins/* and your database
probably in /var/lib/weewx

I'm running Stretch on my station but I've run Buster in a VM for testing
with no problems.

On Sun, Aug 11, 2019 at 11:53 AM Paul Lacatus (Gmail) <
paul.laca...@gmail.com> wrote:

> After recovering the procedure is to reinstall Weewx and after to copy
> the saved database over the new one ?
> Any known issues with weewx on rasbian buster ?
>
>
>
> On 11-Aug-19 21:49, Greg Troxel wrote:
> > If you used sqlite, look for archive/weewx.sdb in your weewx install
> > path.
> >
> > On my system, that's /usr/weewx/archive/weewx.sdb from a manual install.
> >
> > If you used a package, you need to figure out where it put it.
> >
> > For the next round, figure out how to save a copy of weewx.sdb at least
> > weekly.
> >
> >
> >
> >
> >
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/90ce9882-3526-dfc9-1933-57dea0f5c13b%40gmail.com
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM22X1UUu4pJQpBFyRXZqC9ZgFQoEN1aW71PZnKE9ePK2Mg%40mail.gmail.com.

Re: [weewx-user] Recovering Data from a broken RPI installation

[Greg Troxel]

"Paul Lacatus (Gmail)"  writes:

> After recovering the procedure is to reinstall Weewx and after to copy
> the saved database over the new one ?

Right now, your data logger, if your station has one, probably has data
for the downtime.  So what I'd do is:

  disconnect the cable to the logger

  reinstall weewx

  recover the config (and customized skins as someone else suggested)

  copy in the database (and save a copy of the old database multiple
  other places!)

  start up weewx and make sure you can generate plots etc.  The point is
  not that you can't fix that later but it proves that the old data from
  the db is accessible

  shut down weewx, reconnect the wx station cable, and start up

If your station doesn't log, then the disconnect/test/reconnect step is
not in order, and as long as the database is ok you can fix
skin/generation/upload at your leisure.

Note that I have not done what I am telling you to do; it's based on
understanding not experience.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmi5zn3plfg.fsf%40s1.lexort.com.

[weewx-user] Re: Belchertown skin 1.0 released!

[Manfred Maier]

Thanks! The .raw made the decisive difference


Am Sonntag, 11. August 2019 19:01:37 UTC+2 schrieb Pat:
>
> Hi Manfred, I took this one right from the Season's skin, but modified it 
> slightly to include the CSS color so it was inline. Give this a try (remove 
> it from the table's tr's and td's if you're not using a table)
>
> #if $day.txBatteryStatus.has_data
> 
>   
> Transmitter Battery
>   
> #if $current.txBatteryStatus.raw == 0
> OK
> #else
> LOW
> #end if
>   
> 
> #end if
>
>
> On Sunday, August 11, 2019 at 9:44:24 AM UTC-4, Manfred Maier wrote:
>>
>> Thanks Pat! It works.
>>
>> Yet, my website coding skills are unfortunately not the best. 
>> How does your code look like, where you translate the 
>> $current.txBatteryStatus into a green 'OK' (on your about-page)?
>> I've tried all different kinds of if-statements but none worked.
>>
>>
>>
>> Am Sonntag, 11. August 2019 04:16:34 UTC+2 schrieb Pat:
>>>
>>> Is your station or driver tracking the rxCheckPercent? (check your 
>>> database to see if its populated). If so then try $current.rxCheckPercent 
>>> for the text representation. 
>>>
>>> To graph it add this to your graphs.conf
>>>
>>> [about]
>>> show_button = false
>>> time_length = 172800 # 48 hours in seconds
>>> aggregate_type = last
>>> aggregate_interval = 300 # 5 min
>>> gapsize = 30 # 5 min
>>> 
>>> [[rxchart]]
>>> title = ISS Receive Stats
>>> yaxis_max = 100
>>> [[[rxCheckPercent]]]
>>> color = "#268bd2"
>>> 
>>> [[rxchartyear]]
>>> title = ISS Receive Stats Average
>>> yaxis_max = 100
>>> xaxis_groupby = month
>>> xaxis_categories = 'Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 
>>> 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'
>>> time_length = year
>>> [[[rxCheckPercent]]]
>>> aggregate_type = avg
>>> color = "#268bd2"
>>>
>>>
>>>
>>> Then at the top of your about.inc add this line which initializes 
>>> Highcharts for the [about] graph group
>>>
>>> showChart("about");
>>>
>>>
>>> Then inside your about.inc where you want the graph to actually appear 
>>> add this:
>>>
>>> 
>>> 
>>>
>>>
>>> Basically the top of the about.inc will initialize the Highcharts 
>>> [about] code, and the 's tell it where to put those charts. You can 
>>> see that the  is the same name as the chart name inside the [about] 
>>> graph group. 
>>>
>>> With this simple logic in mind, you can put any chart on any page you 
>>> want. 
>>>
>>>
>>> On Saturday, August 10, 2019 at 5:13:31 PM UTC-4, Manfred Maier wrote:

 Hi Pat,
 a quick question: 
 How do I get the Signal Quality / ISS Receive Stats onto the About 
 page? I've tried $station.rxCheckPercent, but that triggered an error.

 Is the about.inc of your page somewhere available?

 Thanks!
 Manfred. 




-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/399a331c-84f1-41a0-be46-c72b705d7942%40googlegroups.com.

Re: [weewx-user] Potential memory issue

[Leon Shaner]

Hey, TK.  WMR300.  I'll see if I can track it down.

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad)

> On Aug 11, 2019, at 12:45 PM, Thomas Keffer  wrote:
> 
> 
> If memory increases every couple of seconds, which suggests that the leak is 
> in the part of device driver that deals with LOOP packets. But, you're on an 
> WMR300, right? As I recall, their LOOP packets are more like 10-20 seconds 
> apart --- too long to correlate with what you're seeing. Or, are you on 
> something like a Vantage with a shorter LOOP packet interval?
> 
> I've noticed memory leaks in other instances, such as my own site 
> http://www.threefools.org/weewx. In my case, I spent a couple of weeks trying 
> to chase it down, and concluded the problem was somewhere in the sqlite 
> database driver, but couldn't put my finger on it conclusively.
> 
> Then, magically, Debian did an update and the problem (nearly) went away. 
> Memory leak dropped from 5 MB/day, to almost nothing (maybe a megabyte or two 
> over a week). Again, it suggests the problem was (is) in a device driver 
> somewhere.
> 
> -tk
> 
>> On Sun, Aug 11, 2019 at 8:55 AM Leon Shaner  wrote:
>> TK, you may want to know...
>> There definitely is a memory leak in weewxd.
>> It grows by 1 KiB about every 2 seconds.
>> 
>> I haven't yet correlated whether weewxd can grow to a point where other 
>> things start dying, and whether that has any impact on the USB stack.
>> 
>> What tipped me off was I just got a warning from sar/sa1 stating it couldn't 
>> do it's job due to "resource unavailable," so I went and had a peek.
>> 
>> This RPI is a Zero W(H), so it has only 1 GB of RAM.
>> It's full enough on memory that it's using some swap.
>> 
>> Here is just one snapshot.  That RES (RZ) value for weewxd goes up by one 
>> digit every 2 seconds.
>> I gleaned that is 1 KiB, but I am not 100% certain. It might only be 1 byte 
>> every 2 seconds -- whatever the actual unit it goes up by one every 2 
>> seconds.  I've never seen it come down.
>> 
>> I may enhance my watchdog to check the weewxd memory size and restart it 
>> after a limit, then see if that has any positive impact on avoiding the USB 
>> stack going south.  Yeah, I guess I'll work on that this week.   I'll put 
>> some logging in so anyone who wants to keep an eye on it can know whether 
>> their setup is memory leaking also.  =D
>> 
>> I have the WMR300 driver, in case the leak could be specific to that driver. 
>>  :-/
>> 
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/D7820F76-CC3A-4CC2-B359-4AF967A32638%40isylum.org.
>> 
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>> 
>> > On Aug 10, 2019, at 9:01 AM, Leon Shaner  wrote:
>> > 
>> > It isn't the weewx version, it's the pi kernel / usb module version.  The 
>> > usb stack hangs.  I wrote a watchdog to detect it and reboot the pi, 
>> > because so far there has been no fix to the issue.  I am not able to 
>> > correlate this to a memory leak.  What are you seeing re: memory?
>> > 
>> > Regards,
>> > \Leon
>> > --
>> > Leon Shaner :: Dearborn, Michigan (iPhone)
>> > 
>> >> On Aug 10, 2019, at 4:29 AM, Gordie Stirling  wrote:
>> >> 
>> >> Hi all,
>> >> 
>> >> I have been runnin Weewx on a Raspberry Pi (model a) for a couple of 
>> >> years with a Maplin NG96Y, without any issues.
>> >> 
>> >> I recently upgraded to a Pi3, running Stetch, and Lighttpd.  the old Pi 
>> >> was starting to struggle and sat at 100% cpu for most of the time.
>> >> 
>> >> All worked well for a month or so, the the station locked up.  After a 
>> >> reset(batteries out, usb disconnected) it works for an hour or so, then 
>> >> locks the connection again. the base station still continues to function.
>> >> 
>> >> Error in syslog is Aug 10 09:17:28 raspberrypi weewx[10377]: fousb: 
>> >> get_records failed: [Errno 110] Operation timed out.
>> >> 
>> >> so far, other than rebooting, i have used Easy Weather to clear tge 
>> >> memory, but alas had no effect, 85 mins later, timeouts start again.
>> >> 
>> >> I am thunking of downgrading the Pi to Jessie, and using reverting to 
>> >> Weewx 3.9.1, but wondered if anyone has had this problem and managed to 
>> >> fix rather than rebuild.
>> >> 
>> >> TIA
>> >> 
>> >> G
>> >> 
>> >> -- 
>> >> 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.
>> >> To view this discussion on the web visit 
>> >> https://groups.google.com/d/msgid/weewx-user/afbf7556-425f-4eca-8088-caaf96c06805%40googlegroups.com.
>> > 
>> > -- 
>> > You received this messag

Re: [weewx-user] Potential memory issue

[Thomas Keffer]

While the tools work well in smaller projects where you can identify and
track every object, in a larger, real-time, project like weewx, there is
just too much going on to make sense of the huge memory trees the tools
produce.

They also suffer from a Heisenberg uncertainty principle: the very act of
measuring consumes memory, which you then chase, looking for your leak.

So, I have taken to a patient, binary approach. I shut down half the
program, say the reporting engine, and see if that makes a difference. If
not, I shut down the other half. Keep dividing by half and eventually
you'll locate the problem. With most leaks, you can only do one iteration
every day or two, so it can take weeks to isolate the problem. With a large
leak, like yours, it can be done in a matter of hours.

Patience is the only thing I've found that works well!

One thing worth noting: Python uses garbage collection, so it doesn't
actually "leak" memory. It may struggle to reclaim memory that has cyclic
references, taking a long time to reclaim it, but eventually it will
(except if a __del__ method is defined and when using a Python version
before 3.4. Weewx never defines __del__, so it is not subject to this
limitation.).

Most of the time the problem is in an underlying "C" routine, specifically
drivers, occasionally graphic utilities.

-tk

On Sun, Aug 11, 2019 at 3:51 PM Leon Shaner  wrote:

> Hey, TK,
>
> Can you please toss me a bone on how to instrument weewx for memory
> profiling?
> I tried python3-memory-profiler but couldn't make it work.  It seems to
> block the normal importing of needed python modules (like weewx.engine).
> Maybe it is because weewx uses precompiled modules?
>
> Other than that I found a thread in the weewx google group where you
> suggested pympler, but I can't seem to find that on Raspbian, and you had a
> specially modified engine.py anyway.  :-/
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Aug 11, 2019, at 4:06 PM, Leon Shaner  wrote:
>
> Hey, TK.  WMR300.  I'll see if I can track it down.
>
> Regards,
> \Leon
> --
> Leon Shaner :: Dearborn, Michigan (iPad)
>
> On Aug 11, 2019, at 12:45 PM, Thomas Keffer  wrote:
>
> 
> If memory increases every couple of seconds, which suggests that the leak
> is in the part of device driver that deals with LOOP packets. But, you're
> on an WMR300, right? As I recall, their LOOP packets are more like 10-20
> seconds apart --- too long to correlate with what you're seeing. Or, are
> you on something like a Vantage with a shorter LOOP packet interval?
>
> I've noticed memory leaks in other instances, such as my own site
> http://www.threefools.org/weewx. In my case, I spent a couple of weeks
> trying to chase it down, and concluded the problem was somewhere in the
> sqlite database driver, but couldn't put my finger on it conclusively.
>
> Then, magically, Debian did an update and the problem (nearly) went away.
> Memory leak dropped from 5 MB/day, to almost nothing (maybe a megabyte or
> two over a week). Again, it suggests the problem was (is) in a device
> driver somewhere.
>
> -tk
>
> On Sun, Aug 11, 2019 at 8:55 AM Leon Shaner  wrote:
>
>> TK, you may want to know...
>> There definitely is a memory leak in weewxd.
>> It grows by 1 KiB about every 2 seconds.
>>
>> I haven't yet correlated whether weewxd can grow to a point where other
>> things start dying, and whether that has any impact on the USB stack.
>>
>> What tipped me off was I just got a warning from sar/sa1 stating it
>> couldn't do it's job due to "resource unavailable," so I went and had a
>> peek.
>>
>> This RPI is a Zero W(H), so it has only 1 GB of RAM.
>> It's full enough on memory that it's using some swap.
>>
>> Here is just one snapshot.  That RES (RZ) value for weewxd goes up by one
>> digit every 2 seconds.
>> I gleaned that is 1 KiB, but I am not 100% certain. It might only be 1
>> byte every 2 seconds -- whatever the actual unit it goes up by one every 2
>> seconds.  I've never seen it come down.
>>
>> I may enhance my watchdog to check the weewxd memory size and restart it
>> after a limit, then see if that has any positive impact on avoiding the USB
>> stack going south.  Yeah, I guess I'll work on that this week.   I'll put
>> some logging in so anyone who wants to keep an eye on it can know whether
>> their setup is memory leaking also.  =D
>>
>> I have the WMR300 driver, in case the leak could be specific to that
>> driver.  :-/
>>
>> --
>> 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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/D7820F76-CC3A-4CC2-B359-4AF967A32638%40isylum.org
>> .
>>
>>
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>>
>> > On Aug 10, 2019, at 9:01 AM, Leon Shaner  wrote:
>> >
>> > 

Re: [weewx-user] Potential memory issue

[Leon Shaner]

TK,
If it helps, I don't use any reporting stuff.
I'm strictly using WMR300 with rapid fire and archive simultaneously.
No other features.

Unfortunately, I've restarted weewxd several times today making the attempt to 
debug it, so I can't share the latest memory usage snapshot.  But as a data 
point my watchdog has to reboot the pi roughly every 3 days.  So now that I've 
restarted weewx I'll see if it goes 6 days instead of the usual 3.

Regards,
\Leon
--
Leon Shaner :: Dearborn, Michigan (iPad)

> On Aug 11, 2019, at 7:22 PM, Thomas Keffer  wrote:
> 
> 
> While the tools work well in smaller projects where you can identify and 
> track every object, in a larger, real-time, project like weewx, there is just 
> too much going on to make sense of the huge memory trees the tools produce.
> 
> They also suffer from a Heisenberg uncertainty principle: the very act of 
> measuring consumes memory, which you then chase, looking for your leak.
> 
> So, I have taken to a patient, binary approach. I shut down half the program, 
> say the reporting engine, and see if that makes a difference. If not, I shut 
> down the other half. Keep dividing by half and eventually you'll locate the 
> problem. With most leaks, you can only do one iteration every day or two, so 
> it can take weeks to isolate the problem. With a large leak, like yours, it 
> can be done in a matter of hours.
> 
> Patience is the only thing I've found that works well!
> 
> One thing worth noting: Python uses garbage collection, so it doesn't 
> actually "leak" memory. It may struggle to reclaim memory that has cyclic 
> references, taking a long time to reclaim it, but eventually it will (except 
> if a __del__ method is defined and when using a Python version before 3.4. 
> Weewx never defines __del__, so it is not subject to this limitation.). 
> 
> Most of the time the problem is in an underlying "C" routine, specifically 
> drivers, occasionally graphic utilities.
> 
> -tk
> 
>> On Sun, Aug 11, 2019 at 3:51 PM Leon Shaner  wrote:
>> Hey, TK,
>> 
>> Can you please toss me a bone on how to instrument weewx for memory 
>> profiling?
>> I tried python3-memory-profiler but couldn't make it work.  It seems to 
>> block the normal importing of needed python modules (like weewx.engine).  
>> Maybe it is because weewx uses precompiled modules?
>> 
>> Other than that I found a thread in the weewx google group where you 
>> suggested pympler, but I can't seem to find that on Raspbian, and you had a 
>> specially modified engine.py anyway.  :-/
>> 
>> Regards,
>> \Leon
>> --
>> Leon Shaner :: Dearborn, Michigan (iPad)
>> 
 On Aug 11, 2019, at 4:06 PM, Leon Shaner  wrote:
 
>>> Hey, TK.  WMR300.  I'll see if I can track it down.
>>> 
>>> Regards,
>>> \Leon
>>> --
>>> Leon Shaner :: Dearborn, Michigan (iPad)
>>> 
> On Aug 11, 2019, at 12:45 PM, Thomas Keffer  wrote:
> 
 
 If memory increases every couple of seconds, which suggests that the leak 
 is in the part of device driver that deals with LOOP packets. But, you're 
 on an WMR300, right? As I recall, their LOOP packets are more like 10-20 
 seconds apart --- too long to correlate with what you're seeing. Or, are 
 you on something like a Vantage with a shorter LOOP packet interval?
 
 I've noticed memory leaks in other instances, such as my own site 
 http://www.threefools.org/weewx. In my case, I spent a couple of weeks 
 trying to chase it down, and concluded the problem was somewhere in the 
 sqlite database driver, but couldn't put my finger on it conclusively.
 
 Then, magically, Debian did an update and the problem (nearly) went away. 
 Memory leak dropped from 5 MB/day, to almost nothing (maybe a megabyte or 
 two over a week). Again, it suggests the problem was (is) in a device 
 driver somewhere.
 
 -tk
 
> On Sun, Aug 11, 2019 at 8:55 AM Leon Shaner  wrote:
> TK, you may want to know...
> There definitely is a memory leak in weewxd.
> It grows by 1 KiB about every 2 seconds.
> 
> I haven't yet correlated whether weewxd can grow to a point where other 
> things start dying, and whether that has any impact on the USB stack.
> 
> What tipped me off was I just got a warning from sar/sa1 stating it 
> couldn't do it's job due to "resource unavailable," so I went and had a 
> peek.
> 
> This RPI is a Zero W(H), so it has only 1 GB of RAM.
> It's full enough on memory that it's using some swap.
> 
> Here is just one snapshot.  That RES (RZ) value for weewxd goes up by one 
> digit every 2 seconds.
> I gleaned that is 1 KiB, but I am not 100% certain. It might only be 1 
> byte every 2 seconds -- whatever the actual unit it goes up by one every 
> 2 seconds.  I've never seen it come down.
> 
> I may enhance my watchdog to check the weewxd memory size and restart it 
> after a limit, then see if that has any positive i

[weewx-user] Wind vector direction pointer

[Greg from Oz]

Hi,

*I have looked at several other 3.9.2 sites and their arrows are pointing 
to the RIGHT as well!*


I think something must have changed in the newer version.


Does anyone know where the directional pointer in the wind vector graph 
gets its orientation from?

I am using weewx 3.9.2 and I have looked at other 3.9.2 sites and the wind 
vector pointer is pointing RIGHT and says N 

Here is my graph.

[image: Screenshot from 2019-08-12 16-15-27.png]

Notice the N in the bottom left hand corner.


Below is from another site (they are on version 3.9.1)

[image: Screenshot from 2019-08-12 16-18-11.png]

Their direction pointer is pointing upward.




-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9b3b29c1-70e0-4630-a851-b4acc4f688f3%40googlegroups.com.

Re: [weewx-user] Wind vector direction pointer

[Graham Eddy]

vector_rotate (degrees) sets the arrow orientation for progressive vector plots 
(in “Customization Guide”)

Graham Eddy

> On 12 Aug 2019, at 4:32 pm, Greg from Oz  wrote:
> 
> Does anyone know where the directional pointer in the wind vector graph gets 
> its orientation from?
> 
> I am using weewx 3.9.2 and I have looked at other 3.9.2 sites and the wind 
> vector pointer is pointing RIGHT and says N

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9C26A040-663E-40CA-902A-90B42AEA69E8%40gmail.com.

Re: [weewx-user] Wind vector direction pointer

[Greg from Oz]

Thanks
I wonder why I changed in 3.9.2?


On Monday, 12 August 2019 16:42:50 UTC+10, Graham Eddy wrote:
>
> vector_rotate (degrees) sets the arrow orientation for progressive vector 
> plots (in “Customization Guide”)
> 
> *Graham Eddy*
>
> On 12 Aug 2019, at 4:32 pm, Greg from Oz > 
> wrote:
>
> Does anyone know where the directional pointer in the wind vector graph 
> gets its orientation from?
>
> I am using weewx 3.9.2 and I have looked at other 3.9.2 sites and the wind 
> vector pointer is pointing RIGHT and says N
>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cf212843-6386-4718-83b2-b4497a39c857%40googlegroups.com.

[weewx-user] How to pronounce "WeeWX"

[Michi Kaa]

I've searched the docs, the forum, the web.

How is "WeeWX" pronounced?

Or maybe first: Is "WeeWX" pronounced? Or do you simply say "double u e e 
double u ex?" or "double u double e double u ex?" Is it an abbreviation? An 
akronym?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/85a5c5e8-c207-401a-8803-047d5bf6c2ab%40googlegroups.com.

Re: [weewx-user] How to pronounce "WeeWX"

[dunbrokin]

I pronounce it WeeWix!

On Mon, Aug 12, 2019 at 6:49 PM Michi Kaa  wrote:

> I've searched the docs, the forum, the web.
>
> How is "WeeWX" pronounced?
>
> Or maybe first: Is "WeeWX" pronounced? Or do you simply say "double u e e
> double u ex?" or "double u double e double u ex?" Is it an abbreviation? An
> akronym?
>
> --
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/85a5c5e8-c207-401a-8803-047d5bf6c2ab%40googlegroups.com
> 
> .
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAF1oafemLrSSAX2ftKqgiaa3Q7a6v3__SOMGUS9QLhifoA83yQ%40mail.gmail.com.

[weewx-user] Re: Installing WeatherCloud Extension - Error

[K Weaver]

Im still getting this error and I added the 0.11


On Monday, April 1, 2019 at 4:29:25 AM UTC-4, Dave McCreath wrote:
>
> Getting a tad fed up with Wunderground and trying to move over to 
> WeatherCloud.
>
> I have weeWX installed and running and updated on a Raspberry Pi currently 
> uploading to Wunderground, no issues.
>
> I followed the instructions on the WeatherCloud site to install alongside 
> weeWX (here ) but after trying to 
> install the file on my RPi I get the following error:
>
> pi@weewx:~ $ wee_extension --install weewx-wcloud-x.y.tgz
> Request to install 'weewx-wcloud-x.y.tgz'
> Traceback (most recent call last):
>   File "/usr/bin/wee_extension", line 83, in 
> main()
>   File "/usr/bin/wee_extension", line 75, in main
> ext.install_extension(options.install)
>   File "/usr/share/weewx/weecfg/extension.py", line 124, in 
> install_extension
> raise InstallError("Extension '%s' not found." % extension_path)
> weecfg.extension.InstallError: Extension 'weewx-wcloud-x.y.tgz' not found.
>
> Anyone got an idea of how to overcome the installation error, I am no 
> expert on 'things' LINUX?
>
> Dave
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4287a1b8-c0d0-4fe9-8fab-74cd24e4cd29%40googlegroups.com.

Re: [weewx-user] How to pronounce "WeeWX"

[Michi Kaa]

Am Montag, 12. August 2019 08:51:54 UTC+2 schrieb monmul:
>
> I pronounce it WeeWix!
>
>
Where I come from this would most likely be understood as "we masturbate". 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/858b3d7b-ba00-44a8-a5d8-034c4d9b8f51%40googlegroups.com.