Re: [weewx-user] segfault after move from Raspberry Pi to CentOS VM

[gjr80]

Oh, and your old data if you have any.

Gary

On Saturday, 28 April 2018 11:11:20 UTC+10, gjr80 wrote:
>
> If it were me I would do a fresh install (as you have) and then copy over 
> any 'skins' directories you have modified, reinstall any extensions/add-ons 
> and maybe do a final diff on your new weewx.conf against your old 
> weewx.conf to see if there is anything you may have missed. No point 
> copying public_html, its all weeWX generated and any old files can only 
> muddy the waters if you need to troubleshoot an issue. If you have added 
> any other custom code it might also be worthwhile looking in $BIN/user to 
> see if there is anything else that was there that is not now.
>
> Gary
>
> On Friday, 27 April 2018 22:50:21 UTC+10, Cycle London wrote:
>>
>> So what do I copy over from my Raspberry Pi tarball? 
>>
>> Aside from 'skins', 'weewx.conf', 'public_html' etc ...  
>>
>

-- 
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] segfault after move from Raspberry Pi to CentOS VM

[gjr80]

If it were me I would do a fresh install (as you have) and then copy over 
any 'skins' directories you have modified, reinstall any extensions/add-ons 
and maybe do a final diff on your new weewx.conf against your old 
weewx.conf to see if there is anything you may have missed. No point 
copying public_html, its all weeWX generated and any old files can only 
muddy the waters if you need to troubleshoot an issue. If you have added 
any other custom code it might also be worthwhile looking in $BIN/user to 
see if there is anything else that was there that is not now.

Gary

On Friday, 27 April 2018 22:50:21 UTC+10, Cycle London wrote:
>
> So what do I copy over from my Raspberry Pi tarball? 
>
> Aside from 'skins', 'weewx.conf', 'public_html' etc ...  
>

-- 
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] WMR200: rain is always zero

[Patrick J]

Hi,

I connected a RaspBerry PI to my WMR200 weather station. I am using the 
latest version of weewx, with version 3.3.4 of driver for WMR200.

I let the system run for a couple of weeks, and noticed that the field rain 
in the archive table is always at 0 or null, even though we had a lot of 
rain. But the field rainRate has different values. As per the user guide, I 
ran weewx directly to see the packets that come out of the station, and 
here is the outcome:

pi@raspberrypi:/usr/share/weewx $ sudo weewxd /etc/weewx/weewx.conf
REC:2018-04-27 16:10:54 UTC (1524845454) altimeter: 29.5299875, 
appTemp: 63.3209288277, barometer: 29.5608564278, cloudbase: 7892.47484776, 
dateTime: 1524845454.0, dewpoint: 36.7002569534, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.54, inDewpoint: 46.1216028652, 
inHeatindex: None, inHumidity: 43, inTemp: 69.62, interval: 1, maxSolarRad: 
None, outHumidity: 31, outTemp: 68.54, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 292.5, windGust: 5.59235462985, windrun: 
33.7987000882, windSpeed: 4.25018951868
REC:2018-04-27 16:11:54 UTC (1524845514) altimeter: 29.5299875, 
appTemp: 63.7582794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845514.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 
1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, windchill: 
None, windDir: 202.5, windGust: 4.25018951868, windrun: 33.8695365802, 
windSpeed: 3.35541277791
REC:2018-04-27 16:12:54 UTC (1524845574) altimeter: 29.5299875, 
appTemp: 63.0022794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845574.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 157.5, windGust: None, windGustDir: None, 
windrun: 33.9254601265, windSpeed: 4.69757788907
REC:2018-04-27 16:13:54 UTC (1524845634) altimeter: 29.5299875, 
appTemp: 63.2542794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845634.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 5.81604881504, windrun: 
34.0037530913, windSpeed: 4.25018951868
REC:2018-04-27 16:14:54 UTC (1524845694) altimeter: 29.5299875, 
appTemp: 62.4982794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845694.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: None, windGustDir: None, 
windrun: 34.0745895833, windSpeed: 5.59235462985
REC:2018-04-27 16:15:54 UTC (1524845754) altimeter: 29.5299875, 
appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845754.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 
34.1677954938, windSpeed: 5.36866044465
REC:2018-04-27 16:16:54 UTC (1524845814) altimeter: 29.5299875, 
appTemp: 62.6242794974, barometer: 29.5610911259, cloudbase: 7704.13634321, 
dateTime: 1524845814.0, dewpoint: 37.3489463735, ET: None, forecastIcon: 1, 
heatindex: None, hourRain: 0.0, humidex: 68.36, inDewpoint: 46.2838848687, 
inHeatindex: None, inHumidity: 43, inTemp: 69.8, interval: 1, maxSolarRad: 
None, outHumidity: 32, outTemp: 68.36, pressure: 28.880327775, rain: 0.0, 
rain24: 1.57, rainRate: 0.0, rainTotal: 1144.4224, usUnits: 1, UV: 255, 
windchill: None, windDir: 202.5, windGust: 6.7108282, windrun: 
34.2572731679, windSpeed: 5.36866044465
REC:2018-04-27 

[weewx-user] Re: raspberry pi 3 and weewx fail at first hurdle

[Andrew Milner]

a silly question - how do you know it is actually running?? how did you 
start it??

there should be at least weewx startup log messages

are you sure the messages are not being diverted to weewx.log??

what command did you use to view the log??



On Friday, 27 April 2018 18:47:36 UTC+3, Stuart Smith wrote:

> On Friday, 27 April 2018 17:19:42 UTC+2, vince  wrote: 
> > On Friday, April 27, 2018 at 8:15:55 AM UTC-7, Stuart Smith wrote: 
> > bought a raspberry pi 3, came with noobs on the sd card, installed 
> raspbian from here. 
> > followed the instructions on installing weewx at 
> www.weewx.com/docs/debian.htm 
> > configured apt, no problem 
> > installed weewx, no problem 
> > step 3 is to check the syslog for message from weewx, there are none 
> whatsoever...the only activity in the log is pasted below. 
> > can anyone pleeaase help? I've looked through the wiki and searched 
> this group but found nothing of help, feel like a complete idiot! 
> > P.S. cannot edit the weewx.conf either, I can open it, tweek it but 
> cannot save it, tells me it cannot open the file to overwrite it. 
> > 
> > 
> > 
> > 
> > 
> > 
> > You're on a pi, so you are likely running as user 'pi' which has no 
> permissions to write to root-owned files. 
> > Try using "sudo" ala "sudo your_command_here" 
> > 
> > 
> > If you're a new Linux user completely, definitely get yourself some 
> online Linux training for the basics. 
> >   
>
> Yup, been using the sudo command...but why is weewx not reporting? Surely 
> my root permission has no bearing on this? 
>
> P.s. thanks for the reply

-- 
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: raspberry pi 3 and weewx fail at first hurdle

['Stuart Smith' via weewx-user]

On Friday, 27 April 2018 17:19:42 UTC+2, vince  wrote:
> On Friday, April 27, 2018 at 8:15:55 AM UTC-7, Stuart Smith wrote:
> bought a raspberry pi 3, came with noobs on the sd card, installed raspbian 
> from here.
> followed the instructions on installing weewx at www.weewx.com/docs/debian.htm
> configured apt, no problem
> installed weewx, no problem
> step 3 is to check the syslog for message from weewx, there are none 
> whatsoever...the only activity in the log is pasted below.
> can anyone pleeaase help? I've looked through the wiki and searched this 
> group but found nothing of help, feel like a complete idiot!
> P.S. cannot edit the weewx.conf either, I can open it, tweek it but cannot 
> save it, tells me it cannot open the file to overwrite it.
> 
> 
> 
> 
> 
> 
> You're on a pi, so you are likely running as user 'pi' which has no 
> permissions to write to root-owned files.
> Try using "sudo" ala "sudo your_command_here"
> 
> 
> If you're a new Linux user completely, definitely get yourself some online 
> Linux training for the basics.
>  

Yup, been using the sudo command...but why is weewx not reporting? Surely my 
root permission has no bearing on this?

P.s. thanks for the reply

-- 
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: raspberry pi 3 and weewx fail at first hurdle

[vince]

On Friday, April 27, 2018 at 8:15:55 AM UTC-7, Stuart Smith wrote:
>
> bought a raspberry pi 3, came with noobs on the sd card, installed 
> raspbian from here.
>
> followed the instructions on installing weewx at 
> www.weewx.com/docs/debian.htm
>
> configured apt, no problem
>
> installed weewx, no problem
>
> step 3 is to check the syslog for message from weewx, there are none 
> whatsoever...the only activity in the log is pasted below.
>
> can anyone pleeaase help? I've looked through the wiki and searched 
> this group but found nothing of help, feel like a complete idiot!
>
> P.S. cannot edit the weewx.conf either, I can open it, tweek it but cannot 
> save it, tells me it cannot open the file to overwrite it.
>
>
>

You're on a pi, so you are likely running as user 'pi' which has no 
permissions to write to root-owned files.
Try using "sudo" ala "sudo your_command_here"

If you're a new Linux user completely, definitely get yourself some online 
Linux training for the basics.
 

-- 
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] raspberry pi 3 and weewx fail at first hurdle

['Stuart Smith' via weewx-user]

Hi all,

bought a raspberry pi 3, came with noobs on the sd card, installed raspbian 
from here.

followed the instructions on installing weewx at www.weewx.com/docs/debian.htm

configured apt, no problem

installed weewx, no problem

step 3 is to check the syslog for message from weewx, there are none 
whatsoever...the only activity in the log is pasted below.

can anyone pleeaase help? I've looked through the wiki and searched this 
group but found nothing of help, feel like a complete idiot!

P.S. cannot edit the weewx.conf either, I can open it, tweek it but cannot save 
it, tells me it cannot open the file to overwrite it.

Apr 27 17:14:27 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease
Apr 27 17:14:34 raspberrypi dhcpcd[353]: wlan0: Router Advertisement from 
fe80::52c7:bfff:fe2e:2e86
Apr 27 17:14:34 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease
Apr 27 17:14:41 raspberrypi dhcpcd[353]: wlan0: Router Advertisement from 
fe80::52c7:bfff:fe2e:2e86
Apr 27 17:14:41 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease
Apr 27 17:14:49 raspberrypi dhcpcd[353]: wlan0: Router Advertisement from 
fe80::52c7:bfff:fe2e:2e86
Apr 27 17:14:49 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease
Apr 27 17:14:56 raspberrypi dhcpcd[353]: wlan0: Router Advertisement from 
fe80::52c7:bfff:fe2e:2e86
Apr 27 17:14:56 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease
Apr 27 17:15:00 raspberrypi dhcpcd[353]: wlan0: Router Advertisement from 
fe80::52c7:bfff:fe2e:2e86
Apr 27 17:15:00 raspberrypi dhcpcd[353]: wlan0: soliciting a DHCPv6 lease

-- 
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]

Hey Martin,
Thank you for your interest!  I don't know if I mentioned it here, but even
cooler than that IMHO, the color scale on all the charts is dynamic, and
will adjust as the range does. The font colors also change dynamically for
better visibility.

For the record, I am not a python programmer by any means, everything I
know is self inflicted, and I am nearly positive that there is a better way
to do everything that I have done here, which is why I haven't submitted
these changes to GitHub for peer analysis, and integration.  Working with
someone else's code and modifying it to work for your needs is difficult,
and not always effective.  When I have time in the next few days, I will
try to pull the code off my machine and post it, with some basic direction,
but the support that I provide will be limited.  If anyone from FuzzyArcher
sees this, I would be happy to submit it to GitHub.  I would hesitate to
say that this is a 'finished' product, but it works for my needs.  Thoughts
and recommendations are welcome!

On Fri, Apr 27, 2018 at 7:25 AM RothMa  wrote:

> Hello Thomas,
> I want to create my own skin for Weewx. My search on how to display
> historical data on the websites led me to
> https://github.com/brewster76/fuzzy-archer and
> https://github.com/weatherstorm/Sofaskin-CW9009. I also found this thread. 
> Thanks
> for the detailed explanations.
> Now I took some code from both Github projects and was able to integrate
> the historical tables in my site using the "historygenerator.py". I'm
> able to change HTML and CSS configurations, but I'm not good at programming
> Python.
> On your wonderful page you have a monthly summary on the right side of the
> tables and an annual overview below each table. Can you please show me
> how you've extended the historygenerator.py to create the Monthly Summary
> column and the Annual Summary row?
>
> thank you very much
> Best regards
> Martin
>
> --
> 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/FHuFLPrg_DE/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.
>


-- 
Thomas Carlin
970-401-3805

-- 
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

[RothMa]

Hello Thomas, 
I want to create my own skin for Weewx. My search on how to display 
historical data on the websites led me to 
https://github.com/brewster76/fuzzy-archer and 
https://github.com/weatherstorm/Sofaskin-CW9009. I also found this thread. 
Thanks 
for the detailed explanations.
Now I took some code from both Github projects and was able to integrate 
the historical tables in my site using the "historygenerator.py". I'm able 
to change HTML and CSS configurations, but I'm not good at programming 
Python.
On your wonderful page you have a monthly summary on the right side of the 
tables and an annual overview below each table. Can you please show me how 
you've extended the historygenerator.py to create the Monthly Summary 
column and the Annual Summary row?

thank you very much
Best regards
Martin

-- 
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] segfault after move from Raspberry Pi to CentOS VM

[Cycle London]

So what do I copy over from my Raspberry Pi tarball? 

Aside from 'skins', 'weewx.conf', 'public_html' etc ...  

-- 
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] segfault after move from Raspberry Pi to CentOS VM

[Cycle London]

On Friday, 27 April 2018 12:21:46 UTC+1, Tom Keffer wrote:

Two things:
>
>1. While WeeWX is "pure Python," if you're going to do a simple copy 
>between machines, it's probably a good idea not to copy the .pyc files. 
>These contain compiled Python, and are highly machine dependent.
>2. The process ID for the segfault (13853) is different from the 
>process ID of all the other log entries (13946) after the initial startup. 
>Are you sure you don't have a second copy of weewx running?
>
>
>>
Hi Tom. 

In answer to your second question, there's definitely no other process 
running.  

[root@db2 /home/weewx]# ps -ef | grep weewx
root 14000  2067  0 13:21 pts/000:00:00 grep weewx


So to answer the first question, I completely removed /home/weewx, grabbed 
another copy of the tarball from the weewx download site, and made a clean 
install (I left the service files in /etc/init.d as I'm guessing that 
they're not the problem..?).  

Now, when I try to start ... 

Apr 27 13:20:33 db2 weewx[13970]: restx: Wunderground: Posting not enabled.
Apr 27 13:20:33 db2 weewx[13970]: restx: PWSweather: Posting not enabled.
Apr 27 13:20:33 db2 weewx[13970]: restx: CWOP: Posting not enabled.
Apr 27 13:20:33 db2 weewx[13970]: restx: WOW: Posting not enabled.
Apr 27 13:20:33 db2 weewx[13970]: restx: AWEKAS: Posting not enabled.
Apr 27 13:20:33 db2 weewx[13970]: engine: Starting up weewx version 3.8.0
Apr 27 13:20:33 db2 weewx[13970]: wmr300: reading records since *** N/A 
*** (N/A   )
Apr 27 13:20:33 db2 weewx[13970]: wmr300: usb failure: [Errno 110] Operation 
timed out
Apr 27 13:20:33 db2 weewx[13970]: engine: Caught WeeWxIOError: [Errno 110] 
Operation timed out
Apr 27 13:20:33 db2 weewx[13970]:   Waiting 60 seconds then retrying
...


That there should be no data is to be expected, as it's a fresh install, 
but the usb failure error is (IIRC) leads me to believe that there's a 
driver issue. 

So what do I copy over from my Raspberry Pi tarball? 

I need : 

1.  a working driver
2.  the 'forecast' module
3.  all my data from January 1st.

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

[weewx-user] Re: Android weather app for weeWx users

[John Smith]

On Friday, 27 April 2018 19:41:34 UTC+10, Greg from Oz wrote:
>
> Looks good.
> I entered in my URL and set the updates to manual and it told me my URL 
> was wrong.
> I changed the updates to every 5 minutes and then it worked!
>

I'm not able to reproduce this, do you know specifically which URL it 
reported as bad?
 

> I have put it back to manual but how do you manually refresh?
>

You long press on what you want to update, I'll add this to the wiki

-- 
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] segfault after move from Raspberry Pi to CentOS VM

[Thomas Keffer]

Two things:

   1. While WeeWX is "pure Python," if you're going to do a simple copy
   between machines, it's probably a good idea not to copy the .pyc files.
   These contain compiled Python, and are highly machine dependent.
   2. The process ID for the segfault (13853) is different from the process
   ID of all the other log entries (13946) after the initial startup. Are you
   sure you don't have a second copy of weewx running?

 -tk

On Fri, Apr 27, 2018 at 3:36 AM, Cycle London 
wrote:

> Hi again,
> I was having massive problems with the Raspberry Pi behind my WMR300.
>  Every day or so, I'd get up and it would have crashed, and there'd only be
> an ntp error in the logs.  I tried disabling ntp completely and setting the
> time manually, but all that happened is that when the system came back up
> after a crash, it was like ten hours out.
>
> OK, enough.
>
> I have a CentOS 6.9 VM sitting on my ESXi host - db2 - so named because
> it's where I do my php and httpd tinkering.   It's 'test & dev' so doesn't
> involve change management to get a change ('change managament' here being
> 'asking my wife if she minds me bringing down the servers for a minute :-)
> ).
>
> Last night, I tar up the contents of /home/weewx on the Pi and scp them
> over to db2.  I shut down the Pi.
>
> This morning, I struggle a bit to get the station recognised by the ESXi
> host, but actually plugging it into the host, sort of helped.
>
> I install weewx from source on db2, and then once I can see that the
> WMR300 is there, I fire her up.
>
> [root@db2 ~]# service weewx start
> Starting weewx:[  OK  ]
>
> In /var/log/messages on db2 ...
>
> Apr 27 11:19:17 db2 weewx[13842]: engine: Initializing weewx version 3.8.0
> Apr 27 11:19:17 db2 weewx[13842]: engine: Using Python 2.6.6 (r266:84292,
> Aug 18 2016, 15:13:37) #012[GCC 4.4.7 20120313 (Red Hat 4.4.7-17)]
> Apr 27 11:19:17 db2 weewx[13842]: engine: Platform
> Linux-2.6.32-696.16.1.el6.x86_64-x86_64-with-centos-6.9-Final
> Apr 27 11:19:17 db2 weewx[13842]: engine: Locale is 'en_US.UTF-8'
> Apr 27 11:19:17 db2 weewx[13842]: engine: pid file is /var/run/weewx.pid
> Apr 27 11:19:17 db2 weewx[13846]: engine: Using configuration file
> /home/weewx/weewx.conf
> Apr 27 11:19:17 db2 weewx[13846]: engine: Loading station type WMR300
> (weewx.drivers.wmr300)
> Apr 27 11:19:17 db2 weewx[13846]: wmr300x: driver version is
> 0.18nolegacy.05.17d
> Apr 27 11:19:17 db2 weewx[13846]: wmr300x: Set to clear history at 5%
> Apr 27 11:19:17 db2 weewx[13846]: wmr300x: using PyUSB backend: libusb1
> Apr 27 11:19:18 db2 kernel: usb 2-2.1: reset full speed USB device number
> 4 using uhci_hcd
> Apr 27 11:19:18 db2 weewx[13846]: wmr300x: send initial heartbeat, try 1
> Apr 27 11:19:18 db2 weewx[13846]: wmr300x: Initiation completed
> Apr 27 11:19:18 db2 weewx[13846]: engine: StdConvert target unit is 0x1
> Apr 27 11:19:18 db2 weewx[13846]: wxcalculate: The following values will
> be calculated: barometer=prefer_hardware, windchill=hardware,
> dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware,
> windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware,
> humidex=prefer_hardware, pressure=prefer_hardware,
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
> cloudbase=prefer_hardware
> Apr 27 11:19:18 db2 weewx[13846]: wxcalculate: The following algorithms
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Apr 27 11:19:18 db2 weewx[13846]: engine: Archive will use data binding
> wx_binding
> Apr 27 11:19:18 db2 weewx[13846]: engine: Record generation will be
> attempted in 'hardware'
> Apr 27 11:19:18 db2 weewx[13846]: engine: Using archive interval of 120
> seconds (specified in weewx configuration)
> Apr 27 11:19:18 db2 weewx[13846]: engine: Using binding 'wx_binding' to
> database 'weewx.sdb'
> Apr 27 11:19:18 db2 weewx[13846]: manager: Starting backfill of daily
> summaries
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Zambretti:
> forecast version 3.2.19
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Zambretti:
> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800
> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast
> version 3.2.19
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: location ID
> (lid) is not specified
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast
> office ID (foid) is not specified
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast will
> not be run
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: WU: forecast
> version 3.2.19
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: WU: interval=10800
> max_age=604800 api_key=XX location=51.45309,0.09846 fc=hourly10day
> Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: OWM: forecast
> version 

[weewx-user] segfault after move from Raspberry Pi to CentOS VM

[Cycle London]

Hi again,
I was having massive problems with the Raspberry Pi behind my WMR300.   
 Every day or so, I'd get up and it would have crashed, and there'd only be 
an ntp error in the logs.  I tried disabling ntp completely and setting the 
time manually, but all that happened is that when the system came back up 
after a crash, it was like ten hours out. 

OK, enough. 

I have a CentOS 6.9 VM sitting on my ESXi host - db2 - so named because 
it's where I do my php and httpd tinkering.   It's 'test & dev' so doesn't 
involve change management to get a change ('change managament' here being 
'asking my wife if she minds me bringing down the servers for a minute :-) 
).  

Last night, I tar up the contents of /home/weewx on the Pi and scp them 
over to db2.  I shut down the Pi.  

This morning, I struggle a bit to get the station recognised by the ESXi 
host, but actually plugging it into the host, sort of helped.   

I install weewx from source on db2, and then once I can see that the WMR300 
is there, I fire her up. 

[root@db2 ~]# service weewx start
Starting weewx:[  OK  ]

In /var/log/messages on db2 ... 

Apr 27 11:19:17 db2 weewx[13842]: engine: Initializing weewx version 3.8.0
Apr 27 11:19:17 db2 weewx[13842]: engine: Using Python 2.6.6 (r266:84292, 
Aug 18 2016, 15:13:37) #012[GCC 4.4.7 20120313 (Red Hat 4.4.7-17)]
Apr 27 11:19:17 db2 weewx[13842]: engine: Platform 
Linux-2.6.32-696.16.1.el6.x86_64-x86_64-with-centos-6.9-Final
Apr 27 11:19:17 db2 weewx[13842]: engine: Locale is 'en_US.UTF-8'
Apr 27 11:19:17 db2 weewx[13842]: engine: pid file is /var/run/weewx.pid
Apr 27 11:19:17 db2 weewx[13846]: engine: Using configuration file 
/home/weewx/weewx.conf
Apr 27 11:19:17 db2 weewx[13846]: engine: Loading station type WMR300 
(weewx.drivers.wmr300)
Apr 27 11:19:17 db2 weewx[13846]: wmr300x: driver version is 
0.18nolegacy.05.17d
Apr 27 11:19:17 db2 weewx[13846]: wmr300x: Set to clear history at 5%
Apr 27 11:19:17 db2 weewx[13846]: wmr300x: using PyUSB backend: libusb1
Apr 27 11:19:18 db2 kernel: usb 2-2.1: reset full speed USB device number 4 
using uhci_hcd
Apr 27 11:19:18 db2 weewx[13846]: wmr300x: send initial heartbeat, try 1
Apr 27 11:19:18 db2 weewx[13846]: wmr300x: Initiation completed
Apr 27 11:19:18 db2 weewx[13846]: engine: StdConvert target unit is 0x1
Apr 27 11:19:18 db2 weewx[13846]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=hardware, 
dewpoint=hardware, appTemp=prefer_hardware, rainRate=hardware, 
windrun=prefer_hardware, heatindex=hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Apr 27 11:19:18 db2 weewx[13846]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 27 11:19:18 db2 weewx[13846]: engine: Archive will use data binding 
wx_binding
Apr 27 11:19:18 db2 weewx[13846]: engine: Record generation will be 
attempted in 'hardware'
Apr 27 11:19:18 db2 weewx[13846]: engine: Using archive interval of 120 
seconds (specified in weewx configuration)
Apr 27 11:19:18 db2 weewx[13846]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Apr 27 11:19:18 db2 weewx[13846]: manager: Starting backfill of daily 
summaries
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Zambretti: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Zambretti: 
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: location ID 
(lid) is not specified
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast 
office ID (foid) is not specified
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: NWS: forecast will 
not be run
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: WU: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: WU: interval=10800 
max_age=604800 api_key=XX location=51.45309,0.09846 fc=hourly10day
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: OWM: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: OWM: API key 
(api_key) is not specified
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: OWM: forecast will 
not be run
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: UKMO: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: UKMO: 
interval=10800 max_age=604800 api_key=XX location=XX
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Aeris: forecast 
version 3.2.19
Apr 27 11:19:19 db2 weewx[13846]: forecast: MainThread: Aeris: client 
identifier (client_id) is not specified
Apr 27 11:19:19 db2 weewx[13846]: 

[weewx-user] Re: Android weather app for weeWx users

[Greg from Oz]

Looks good.
I entered in my URL and set the updates to manual and it told me my URL was 
wrong.
I changed the updates to every 5 minutes and then it worked!
I have put it back to manual but how do you manually refresh?

Thanks


On Tuesday, 10 April 2018 19:01:46 UTC+10, John Smith wrote:
>
> Just to give some background I made an android app similar to Pocket PWS. 
> I liked the app, but it was closed source so I couldn't do anything to add 
> new features.
>
> With Tom's blessing I named the app weeWx Weather App and I have published 
> it to google play 
> https://play.google.com/store/apps/details?id=com.odiousapps.weewxweather
>
> To use the app there needs to be some small changes made to weeWx, to 
> automate some of the steps needed I created a pair of weeWx extensions, one 
> for metric and one for imperial units.
>
> I've outlined the installation steps on github: 
> https://github.com/evilbunny2008/weeWxWeatherApp/wiki#concise-instructions
>
> All comments and requests about the app should go to github 
> https://github.com/evilbunny2008/weeWxWeatherApp/issues
>

-- 
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.