Re: [weewx-user] weewx-Weather34 installation questions

[vince]

On Monday, September 7, 2020 at 6:48:41 PM UTC-7, ExprmntAl wrote:
>
> I didn't see this installation mentioned anywhere in the weewx-Weather34 
> installation instructions "
> https://github.com/steepleian/weewx-Weather34/blob/master/INSTALLATION_GUIDE.md;,
>  
> and I have had weewx running for over a month with no issues so I'm not 
> sure how I would know about this.  
>
> Are the instructions on how to install this (configobj) available 
> somewhere else?  I'm very grateful to Ian for helping me work through this 
> installation step by step and it looks like I am getting closer to the end 
> so I'm appreciative to anyone who is willing to help.
>
>
>
I was referring to the weewx installation procedure - pick your method at 
http://weewx.com/docs/usersguide.htm#installing depending on how you 
installed it.I have no idea what is (or is not) in Ian's guide for his 
specific software.

-- 
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/8417958a-1509-4502-aa64-56b46989b894o%40googlegroups.com.

Re: [weewx-user] weewx-Weather34 installation questions

[ExprmntAl]

I didn't see this installation mentioned anywhere in the weewx-Weather34 
installation instructions "
https://github.com/steepleian/weewx-Weather34/blob/master/INSTALLATION_GUIDE.md;,
 
and I have had weewx running for over a month with no issues so I'm not 
sure how I would know about this.  

Are the instructions on how to install this (configobj) available somewhere 
else?  I'm very grateful to Ian for helping me work through this 
installation step by step and it looks like I am getting closer to the end 
so I'm appreciative to anyone who is willing to help.

Cheers,

Allan

On Monday, September 7, 2020 at 5:18:50 PM UTC-5 vince wrote:

> On Monday, September 7, 2020 at 3:12:44 PM UTC-7, ExprmntAl wrote:
>>
>> *ImportError: No module named configobj*
>>
>> Any ideas on why this error is happening?
>>
>>
>>
> Yes, you did not install the configobj module per the weewx prerequisites.
>  
>

-- 
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/42155839-793e-4ba0-aeb3-a71f3e4242b1n%40googlegroups.com.

Re: [weewx-user] WS23xx error when trying to set interval

[Tom Keffer]

Let's try that again. How about this version?



On Sun, Sep 6, 2020 at 11:00 AM Devonian  wrote:

> humpf - I don't like this new fangle google group on-line...
>
> Should be
>
> root@raspberrypi:/home/weewx/bin# ./wee_device --set-interval=5
> Using configuration file /home/weewx/weewx.conf
> Using WS23xx driver version 0.41 (weewx.drivers.ws23xx)
> Changing the interval will clear the station memory.
> Interval is 60
> Set interval to 5 minutes (y/n)? y
> Traceback (most recent call last):
>   File "./wee_device", line 78, in 
> main()
>   File "./wee_device", line 74, in main
> device.configure(config_dict)
>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
> self.do_options(options, parser, config_dict, not options.noprompt)
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 316, in do_options
> self.set_interval(options.interval, prompt)
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 378, in set_interval
> self.station.setArchiveInterval(interval)
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 540, in
> setArchiveInterval
> self.station.set_archive_interval(interval)
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 686, in
> set_archive_interval
> self.ws.write_safe(m.address, *cmd[1:])
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1115, in write_safe
> command_data = self.write_data(nybble_address,nybbles,encode_constant)
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1099, in write_data
> self.write_byte(encoded_data[i])
>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1012, in write_byte
> self.log("%02x" % six.byte2int(data))
> TypeError: 'int' object is not subscriptable
>
>
> Nigel
>
> On Sunday, 6 September 2020 at 18:58:20 UTC+1 Devonian wrote:
>
>> ooops, ignore the first couple of lines above, copy/paste error
>>
>> Nigel
>>
>> On Sunday, 6 September 2020 at 18:56:22 UTC+1 Devonian wrote:
>>
>>> Hi Tom,
>>>
>>> Thanks, but...
>>>
>>> root@raspberrypi:/home/weewx/bin# ./wee_device --set-interval=5
>>> Using configuration file /home/weewx/weewx.conf
>>> Using WS23xx driver version 0.41 (weewx.drivers.ws23xx)
>>> Changing the interval will clear the station memory.
>>> Interval is 60
>>> Set interval to 5 minutes (y/n)? y
>>> Traceback (most recent call last):
>>>   File "./wee_device", line 78, in 
>>> main()
>>>   File "./wee_device", line 74, in main
>>> device.configure(config_dict)
>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 316, in do_options
>>> self.set_interval(options.interval, prompt)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 378, in
>>> set_interval
>>> self.station.setArchiveInterval(interval)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 540, in
>>> setArchiveInterval
>>> self.station.set_archive_interval(interval)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 686, in
>>> set_archive_interval
>>> self.ws.write_safe(m.address, *cmd[1:])
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1115, in
>>> write_safe
>>> command_data =
>>> self.write_data(nybble_address,nybbles,encode_constant)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1099, in
>>> write_data
>>> self.write_byte(encoded_data[i])
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 1012, in
>>> write_byte
>>> self.log("%02x" % six.byte2int(data))
>>> TypeError: 'int' object is not subscriptable
>>>
>>>
>>> ---
>>>
>>> root@raspberrypi:/home/weewx/bin# ./wee_device --info
>>> Using configuration file /home/weewx/weewx.conf
>>> Using WS23xx driver version 0.41 (weewx.drivers.ws23xx)
>>> Querying the station for the configuration...
>>> Traceback (most recent call last):
>>>   File "./wee_device", line 78, in 
>>> main()
>>>   File "./wee_device", line 74, in main
>>> device.configure(config_dict)
>>>   File "/home/weewx/bin/weewx/drivers/__init__.py", line 67, in configure
>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 320, in do_options
>>> self.show_info()
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 326, in show_info
>>> config = self.station.getConfig()
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 548, in getConfig
>>> data = self.station.get_raw_data(list(Measure.IDS.keys()))
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 791, in
>>> get_raw_data
>>> data_dict = dict(list(zip(labels, [m.conv.binary2value(d) for m, d
>>> in zip(measures, raw_data)])))
>>>   File "/home/weewx/bin/weewx/drivers/ws23xx.py", line 791, in 
>>> data_dict = 

Re: [weewx-user] weewx upgrade from python2 to python3

[Tom Keffer]

There are now three, unrelated, support issues scrambled together in this
thread.

If you are having problems transitioning from Python 2 to Python 3,
please *start
a new thread!* It's getting terribly confusing untangling the responses.

On Mon, Sep 7, 2020 at 3:47 PM Tom Keffer  wrote:

> In the file emoncms.py, try changing lines 290-293 from
>
> def check_response(self, response):
> txt = response.read()
> if txt != 'ok' :
> raise weewx.restx.FailedPost("Server returned '%s'" % txt)
>
> to
>
> def check_response(self, response):
> txt = response.read().decode()
> if txt != u'ok' :
> raise weewx.restx.FailedPost("Server returned '%s'" % txt)
>
> On Mon, Sep 7, 2020 at 3:18 PM bgra...@umw.edu  wrote:
>
>> To add to this, it seems my local server is being updated correctly as
>> before even though the 3 failed attempts still appear in the log. Is it
>> possible that the software is also trying to send data to emoncms.org? I
>> only send data to my local server so could there be some code I need to
>> remove to not keep it from sending it to emoncms.org?
>>
>> On Monday, September 7, 2020 at 4:39:00 PM UTC-4 bgra...@umw.edu wrote:
>>
>>> Having another problem with the move to python3. This time it's the
>>> weewx-emoncms extension. I have installed the latest version which should
>>> run on python3, from what I understand.
>>> At bootup, I get the normal:
>>>
>>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: service
>>> version is 0.17
>>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: node is 0
>>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: Data will be
>>> uploaded with token=b634
>>>
>>> In weewx.config I have:
>>>
>>> [StdRESTful]
>>>   [[EmonCMS]]
>>>
>>> url = http://192.168.1.103/emoncms/input/post.json
>>> token = b634
>>>
>>> But I get:
>>> weewx.log:
>>> Sep  7 16:15:16 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>>> upload attempt 1: Server returned 'b'ok''
>>> Sep  7 16:15:21 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>>> upload attempt 2: Server returned 'b'ok''
>>> Sep  7 16:15:26 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>>> upload attempt 3: Server returned 'b'ok''
>>> Sep  7 16:15:26 n4mrv weewx[27417] ERROR weewx.restx: EmonCMS: Failed to
>>> publish record 2020-09-07 16:15:00 EDT (1599509700): Failed upload after 3
>>> tries
>>>
>>> It was working fine in python2. The token and local server are the same
>>> and correct. I'm not sure I understand the debug error. Can anyone help?
>>> Thanks in advance.
>>> Bob
>>>
>>>
>>>
>>> On Tuesday, September 1, 2020 at 5:01:03 PM UTC-4, Bob Grattan wrote:

 Thanks to everyone for the help.
 Bob

 On Tuesday, September 1, 2020 at 2:50:51 PM UTC-4 wwwd...@gmail.com
 wrote:

> I just went through the same thing, as was mentioned above make sure
> all of your plugins have been updated to the latest version. I had a few
> plugins that I no longer run as they hadn't been upgraded and after a look
> at the code the work to upgrade them was more than I was willing to 
> tackle.
> WeeWX-WD for example (although someone has a work-in-progress repo where
> it's being worked on, but doesn't have any releases yet -- I did an 
> install
> from a GitHub clone and it seems to be working so far).
>
> At least for the two simple plugins I wrote I just had to change Queue
> to queue and replace urllib2 with urllib.request.
>
> On Tuesday, September 1, 2020 at 11:32:49 AM UTC-7 tke...@gmail.com
> wrote:
>
>> Same issue, except this time, it's cmon. Your version has not been
>> ported to Python 3. Fortunately, a newer version is available which has.
>>
>> On Tue, Sep 1, 2020 at 11:28 AM bgra...@umw.edu 
>> wrote:
>>
>>> Hello,
>>> Seeing the discussion of python3, I thought I would do the switch
>>> myself but ran into some errors. See below:
>>>
>>> +++
>>> /var/log/weewx.log:
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Initializing weewx
>>> version 4.1.1
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using Python 3.6.9
>>> (default, Jul 17 2020, 12:50:27) #012[GCC 8.4.0]
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Platform
>>> Linux-4.15.0-115-generic-x86_64-with-Ubuntu-18.04-bionic
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Locale is
>>> 'en_US.UTF-8'
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using configuration
>>> file /home/weewx/weewx.conf
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Debug is 0
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: Loading station
>>> type Vantage (weewx.drivers.vantage)
>>> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: StdConvert

Re: [weewx-user] weewx upgrade from python2 to python3

[Tom Keffer]

In the file emoncms.py, try changing lines 290-293 from

def check_response(self, response):
txt = response.read()
if txt != 'ok' :
raise weewx.restx.FailedPost("Server returned '%s'" % txt)

to

def check_response(self, response):
txt = response.read().decode()
if txt != u'ok' :
raise weewx.restx.FailedPost("Server returned '%s'" % txt)

On Mon, Sep 7, 2020 at 3:18 PM bgra...@umw.edu  wrote:

> To add to this, it seems my local server is being updated correctly as
> before even though the 3 failed attempts still appear in the log. Is it
> possible that the software is also trying to send data to emoncms.org? I
> only send data to my local server so could there be some code I need to
> remove to not keep it from sending it to emoncms.org?
>
> On Monday, September 7, 2020 at 4:39:00 PM UTC-4 bgra...@umw.edu wrote:
>
>> Having another problem with the move to python3. This time it's the
>> weewx-emoncms extension. I have installed the latest version which should
>> run on python3, from what I understand.
>> At bootup, I get the normal:
>>
>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: service
>> version is 0.17
>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: node is 0
>> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: Data will be
>> uploaded with token=b634
>>
>> In weewx.config I have:
>>
>> [StdRESTful]
>>   [[EmonCMS]]
>>
>> url = http://192.168.1.103/emoncms/input/post.json
>> token = b634
>>
>> But I get:
>> weewx.log:
>> Sep  7 16:15:16 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>> upload attempt 1: Server returned 'b'ok''
>> Sep  7 16:15:21 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>> upload attempt 2: Server returned 'b'ok''
>> Sep  7 16:15:26 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed
>> upload attempt 3: Server returned 'b'ok''
>> Sep  7 16:15:26 n4mrv weewx[27417] ERROR weewx.restx: EmonCMS: Failed to
>> publish record 2020-09-07 16:15:00 EDT (1599509700): Failed upload after 3
>> tries
>>
>> It was working fine in python2. The token and local server are the same
>> and correct. I'm not sure I understand the debug error. Can anyone help?
>> Thanks in advance.
>> Bob
>>
>>
>>
>> On Tuesday, September 1, 2020 at 5:01:03 PM UTC-4, Bob Grattan wrote:
>>>
>>> Thanks to everyone for the help.
>>> Bob
>>>
>>> On Tuesday, September 1, 2020 at 2:50:51 PM UTC-4 wwwd...@gmail.com
>>> wrote:
>>>
 I just went through the same thing, as was mentioned above make sure
 all of your plugins have been updated to the latest version. I had a few
 plugins that I no longer run as they hadn't been upgraded and after a look
 at the code the work to upgrade them was more than I was willing to tackle.
 WeeWX-WD for example (although someone has a work-in-progress repo where
 it's being worked on, but doesn't have any releases yet -- I did an install
 from a GitHub clone and it seems to be working so far).

 At least for the two simple plugins I wrote I just had to change Queue
 to queue and replace urllib2 with urllib.request.

 On Tuesday, September 1, 2020 at 11:32:49 AM UTC-7 tke...@gmail.com
 wrote:

> Same issue, except this time, it's cmon. Your version has not been
> ported to Python 3. Fortunately, a newer version is available which has.
>
> On Tue, Sep 1, 2020 at 11:28 AM bgra...@umw.edu 
> wrote:
>
>> Hello,
>> Seeing the discussion of python3, I thought I would do the switch
>> myself but ran into some errors. See below:
>>
>> +++
>> /var/log/weewx.log:
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Initializing weewx
>> version 4.1.1
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using Python 3.6.9
>> (default, Jul 17 2020, 12:50:27) #012[GCC 8.4.0]
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Platform
>> Linux-4.15.0-115-generic-x86_64-with-Ubuntu-18.04-bionic
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Locale is
>> 'en_US.UTF-8'
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using configuration
>> file /home/weewx/weewx.conf
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Debug is 0
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: Loading station
>> type Vantage (weewx.drivers.vantage)
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: StdConvert
>> target unit is 0x1
>> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.wxservices: The
>> following values will be calculated: pressure=prefer_hardware,
>> barometer=prefer_hardware, altimeter=prefer_hardware,
>> windchill=prefer_hardware, heatindex=prefer_hardware,
>> dewpoint=prefer_hardware, inDewpoint=prefer_hardware,
>> rainRate=prefer_hardware, maxSolarRad=prefer_hardware,
>> 

[weewx-user] Re: MQTT - extension / Belchertown skin / Failed connecting ....

[vince]

On Monday, September 7, 2020 at 9:50:27 AM UTC-7, Tom Cichowicz wrote:
>
>  I've successfully installed  the MQTT extension, to attempt to get 
> forecast data displayed on the skin pages... 
>   I have also installed an MQTT , for web socket requirements, and finally 
> got it publishing records...
> Sep  7 12:43:29 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
> 2020-09-07 12:43:25 EDT (1599497005)
> Sep  7 12:43:32 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
> 2020-09-07 12:43:28 EDT (1599497008)
> Sep  7 12:43:34 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
> 2020-09-07 12:43:31 EDT (1599497011)
>
> Still haven't figured out the message on the index.html page...
> *"Failed connecting to the weather station. Please try again later!"*
>
>anyone that can comment to help would be appreciated...
>   
>

Again - search the group archives please. This has come up a dozen times.

You need a MQTT broker (ie, a server) that has websockets configured 
correctly.  You also need your weewx.conf to match that setup.

There are several examples folks have previously posted on what 'correct' 
looks like. 

-- 
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/16eadf6f-11a7-434e-927e-069f321955b9o%40googlegroups.com.

Re: [weewx-user] weewx-Weather34 installation questions

[vince]

On Monday, September 7, 2020 at 3:12:44 PM UTC-7, ExprmntAl wrote:
>
> *ImportError: No module named configobj*
>
> Any ideas on why this error is happening?
>
>
>
Yes, you did not install the configobj module per the weewx prerequisites.
 

-- 
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/439746e7-3b33-4dfe-963e-8e3060c62134o%40googlegroups.com.

Re: [weewx-user] weewx upgrade from python2 to python3

[bgra...@umw.edu]

To add to this, it seems my local server is being updated correctly as 
before even though the 3 failed attempts still appear in the log. Is it 
possible that the software is also trying to send data to emoncms.org? I 
only send data to my local server so could there be some code I need to 
remove to not keep it from sending it to emoncms.org? 

On Monday, September 7, 2020 at 4:39:00 PM UTC-4 bgra...@umw.edu wrote:

> Having another problem with the move to python3. This time it's the 
> weewx-emoncms extension. I have installed the latest version which should 
> run on python3, from what I understand.
> At bootup, I get the normal:
>
> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: service 
> version is 0.17
> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: node is 0
> Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: Data will be 
> uploaded with token=b634 
>
> In weewx.config I have:
>
> [StdRESTful]
>   [[EmonCMS]]
>
> url = http://192.168.1.103/emoncms/input/post.json
> token = b634
>
> But I get:
> weewx.log:
> Sep  7 16:15:16 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
> upload attempt 1: Server returned 'b'ok''
> Sep  7 16:15:21 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
> upload attempt 2: Server returned 'b'ok''
> Sep  7 16:15:26 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
> upload attempt 3: Server returned 'b'ok''
> Sep  7 16:15:26 n4mrv weewx[27417] ERROR weewx.restx: EmonCMS: Failed to 
> publish record 2020-09-07 16:15:00 EDT (1599509700): Failed upload after 3 
> tries
>
> It was working fine in python2. The token and local server are the same 
> and correct. I'm not sure I understand the debug error. Can anyone help?  
> Thanks in advance.
> Bob
>
>
>
> On Tuesday, September 1, 2020 at 5:01:03 PM UTC-4, Bob Grattan wrote:
>>
>> Thanks to everyone for the help.
>> Bob
>>
>> On Tuesday, September 1, 2020 at 2:50:51 PM UTC-4 wwwd...@gmail.com 
>> wrote:
>>
>>> I just went through the same thing, as was mentioned above make sure all 
>>> of your plugins have been updated to the latest version. I had a few 
>>> plugins that I no longer run as they hadn't been upgraded and after a look 
>>> at the code the work to upgrade them was more than I was willing to tackle. 
>>> WeeWX-WD for example (although someone has a work-in-progress repo where 
>>> it's being worked on, but doesn't have any releases yet -- I did an install 
>>> from a GitHub clone and it seems to be working so far).
>>>
>>> At least for the two simple plugins I wrote I just had to change Queue 
>>> to queue and replace urllib2 with urllib.request.
>>>
>>> On Tuesday, September 1, 2020 at 11:32:49 AM UTC-7 tke...@gmail.com 
>>> wrote:
>>>
 Same issue, except this time, it's cmon. Your version has not been 
 ported to Python 3. Fortunately, a newer version is available which has.

 On Tue, Sep 1, 2020 at 11:28 AM bgra...@umw.edu  
 wrote:

> Hello,
> Seeing the discussion of python3, I thought I would do the switch 
> myself but ran into some errors. See below:
>
> +++
> /var/log/weewx.log:
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Initializing weewx 
> version 4.1.1
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using Python 3.6.9 
> (default, Jul 17 2020, 12:50:27) #012[GCC 8.4.0]
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Platform 
> Linux-4.15.0-115-generic-x86_64-with-Ubuntu-18.04-bionic
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Locale is 
> 'en_US.UTF-8'
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using configuration 
> file /home/weewx/weewx.conf
> Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Debug is 0
> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.wxservices: The following 
> values will be calculated: pressure=prefer_hardware, 
> barometer=prefer_hardware, altimeter=prefer_hardware, 
> windchill=prefer_hardware, heatindex=prefer_hardware, 
> dewpoint=prefer_hardware, inDewpoint=prefer_hardware, 
> rainRate=prefer_hardware, maxSolarRad=prefer_hardware, 
> cloudbase=prefer_hardware, humidex=prefer_hardware, 
> appTemp=prefer_hardware, ET=prefer_hardware, windrun=prefer_hardware
> Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.wxservices: The following 
> algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
> Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__: Caught 
> unrecoverable exception:
> Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__:   invalid 
> syntax (cmon.py, line 315)
> Sep  1 11:51:21 n4mrv weewx[3283] 

Re: [weewx-user] weewx-Weather34 installation questions

[ExprmntAl]

Tried the rest of the installation and ran into trouble when running the 
installer for weewx-Weather34 per the 3 commands below:

 *sudo git clone https://github.com/steepleian/weewx-Weather34.git 
 *
* cd weewx-Weather34 *
* sudo python w34_installer.py*  

The first 2 commands ran fine but the third command came up with an error 
(see below):

*pi@raspberrypi:~ $ sudo git 
clone https://github.com/steepleian/weewx-Weather34.git 
*
*Cloning into 'weewx-Weather34'...*
*remote: Enumerating objects: 734, done.*
*remote: Counting objects: 100% (734/734), done.*
*remote: Compressing objects: 100% (726/726), done.*
*remote: Total 734 (delta 241), reused 0 (delta 0), pack-reused 0*
*Receiving objects: 100% (734/734), 3.44 MiB | 1.13 MiB/s, done.*
*Resolving deltas: 100% (241/241), done.*
*pi@raspberrypi:~ $ cd weewx-Weather34*
*pi@raspberrypi:~/weewx-Weather34 $ sudo python w34_installer.py*
*Traceback (most recent call last):*
*  File "w34_installer.py", line 2, in *
*from configobj import ConfigObj*
*ImportError: No module named configobj*

Any ideas on why this error is happening?

On Sunday, September 6, 2020 at 10:22:49 AM UTC-5 steep...@gmail.com wrote:

> No you need to install it. Have a look here 
> http://weewx.com/docs/usersguide.htm#integrating_with_webserver
>
>  
>
> This is a distillation of the instructions to install Apache and PHP and 
> associated libraries: -
>
>  
>
> sudo apt update
>
>  
>
> sudo apt install apache2
>
>  
>
> sudo apt-get install php
>
>  
>
> sudo apt-get install php-cli php-fpm php-json php-sqlite3 php-zip php-gd  
> php-mbstring php-curl php-xml php-pear php-bcmath
>
>  
>
> sudo apt-get install libapache2-mod-php
>
>  
>
> sudo a2enmod php7.3
>
>  
>
> sudo systemctl restart apache2
>
>  
>
> IM.
>
>  
>
>  
>
>  
>
>  
>
> Sent from Mail  for 
> Windows 10
>
>  
>
> *From: *ExprmntAl
> *Sent: *06 September 2020 15:42
> *To: *weewx-user
> *Subject: *Re: [weewx-user] weewx-Weather34 installation questions
>
>  
>
> I was under the impression that Apache2 was installed as part of the weewx 
> installation already.  I am concerned that I will break something if I just 
> start installing things without understanding them fully if they are 
> already installed.  So if I  install Apache2, PHP7.x and the PHP 
> libraries as you suggest, is there a chance I will break what is already 
> working (in the case of Apache2 if it is already installed)?  
>
>  
>
> Is there a good tutorial somewhere for these installations?  There seem to 
> be a number of versions of PHP which is also confusing.
>
> On Sunday, September 6, 2020 at 9:03:54 AM UTC-5 steep...@gmail.com wrote:
>
> OK,
>
>  
>
> I also have the Seasons and Belchertown skin installed as well as my own 
> Weather34.
>
>  
>
> I would go ahead and install Apache2, PHP7.x and the PHP libraries. When 
> you install the libraries you should pick up things like curl along the way.
>
>  
>
> Then install Weather34 following the instructions carefully.
>
>  
>
> Belchertown is also very well documented and is straightforward to 
> install. Some people have a problem setting up MQTT but again I found it 
> straight forward to setup my own server on my own Pi. There is excellent 
> support from Pat and Belchertown users if you get into trouble.
>
>  
>
> IM
>
>  
>
> On Sun, 6 Sep 2020 at 14:44, ExprmntAl <72604...@compuserve.com> wrote:
>
> Ian, I should have noted that I'm running on a Raspberry Pi 4 with the 
> full version of the Raspberry Pi OS.  Weewx has been running fine for over 
> a month using the weatherflow extension (Tempest).  At this point I haven't 
> installed anything else and have been using the seasons skin.  I wanted to 
> start playing around with Belchertown and Weather34 now that I have gotten 
> my feet wet.
>
>  
>
> I had tried the "php -v" command already but it did not work and returned 
> "command not found".  Here is what I get when I run the two commands:
>
>  
>
> *pi@raspberrypi:~ $ apachectl -v*
>
> *bash: apachectl: command not found*
>
> *pi@raspberrypi:~ $ sudo apachectl -v*
>
> *sudo: apachectl: command not found*
>
> *pi@raspberrypi:~ $ php -v*
>
> *bash: php: command not found*
>
> *pi@raspberrypi:~ $ sudo php -v*
>
> *sudo: php: command not found*
>
> *pi@raspberrypi:~ $ *
>
>  
>
> Also, what about curl?  
>
>  
>
>  
>
> On Sunday, September 6, 2020 at 1:26:30 AM UTC-5 stee...@gmail.com wrote:
>
> To determine the versions of Apache and PHP installed: -
>
>  
>
> From the command line run: -
>
>  
>
> apachectl -v
>
> php -v
>
>  
>
>  
>
> IM
>
>  
>
>  
>
>  
>
> On Sun, 6 Sep 2020 at 07:07, steeple ian  wrote:
>
> Hi,
>
> I assume you are running a Debian based OS, Raspberry Pi OS or Ubuntu 
> perhaps?
>
> IM
>
>  
>
> On Sun, 6 Sep 2020 at 05:14, ExprmntAl <72604...@compuserve.com> wrote:
>
> In the installation instructions for 

Re: [weewx-user] weewx upgrade from python2 to python3

[Bob Grattan]

Having another problem with the move to python3. This time it's the 
weewx-emoncms extension. I have installed the latest version which should 
run on python3, from what I understand.
At bootup, I get the normal:

Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: service version 
is 0.17
Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: node is 0
Sep  7 16:04:07 n4mrv wee_reports[27467] INFO user.emoncms: Data will be 
uploaded with token=b634 

In weewx.config I have:

[StdRESTful]
  [[EmonCMS]]

url = http://192.168.1.103/emoncms/input/post.json
token = b634

But I get:
weewx.log:
Sep  7 16:15:16 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
upload attempt 1: Server returned 'b'ok''
Sep  7 16:15:21 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
upload attempt 2: Server returned 'b'ok''
Sep  7 16:15:26 n4mrv weewx[27417] DEBUG weewx.restx: EmonCMS: Failed 
upload attempt 3: Server returned 'b'ok''
Sep  7 16:15:26 n4mrv weewx[27417] ERROR weewx.restx: EmonCMS: Failed to 
publish record 2020-09-07 16:15:00 EDT (1599509700): Failed upload after 3 
tries

It was working fine in python2. The token and local server are the same and 
correct. I'm not sure I understand the debug error. Can anyone help?  
Thanks in advance.
Bob



On Tuesday, September 1, 2020 at 5:01:03 PM UTC-4, Bob Grattan wrote:
>
> Thanks to everyone for the help.
> Bob
>
> On Tuesday, September 1, 2020 at 2:50:51 PM UTC-4 wwwd...@gmail.com wrote:
>
>> I just went through the same thing, as was mentioned above make sure all 
>> of your plugins have been updated to the latest version. I had a few 
>> plugins that I no longer run as they hadn't been upgraded and after a look 
>> at the code the work to upgrade them was more than I was willing to tackle. 
>> WeeWX-WD for example (although someone has a work-in-progress repo where 
>> it's being worked on, but doesn't have any releases yet -- I did an install 
>> from a GitHub clone and it seems to be working so far).
>>
>> At least for the two simple plugins I wrote I just had to change Queue to 
>> queue and replace urllib2 with urllib.request.
>>
>> On Tuesday, September 1, 2020 at 11:32:49 AM UTC-7 tke...@gmail.com 
>> wrote:
>>
>>> Same issue, except this time, it's cmon. Your version has not been 
>>> ported to Python 3. Fortunately, a newer version is available which has.
>>>
>>> On Tue, Sep 1, 2020 at 11:28 AM bgra...@umw.edu  wrote:
>>>
 Hello,
 Seeing the discussion of python3, I thought I would do the switch 
 myself but ran into some errors. See below:

 +++
 /var/log/weewx.log:
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Initializing weewx 
 version 4.1.1
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using Python 3.6.9 
 (default, Jul 17 2020, 12:50:27) #012[GCC 8.4.0]
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Platform 
 Linux-4.15.0-115-generic-x86_64-with-Ubuntu-18.04-bionic
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Locale is 'en_US.UTF-8'
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Using configuration 
 file /home/weewx/weewx.conf
 Sep  1 11:51:21 n4mrv weewx[3283] INFO __main__: Debug is 0
 Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: Loading station 
 type Vantage (weewx.drivers.vantage)
 Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.engine: StdConvert target 
 unit is 0x1
 Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.wxservices: The following 
 values will be calculated: pressure=prefer_hardware, 
 barometer=prefer_hardware, altimeter=prefer_hardware, 
 windchill=prefer_hardware, heatindex=prefer_hardware, 
 dewpoint=prefer_hardware, inDewpoint=prefer_hardware, 
 rainRate=prefer_hardware, maxSolarRad=prefer_hardware, 
 cloudbase=prefer_hardware, humidex=prefer_hardware, 
 appTemp=prefer_hardware, ET=prefer_hardware, windrun=prefer_hardware
 Sep  1 11:51:21 n4mrv weewx[3283] INFO weewx.wxservices: The following 
 algorithms will be used for calculations: altimeter=aaASOS, maxSolarRad=RS
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__: Caught 
 unrecoverable exception:
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__:   invalid 
 syntax (cmon.py, line 315)
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__:   
 Traceback (most recent call last):
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__: File 
 "./bin/weewxd", line 148, in main
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__:   
 engine = weewx.engine.StdEngine(config_dict)
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__: File 
 "/home/weewx/bin/weewx/engine.py", line 75, in __init__
 Sep  1 11:51:21 n4mrv weewx[3283] CRITICAL __main__:   
 self.loadServices(config_dict)
 Sep  1 

Re: [weewx-user] Enabling historical data collection on new install

[icoj...@gmail.com]

I'm looking through the various weewx utilities and using wee_debug I've 
come across this...

Archive info
Database name: weewx.sdb
Table name: archive
Version 2.0
Unit system: 1 (US)
First good timestamp: 2020-09-03 12:10:00 BST (1599131400)
Last good timestamp: 2020-09-07 21:15:00 BST (1599509700)
Number of records: 1284
weewx (weewx.conf) is set to use an archive interval of 300 seconds.
The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf
Database name: weewx.sdb
Database driver: weedb.sqlite

Database name: weewx
Database driver: weedb.mysql
Database host: localhost

Comparing this to the old installation below...

Archive info
Database name: weewx.sdb
Table name: archive
Version 2.0
Unit system: 1 (US)
First good timestamp: 2018-04-14 17:06:58 BST (1523722018)
Last good timestamp: 2020-09-06 17:16:01 BST (1599408961)
Number of records: 319647
weewx (weewx.conf) is set to use an archive interval of 300 seconds.
The station hardware was not interrogated in determining archive interval.


Databases configured in weewx.conf
Database name: weewx.sdb
Database driver: weedb.sqlite


Database name: weewx
Database driver: weedb.mysql
Database host: localhost


Database name: forecast.sdb
Database driver: weedb.sqlite


This clearly shows that there are no records prior to the time the 
installation completed.  I'm also wondering why the database host entries 
are missing in the new installation.  Is there anyone who understands what 
this may be telling me please?!

On Monday, 7 September 2020 at 21:11:43 UTC+1 icoj...@gmail.com wrote:

> I've checked the weather station and the historic data is present.  I've 
> still got the old installation, it's still running at least the back end 
> is.  I'll see what's involved in migrating that to the new installation.
>
> Thanks for your help.
>
> On Monday, 7 September 2020 at 16:13:02 UTC+1 steep...@gmail.com wrote:
>
>> Very odd. Is there any chance you may have accidentally flushed your 
>> weather station memory.
>>
>> Did you save a copy of your old database? If you did you can update that 
>> to the new schema as per the WeeWX documentation.
>>
>> On Mon, 7 Sep 2020 at 16:05, icoj...@gmail.com  wrote:
>>
>>> Thank you.  I've set up meteoalarm, I think, and have included a 
>>> screenshot to show what I'm seeing.  There is no historical data and at no 
>>> point during my random checks of the log over the almost 5 days it's been 
>>> running show any records to suggest it's recorded any.  I'm stumped, the 
>>> config is the same as the previous installation which updated historical 
>>> data within the first 24 hours.
>>>
>>> [image: Untitled.png]
>>>
>>> On Monday, 7 September 2020 at 15:56:53 UTC+1 steep...@gmail.com wrote:
>>>
 That all seems to be as I would expect except you have not setup the 
 Meteoalarm web service hence that error. It certainly looks like it has 
 finished downloading the historic data.


 On Mon, 7 Sep 2020 at 13:06, icoj...@gmail.com  
 wrote:

> Thank you.  I've done that and pasted below is what I am seeing...
>
> Sep 7 12:55:35 rasptest weewx[340] INFO weewx.cheetahgenerator: 
> Generated 7 files for report w34Highcharts in 1.30 seconds
> Sep 7 12:55:35 rasptest weewx[340] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx/weather34/w34highcharts
> Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover 
> url1 exit code 0
> Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover 
> url2 exit code 0
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
> 'IHDR' 16 13
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
> 'gAMA' 41 4
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
> 'pHYs' 57 9
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
> 'IDAT' 78 65458
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.Image: Error closing: 
> 'Image' object has no attribute 'fp'
> Sep 7 12:57:37 rasptest weewx[340] ERROR user.weather34: Failed 
> getting web service data. URL: 
> http://000.000.000.000/weewx/weather34/eualert.php?country=UK=013 
> Header: ["'User-Agent'", "'Mozilla/5.0 (Macintosh; U; Intel Mac OS X 
> 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 
> Safari/534.3'"], Error: HTTP Error 400: Bad Request
> Sep 7 13:00:29 rasptest weewx[340] DEBUG user.weather34: CloudCover: 
> Percent value is 55.0
> Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
> 2020-09-07 13:00:00 BST (159948) to database 'weewx.sdb'
> Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
> 2020-09-07 13:00:00 BST (159948) to daily summary in 'weewx.sdb'
> Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running 
> reports for latest time 

Re: [weewx-user] Enabling historical data collection on new install

[icoj...@gmail.com]

I've checked the weather station and the historic data is present.  I've 
still got the old installation, it's still running at least the back end 
is.  I'll see what's involved in migrating that to the new installation.

Thanks for your help.

On Monday, 7 September 2020 at 16:13:02 UTC+1 steep...@gmail.com wrote:

> Very odd. Is there any chance you may have accidentally flushed your 
> weather station memory.
>
> Did you save a copy of your old database? If you did you can update that 
> to the new schema as per the WeeWX documentation.
>
> On Mon, 7 Sep 2020 at 16:05, icoj...@gmail.com  wrote:
>
>> Thank you.  I've set up meteoalarm, I think, and have included a 
>> screenshot to show what I'm seeing.  There is no historical data and at no 
>> point during my random checks of the log over the almost 5 days it's been 
>> running show any records to suggest it's recorded any.  I'm stumped, the 
>> config is the same as the previous installation which updated historical 
>> data within the first 24 hours.
>>
>> [image: Untitled.png]
>>
>> On Monday, 7 September 2020 at 15:56:53 UTC+1 steep...@gmail.com wrote:
>>
>>> That all seems to be as I would expect except you have not setup the 
>>> Meteoalarm web service hence that error. It certainly looks like it has 
>>> finished downloading the historic data.
>>>
>>>
>>> On Mon, 7 Sep 2020 at 13:06, icoj...@gmail.com  
>>> wrote:
>>>
 Thank you.  I've done that and pasted below is what I am seeing...

 Sep 7 12:55:35 rasptest weewx[340] INFO weewx.cheetahgenerator: 
 Generated 7 files for report w34Highcharts in 1.30 seconds
 Sep 7 12:55:35 rasptest weewx[340] INFO weewx.reportengine: Copied 0 
 files to /var/www/html/weewx/weather34/w34highcharts
 Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover 
 url1 exit code 0
 Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover 
 url2 exit code 0
 Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
 'IHDR' 16 13
 Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
 'gAMA' 41 4
 Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
 'pHYs' 57 9
 Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 
 'IDAT' 78 65458
 Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.Image: Error closing: 
 'Image' object has no attribute 'fp'
 Sep 7 12:57:37 rasptest weewx[340] ERROR user.weather34: Failed getting 
 web service data. URL: 
 http://000.000.000.000/weewx/weather34/eualert.php?country=UK=013 
 Header: ["'User-Agent'", "'Mozilla/5.0 (Macintosh; U; Intel Mac OS X 
 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 
 Safari/534.3'"], Error: HTTP Error 400: Bad Request
 Sep 7 13:00:29 rasptest weewx[340] DEBUG user.weather34: CloudCover: 
 Percent value is 55.0
 Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
 2020-09-07 13:00:00 BST (159948) to database 'weewx.sdb'
 Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
 2020-09-07 13:00:00 BST (159948) to daily summary in 'weewx.sdb'
 Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running 
 reports for latest time in the database.
 Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running 
 report 'SeasonsReport'
 Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Found 
 configuration file /home/weewx/skins/Seasons/skin.conf for report 
 'SeasonsReport'
 Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using 
 search list ['weewx.cheetahgenerator.Almanac', 
 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
 'weewx.cheetahgenerator.Extras']
 Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.manager: Daily summary 
 version is 2.0
 Sep 7 13:00:32 rasptest weewx[340] INFO weewx.cheetahgenerator: 
 Generated 8 files for report SeasonsReport in 1.79 seconds
 Sep 7 13:00:32 rasptest weewx[340] DEBUG weewx.manager: Daily summary 
 version is 2.0
 Sep 7 13:00:38 rasptest weewx[340] INFO weewx.imagegenerator: Generated 
 30 images for report SeasonsReport in 5.35 seconds
 Sep 7 13:00:38 rasptest weewx[340] INFO weewx.reportengine: Copied 0 
 files to /var/www/html/
 Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
 'SmartphoneReport' not enabled. Skipping.
 Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
 'MobileReport' not enabled. Skipping.
 Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
 'StandardReport' not enabled. Skipping.
 Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
 'FTP' not enabled. Skipping.
 Sep 7 13:00:38 rasptest weewx[340] DEBUG 

[weewx-user] MQTT - extension / Belchertown skin / Failed connecting ....

[Tom Cichowicz]

Well, I'm plugging away trying different options with my new toy weeWX.

 I've been successful getting much of my orig. WeatherFlow Air/Sky sensor 
data up and running within the system.
 I've successfully installed  the MQTT extension, to attempt to get 
forecast data displayed on the skin pages... 
  I have also installed an MQTT , for web socket requirements, and finally 
got it publishing records...
Sep  7 12:43:29 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
2020-09-07 12:43:25 EDT (1599497005)
Sep  7 12:43:32 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
2020-09-07 12:43:28 EDT (1599497008)
Sep  7 12:43:34 weewx weewx[8055] INFO weewx.restx: MQTT: Published record 
2020-09-07 12:43:31 EDT (1599497011)

Still haven't figured out the message on the index.html page...
*"Failed connecting to the weather station. Please try again later!"*
All my data appears to be up to date. 

   anyone that can comment to help would be appreciated...
  

-- 
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/458accba-058d-45c2-b0a9-50228e137d05n%40googlegroups.com.

Re: [weewx-user] Enabling historical data collection on new install

[steeple ian]

That all seems to be as I would expect except you have not setup the
Meteoalarm web service hence that error. It certainly looks like it has
finished downloading the historic data.


On Mon, 7 Sep 2020 at 13:06, icoj...@gmail.com  wrote:

> Thank you.  I've done that and pasted below is what I am seeing...
>
> Sep 7 12:55:35 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated
> 7 files for report w34Highcharts in 1.30 seconds
> Sep 7 12:55:35 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files
> to /var/www/html/weewx/weather34/w34highcharts
> Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover url1
> exit code 0
> Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover url2
> exit code 0
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'IHDR'
> 16 13
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'gAMA'
> 41 4
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'pHYs'
> 57 9
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'IDAT'
> 78 65458
> Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.Image: Error closing: 'Image'
> object has no attribute 'fp'
> Sep 7 12:57:37 rasptest weewx[340] ERROR user.weather34: Failed getting
> web service data. URL:
> http://000.000.000.000/weewx/weather34/eualert.php?country=UK=013
> Header: ["'User-Agent'", "'Mozilla/5.0 (Macintosh; U; Intel Mac OS X
> 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63
> Safari/534.3'"], Error: HTTP Error 400: Bad Request
> Sep 7 13:00:29 rasptest weewx[340] DEBUG user.weather34: CloudCover:
> Percent value is 55.0
> Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record
> 2020-09-07 13:00:00 BST (159948) to database 'weewx.sdb'
> Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record
> 2020-09-07 13:00:00 BST (159948) to daily summary in 'weewx.sdb'
> Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
> Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
> Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Found
> configuration file /home/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
> Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras']
> Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.manager: Daily summary
> version is 2.0
> Sep 7 13:00:32 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated
> 8 files for report SeasonsReport in 1.79 seconds
> Sep 7 13:00:32 rasptest weewx[340] DEBUG weewx.manager: Daily summary
> version is 2.0
> Sep 7 13:00:38 rasptest weewx[340] INFO weewx.imagegenerator: Generated 30
> images for report SeasonsReport in 5.35 seconds
> Sep 7 13:00:38 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files
> to /var/www/html/
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report
> 'SmartphoneReport' not enabled. Skipping.
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report
> 'MobileReport' not enabled. Skipping.
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report
> 'StandardReport' not enabled. Skipping.
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 'FTP'
> not enabled. Skipping.
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report
> 'RSYNC' not enabled. Skipping.
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Running
> report 'Weather34Report'
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Found
> configuration file /home/weewx/skins/Weather34/skin.conf for report
> 'Weather34Report'
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras', u'user.stats.MyStats',
> u'user.lastrain.lastRainTags']
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.manager: Daily summary
> version is 2.0
> Sep 7 13:00:38 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated
> 2 files for report Weather34Report in 0.34 seconds
> Sep 7 13:00:38 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files
> to /var/www/html/weewx/weather34/
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Running
> report 'w34Highcharts'
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Found
> configuration file /home/weewx/skins/w34Highcharts/skin.conf for report
> 'w34Highcharts'
> Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 

Re: [weewx-user] weewx stops reporting data

[gjr80]

The failed attempts highlighted below are exactly that; a failed attempt to 
communicate with the GW1000 (and in each case attempt 2 was successful). 
When sending a command to the GW1000 the driver will attempt to send the 
command (and obtain a response) a set number of times (three is the 
default) before giving up. This is fairly standard behaviour in most WeeWX 
drivers. It is only once all attempts fail that the driver considers 
contact with the GW1000 has been lost and the 'lost contact' procedure 
implemented. 

As for the frequency of failed attempts, I have noticed the odd failure 
during testing/development which I have put down to the vagaries of 
communicating with a device over a network/wifi or the device being busy 
while doing something else (posting to WU/Ecowitt, talking to sensors etc). 
Can't say I have seen any 104 errors, only timeouts. Such problems will not 
be IP address issues as the second or third attempt works and a changed IP 
address would result in all attempts failing (the driver will only work 
through lost contact if all three attempts fail). I don't run my on-line 
GW1000 instance with debug=1 so I would not see any single or double 
attempt failures there and I am yet to have an all attempts failure. I 
might try running with debug=1 to see if there are any single or double 
failures.

Can't say I have seen any pm2.5 anomalies such as you describe either.

Gary

On Monday, 7 September 2020 at 13:30:15 UTC+10 graha...@gmail.com wrote:

> interesting. i have been running gw1000.py b12 since its release, and 
> stopped watching closely as it was all working fine (no weewx losses - 
> apart from pm2.5 sensors, which is different story). now that i go back to 
> logs (debug==1), i see gw1000 
>
service reported about 24 errors over last 36 hours at apparently random 
> intervals (5 mins to 5 hours). service recovers cleanly, so i hadn’t 
> noticed.
> but it shows how critical the recovery function is to the gw1000 service - 
> who know what evil lurks under the “WS View” phone app provided...
>
> mostly gw1000 service reports a single timeout.
>
> Sep  7 11:34:19 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
> Sep  7 11:34:41 dizzy weewx[7853] DEBUG user.*gw1000*: Failed to obtain 
> response to attempt 1 to send command 'CMD_GW1000_LIVEDATA': timed out
> Sep  7 11:34:52 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
>
>
> occasionally it is a "connection reset" - presumably just happens to catch 
> the GW1000 controller while it is failing.
>
> Sep  7 02:27:41 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
> Sep  7 02:28:02 dizzy weewx[7853] DEBUG user.*gw1000*: Failed attempt 1 
> to send command 'CMD_READ_SENSOR_ID': [Errno 104] Connection reset by peer
> Sep  7 02:28:13 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
> Sep  7 02:28:21 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
> Sep  7 02:28:21 dizzy weewx[7853] INFO user.*gw1000*: Lightning counter 
> wraparound detected: new=0 last=1
> Sep  7 02:28:41 dizzy weewx[7853] DEBUG user.*gw1000*: Next update in 20 
> seconds
>
>
> in my case, it is not a DHCP issue as the ipaddr doesn’t change, the 
> period between failures is far too short for lease expiries, and it is 
> assigned ipaddr by mac address anyway. prime facie the GW1000 controller 
> (or at least its wifi interface) is resetting itself at random intervals. 
> has this behaviour been seen elsewhere?
>
> now i bring in my pm2.5 sensors reporting to the GW1000 controller. i have 
> two. they both reset sporadically (losing state, so it is not just 
> interface reset), and often at the same time. this interval appears to be 
> several days, not 1½ hours like above. i wonder if it is related to the 
> apparent GW1000 controller resets
>
>

-- 
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/bd063697-8be8-45e9-b8f7-8a92a8c8ff54n%40googlegroups.com.

Re: [weewx-user] FTP upload template

[Martin Madara]

Oh, great, thanks Tom, weewx simplicity rocks!!

On Monday, September 7, 2020 at 3:08:19 PM UTC+2 tke...@gmail.com wrote:

> Why not just use the $hour tag?
>
> #for $record in $hour.records
> ...
> #end for
>
>
> -tk
>
> On Sun, Sep 6, 2020 at 11:31 PM Martin Madara  wrote:
>
>> Hi folks,
>>
>> hope you are all doing well.  I'm using below template for FTP upload, 
>> but its giving me each time records for whole day. Is it possible to adjust 
>> below template to give me records let's say for last hour only?
>>
>>
>> #for $record in $day.records
>>
>> $record.dateTime--$record.windDir.format(add_label=False)--$record.windSpeed.format(add_label=False)--$record.windGust.format(add_label=False)--$record.outHumidity.format(add_label=False)--$record.outTemp.format(add_label=False)--$record.inTemp.format(add_label=False)
>> #end for
>>
>> Appreciate your help on this!
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/8558dd50-ab8e-48f7-ad6a-89b6507378e4n%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/b2ad54e1-7870-449a-9db4-a369abfbe203n%40googlegroups.com.

Re: [weewx-user] FTP upload template

[Tom Keffer]

Why not just use the $hour tag?

#for $record in $hour.records
...
#end for


-tk

On Sun, Sep 6, 2020 at 11:31 PM Martin Madara  wrote:

> Hi folks,
>
> hope you are all doing well.  I'm using below template for FTP upload, but
> its giving me each time records for whole day. Is it possible to adjust
> below template to give me records let's say for last hour only?
>
>
> #for $record in $day.records
>
> $record.dateTime--$record.windDir.format(add_label=False)--$record.windSpeed.format(add_label=False)--$record.windGust.format(add_label=False)--$record.outHumidity.format(add_label=False)--$record.outTemp.format(add_label=False)--$record.inTemp.format(add_label=False)
> #end for
>
> Appreciate your help on this!
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8558dd50-ab8e-48f7-ad6a-89b6507378e4n%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/CAPq0zEAR2pxuDSt-UG%3DyKWBYRRcMve0vjnmkMP8mj5UZM30WqQ%40mail.gmail.com.

Re: [weewx-user] Enabling historical data collection on new install

[icoj...@gmail.com]

Thank you.  I've done that and pasted below is what I am seeing...

Sep 7 12:55:35 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated 7 
files for report w34Highcharts in 1.30 seconds
Sep 7 12:55:35 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/weather34/w34highcharts
Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover url1 
exit code 0
Sep 7 12:56:39 rasptest weewx[340] DEBUG user.weather34: CloudCover url2 
exit code 0
Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'IHDR' 
16 13
Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'gAMA' 
41 4
Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'pHYs' 
57 9
Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.PngImagePlugin: STREAM 'IDAT' 
78 65458
Sep 7 12:56:39 rasptest weewx[340] DEBUG PIL.Image: Error closing: 'Image' 
object has no attribute 'fp'
Sep 7 12:57:37 rasptest weewx[340] ERROR user.weather34: Failed getting web 
service data. URL: 
http://000.000.000.000/weewx/weather34/eualert.php?country=UK=013 
Header: ["'User-Agent'", "'Mozilla/5.0 (Macintosh; U; Intel Mac OS X 
10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 
Safari/534.3'"], Error: HTTP Error 400: Bad Request
Sep 7 13:00:29 rasptest weewx[340] DEBUG user.weather34: CloudCover: 
Percent value is 55.0
Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
2020-09-07 13:00:00 BST (159948) to database 'weewx.sdb'
Sep 7 13:00:29 rasptest weewx[340] INFO weewx.manager: Added record 
2020-09-07 13:00:00 BST (159948) to daily summary in 'weewx.sdb'
Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Running report 
'SeasonsReport'
Sep 7 13:00:30 rasptest weewx[340] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport'
Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras']
Sep 7 13:00:31 rasptest weewx[340] DEBUG weewx.manager: Daily summary 
version is 2.0
Sep 7 13:00:32 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 1.79 seconds
Sep 7 13:00:32 rasptest weewx[340] DEBUG weewx.manager: Daily summary 
version is 2.0
Sep 7 13:00:38 rasptest weewx[340] INFO weewx.imagegenerator: Generated 30 
images for report SeasonsReport in 5.35 seconds
Sep 7 13:00:38 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 
'StandardReport' not enabled. Skipping.
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 'FTP' 
not enabled. Skipping.
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Report 'RSYNC' 
not enabled. Skipping.
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Running report 
'Weather34Report'
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/Weather34/skin.conf for report 
'Weather34Report'
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.stats.MyStats', 
u'user.lastrain.lastRainTags']
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.manager: Daily summary 
version is 2.0
Sep 7 13:00:38 rasptest weewx[340] INFO weewx.cheetahgenerator: Generated 2 
files for report Weather34Report in 0.34 seconds
Sep 7 13:00:38 rasptest weewx[340] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/weather34/
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Running report 
'w34Highcharts'
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.reportengine: Found 
configuration file /home/weewx/skins/w34Highcharts/skin.conf for report 
'w34Highcharts'
Sep 7 13:00:38 rasptest weewx[340] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', 
u'user.w34highchartsSearchX.w34highcharts_temp_week', 
u'user.w34highchartsSearchX.w34highcharts_bar_rain_week', 
u'user.w34highchartsSearchX.w34highcharts_wind_week', 

Re: [weewx-user] Enabling historical data collection on new install

[steeple ian]

Change you debug level to debug = 2 and see if that reveals any more
information.

On Mon, 7 Sep 2020 at 12:36, Matt C  wrote:

> Exactly the same as my previous reply.  It appears to be adding a record
> to the DB on each loop but there’s no log entry for historical data.
>
>
>
> *From: *steeple ian 
> *Sent: *07 September 2020 09:25
> *To: *weewx-user@googlegroups.com
> *Subject: *Re: [weewx-user] Enabling historical data collection on new
> install
>
>
>
> what is your syslog showing?
>
>
>
> On Mon, 7 Sep 2020 at 09:18, icoj...@gmail.com  wrote:
>
> Still nothing...
>
> On Friday, 4 September 2020 at 12:30:07 UTC+1 steep...@gmail.com wrote:
>
> Patience is a virtue:-)
>
>
>
> On Fri, 4 Sep 2020 at 12:22, icoj...@gmail.com  wrote:
>
> Hi,
>
>
>
> It's a aercus badged device.  I have looked at the syslog periodically
> since it's been up and running and I'm only seeing writes to the database
> on each current loop, shown below, there are no log records of any other
> database activity.
>
>
>
> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record
> 2020-09-04 12:20:00 BST (1599218400) to database 'weewx.sdb'
>
> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record
> 2020-09-04 12:20:00 BST (1599218400) to daily summary in 'weewx.sdb'
>
>
>
> Thanks for your help
>
>
>
> On Friday, 4 September 2020 at 12:10:29 UTC+1 steep...@gmail.com wrote:
>
> I assume yours is a Maplin badged device? From what I remember when I had
> the same model it took nearly a day to download a couple of years’ worth of
> data. Have you looked into the syslog to see what is happening in real
> time? From the command line run to watch the progress: -
>
>
>
> *sudo tail -f /var/log/syslog *
>
>
>
> On Fri, 4 Sep 2020 at 11:58, Matt C  wrote:
>
> Hi,
>
>
>
> I think I’ve got about 4-5 years worth but the issue is I’m not seeing any
> of that yet, I don’t see any data prior to yesterday, so I don’t think the
> process has even started.
>
>
>
> Regards
>
>
>
> *From: *steeple ian
> *Sent: *04 September 2020 11:53
> *To: *weewx...@googlegroups.com
> *Subject: *Re: [weewx-user] Enabling historical data collection on new
> install
>
>
>
> Matt,
>
> From previous experience using an HP1000 it takes a long time to download
> the data stored on your device. How many years worth?
>
>
>
> -im
>
>
>
> On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com  wrote:
>
> Hi,
>
>
>
> When I first installed weewx a year ago I noticed that it went through a
> process of adding all the historical data over the course of the first few
> days.  This then gave me a good historical picture for trend analysis.
>
>
>
> I've done a fresh install of 4.1.1 on a separate RPi this week and after 2
> days I cannot see any historical data.  Is there something I need to do?
>
>
>
> 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+...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com
> 
> .
>
> --
> 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/RovNaHpvlJs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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+...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol
> 
> .
>
>
>
>
>
>
>
>
>
>
> --
>
>
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
>
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+...@googlegroups.com.
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/5b96f3f1-09a9-4e7d-8e02-5f81fa6d1e13n%40googlegroups.com
> 

RE: [weewx-user] Enabling historical data collection on new install

[Matt C]

Exactly the same as my previous reply.  It appears to be adding a record to the DB on each loop but there’s no log entry for historical data. From: steeple ianSent: 07 September 2020 09:25To: weewx-user@googlegroups.comSubject: Re: [weewx-user] Enabling historical data collection on new install what is your syslog showing? On Mon, 7 Sep 2020 at 09:18, icoj...@gmail.com  wrote:Still nothing...On Friday, 4 September 2020 at 12:30:07 UTC+1 steep...@gmail.com wrote:Patience is a virtue:-) On Fri, 4 Sep 2020 at 12:22, icoj...@gmail.com  wrote:Hi, It's a aercus badged device.  I have looked at the syslog periodically since it's been up and running and I'm only seeing writes to the database on each current loop, shown below, there are no log records of any other database activity. Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 2020-09-04 12:20:00 BST (1599218400) to database 'weewx.sdb'Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 2020-09-04 12:20:00 BST (1599218400) to daily summary in 'weewx.sdb' Thanks for your help On Friday, 4 September 2020 at 12:10:29 UTC+1 steep...@gmail.com wrote:I assume yours is a Maplin badged device? From what I remember when I had the same model it took nearly a day to download a couple of years’ worth of data. Have you looked into the syslog to see what is happening in real time? From the command line run to watch the progress: - sudo tail -f /var/log/syslog  On Fri, 4 Sep 2020 at 11:58, Matt C  wrote:Hi, I think I’ve got about 4-5 years worth but the issue is I’m not seeing any of that yet, I don’t see any data prior to yesterday, so I don’t think the process has even started.   Regards From: steeple ianSent: 04 September 2020 11:53To: weewx...@googlegroups.comSubject: Re: [weewx-user] Enabling historical data collection on new install Matt,From previous experience using an HP1000 it takes a long time to download the data stored on your device. How many years worth? -im On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com  wrote:Hi, When I first installed weewx a year ago I noticed that it went through a process of adding all the historical data over the course of the first few days.  This then gave me a good historical picture for trend analysis. I've done a fresh install of 4.1.1 on a separate RPi this week and after 2 days I cannot see any historical data.  Is there something I need to do? 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+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com.-- 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/RovNaHpvlJs/unsubscribe.To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol. -- You received this message because you are subscribed to the Google Groups "weewx-user" group.To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5b96f3f1-09a9-4e7d-8e02-5f81fa6d1e13n%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/e80cba1f-3faa-4573-9cb5-43a751d8fdcan%40googlegroups.com.-- 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/RovNaHpvlJs/unsubscribe.To unsubscribe from this group and all its topics, 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/CADASSaQ7Kup6Ki9R4Kh%3DYaMABGxzpN634w3962a-KuwPj8fApw%40mail.gmail.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 

Re: [weewx-user] Enabling historical data collection on new install

[steeple ian]

what is your syslog showing?

On Mon, 7 Sep 2020 at 09:18, icoj...@gmail.com  wrote:

> Still nothing...
>
> On Friday, 4 September 2020 at 12:30:07 UTC+1 steep...@gmail.com wrote:
>
>> Patience is a virtue:-)
>>
>> On Fri, 4 Sep 2020 at 12:22, icoj...@gmail.com  wrote:
>>
>>> Hi,
>>>
>>> It's a aercus badged device.  I have looked at the syslog periodically
>>> since it's been up and running and I'm only seeing writes to the database
>>> on each current loop, shown below, there are no log records of any other
>>> database activity.
>>>
>>> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record
>>> 2020-09-04 12:20:00 BST (1599218400) to database 'weewx.sdb'
>>> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record
>>> 2020-09-04 12:20:00 BST (1599218400) to daily summary in 'weewx.sdb'
>>>
>>> Thanks for your help
>>>
>>> On Friday, 4 September 2020 at 12:10:29 UTC+1 steep...@gmail.com wrote:
>>>
 I assume yours is a Maplin badged device? From what I remember when I
 had the same model it took nearly a day to download a couple of years’
 worth of data. Have you looked into the syslog to see what is happening in
 real time? From the command line run to watch the progress: -

 sudo tail -f /var/log/syslog

 On Fri, 4 Sep 2020 at 11:58, Matt C  wrote:

> Hi,
>
>
>
> I think I’ve got about 4-5 years worth but the issue is I’m not seeing
> any of that yet, I don’t see any data prior to yesterday, so I don’t think
> the process has even started.
>
>
>
> Regards
>
>
>
> *From: *steeple ian
> *Sent: *04 September 2020 11:53
> *To: *weewx...@googlegroups.com
> *Subject: *Re: [weewx-user] Enabling historical data collection on
> new install
>
>
>
> Matt,
>
> From previous experience using an HP1000 it takes a long time to
> download the data stored on your device. How many years worth?
>
>
>
> -im
>
>
>
> On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com 
> wrote:
>
> Hi,
>
>
>
> When I first installed weewx a year ago I noticed that it went through
> a process of adding all the historical data over the course of the first
> few days.  This then gave me a good historical picture for trend analysis.
>
>
>
> I've done a fresh install of 4.1.1 on a separate RPi this week and
> after 2 days I cannot see any historical data.  Is there something I need
> to do?
>
>
>
> 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+...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com
> 
> .
>
> --
> 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/RovNaHpvlJs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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+...@googlegroups.com.
>
>
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol
> 
> .
>
>
>


>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>>
>>>
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>>>
>>> To view this discussion on the web visit
>>> 

Re: [weewx-user] Enabling historical data collection on new install

[icoj...@gmail.com]

Still nothing...

On Friday, 4 September 2020 at 12:30:07 UTC+1 steep...@gmail.com wrote:

> Patience is a virtue:-)
>
> On Fri, 4 Sep 2020 at 12:22, icoj...@gmail.com  wrote:
>
>> Hi,
>>
>> It's a aercus badged device.  I have looked at the syslog periodically 
>> since it's been up and running and I'm only seeing writes to the database 
>> on each current loop, shown below, there are no log records of any other 
>> database activity.
>>
>> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 
>> 2020-09-04 12:20:00 BST (1599218400) to database 'weewx.sdb'
>> Sep  4 12:20:30 rasptest weewx[17241] INFO weewx.manager: Added record 
>> 2020-09-04 12:20:00 BST (1599218400) to daily summary in 'weewx.sdb'
>>
>> Thanks for your help
>>
>> On Friday, 4 September 2020 at 12:10:29 UTC+1 steep...@gmail.com wrote:
>>
>>> I assume yours is a Maplin badged device? From what I remember when I 
>>> had the same model it took nearly a day to download a couple of years’ 
>>> worth of data. Have you looked into the syslog to see what is happening in 
>>> real time? From the command line run to watch the progress: -
>>>
>>> sudo tail -f /var/log/syslog 
>>>
>>> On Fri, 4 Sep 2020 at 11:58, Matt C  wrote:
>>>
 Hi,

  

 I think I’ve got about 4-5 years worth but the issue is I’m not seeing 
 any of that yet, I don’t see any data prior to yesterday, so I don’t think 
 the process has even started.  

  

 Regards

  

 *From: *steeple ian
 *Sent: *04 September 2020 11:53
 *To: *weewx...@googlegroups.com
 *Subject: *Re: [weewx-user] Enabling historical data collection on new 
 install

  

 Matt,

 From previous experience using an HP1000 it takes a long time to 
 download the data stored on your device. How many years worth?

  

 -im

  

 On Fri, 4 Sep 2020 at 10:13, icoj...@gmail.com  
 wrote:

 Hi,

  

 When I first installed weewx a year ago I noticed that it went through 
 a process of adding all the historical data over the course of the first 
 few days.  This then gave me a good historical picture for trend analysis.

  

 I've done a fresh install of 4.1.1 on a separate RPi this week and 
 after 2 days I cannot see any historical data.  Is there something I need 
 to do?

  

 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+...@googlegroups.com.


 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/dbc86e88-e951-482e-92fc-bf086a21c783n%40googlegroups.com
  
 
 .

 -- 
 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/RovNaHpvlJs/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/CADASSaRQ_Y4f1NQJEkDk5zg9PFcYm%3DWmJJwW2jxg%2BksxzjrZAA%40mail.gmail.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+...@googlegroups.com.


 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/2310EA5B-2C2F-4904-A8CE-AAEF21E23E70%40hxcore.ol
  
 
 .



>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>> -- 
>>
>>
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>>
>>
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
>>
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/5b96f3f1-09a9-4e7d-8e02-5f81fa6d1e13n%40googlegroups.com
>>  
>> 
>> .
>>
>>
>>

-- 
You 

[weewx-user] FTP upload template

[Martin Madara]

Hi folks,

hope you are all doing well.  I'm using below template for FTP upload, but 
its giving me each time records for whole day. Is it possible to adjust 
below template to give me records let's say for last hour only?


#for $record in $day.records
$record.dateTime--$record.windDir.format(add_label=False)--$record.windSpeed.format(add_label=False)--$record.windGust.format(add_label=False)--$record.outHumidity.format(add_label=False)--$record.outTemp.format(add_label=False)--$record.inTemp.format(add_label=False)
#end for

Appreciate your help on this!
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8558dd50-ab8e-48f7-ad6a-89b6507378e4n%40googlegroups.com.