date:20200502

This may be a problem? After changing to python3 ..

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: Caught
unrecoverable exception:

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   invalid
syntax (mqtt.py, line 196)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   Traceback
(most recent call last):

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewxd", line 148, in main

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   engine
= weewx.engine.StdEngine(config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 75, in __init__

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
self.loadServices(config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weewx/engine.py", line 138, in loadServices

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   obj
= weeutil.weeutil.get_object(svc)(self,config_dict)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/weeutil/weeutil.py", line 1093, in get_object

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   mod
= __import__(module)

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: File
"/usr/share/weewx/user/mqtt.py", line 196

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__:   except
KeyError, e:

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
^

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
SyntaxError:
invalid syntax

May  3 16:28:06 raspberrypi weewx[5437] CRITICAL __main__: 
Exiting.

On Sun, 3 May 2020 at 15:45, Colin Larsen  wrote:

> Ah .. that will be the missing piece of the puzzle! Off to sort that
> now, will report back.
>
> Thanks!
>
> On Sun, 3 May 2020 at 15:30, mwall  wrote:
>
>> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>>
>>> I found this /etc/default
>>>
>>> WEEWX_PYTHON=python2
>>>
>>> WEEWX_BINDIR=/usr/share/weewx
>>>
>>> WEEWX_BIN=/usr/bin/weewxd
>>>
>>> WEEWX_CFG=/etc/weewx/weewx.conf
>>>
>>>
>>> Changing it to python3 breaks weewx so I'll just leave well enough alone
>>>
>>
>> you *should* be able to switch from python2 to python3 simply by changing
>> the WEEWX_PYTHON line.  however, if you were running with python2 and you
>> have not installed the python3 dependencies, then of course weewx won't run.
>>
>> m
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%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/CACjxfUuaE3hjkN14VvRaCpsgc1d6Lgan5HL0972%2BdmThXGbD0w%40mail.gmail.com.

[weewx-user] Re: Belchertown highcharts : from a specific day to now & cumulative temp

2020-05-02 Thread Eric 972

Ah OK, thank you, I hadn't thought of that !

-- 
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/c7f3ea94-e7f9-4272-acb6-2596f1d99fe6%40googlegroups.com.

Re: [weewx-user] Python versions

Ah .. that will be the missing piece of the puzzle! Off to sort that
now, will report back.

Thanks!

On Sun, 3 May 2020 at 15:30, mwall  wrote:

> On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>>
>> I found this /etc/default
>>
>> WEEWX_PYTHON=python2
>>
>> WEEWX_BINDIR=/usr/share/weewx
>>
>> WEEWX_BIN=/usr/bin/weewxd
>>
>> WEEWX_CFG=/etc/weewx/weewx.conf
>>
>>
>> Changing it to python3 breaks weewx so I'll just leave well enough alone
>>
>
> you *should* be able to switch from python2 to python3 simply by changing
> the WEEWX_PYTHON line.  however, if you were running with python2 and you
> have not installed the python3 dependencies, then of course weewx won't run.
>
> m
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%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/CACjxfUtM_R7ZeBsCQ%2B4UoZPLDnFQQP3cMygOryLWNj5cHDsBtQ%40mail.gmail.com.

Re: [weewx-user] Python versions

On Saturday, May 2, 2020 at 9:11:51 PM UTC-4, Colin Larsen wrote:
>
> I found this /etc/default
>
> WEEWX_PYTHON=python2
>
> WEEWX_BINDIR=/usr/share/weewx
>
> WEEWX_BIN=/usr/bin/weewxd
>
> WEEWX_CFG=/etc/weewx/weewx.conf
>
>
> Changing it to python3 breaks weewx so I'll just leave well enough alone
>

you *should* be able to switch from python2 to python3 simply by changing 
the WEEWX_PYTHON line.  however, if you were running with python2 and you 
have not installed the python3 dependencies, then of course weewx won't run.

m 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/973baa2b-1c38-45c8-a3ed-630835e0bfdd%40googlegroups.com.

Re: [weewx-user] Python versions

On Saturday, May 2, 2020 at 9:12:41 PM UTC-4, Colin Larsen wrote:
>
> Whoops sorry /etc/default/weewx that should have been
>

colin has it right.  one of the things we did in the weewx4 packaging for 
debian, redhat (and soon suse and *bsd) is to put the parameters into 
/etc/default/weewx (it will be /etc/defaults/weewx on *bsd)

since the weewx installation is exactly the same for both python2 and 
python3, all you have to do is change the interpreter that invokes weewxd, 
wee_config, or any other weewx entry point.

there are scripts in /usr/bin/wee* and these simply pull in the variables 
from /etc/default/weewx then invoke the corresponding wee* 'binaries'

the /etc/init.d/weewx scripts for debian, redhad, suse, and *bsd use this 
pattern

if you install from setup.py then you would have to install 
/etc/default/weewx yourself (it is in the util directory)

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/01ea7447-8a09-4e0d-acc6-9f628dc1bdc6%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

On Saturday, May 2, 2020 at 2:27:49 PM UTC-4, mwall wrote:
>
> On Saturday, May 2, 2020 at 10:01:39 AM UTC-4, Tom Keffer wrote:
>>
>> The weewx usage map  shows 26 
>> installations (out of 1471 registered stations), or less than 2%. That's 
>> not enough usage to justify the work. Get your friends to use it!
>>
>> Still, I'll see what I can do...
>>
>>>
>>>
> tom,
>
> i'll take care of it - its one of my drivers.  but its over 50F for the 
> first time in weeks, so it will have to wait until after sunset US eastern 
> time :)
>

sorry to reply to myself, but a little update: the certs expired on the vpn 
on which my wh23xx is running, so i won't be able to test with the hardware 
until i get on site.  luckily that *should* be tuesday, not months from now.

-- 
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/87200d54-73e6-450a-9e61-7099e36a5856%40googlegroups.com.

Re: [weewx-user] Re: Rasbian 10 - Update failed

2020-05-02 Thread John Kline

> TypeError: a bytes-like object is required, not 'str'
I do not use this extension, but the error is an indication that the extension 
was not ported to work with Python 3 (bytes and str are different types in 
Python 3).

I don’t know if it the author claims WeeWX 4 comparability, but if he does, he 
may not have tested it with WeeWX 4/Python 3.


> On May 1, 2020, at 9:53 AM, Manfred Maier  wrote:
> 
> 
> Apologies for talking to myself here :)
> 
> I've now updated the SFTP extension. 
> At least the error massaged changed:
> 
> pi@raspberrypi:~ $ sudo wee_reports
> 
> Using configuration file /etc/weewx/weewx.conf
> 
> Generating for all time
> 
> Traceback (most recent call last):
> 
>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
> 
> obj.start()
> 
>   File "/usr/share/weewx/weewx/reportengine.py", line 280, in start
> 
> self.run()
> 
>   File "/usr/share/weewx/user/sftp.py", line 259, in run
> 
> n = uploader.run()
> 
>   File "/usr/share/weewx/user/sftp.py", line 89, in run
> 
> (timestamp, fileset) = self.get_last_upload()
> 
>   File "/usr/share/weewx/user/sftp.py", line 158, in get_last_upload
> 
> timestamp = cPickle.load(f)
> 
> TypeError: a bytes-like object is required, not 'str'
> 
> 
> 
> 
> 
> Now I'm really running out of ideas.
> 
> 
>> 
> 
> -- 
> 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/1e213c8a-579e-44c8-9da6-c73b47071061%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/E485C8F2-58BB-4446-BC50-150A83DD4F27%40johnkline.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

Interesting, there is a 'Number of wind samples' field in the archive 
record emitted by the console/logger but my reading of the vantage driver 
is that it is used to calculate rxCheckPercent but otherwise ignored. I 
thought the vantage driver passed on almost everything and let the 
user/WeeWX decide whether to use it or lose it, apparently not. One for Tom 
I suspect.

Gary

On Sunday, 3 May 2020 12:09:25 UTC+10, Hyrules wrote:
>
> Thanks for the clarification Gary. This seems to be exactly what was 
> happening here. Everything seems to be in order for now thanks. 
>
> Now my only question left is : is it possible to get the number of Wind 
> Samples sent by the weather station or do I have to calculate it from the 
> rxCheckPercent and kinda reverse the _rxcheck function in the driver ?
>
> On Saturday, May 2, 2020 at 7:44:53 PM UTC-4, gjr80 wrote:
>>
>> Quite possibly you had corrupt station memory 
>> ,
>>  
>> a symptom of which is that loop packets are received from the 
>> console/logger but (hardware) archive records are not. If you happen to be 
>> running with software record generation you will see no problems since 
>> WeeWX is synthesising archive records from the loop packets rather than 
>> asking the console/logger for archive records. However, when you change to 
>> hardware record generation WeeWX now asks the console/logger for an archive 
>> record but the console/logger cannot provide one (due to corrupt memory). 
>> WeeWX carries on but with no archive records being saved to archive; 
>> reports are run but with no updated data, basically the system does not 
>> update. When you look at the log it is quite evident; no records being 
>> saved but reports being run.
>>
>> The usual fix is to clear the device memory with wee_device, but 
>> changing the console archive interval also clears the memory thus fixing 
>> the corrupt station memory.
>>
>> Gary
>>
>> On Sunday, 3 May 2020 06:05:21 UTC+10, Hyrules wrote:
>>>
>>> ok we have a winner ! I used wee_device to set the interval to 1 minutes 
>>> and settings the interval of archive in weewx.conf as I like it and bam ! 
>>> Record coming in and rxCheckPercent populated !
>>>
>>> Thanks for your help and time Tom. Keep up the good work.
>>>
>>> On Saturday, May 2, 2020 at 3:53:11 PM UTC-4, Hyrules wrote:

 Never had any problem with the logger itself . I just reinstalled a 
 fresh version of weewx 4.0 and remove every addons I had as well and skin 
 and I still don’t get a REC when I run weewxd. Plenty of loops coming in 
 but the logger does not seems to be pushing any records or weewx grabbing 
 a 
 record. I’ve been running this for at least an hour and looking at the 
 screen. This station has nothing special. it has a USB logger and I got it 
 about 10 years ago. Still working really well.

 *From:* weewx...@googlegroups.com  *On 
 Behalf Of *Tom Keffer
 *Sent:* May 2, 2020 15:47
 *To:* weewx-user 
 *Subject:* Re: [weewx-user] Re: rxCheckPercent always zero and number 
 of wind samples

 The Vantage loggers work very well, with one flaw: they don't get it 
 right over daylight savings time transitions. Other than that, there's no 
 reason not to use them.

 -tk

 On Sat, May 2, 2020 at 12:20 PM Hyrules  wrote:

 I don’t understand why I was on software generation I don’t remember 
 why I would prefer software over hardware. I still haven’t seen a archive 
 packet that’s really odd.

 On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:

 There must have been some reason you were using software record 
 generation. You may "fix" this, but break something else!

 On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:

 That must be it. The setting record_generation was software changed it 
 to hardware in weewx.conf. Waiting for a archive packet.

 On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:

 Are you using software record generation?

 If so, weewx will not retrieve the archive record from the logger and, 
 instead, calculates the archive record in software. The logger is what 
 supplies the number of wind samples, so it is only available if you 
 download an archive record.

 -tk

 On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:

 Well that's not it. I ahve reflashed with the wireless version and 
 still not seeing the rxCheckPercent and Wind Samples

 On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:

 Crap I think I have and Idea what is happening I might have flashed the 
 cabled version firmware. Will try to reflash the wireless version because 
 my station is

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

Thanks for the clarification Gary. This seems to be exactly what was 
happening here. Everything seems to be in order for now thanks. 

Now my only question left is : is it possible to get the number of Wind 
Samples sent by the weather station or do I have to calculate it from the 
rxCheckPercent and kinda reverse the _rxcheck function in the driver ?

On Saturday, May 2, 2020 at 7:44:53 PM UTC-4, gjr80 wrote:
>
> Quite possibly you had corrupt station memory 
> ,
>  
> a symptom of which is that loop packets are received from the 
> console/logger but (hardware) archive records are not. If you happen to be 
> running with software record generation you will see no problems since 
> WeeWX is synthesising archive records from the loop packets rather than 
> asking the console/logger for archive records. However, when you change to 
> hardware record generation WeeWX now asks the console/logger for an archive 
> record but the console/logger cannot provide one (due to corrupt memory). 
> WeeWX carries on but with no archive records being saved to archive; 
> reports are run but with no updated data, basically the system does not 
> update. When you look at the log it is quite evident; no records being 
> saved but reports being run.
>
> The usual fix is to clear the device memory with wee_device, but changing 
> the console archive interval also clears the memory thus fixing the corrupt 
> station memory.
>
> Gary
>
> On Sunday, 3 May 2020 06:05:21 UTC+10, Hyrules wrote:
>>
>> ok we have a winner ! I used wee_device to set the interval to 1 minutes 
>> and settings the interval of archive in weewx.conf as I like it and bam ! 
>> Record coming in and rxCheckPercent populated !
>>
>> Thanks for your help and time Tom. Keep up the good work.
>>
>> On Saturday, May 2, 2020 at 3:53:11 PM UTC-4, Hyrules wrote:
>>>
>>> Never had any problem with the logger itself . I just reinstalled a 
>>> fresh version of weewx 4.0 and remove every addons I had as well and skin 
>>> and I still don’t get a REC when I run weewxd. Plenty of loops coming in 
>>> but the logger does not seems to be pushing any records or weewx grabbing a 
>>> record. I’ve been running this for at least an hour and looking at the 
>>> screen. This station has nothing special. it has a USB logger and I got it 
>>> about 10 years ago. Still working really well.
>>>
>>> *From:* weewx...@googlegroups.com  *On 
>>> Behalf Of *Tom Keffer
>>> *Sent:* May 2, 2020 15:47
>>> *To:* weewx-user 
>>> *Subject:* Re: [weewx-user] Re: rxCheckPercent always zero and number 
>>> of wind samples
>>>
>>>  
>>>
>>> The Vantage loggers work very well, with one flaw: they don't get it 
>>> right over daylight savings time transitions. Other than that, there's no 
>>> reason not to use them.
>>>
>>>  
>>>
>>> -tk
>>>
>>>  
>>>
>>> On Sat, May 2, 2020 at 12:20 PM Hyrules  wrote:
>>>
>>> I don’t understand why I was on software generation I don’t remember why 
>>> I would prefer software over hardware. I still haven’t seen a archive 
>>> packet that’s really odd.
>>>
>>>
>>>
>>> On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:
>>>
>>> There must have been some reason you were using software record 
>>> generation. You may "fix" this, but break something else!
>>>
>>>  
>>>
>>> On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:
>>>
>>> That must be it. The setting record_generation was software changed it 
>>> to hardware in weewx.conf. Waiting for a archive packet.
>>>
>>> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>>>
>>> Are you using software record generation?
>>>
>>>  
>>>
>>> If so, weewx will not retrieve the archive record from the logger and, 
>>> instead, calculates the archive record in software. The logger is what 
>>> supplies the number of wind samples, so it is only available if you 
>>> download an archive record.
>>>
>>>  
>>>
>>> -tk
>>>
>>>  
>>>
>>> On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:
>>>
>>> Well that's not it. I ahve reflashed with the wireless version and still 
>>> not seeing the rxCheckPercent and Wind Samples
>>>
>>> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>>>
>>> Crap I think I have and Idea what is happening I might have flashed the 
>>> cabled version firmware. Will try to reflash the wireless version because 
>>> my station is wireless.
>>>
>>> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>>
>>> Hi everyone,
>>>
>>>  
>>>
>>> I have a vantage pro 2 and was wondering what might be the issue of the 
>>> following my rc_CheckPercent is always at zero. I have a point in my sql 
>>> data when I temporarily got some value but at the moment it's zero. This is 
>>> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>>>
>>> Also is it possible to get the number of wind sample ? The skin that i'm 
>>> creating requires it and i have hard time finding any info on

[weewx-user] Re: Raspberry Pi crashed so I had to reinstall WeeWx

2020-05-02 Thread Michael Sanphillipo

I was able to recover the weewx.sdb file and copied it over so I'm only 
missing May 1st and 2nd. Much better than a whole year. Is there a way to 
edit weewx.sdb?

On Saturday, May 2, 2020 at 7:55:42 PM UTC-4, Michael Sanphillipo wrote:
>
> My Pi SD card was corrupted and I had to reload Debian along with WeeWx. I 
> lost a years' worth of data. Is there a way to recover the files and where 
> should I look on my old SD card?
>

-- 
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/bd455dd1-068b-4349-8fef-fcb10608a46f%40googlegroups.com.

Re: [weewx-user] Re: 4.x logging format

simplified logging stanza doesn’t work and shows type conversion fix needed.
details follow...

using that simplified stanza in weewx.conf gives runtime error:

  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
 line 381, in resolve
name = s.split('.')
AttributeError: 'NoneType' object has no attribute 'split'

adding class line back into config viz:

[Logging]
#  [[loggers]]
#[[[root]]]
#  level = DEBUG
#  propogate = True
#  handlers = syslog, rotate
  [[handlers]]
[[[rotate]]]
#  level = DEBUG
#  formatter = standard
  class = logging.handlers.RotatingFileHandler
  filename = /tmp/weewx.log
#  maxBytes = 1000
#  backupCount = 2

does not give immediate runtime error
but also adds no logging messages to /tmp/weewx.log

RotatingFileHandler documentation says defaults for maxBytes and backupCount 
are zero
and either of these being zero means logging is not done.
experimentation shows documentation is correct i.e. this config does not work
therefore both maxBytes and backupCount must be definable to be non-zero
so we need the type conversion fix

note: i am using /tmp/weewx.log here because i am presently fiddling with new 
version on test system and don’t want weewxd running rampant with root 
privilege. at least, not yet :-)


> On 3 May 2020, at 5:07 am, Tom Keffer  wrote:
> 
> Great ideas! Thanks for your thoughts.
> 
> Try this version of weeutil/logger.py. It includes a shim that does the 
> proper type conversion before passing on arguments to 
> logging.handlers.RotatingFileHandler.
> 
> To use should be as simple as adding this to weewx.conf (alas, NOT TESTED):
> 
> [Logging]
>   [[loggers]]
> [[[root]]]
>   handlers = syslog, rotate
>   [[handlers]]
> [[[rotate]]]
>   filename = /tmp/weewx.log
> 
> By default, it logs to /var/log/weewx.log. Hence, the need to override that 
> option if you want to log to /tmp/weewx.log.
> 
> -tk
> 
> 
> On Sat, May 2, 2020 at 8:05 AM Graham Eddy  > wrote:
> i think we all agree that syslog on macos is a lost cause.
> the corollary is that pointing python logging at syslog (via 
> logging.handlers.SysLogHandler) is doomed
> 
> i accept that syslog works fine on most platforms, but it is not feasible for 
> macos
> but there is the simple alternative for macos users of using a different 
> handler:
> 
> i patched log_dict in bin/weeutil/logger.py to add a 
> logging.handlers.RotatingFileHandler and it worked fine.
> adding it via weewx.conf gives a type conversion error that seems simple to 
> fix.
> with the fix, i would suggest this be added to the macos installation 
> instructions for user to add to weewx.conf (or make it part of the 
> installation process)
> 
> details follow...
> 
> weewx.conf (yes, using that ‘root’ hack introduced to work around a ConfigObj 
> limitation):
> 
> [Logging]
>   [[loggers]]
> [[[root]]]
>   level = DEBUG
>   propogate = True
>   handlers = syslog, rotate
>   [[handlers]]
> [[[rotate]]]
>   level = DEBUG
>   formatter = standard
>   class = logging.handlers.RotatingFileHandler
>   filename = /tmp/weewx.log
>   maxBytes = 1000
>   backupCount = 2

-- 
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/DB9C3A14-40D2-4B9A-9604-19ED16BC9BAB%40gmail.com.

Re: [weewx-user] Python versions

Whoops sorry /etc/default/weewx that should have been

On Sun, 3 May 2020 at 13:11, Colin Larsen  wrote:

> I found this /etc/default
>
> WEEWX_PYTHON=python2
>
> WEEWX_BINDIR=/usr/share/weewx
>
> WEEWX_BIN=/usr/bin/weewxd
>
> WEEWX_CFG=/etc/weewx/weewx.conf
>
>
> Changing it to python3 breaks weewx so I'll just leave well enough alone
>
>
> Colin
>
> On Sun, 3 May 2020 at 12:54, Colin Larsen  wrote:
>
>> Hi Graham
>>
>> Thanks for that and I understand all of what you are saying - except I
>> have no idea whereabouts in /etc/init.d/weewx to change to make it use
>> Python3. I thought I might find the line command line containing weewxd in
>> there somewhere but alas no (or I've done a "boy look"). And I know enough
>> this part of the system to be dangerous, so I'll keep fingers off until I
>> can actually figure this out! Still learning lots here so appreciate the
>> patience and explanations :)
>>
>> Colin
>>
>> On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:
>>
>>> as others have already mentioned you can instruct use of python3 either
>>>  (a) system-wide e.g. /etc/default or defaults
>>>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
>>> .weewx.weewxd
>>>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>>>
>>> my platform (macos) provides python2.7 native not python3.7 and i
>>> hesitate to set system-wide in case it impacts some other platform-provided
>>> utilities. i find startup approach inconvenient on macos so i usually use
>>> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
>>> where macports puts python3
>>>
>>> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>>>
>>> Thanks Tom
>>>
>>> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
>>> that but to be honest the innards of that file is out of my depth.
>>>
>>> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>>>
 You will have to edit whatever script you use to start weewx as a
 daemon.

 Look in /etc/init.d/weewx. If not there, then
 /etc/systemd/system/weewx.service.

 -tk

 On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
 wrote:

> Hi all
>
> I know that this is buried somewhere in the threads of information,
> sorry apologies for not being able to find it.
>
> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
> method. Ihas Python3 installed but is still using Python2 as can be seen
> here. I thought I had read that if Python3 was already installed then the
> update would use that version - apparently not :)
>

>>> --
>>> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.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/CACjxfUsP%2B31UVQ2tKBVmLFTgkt9OxfM5t96hy3hxUtar6RjJvw%40mail.gmail.com.

Re: [weewx-user] Python versions

I found this /etc/default

WEEWX_PYTHON=python2

WEEWX_BINDIR=/usr/share/weewx

WEEWX_BIN=/usr/bin/weewxd

WEEWX_CFG=/etc/weewx/weewx.conf


Changing it to python3 breaks weewx so I'll just leave well enough alone


Colin

On Sun, 3 May 2020 at 12:54, Colin Larsen  wrote:

> Hi Graham
>
> Thanks for that and I understand all of what you are saying - except I
> have no idea whereabouts in /etc/init.d/weewx to change to make it use
> Python3. I thought I might find the line command line containing weewxd in
> there somewhere but alas no (or I've done a "boy look"). And I know enough
> this part of the system to be dangerous, so I'll keep fingers off until I
> can actually figure this out! Still learning lots here so appreciate the
> patience and explanations :)
>
> Colin
>
> On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:
>
>> as others have already mentioned you can instruct use of python3 either
>>  (a) system-wide e.g. /etc/default or defaults
>>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
>> .weewx.weewxd
>>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>>
>> my platform (macos) provides python2.7 native not python3.7 and i
>> hesitate to set system-wide in case it impacts some other platform-provided
>> utilities. i find startup approach inconvenient on macos so i usually use
>> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
>> where macports puts python3
>>
>> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>>
>> Thanks Tom
>>
>> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
>> that but to be honest the innards of that file is out of my depth.
>>
>> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>>
>>> You will have to edit whatever script you use to start weewx as a daemon.
>>>
>>> Look in /etc/init.d/weewx. If not there, then
>>> /etc/systemd/system/weewx.service.
>>>
>>> -tk
>>>
>>> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
>>> wrote:
>>>
 Hi all

 I know that this is buried somewhere in the threads of information,
 sorry apologies for not being able to find it.

 I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
 method. Ihas Python3 installed but is still using Python2 as can be seen
 here. I thought I had read that if Python3 was already installed then the
 update would use that version - apparently not :)

>>>
>> --
>> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.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/CACjxfUviu1eGsfs5hXO4wOeivJCN267BKYk74-kF_v5DvxRtHQ%40mail.gmail.com.

Re: [weewx-user] need to modify daily rain in weewx.sdb

wview was brilliant in its time but it was brittle.
weewx is a lot more forgiving and flexible so “having a bit of a fiddle” is 
fine (as long as you save the master data beforehand :-)
the biggest rigidity removed was wview’s reliance on invariant archiveInterval 
- weewx is happy to intermix timestamps so you need not fear getting *every* 
record *exactly right*

with respect to database, weewx like wview can regenerate everything from the 
core data.
keep the ‘archive’ table intact, and there are a couple of weewx tools that 
will rebuild (or expand) everything

in this context, using sql directly on database is relatively safe
(just slide saved copy back into place if it gets stuffed up)

> On 3 May 2020, at 1:50 am, Bob Grattan  wrote:
> 
> 2. Once the "rain" amount in weewx.sdb is modified, how do I get the system 
> to incorporate the new total in the various displays such as for month and 
> year? In wview I was able to erase certain indexes and they were recreated 
> using the new values from the db; however, I'm not sure how this works in 
> weewx.

-- 
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/35B65D97-2500-45E2-B36D-2692D7AD644E%40gmail.com.

Re: [weewx-user] Python versions

Hi Graham

Thanks for that and I understand all of what you are saying - except I have
no idea whereabouts in /etc/init.d/weewx to change to make it use Python3.
I thought I might find the line command line containing weewxd in there
somewhere but alas no (or I've done a "boy look"). And I know enough this
part of the system to be dangerous, so I'll keep fingers off until I can
actually figure this out! Still learning lots here so appreciate the
patience and explanations :)

Colin

On Sun, 3 May 2020 at 12:44, Graham Eddy  wrote:

> as others have already mentioned you can instruct use of python3 either
>  (a) system-wide e.g. /etc/default or defaults
>  (b) startup e.g. /etc/init.d/weewx or /Library/LaunchDaemons/com
> .weewx.weewxd
>  (c) embedded e.g. shebang (insert #!python3 in first line of weewxd)
>
> my platform (macos) provides python2.7 native not python3.7 and i hesitate
> to set system-wide in case it impacts some other platform-provided
> utilities. i find startup approach inconvenient on macos so i usually use
> embedded (shebang), in my case #!/opt/local/bin/python3.7 because that’s
> where macports puts python3
>
> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
>
> Thanks Tom
>
> Well /etc/init.d/weewx is there and the other one isn't so I'll go with
> that but to be honest the innards of that file is out of my depth.
>
> On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:
>
>> You will have to edit whatever script you use to start weewx as a daemon.
>>
>> Look in /etc/init.d/weewx. If not there, then
>> /etc/systemd/system/weewx.service.
>>
>> -tk
>>
>> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
>> wrote:
>>
>>> Hi all
>>>
>>> I know that this is buried somewhere in the threads of information,
>>> sorry apologies for not being able to find it.
>>>
>>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>>> method. Ihas Python3 installed but is still using Python2 as can be seen
>>> here. I thought I had read that if Python3 was already installed then the
>>> update would use that version - apparently not :)
>>>
>>
> --
> 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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.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/CACjxfUsK1bUg9xt0_ecvhQG3%3DYgMya%3DjeET_1YsvrxMCukBwoA%40mail.gmail.com.

[weewx-user] Re: Raspberry Pi crashed so I had to reinstall WeeWx

On Saturday, May 2, 2020 at 4:55:42 PM UTC-7, Michael Sanphillipo wrote:
>
> My Pi SD card was corrupted and I had to reload Debian along with WeeWx. I 
> lost a years' worth of data. Is there a way to recover the files and where 
> should I look on my old SD card?
>

If you reimaged your corrupt SD card, that data is gone almost certainly

FWIW, you might want to keep a couple $6 cards around in the future so if 
it ever happens again, you can install to a clean card and try to get your 
old data off the messed up one in parallel on a different system.  And as 
Tom said, do a backup occasionally of at least your weewx.sdb file.

-- 
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/edb5dcc7-16d2-485e-bf2b-85cc31c807b3%40googlegroups.com.

Re: [weewx-user] Python versions

as others have already mentioned you can instruct use of python3 either
 (a) system-widee.g. /etc/default or defaults
 (b) startupe.g. /etc/init.d/weewx or /Library/LaunchDaemons/com 
.weewx.weewxd
 (c) embedded   e.g. shebang (insert #!python3 in first line of weewxd)

my platform (macos) provides python2.7 native not python3.7 and i hesitate to 
set system-wide in case it impacts some other platform-provided utilities. i 
find startup approach inconvenient on macos so i usually use embedded 
(shebang), in my case #!/opt/local/bin/python3.7 because that’s where macports 
puts python3

> On 3 May 2020, at 10:30 am, Colin Larsen  wrote:
> 
> Thanks Tom
> 
> Well /etc/init.d/weewx is there and the other one isn't so I'll go with that 
> but to be honest the innards of that file is out of my depth. 
> 
> On Sun, 3 May 2020 at 12:20, Tom Keffer  > wrote:
> You will have to edit whatever script you use to start weewx as a daemon.
> 
> Look in /etc/init.d/weewx. If not there, then 
> /etc/systemd/system/weewx.service.
> 
> -tk
> 
> On Sat, May 2, 2020 at 5:13 PM Colin Larsen  > wrote:
> Hi all
> 
> I know that this is buried somewhere in the threads of information, sorry 
> apologies for not being able to find it.
> 
> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get method. 
> Ihas Python3 installed but is still using Python2 as can be seen here. I 
> thought I had read that if Python3 was already installed then the update 
> would use that version - apparently not :)

-- 
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/2BE0524D-D87A-45EB-8A45-A6ED93BD087B%40gmail.com.

Re: [weewx-user] Raspberry Pi crashed so I had to reinstall WeeWx

Hi,

If you do manage to access your old SD card and if you were using SQLite 
(the default) to store your data, the file you are after is weewx.sdb 
(again assuming you used the default) which is in /home/weewx/archive or 
/var/lib/weewx depending on how you installed WeeWX. Refer to Where to find 
things  in the 
User's 
Guide .

Gary

On Sunday, 3 May 2020 10:16:16 UTC+10, Tom Keffer wrote:
>
> That sounds like a systems ops question. Try googling for "recovering lost 
> files from sd card" or something like that.
>
> As a last resort, if you posted to the Weather Underground, you can use 
> wee_import  
> to import the data back in.
>
> Next time, make sure you do back ups!
>
>
>
> On Sat, May 2, 2020 at 4:55 PM Michael Sanphillipo  > wrote:
>
>> My Pi SD card was corrupted and I had to reload Debian along with WeeWx. 
>> I lost a years' worth of data. Is there a way to recover the files and 
>> where should I look on my old SD card?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0dff1031-8470-4110-ba4b-e22e9343f986%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/02c570da-fcd9-415a-ba35-6e7675020c6b%40googlegroups.com.

Re: [weewx-user] Python versions

Thanks Tom

Well /etc/init.d/weewx is there and the other one isn't so I'll go with
that but to be honest the innards of that file is out of my depth.

On Sun, 3 May 2020 at 12:20, Tom Keffer  wrote:

> You will have to edit whatever script you use to start weewx as a daemon.
>
> Look in /etc/init.d/weewx. If not there, then
> /etc/systemd/system/weewx.service.
>
> -tk
>
> On Sat, May 2, 2020 at 5:13 PM Colin Larsen 
> wrote:
>
>> Hi all
>>
>> I know that this is buried somewhere in the threads of information, sorry
>> apologies for not being able to find it.
>>
>> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
>> method. Ihas Python3 installed but is still using Python2 as can be seen
>> here. I thought I had read that if Python3 was already installed then the
>> update would use that version - apparently not :)
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>>
>> permitted by applicable law.
>>
>> Last login: Wed Apr 29 09:47:37 2020 from 192.168.20.45
>>
>> *pi@raspberrypi*:*~ $* ps -ef|grep weewx
>>
>> pi   30253 30223  0 12:01 pts/000:00:00 grep --color=auto *weewx*
>>
>> root 32235 1  5 May01 ?02:23:06 python2 /usr/share/
>> *weewx*/*weewx*d --daemon --pidfile=/var/run/*weewx*.pid /etc/*weewx*/
>> *weewx*.conf
>>
>> *pi@raspberrypi*:*~ $* python3 --version
>>
>> Python 3.5.3
>>
>> *pi@raspberrypi*:*~ $*
>>
>>
>> Whats the trick that I've missed to tell it to use Python3?
>>
>>
>> Many thanks
>>
>> Colin
>>
>> --
>> 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/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zECE9FUpRR_gZ6TCrRM6zp1msX0OhGPVpbFBgSpP93TdOA%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACjxfUsEoKux5XztQik_7Yj16fsj59EE6w02pJyQFFu5Evby%2BQ%40mail.gmail.com.

Re: [weewx-user] Python versions

You will have to edit whatever script you use to start weewx as a daemon.

Look in /etc/init.d/weewx. If not there, then
/etc/systemd/system/weewx.service.

-tk

On Sat, May 2, 2020 at 5:13 PM Colin Larsen  wrote:

> Hi all
>
> I know that this is buried somewhere in the threads of information, sorry
> apologies for not being able to find it.
>
> I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
> method. Ihas Python3 installed but is still using Python2 as can be seen
> here. I thought I had read that if Python3 was already installed then the
> update would use that version - apparently not :)
>
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>
> permitted by applicable law.
>
> Last login: Wed Apr 29 09:47:37 2020 from 192.168.20.45
>
> *pi@raspberrypi*:*~ $* ps -ef|grep weewx
>
> pi   30253 30223  0 12:01 pts/000:00:00 grep --color=auto *weewx*
>
> root 32235 1  5 May01 ?02:23:06 python2 /usr/share/*weewx*
> /*weewx*d --daemon --pidfile=/var/run/*weewx*.pid /etc/*weewx*/*weewx*
> .conf
>
> *pi@raspberrypi*:*~ $* python3 --version
>
> Python 3.5.3
>
> *pi@raspberrypi*:*~ $*
>
>
> Whats the trick that I've missed to tell it to use Python3?
>
>
> Many thanks
>
> Colin
>
> --
> 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/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECE9FUpRR_gZ6TCrRM6zp1msX0OhGPVpbFBgSpP93TdOA%40mail.gmail.com.

Re: [weewx-user] Raspberry Pi crashed so I had to reinstall WeeWx

That sounds like a systems ops question. Try googling for "recovering lost
files from sd card" or something like that.

As a last resort, if you posted to the Weather Underground, you can use
wee_import  to
import the data back in.

Next time, make sure you do back ups!



On Sat, May 2, 2020 at 4:55 PM Michael Sanphillipo 
wrote:

> My Pi SD card was corrupted and I had to reload Debian along with WeeWx. I
> lost a years' worth of data. Is there a way to recover the files and where
> should I look on my old SD card?
>
> --
> 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/0dff1031-8470-4110-ba4b-e22e9343f986%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/CAPq0zEDjrRBpHUyOvv7KfaJtiNJU8bN6pzTTffTPPQTYHTms%2Bg%40mail.gmail.com.

[weewx-user] Python versions

Hi all

I know that this is buried somewhere in the threads of information, sorry
apologies for not being able to find it.

I've just upgraded my Pi based station to Weewx 4.0 using the apt-get
method. Ihas Python3 installed but is still using Python2 as can be seen
here. I thought I had read that if Python3 was already installed then the
update would use that version - apparently not :)

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

permitted by applicable law.

Last login: Wed Apr 29 09:47:37 2020 from 192.168.20.45

*pi@raspberrypi*:*~ $* ps -ef|grep weewx

pi   30253 30223  0 12:01 pts/000:00:00 grep --color=auto *weewx*

root 32235 1  5 May01 ?02:23:06 python2 /usr/share/*weewx*/
*weewx*d --daemon --pidfile=/var/run/*weewx*.pid /etc/*weewx*/*weewx*.conf

*pi@raspberrypi*:*~ $* python3 --version

Python 3.5.3

*pi@raspberrypi*:*~ $*


Whats the trick that I've missed to tell it to use Python3?


Many thanks

Colin

-- 
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/CACjxfUv_62X8mX2Q8zG7SO6-9TWXgWaFHYLRO8LTnPmrMRTJYw%40mail.gmail.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

Nigel,

A comma can certainly cause a problem, the config file parser will treat 
the comma in the setting as a delimiter and return two settings. If you 
want your comma back you should be able to put it back if you enclose the 
entire setting in quotes, eg:

[[Text]]
text = "Real Time Gauges - Local Time is %H:%M, Next gauge update 
in..."


Gary

On Sunday, 3 May 2020 05:51:00 UTC+10, Devonian wrote:

> OK, I figured it for the scroller text - it doesn't like a comma (,) in 
> the text.
> I now have it running and picking up local time, by adding this to the 
> [RealtimegaugeData] in weewx.conf
> [[Text]]
> text = Real Time Gauges - Local Time is %H:%M - Next gauge update 
> in...
>
> Nigel.
>
>
> On Saturday, 2 May 2020 11:33:44 UTC+1, Devonian wrote:
>>
>> @ Gary,
>>
>> I've updated my SteelSeries and rtgd and all working now.
>> One small thing has changed since my original install is that the 
>> scroller text is now missing (had to remove the old method that picked up 
>> local time as it didn't like that now).
>> How do I add some text to the scroller now?
>>
>> Nigel.
>>
>

-- 
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/9ac68f21-f5d6-4b22-94c0-8d82f88f329b%40googlegroups.com.

[weewx-user] Raspberry Pi crashed so I had to reinstall WeeWx

2020-05-02 Thread Michael Sanphillipo

My Pi SD card was corrupted and I had to reload Debian along with WeeWx. I 
lost a years' worth of data. Is there a way to recover the files and where 
should I look on my old SD card?

-- 
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/0dff1031-8470-4110-ba4b-e22e9343f986%40googlegroups.com.

[weewx-user] Instructions for Install Of Python 3.8 on Raspberry Pi3

2020-05-02 Thread Burt Wizeman

I have seen a couple of issues regarding the install of Python 3.  I found 
this site that worked without flaw for my install onto my Pi3+.  I like to 
do things step by step.  So if you have had some issues with the Python 
portion of your upgrade, check this site out.  Ia Pi3.
Following this install, the install of WeeWx Version 4 went without a 
hiccup.

https://installvirtual.com/how-to-install-python-3-8-on-raspberry-pi-raspbian/
 


Burt
K4SRQ


-- 
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/e8f76aec-dd5f-4312-bbb6-5502b5c91e8e%40googlegroups.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

Quite possibly you had corrupt station memory 
,
 
a symptom of which is that loop packets are received from the 
console/logger but (hardware) archive records are not. If you happen to be 
running with software record generation you will see no problems since 
WeeWX is synthesising archive records from the loop packets rather than 
asking the console/logger for archive records. However, when you change to 
hardware record generation WeeWX now asks the console/logger for an archive 
record but the console/logger cannot provide one (due to corrupt memory). 
WeeWX carries on but with no archive records being saved to archive; 
reports are run but with no updated data, basically the system does not 
update. When you look at the log it is quite evident; no records being 
saved but reports being run.

The usual fix is to clear the device memory with wee_device, but changing 
the console archive interval also clears the memory thus fixing the corrupt 
station memory.

Gary

On Sunday, 3 May 2020 06:05:21 UTC+10, Hyrules wrote:
>
> ok we have a winner ! I used wee_device to set the interval to 1 minutes 
> and settings the interval of archive in weewx.conf as I like it and bam ! 
> Record coming in and rxCheckPercent populated !
>
> Thanks for your help and time Tom. Keep up the good work.
>
> On Saturday, May 2, 2020 at 3:53:11 PM UTC-4, Hyrules wrote:
>>
>> Never had any problem with the logger itself . I just reinstalled a fresh 
>> version of weewx 4.0 and remove every addons I had as well and skin and I 
>> still don’t get a REC when I run weewxd. Plenty of loops coming in but the 
>> logger does not seems to be pushing any records or weewx grabbing a record. 
>> I’ve been running this for at least an hour and looking at the screen. This 
>> station has nothing special. it has a USB logger and I got it about 10 
>> years ago. Still working really well.
>>
>> *From:* weewx...@googlegroups.com  <
>> weewx...@googlegroups.com > *On Behalf Of *Tom Keffer
>> *Sent:* May 2, 2020 15:47
>> *To:* weewx-user >
>> *Subject:* Re: [weewx-user] Re: rxCheckPercent always zero and number of 
>> wind samples
>>
>>  
>>
>> The Vantage loggers work very well, with one flaw: they don't get it 
>> right over daylight savings time transitions. Other than that, there's no 
>> reason not to use them.
>>
>>  
>>
>> -tk
>>
>>  
>>
>> On Sat, May 2, 2020 at 12:20 PM Hyrules > 
>> wrote:
>>
>> I don’t understand why I was on software generation I don’t remember why 
>> I would prefer software over hardware. I still haven’t seen a archive 
>> packet that’s really odd.
>>
>>
>>
>> On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:
>>
>> There must have been some reason you were using software record 
>> generation. You may "fix" this, but break something else!
>>
>>  
>>
>> On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:
>>
>> That must be it. The setting record_generation was software changed it to 
>> hardware in weewx.conf. Waiting for a archive packet.
>>
>> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>>
>> Are you using software record generation?
>>
>>  
>>
>> If so, weewx will not retrieve the archive record from the logger and, 
>> instead, calculates the archive record in software. The logger is what 
>> supplies the number of wind samples, so it is only available if you 
>> download an archive record.
>>
>>  
>>
>> -tk
>>
>>  
>>
>> On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:
>>
>> Well that's not it. I ahve reflashed with the wireless version and still 
>> not seeing the rxCheckPercent and Wind Samples
>>
>> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>>
>> Crap I think I have and Idea what is happening I might have flashed the 
>> cabled version firmware. Will try to reflash the wireless version because 
>> my station is wireless.
>>
>> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>
>> Hi everyone,
>>
>>  
>>
>> I have a vantage pro 2 and was wondering what might be the issue of the 
>> following my rc_CheckPercent is always at zero. I have a point in my sql 
>> data when I temporarily got some value but at the moment it's zero. This is 
>> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>>
>> Also is it possible to get the number of wind sample ? The skin that i'm 
>> creating requires it and i have hard time finding any info on it in the 
>> documentation.
>>
>>  
>>
>> Anyone has any input.
>>
>>  
>>
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%40googlegroups.com
>>  
>>

[weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Xant

Tom

Just to report, that is "nothing" to report (and that's a good thing)

WeeWx 4.0 working fine on my setup:

   - rPi 4
   - Python 3
   - WeatherFlow
   - QNAP NAS (as webserver)
   - Belchertown skin 1.1

Update was smooth. I still keeps the original path (instead 'home'), but 
just edited 'setup.cfg'.

--

For those that still keeps the original path, the following is my update 
'howto' for rPi:

1) Backup 
/etc/weewx
/usr/share/weewx

2) Download
# wget http://www.weewx.com/downloads/weewx-4.0.0.tar.gz (or other newer, 
if the case)
# tar zxvf [weewx-xxx.tar.gz]

3) Config
# cd weewx-xxx
# nano setup.cfg


- Edit to install locations
[install]
home = /etc/weewx
prefix =
exec-prefix =
install_lib = /usr/share/weewx
install_scripts = /usr/share/weewx

# ./setup.py build 
# ./setup.py install

- copy old files from backup, if necessary (as weewx.conf, extensions.py, 
or other)
# cp extensions.py - to - /usr/share/weewx/user
# cp [driver].py* - to - /usr/share/weewx/user

# service weewx start
# tail -f /var/log/syslog
# wee_reports

Xant

-- 
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/f839fcdb-ef5b-4a5f-905a-7797bccfc67d%40googlegroups.com.

Re: [weewx-user] Re: Ultimeter 2100 WeeWx Behind Actual Rain Rain Rate is Actual Rain Total

You could put the following in the [StdCalibrate] section of weewx.conf:

[StdCalibrate]
[[Corrections]]
dayRain = daily_rain

This will set type dayRain to what is being emitted by your hardware. It
will then be passed on to CWOP, instead of looked up in the database.

Unfortunately, CWOP also wants rain over the last 24 hours, and rain over
the last hour, but the Ultimeter does not emit those. So, they will
continue to have to be calculated from the database.

-tk

On Sat, May 2, 2020 at 2:22 PM Burt Wizeman  wrote:

> You are correct -  From weewxd after dumping some water into the bucket,
> the display reports .14 and in the output of weewxd  'daily_rain: 0.14'
> and  'rain_total 5.84' which was at 5.7 until I added the water for today's
> test.   I have attached the output.   So, is there a way for the hardware
> to directly send the data to the cwop and pws sentence, mapped
> appropriately, bypassing the calc?  Remember that both PWS and CWOP show
> the same rain.
>
> BTW, I installed Version 4 with Python 3.8.  No hitches!
>
> Thanks Tom
>
> On Friday, May 1, 2020 at 11:23:59 AM UTC-4, Tom Keffer wrote:
>>
>> I think the problem is differences in what "today's rain" means.
>>
>> The ultimeter driver emits observation types rain_total and daily_rain.
>> These are direct from the hardware, so they should match what you're seeing
>> on the console. You can check by running weewxd directly from the
>> command line. It will print out all values.
>>
>> However, the values being sent to CWOP are observation types rain24 and
>> dayRain. If they are not supplied by the hardware, then WeeWX calculates
>> them from the database.
>>
>> So, you're looking at two different things, both, in their own way,
>> correct.
>>
>> But, this makes me think that the Ultimeter driver really should be
>> emitting rain24 and dayRain.
>>
>> Run weewxd directly and see what it says.
>>
>> -tk
>>
>>
>>
>>
>> On Thu, Apr 30, 2020 at 9:05 PM Burt Wizeman  wrote:
>>
>>> Good Evening Tom,
>>>
>>> Thanks for taking a look at this.  No rain tonight so I poured some
>>> water into the bucket to get some data.  It happened at 22:40:15.  Now for
>>> some clarification:
>>> My Ultimeter currently reads .90 for the daily rain after the
>>> experimental water.  That is the total rain over 24 hours.  What is being
>>> sent in the string from WeeWx is .56 and .03 is the amount weewx sensed
>>> from my water dump into the rain bucket.
>>> So the Ultimeter says .90 now, the string to CWOP and PWS says .56.  I
>>> have included  a minicomp dump from the datastream out of the 2100.
>>>
>>>
>>>
>>> Thanks Again for your help
>>>
>>> Burt
>>> K4SRQ
>>>
>>>
>>>
>>> On Thursday, April 30, 2020 at 3:42:17 PM UTC-4, Tom Keffer wrote:

 Hi, Burt

 Unless you're sending sensitive password information, I'd prefer to
 keep the exchange here. That way, others can learn, and it becomes a
 thread-of-record should someone have a similar problem in the future.

 -tk

 On Thu, Apr 30, 2020 at 12:12 PM Burt Wizeman  wrote:

> Hey Tom,
> Earlier my numbers to you were wrong.  I caught it between updates
> from when I first noticed it.  The numbers were .53 at CWOP and PWS, .83 
> on
> the display.  Sorry, I was in a rush to get to work.  If I could have an
> email to contact you at, I am reviewing the app for our West Central
> Florida Section of the ARRL Technical Newsletter.  Peet is big here with
> Hams in Florida as they are on the other coast.  I will follow through 
> with
> data for debug=2.
>
> Thanks,
> Burt
> K4SRQ
> burt at k4srq.net
>
> On Thursday, April 30, 2020 at 11:40:48 AM UTC-4, Burt Wizeman wrote:
>>
>> Will do,
>> Thanks,
>> Burt
>>
>> On Thursday, April 30, 2020 at 10:09:49 AM UTC-4, Tom Keffer wrote:
>>>
>>> 0x53 is actually 83 decimal.
>>>
>>> Looking through the Ultimeter code, it seems to be converted from
>>> hexadecimal to decimal correctly.
>>>
>>> Try running with debug=2. The driver will include the raw data in
>>> the system log.
>>>
>>> -tk
>>>
>>> On Thu, Apr 30, 2020 at 6:24 AM Burt Wizeman 
>>> wrote:
>>>
 Still looking into the rain.  To refresh the discussion, as of the
 moment of this writing, the Ultimeter is displaying .82 inches since
 midnight.  It is at midnight that the daily data is reset to 0.  Yet, 
 WeeWx
 in Linux and CWOP show .53. 53 HEX is 82 Decimal!   What is happening 
 is
 that the number 53HEX is being sent from the Ultimeter data string 
 which is
 Hex but displays .82 decimal on the display which is expected.  But 
 what
 CWOP is getting is the HEX value of .53.  This is labeled as Rain
 last 24 hours 0.53 inches
 So the driver is not converting the Hex 53 to the decimal
 equivalent, it is

Re: [weewx-user] Re: Ultimeter 2100 WeeWx Behind Actual Rain Rain Rate is Actual Rain Total

2020-05-02 Thread Burt Wizeman

You are correct -  From weewxd after dumping some water into the bucket, 
the display reports .14 and in the output of weewxd  'daily_rain: 0.14' 
and  'rain_total 5.84' which was at 5.7 until I added the water for today's 
test.   I have attached the output.   So, is there a way for the hardware 
to directly send the data to the cwop and pws sentence, mapped 
appropriately, bypassing the calc?  Remember that both PWS and CWOP show 
the same rain.

BTW, I installed Version 4 with Python 3.8.  No hitches!

Thanks Tom 

On Friday, May 1, 2020 at 11:23:59 AM UTC-4, Tom Keffer wrote:
>
> I think the problem is differences in what "today's rain" means.
>
> The ultimeter driver emits observation types rain_total and daily_rain. 
> These are direct from the hardware, so they should match what you're seeing 
> on the console. You can check by running weewxd directly from the command 
> line. It will print out all values.
>
> However, the values being sent to CWOP are observation types rain24 and 
> dayRain. If they are not supplied by the hardware, then WeeWX calculates 
> them from the database.
>
> So, you're looking at two different things, both, in their own way, 
> correct.
>
> But, this makes me think that the Ultimeter driver really should be 
> emitting rain24 and dayRain.
>
> Run weewxd directly and see what it says.
>
> -tk
>
>
>
>
> On Thu, Apr 30, 2020 at 9:05 PM Burt Wizeman  > wrote:
>
>> Good Evening Tom,
>>
>> Thanks for taking a look at this.  No rain tonight so I poured some water 
>> into the bucket to get some data.  It happened at 22:40:15.  Now for some 
>> clarification:
>> My Ultimeter currently reads .90 for the daily rain after the 
>> experimental water.  That is the total rain over 24 hours.  What is being 
>> sent in the string from WeeWx is .56 and .03 is the amount weewx sensed 
>> from my water dump into the rain bucket. 
>> So the Ultimeter says .90 now, the string to CWOP and PWS says .56.  I 
>> have included  a minicomp dump from the datastream out of the 2100.
>>
>>
>>
>> Thanks Again for your help
>>
>> Burt
>> K4SRQ
>>
>>
>>
>> On Thursday, April 30, 2020 at 3:42:17 PM UTC-4, Tom Keffer wrote:
>>>
>>> Hi, Burt
>>>
>>> Unless you're sending sensitive password information, I'd prefer to keep 
>>> the exchange here. That way, others can learn, and it becomes a 
>>> thread-of-record should someone have a similar problem in the future.
>>>
>>> -tk
>>>
>>> On Thu, Apr 30, 2020 at 12:12 PM Burt Wizeman  wrote:
>>>
 Hey Tom,
 Earlier my numbers to you were wrong.  I caught it between updates from 
 when I first noticed it.  The numbers were .53 at CWOP and PWS, .83 on the 
 display.  Sorry, I was in a rush to get to work.  If I could have an email 
 to contact you at, I am reviewing the app for our West Central Florida 
 Section of the ARRL Technical Newsletter.  Peet is big here with Hams in 
 Florida as they are on the other coast.  I will follow through with data 
 for debug=2.

 Thanks,
 Burt
 K4SRQ
 burt at k4srq.net

 On Thursday, April 30, 2020 at 11:40:48 AM UTC-4, Burt Wizeman wrote:
>
> Will do,
> Thanks,
> Burt
>
> On Thursday, April 30, 2020 at 10:09:49 AM UTC-4, Tom Keffer wrote:
>>
>> 0x53 is actually 83 decimal. 
>>
>> Looking through the Ultimeter code, it seems to be converted from 
>> hexadecimal to decimal correctly. 
>>
>> Try running with debug=2. The driver will include the raw data in the 
>> system log.
>>
>> -tk
>>
>> On Thu, Apr 30, 2020 at 6:24 AM Burt Wizeman  
>> wrote:
>>
>>> Still looking into the rain.  To refresh the discussion, as of the 
>>> moment of this writing, the Ultimeter is displaying .82 inches since 
>>> midnight.  It is at midnight that the daily data is reset to 0.  Yet, 
>>> WeeWx 
>>> in Linux and CWOP show .53. 53 HEX is 82 Decimal!   What is happening 
>>> is 
>>> that the number 53HEX is being sent from the Ultimeter data string 
>>> which is 
>>> Hex but displays .82 decimal on the display which is expected.  But 
>>> what 
>>> CWOP is getting is the HEX value of .53.  This is labeled as Rain 
>>> last 24 hours 0.53 inches 
>>> So the driver is not converting the Hex 53 to the decimal 
>>> equivalent, it is passing it through giving CWOP .53
>>> I won't be able to look at the driver until Saturday.  Can you point 
>>> me to the Ultimeter driver section for the function to convert data to 
>>> Hex?
>>>
>>> Thanks,
>>> Burt
>>> K4SRQ
>>>
>>>
>>> On Saturday, April 25, 2020 at 12:01:31 AM UTC-4, Burt Wizeman wrote:

 WeeWix is treating Rain Rate as the actual Rain Total for the day 
 when running with the Ultimeter 2100.  Throughout this storm, the rain 
 gauge data displayed on the Ultimeter has been quite a bit ahead of 
 what 
 WeeWix is generating

[weewx-user] Re: Belchertown highcharts : from a specific day to now & cumulative temp

Hi Eric,
concerning your first question: What version of weewx are you using? 

I've been on 3.9.2 and the timespan_specific also didn't work for me.
After upgrading to version 4.0 (Python 3) the specific timespan now works.

Manfred 


Am Freitag, 1. Mai 2020 10:43:03 UTC+2 schrieb Eric 972:
>
> Hi all,
> I am a farmer and I would like to follow my sowing of barley since the 
> sowing date, especially with rain and cumulative temperature which are 
> relevant parameters for analyzing growth.
>
> 1. I used timespan parameters like "2019 bomb cyclone example" but it 
> does'nt work. The sowing date is 14th of April. 
>
> 2. We all know rainTotal, but how could we obtain something like tempTotal 
> which should be the sum of average daily temp from the sewing date to now.
>
> Thanks in advance. 
>
> Sorry for my froggy English lamguage
>
>

-- 
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/20ae61a8-4024-429a-a8ec-a3a113addacb%40googlegroups.com.

[weewx-user] Re: weewx.wxservices: Unknown extensible type 'UV'

On Saturday, May 2, 2020 at 12:38:34 PM UTC-7, dshanske wrote:
>
> I thought UV was already there, but this keeps coming up in the logs. Is 
> there something I'm not understanding?
>

I think you're missing the 'how to report a bug' frequently asked question 
and guidance.

We can do little without seeing your logs. 

-- 
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/bd5957d6-99f7-468d-addb-d8ea35dec8eb%40googlegroups.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

On Saturday, May 2, 2020 at 1:37:30 PM UTC-7, Manfred Maier wrote:
>
> 1) Is there somewhere a list of packages that should be updated to Python 
> 3?
>

http://www.weewx.com/docs/setup.htm has a nice list

 

-- 
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/e68f800a-e384-4a04-917d-4f47848b02a6%40googlegroups.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

User 'Dale' nailed it!

After installing ephem for Python3 I have maxSolarRad back in my database 
:). 
Thanks so much! The support here is absolutely fantastic!

Three related questions:
1) Is there somewhere a list of packages that should be updated to Python 3?
2) Is there a way to calculate maxSolarRad for the missing times in the 
database?
3) Is there somewhere a 'piggybank' for the weewx developers? Haven't found 
anything on the website.

Manfred 



Am Samstag, 2. Mai 2020 22:24:10 UTC+2 schrieb Tom Keffer:
>
> Manfred, user 'Dale' suggested to me offline that the problem could be 
> that you have not installed the package 'ephem' for Python 3.
>
> *sudo apt install python3-ephem*
>
> -tk
>
>
>>>
>>>

-- 
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/f10ec4eb-03ac-48bb-878e-e404d1d8ab26%40googlegroups.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

Manfred, user 'Dale' suggested to me offline that the problem could be that
you have not installed the package 'ephem' for Python 3.

*sudo apt install python3-ephem*

-tk

On Sat, May 2, 2020 at 1:20 PM Tom Keffer  wrote:

> That looks normal.
>
> When you run weewxd directly from the command line, what do you see for
> maxSolarRad values? Check both LOOP packets (marked with LOOP:) and archive
> records (marked with REC:)
>
> -tk
>
> On Sat, May 2, 2020 at 1:12 PM Manfred Maier 
> wrote:
>
>> Here you go.
>> syslog since the restart of weewx
>>
>> --
>> 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/1325bd11-dfd0-4683-98aa-ae2835321cb0%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/CAPq0zEBzDuRXcww3Wf-wm8FkP9JQ36qtXYCY-pNhZniYJvA8Kw%40mail.gmail.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

That looks normal.

When you run weewxd directly from the command line, what do you see for
maxSolarRad values? Check both LOOP packets (marked with LOOP:) and archive
records (marked with REC:)

-tk

On Sat, May 2, 2020 at 1:12 PM Manfred Maier 
wrote:

> Here you go.
> syslog since the restart of weewx
>
> --
> 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/1325bd11-dfd0-4683-98aa-ae2835321cb0%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/CAPq0zEC8v2F9K16t3L6s0Nu1W4fE4G4u%2B0fdyCg7K6%2BdPsgyuw%40mail.gmail.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

Here you go.
syslog since the restart of weewx

-- 
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/1325bd11-dfd0-4683-98aa-ae2835321cb0%40googlegroups.com.
May  2 21:58:00 raspberrypi systemd[1]: Starting LSB: weewx weather system...
May  2 21:58:00 raspberrypi weewx[2187] INFO __main__: Initializing weewx 
version 4.0.0
May  2 21:58:00 raspberrypi weewx[2187] INFO __main__: Using Python 3.7.3 
(default, Apr  3 2019, 05:39:12) #012[GCC 8.2.0]
May  2 21:58:00 raspberrypi weewx[2187] INFO __main__: Platform 
Linux-4.19.58-v7l+-armv7l-with-debian-10.0
May  2 21:58:00 raspberrypi weewx[2187] INFO __main__: Locale is 'de_DE.UTF-8'
May  2 21:58:00 raspberrypi weewx[2187] INFO __main__: PID file is 
/var/run/weewx.pid
May  2 21:58:00 raspberrypi weewx[2191] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
May  2 21:58:00 raspberrypi weewx[2191] DEBUG __main__: Initializing engine
May  2 21:58:00 raspberrypi weewx[2191] INFO weewx.engine: Loading station type 
Meteostick (user.meteostick)
May  2 21:58:00 raspberrypi weewx[2175]: Starting weewx weather system: weewx.
May  2 21:58:00 raspberrypi systemd[1]: Started LSB: weewx weather system.
May  2 21:58:00 raspberrypi /weewxd: meteostick: driver version is 0.61
May  2 21:58:00 raspberrypi /weewxd: meteostick: using rain_bucket_type 1
May  2 21:58:00 raspberrypi /weewxd: meteostick: sensor map is: {'pressure': 
'pressure', 'inTemp': 'temp_in', 'windSpeed': 'wind_speed', 'windDir': 
'wind_dir', 'outTemp': 'temperature', 'outHumidity': 'humidity', 'inHumidity': 
'humidity_in', 'radiation': 'solar_radiation', 'UV': 'uv', 'rxCheckPercent': 
'pct_good', 'soilTemp1': 'soil_temp_1', 'soilTemp2': 'soil_temp_2', 
'soilTemp3': 'soil_temp_3', 'soilTemp4': 'soil_temp_4', 'soilMoist1': 
'soil_moisture_1', 'soilMoist2': 'soil_moisture_2', 'soilMoist3': 
'soil_moisture_3', 'soilMoist4': 'soil_moisture_4', 'leafWet1': 
'leaf_wetness_1', 'leafWet2': 'leaf_wetness_2', 'leafTemp1': 'leaf_temp_1', 
'leafTemp2': 'leaf_temp_2', 'extraTemp1': 'temp_1', 'extraTemp2': 'temp_2', 
'extraTemp3': 'temp_3', 'extraHumid1': 'humid_1', 'extraHumid2': 'humid_2', 
'txBatteryStatus': 'bat_iss', 'windBatteryStatus': 'bat_anemometer', 
'rainBatteryStatus': 'bat_leaf_soil', 'outTempBatteryStatus': 'bat_th_1', 
'inTempBatteryStatus': 'bat_th_2', 'referenceVoltage': 'solar_power', 
'supplyVoltage': 'supercap_volt'}
May  2 21:58:00 raspberrypi /weewxd: meteostick: using serial port /dev/ttyUSB0
May  2 21:58:00 raspberrypi /weewxd: meteostick: using baudrate 115200
May  2 21:58:00 raspberrypi /weewxd: meteostick: using frequency EU
May  2 21:58:00 raspberrypi /weewxd: meteostick: using rf sensitivity 90 (-90 
dB)
May  2 21:58:00 raspberrypi /weewxd: meteostick: using iss_channel 1
May  2 21:58:00 raspberrypi /weewxd: meteostick: using anemometer_channel 2
May  2 21:58:00 raspberrypi /weewxd: meteostick: using leaf_soil_channel 0
May  2 21:58:00 raspberrypi /weewxd: meteostick: using temp_hum_1_channel 0
May  2 21:58:00 raspberrypi /weewxd: meteostick: using temp_hum_2_channel 0
May  2 21:58:00 raspberrypi /weewxd: meteostick: using transmitters 03
May  2 21:58:00 raspberrypi /weewxd: meteostick: establish communication with 
the meteostick
May  2 21:58:02 raspberrypi /weewxd: meteostick: reset: 
May  2 21:58:02 raspberrypi /weewxd: meteostick: configure meteostick to logger 
mode
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
May  2 21:58:04 raspberrypi weewx[2191] INFO weewx.engine: StdConvert target 
unit is 0x1
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
May  2 21:58:04 raspberrypi weewx[2191] DEBUG weewx.manager: Daily summary 
version is 2.0
May  2 21:58:04 raspberrypi weewx[2191] INFO weewx.wxservices: The following 
values will be calculated: pressure=prefer_hardware, barometer=prefer_hardware, 
altimeter=prefer_hardware, windchill=prefer_hardware, 
heatindex=prefer_hardware,

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

ok we have a winner ! I used wee_device to set the interval to 1 minutes 
and settings the interval of archive in weewx.conf as I like it and bam ! 
Record coming in and rxCheckPercent populated !

Thanks for your help and time Tom. Keep up the good work.

On Saturday, May 2, 2020 at 3:53:11 PM UTC-4, Hyrules wrote:
>
> Never had any problem with the logger itself . I just reinstalled a fresh 
> version of weewx 4.0 and remove every addons I had as well and skin and I 
> still don’t get a REC when I run weewxd. Plenty of loops coming in but the 
> logger does not seems to be pushing any records or weewx grabbing a record. 
> I’ve been running this for at least an hour and looking at the screen. This 
> station has nothing special. it has a USB logger and I got it about 10 
> years ago. Still working really well.
>
> *From:* weewx-user@googlegroups.com  *On 
> Behalf Of *Tom Keffer
> *Sent:* May 2, 2020 15:47
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: rxCheckPercent always zero and number of 
> wind samples
>
>  
>
> The Vantage loggers work very well, with one flaw: they don't get it right 
> over daylight savings time transitions. Other than that, there's no reason 
> not to use them.
>
>  
>
> -tk
>
>  
>
> On Sat, May 2, 2020 at 12:20 PM Hyrules  wrote:
>
> I don’t understand why I was on software generation I don’t remember why I 
> would prefer software over hardware. I still haven’t seen a archive packet 
> that’s really odd.
>
>
>
> On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:
>
> There must have been some reason you were using software record 
> generation. You may "fix" this, but break something else!
>
>  
>
> On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:
>
> That must be it. The setting record_generation was software changed it to 
> hardware in weewx.conf. Waiting for a archive packet.
>
> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>
> Are you using software record generation?
>
>  
>
> If so, weewx will not retrieve the archive record from the logger and, 
> instead, calculates the archive record in software. The logger is what 
> supplies the number of wind samples, so it is only available if you 
> download an archive record.
>
>  
>
> -tk
>
>  
>
> On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:
>
> Well that's not it. I ahve reflashed with the wireless version and still 
> not seeing the rxCheckPercent and Wind Samples
>
> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>
> Crap I think I have and Idea what is happening I might have flashed the 
> cabled version firmware. Will try to reflash the wireless version because 
> my station is wireless.
>
> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>
> Hi everyone,
>
>  
>
> I have a vantage pro 2 and was wondering what might be the issue of the 
> following my rc_CheckPercent is always at zero. I have a point in my sql 
> data when I temporarily got some value but at the moment it's zero. This is 
> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>
> Also is it possible to get the number of wind sample ? The skin that i'm 
> creating requires it and i have hard time finding any info on it in the 
> documentation.
>
>  
>
> Anyone has any input.
>
>  
>
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/43011f58-be98-44a2-8e71-3dd1711be9bf%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/632b62a3-7569-4474-a798-a97946d90244%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 
>

RE: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

2020-05-02 Thread hyrules

Never had any problem with the logger itself . I just reinstalled a fresh 
version of weewx 4.0 and remove every addons I had as well and skin and I still 
don’t get a REC when I run weewxd. Plenty of loops coming in but the logger 
does not seems to be pushing any records or weewx grabbing a record. I’ve been 
running this for at least an hour and looking at the screen. This station has 
nothing special. it has a USB logger and I got it about 10 years ago. Still 
working really well.

From: weewx-user@googlegroups.com  On Behalf Of 
Tom Keffer
Sent: May 2, 2020 15:47
To: weewx-user 
Subject: Re: [weewx-user] Re: rxCheckPercent always zero and number of wind 
samples

 

The Vantage loggers work very well, with one flaw: they don't get it right over 
daylight savings time transitions. Other than that, there's no reason not to 
use them.

 

-tk

 

On Sat, May 2, 2020 at 12:20 PM Hyrules mailto:hyru...@gmail.com> > wrote:

I don’t understand why I was on software generation I don’t remember why I 
would prefer software over hardware. I still haven’t seen a archive packet 
that’s really odd.



On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:

There must have been some reason you were using software record generation. You 
may "fix" this, but break something else!

 

On Sat, May 2, 2020 at 11:00 AM Hyrules mailto:hyr...@gmail.com> > wrote:

That must be it. The setting record_generation was software changed it to 
hardware in weewx.conf. Waiting for a archive packet.

On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:

Are you using software record generation?

 

If so, weewx will not retrieve the archive record from the logger and, instead, 
calculates the archive record in software. The logger is what supplies the 
number of wind samples, so it is only available if you download an archive 
record.

 

-tk

 

On Sat, May 2, 2020 at 10:27 AM Hyrules mailto:hyr...@gmail.com> > wrote:

Well that's not it. I ahve reflashed with the wireless version and still not 
seeing the rxCheckPercent and Wind Samples

On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:

Crap I think I have and Idea what is happening I might have flashed the cabled 
version firmware. Will try to reflash the wireless version because my station 
is wireless.

On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:

Hi everyone,

 

I have a vantage pro 2 and was wondering what might be the issue of the 
following my rc_CheckPercent is always at zero. I have a point in my sql data 
when I temporarily got some value but at the moment it's zero. This is 
happening in Weewx 4.0 but was also happening in Weewx 3.9.x

Also is it possible to get the number of wind sample ? The skin that i'm 
creating requires it and i have hard time finding any info on it in the 
documentation.

 

Anyone has any input.

 

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...@googlegroups.com  .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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...@googlegroups.com  .
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/43011f58-be98-44a2-8e71-3dd1711be9bf%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/632b62a3-7569-4474-a798-a97946d90244%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/k9NXJPytVyk/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

Re: [weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Devonian

OK, I figured it for the scroller text - it doesn't like a comma (,) in the 
text.
I now have it running and picking up local time, by adding this to the 
[RealtimegaugeData] in weewx.conf
[[Text]]
text = Real Time Gauges - Local Time is %H:%M - Next gauge update 
in...

Nigel.


On Saturday, 2 May 2020 11:33:44 UTC+1, Devonian wrote:
>
> @ Gary,
>
> I've updated my SteelSeries and rtgd and all working now.
> One small thing has changed since my original install is that the scroller 
> text is now missing (had to remove the old method that picked up local time 
> as it didn't like that now).
> How do I add some text to the scroller now?
>
> Nigel.
>

-- 
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/33c5cd2a-02e9-404a-b1a3-67ab3f60450f%40googlegroups.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

The Vantage loggers work very well, with one flaw: they don't get it right
over daylight savings time transitions. Other than that, there's no reason
not to use them.

-tk

On Sat, May 2, 2020 at 12:20 PM Hyrules  wrote:

> I don’t understand why I was on software generation I don’t remember why I
> would prefer software over hardware. I still haven’t seen a archive packet
> that’s really odd.
>
>
> On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:
>>
>> There must have been some reason you were using software record
>> generation. You may "fix" this, but break something else!
>>
>> On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:
>>
>>> That must be it. The setting record_generation was software changed it
>>> to hardware in weewx.conf. Waiting for a archive packet.
>>>
>>> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:

 Are you using software record generation?

 If so, weewx will not retrieve the archive record from the logger and,
 instead, calculates the archive record in software. The logger is what
 supplies the number of wind samples, so it is only available if you
 download an archive record.

 -tk

 On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:

> Well that's not it. I ahve reflashed with the wireless version and
> still not seeing the rxCheckPercent and Wind Samples
>
> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>>
>> Crap I think I have and Idea what is happening I might have flashed
>> the cabled version firmware. Will try to reflash the wireless version
>> because my station is wireless.
>>
>> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>>
>>> Hi everyone,
>>>
>>> I have a vantage pro 2 and was wondering what might be the issue of
>>> the following my rc_CheckPercent is always at zero. I have a point in my
>>> sql data when I temporarily got some value but at the moment it's zero.
>>> This is happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>>> Also is it possible to get the number of wind sample ? The skin that
>>> i'm creating requires it and i have hard time finding any info on it in 
>>> the
>>> documentation.
>>>
>>> Anyone has any input.
>>>
>>> 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...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/43011f58-be98-44a2-8e71-3dd1711be9bf%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/632b62a3-7569-4474-a798-a97946d90244%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/CAPq0zEB8_Mwgapj%2BYLy3E41b0eXRCt_ZVHse0hEh0P8McioZhA%40mail.gmail.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

I suspect that you're missing something to do the calculation. Let's check
by using the attached instrumented version of wxservices.py.

If you used a package installer, it goes in
/usr/share/weewx/weewx/wxservices.py

If you used the setup.py install method, it goes in
/home/weewx/bin/weewx/wxservices.py.

Restart weewx. Let it run for an archive interval, post the log.

-tk

On Sat, May 2, 2020 at 12:30 PM Manfred Maier 
wrote:

> 1) In the archive table in the database it's  since I've switched to
> the Python 3 version.
> I've just noticed, that appTemp and windrun were also affected for a
> couple of hours (also ). But both meanwhile get calculated and have
> valid values in the database
>
> 2) This is what I find in the log:
>
> May  2 21:01:43 raspberrypi wee_reports[3538] 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,
> windrun=prefer_hardware, appTemp=prefer_hardware,
> cloudbase=prefer_hardware, humidex=prefer_hardware, ET=prefer_hardware
>
> May  2 21:01:43 raspberrypi wee_reports[3538] INFO weewx.wxservices: The
> following algorithms will be used for calculations: altimeter=aaASOS,
> maxSolarRad=RS
>
>
>
>
> Am Samstag, 2. Mai 2020 21:18:39 UTC+2 schrieb Tom Keffer:
>>
>> 1. When you say "maxSolarRadiation isn't calculated" do you mean it does
>> not appear in LOOP or archive records at all? Or, that it has value None?
>>
>> 2. Look in the system log for something like
>>
>> May  2 07:21:39 nuc weewx[110614] INFO weewx.wxservices: The following
>> values will be calculated: pressure=prefer_hardware,
>> altimeter=prefer_hardware, appTemp=prefer_hardware,
>> barometer=prefer_hardware, beaufort=prefer_hardware,
>> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware,
>> heatindex=prefer_hardware, humidex=prefer_hardware,
>> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware,
>> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
>>
>> What does it say?
>>
>> -tk
>>
>>
>>
>> On Sat, May 2, 2020 at 11:57 AM Manfred Maier  wrote:
>>
>>> Hi,
>>> I've just detected that maxSolarRadiation isn't calculated since I've
>>> switched to the Python 3 version of Weewx.
>>> Before switching to Python 3, I already had the Python 2 version of
>>> 4.0.0 installed for a couple of hours. maxSolarRad got calculated during
>>> that time.
>>>
>>> Any idea what the issue could be?
>>>
>>> maxSolarRad is included in the weewx.conf.
>>> I've tried the prefer_hardware and software option.
>>>
>>> [StdWXCalculate]
>>>
>>>
>>> [[Calculations]]
>>>
>>> # How to calculate derived quantities.  Possible values are:
>>>
>>> #  hardware- use the value provided by hardware
>>>
>>> #  software- use the value calculated by weewx
>>>
>>> #  prefer_hardware - use value provide by hardware if available,
>>>
>>> #  otherwise use value calculated by weewx
>>>
>>>
>>> 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
>>>
>>> windrun = prefer_hardware
>>>
>>> appTemp = prefer_hardware
>>>
>>> cloudbase = prefer_hardware
>>>
>>> humidex = prefer_hardware
>>>
>>> ET = prefer_hardware
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/c1744cac-b0ab-4d71-bda3-bbfe438ddf42%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/e7ffbd8a-3d0c-46cd-b3c3-86d5005d76d8%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,

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

1) In the archive table in the database it's  since I've switched to 
the Python 3 version. 
I've just noticed, that appTemp and windrun were also affected for a couple 
of hours (also ). But both meanwhile get calculated and have valid 
values in the database

2) This is what I find in the log:

May  2 21:01:43 raspberrypi wee_reports[3538] 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, 
windrun=prefer_hardware, appTemp=prefer_hardware, 
cloudbase=prefer_hardware, humidex=prefer_hardware, ET=prefer_hardware

May  2 21:01:43 raspberrypi wee_reports[3538] INFO weewx.wxservices: The 
following algorithms will be used for calculations: altimeter=aaASOS, 
maxSolarRad=RS




Am Samstag, 2. Mai 2020 21:18:39 UTC+2 schrieb Tom Keffer:
>
> 1. When you say "maxSolarRadiation isn't calculated" do you mean it does 
> not appear in LOOP or archive records at all? Or, that it has value None?
>
> 2. Look in the system log for something like
>
> May  2 07:21:39 nuc weewx[110614] INFO weewx.wxservices: The following 
> values will be calculated: pressure=prefer_hardware, 
> altimeter=prefer_hardware, appTemp=prefer_hardware, 
> barometer=prefer_hardware, beaufort=prefer_hardware, 
> cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware, 
> heatindex=prefer_hardware, humidex=prefer_hardware, 
> inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware, 
> rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware
>
> What does it say?
>
> -tk
>
>
>
> On Sat, May 2, 2020 at 11:57 AM Manfred Maier  > wrote:
>
>> Hi,
>> I've just detected that maxSolarRadiation isn't calculated since I've 
>> switched to the Python 3 version of Weewx.
>> Before switching to Python 3, I already had the Python 2 version of 4.0.0 
>> installed for a couple of hours. maxSolarRad got calculated during that 
>> time.
>>
>> Any idea what the issue could be? 
>>
>> maxSolarRad is included in the weewx.conf.
>> I've tried the prefer_hardware and software option.
>>
>> [StdWXCalculate]
>>
>>
>> [[Calculations]]
>>
>> # How to calculate derived quantities.  Possible values are:
>>
>> #  hardware- use the value provided by hardware
>>
>> #  software- use the value calculated by weewx
>>
>> #  prefer_hardware - use value provide by hardware if available,
>>
>> #  otherwise use value calculated by weewx
>>
>>
>> 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
>>
>> windrun = prefer_hardware
>>
>> appTemp = prefer_hardware
>>
>> cloudbase = prefer_hardware
>>
>> humidex = prefer_hardware
>>
>> ET = prefer_hardware
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c1744cac-b0ab-4d71-bda3-bbfe438ddf42%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/e7ffbd8a-3d0c-46cd-b3c3-86d5005d76d8%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Bill M

Finally got a few minutes to upgrade, still using Python 2.7 and Debian 9 
but it went smoothly almost.

Must have missed comments that maxSolrRad is now maxSolarRad

Would have only taken 5 minutes if I'd seen that first
No biggie

-- 
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/36e9db90-c3f7-4480-be4f-ed342e86%40googlegroups.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

 

I don’t understand why I was on software generation I don’t remember why I 
would prefer software over hardware. I still haven’t seen a archive packet 
that’s really odd.


On Saturday, May 2, 2020 at 2:22:01 PM UTC-4, Tom Keffer wrote:
>
> There must have been some reason you were using software record 
> generation. You may "fix" this, but break something else!
>
> On Sat, May 2, 2020 at 11:00 AM Hyrules > 
> wrote:
>
>> That must be it. The setting record_generation was software changed it to 
>> hardware in weewx.conf. Waiting for a archive packet.
>>
>> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>>>
>>> Are you using software record generation?
>>>
>>> If so, weewx will not retrieve the archive record from the logger and, 
>>> instead, calculates the archive record in software. The logger is what 
>>> supplies the number of wind samples, so it is only available if you 
>>> download an archive record.
>>>
>>> -tk
>>>
>>> On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:
>>>
 Well that's not it. I ahve reflashed with the wireless version and 
 still not seeing the rxCheckPercent and Wind Samples

 On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>
> Crap I think I have and Idea what is happening I might have flashed 
> the cabled version firmware. Will try to reflash the wireless version 
> because my station is wireless.
>
> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>
>> Hi everyone,
>>
>> I have a vantage pro 2 and was wondering what might be the issue of 
>> the following my rc_CheckPercent is always at zero. I have a point in my 
>> sql data when I temporarily got some value but at the moment it's zero. 
>> This is happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>> Also is it possible to get the number of wind sample ? The skin that 
>> i'm creating requires it and i have hard time finding any info on it in 
>> the 
>> documentation.
>>
>> Anyone has any input.
>>
>> 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...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/43011f58-be98-44a2-8e71-3dd1711be9bf%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/632b62a3-7569-4474-a798-a97946d90244%40googlegroups.com.

Re: [weewx-user] maxSolarRad not calculated since switching to Python 3

1. When you say "maxSolarRadiation isn't calculated" do you mean it does
not appear in LOOP or archive records at all? Or, that it has value None?

2. Look in the system log for something like

May  2 07:21:39 nuc weewx[110614] INFO weewx.wxservices: The following
values will be calculated: pressure=prefer_hardware,
altimeter=prefer_hardware, appTemp=prefer_hardware,
barometer=prefer_hardware, beaufort=prefer_hardware,
cloudbase=prefer_hardware, dewpoint=prefer_hardware, ET=prefer_hardware,
heatindex=prefer_hardware, humidex=prefer_hardware,
inDewpoint=prefer_hardware, maxSolarRad=prefer_hardware,
rainRate=prefer_hardware, windchill=prefer_hardware, windrun=prefer_hardware

What does it say?

-tk



On Sat, May 2, 2020 at 11:57 AM Manfred Maier 
wrote:

> Hi,
> I've just detected that maxSolarRadiation isn't calculated since I've
> switched to the Python 3 version of Weewx.
> Before switching to Python 3, I already had the Python 2 version of 4.0.0
> installed for a couple of hours. maxSolarRad got calculated during that
> time.
>
> Any idea what the issue could be?
>
> maxSolarRad is included in the weewx.conf.
> I've tried the prefer_hardware and software option.
>
> [StdWXCalculate]
>
>
> [[Calculations]]
>
> # How to calculate derived quantities.  Possible values are:
>
> #  hardware- use the value provided by hardware
>
> #  software- use the value calculated by weewx
>
> #  prefer_hardware - use value provide by hardware if available,
>
> #  otherwise use value calculated by weewx
>
>
> 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
>
> windrun = prefer_hardware
>
> appTemp = prefer_hardware
>
> cloudbase = prefer_hardware
>
> humidex = prefer_hardware
>
> ET = prefer_hardware
>
> --
> 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/c1744cac-b0ab-4d71-bda3-bbfe438ddf42%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/CAPq0zEDYmcNKO2y0WbABL34Ba6_Juk695tAch3xLhj0Qcpv9XQ%40mail.gmail.com.

Re: [weewx-user] Re: 4.x logging format

Great ideas! Thanks for your thoughts.

Try this version of weeutil/logger.py. It includes a shim that does the
proper type conversion before passing on arguments to
logging.handlers.RotatingFileHandler.

To use should be as simple as adding this to weewx.conf (alas, NOT TESTED):

[Logging]
  [[loggers]]
[[[root]]]
  handlers = syslog, rotate
  [[handlers]]
[[[rotate]]]
  filename = /tmp/weewx.log

By default, it logs to /var/log/weewx.log. Hence, the need to override that
option if you want to log to /tmp/weewx.log.

-tk


On Sat, May 2, 2020 at 8:05 AM Graham Eddy  wrote:

> i think we all agree that syslog on macos is a lost cause.
> the corollary is that pointing python logging at syslog (via
> logging.handlers.SysLogHandler) is doomed
>
> i accept that syslog works fine on most platforms, but it is not feasible
> for macos
> but there is the simple alternative for macos users of using a different
> handler:
>
> i patched log_dict in bin/weeutil/logger.py to add a
> logging.handlers.RotatingFileHandler and it worked fine.
> adding it via weewx.conf gives a type conversion error that seems simple
> to fix.
> with the fix, i would suggest this be added to the macos installation
> instructions for user to add to weewx.conf (or make it part of the
> installation process)
>
> details follow...
>
> weewx.conf (yes, using that ‘root’ hack introduced to work around a
> ConfigObj limitation):
>
> [Logging]
>   [[loggers]]
> [[[root]]]
>   level = DEBUG
>   propogate = True
>   handlers = syslog, rotate
>   [[handlers]]
> [[[rotate]]]
>   level = DEBUG
>   formatter = standard
>   class = logging.handlers.RotatingFileHandler
>   filename = /tmp/weewx.log
>   maxBytes = 1000
>   backupCount = 2
>
>
> gives the following error, which on the face of it would take a simple fix
> of type conversions:
>
> Traceback (most recent call last):
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
> line 563, in configure
> handler = self.configure_handler(handlers[name])
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
> line 736, in configure_handler
> result = factory(**kwargs)
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/handlers.py",
> line 146, in __init__
> if maxBytes > 0:
> TypeError: '>' not supported between instances of 'str' and ‘int’ < - - -
> SEE HER*E*
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
>   File "bin/weewxd", line 261, in 
> main()
>   File "bin/weewxd", line 136, in main
> weeutil.logger.setup(options.log_label, config_dict)
>   File "/opt/weewx/bin/weeutil/logger.py", line 203, in setup
> logging.config.dictConfig(log_dict)
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
> line 800, in dictConfig
> dictConfigClass(config).configure()
>   File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
> line 571, in configure
> '%r' % name) from e
> ValueError: Unable to configure handler 'rotate'
>
>
> the log_dict it produces before crashing seems correct:
>
> {'version': 1, 'disable_existing_loggers': False, 'loggers': {'':
> {'level': 'DEBUG', 'propagate': True, 'handlers': ['syslog'], 'propogate':
> 'True'}}, 'handlers': {'syslog': {'level': 'DEBUG', 'formatter':
> 'standard', 'class': 'logging.handlers.SysLogHandler', 'address':
> '/var/run/syslog', 'facility': 'local1'}, 'console': {'level': 'DEBUG',
> 'formatter': 'verbose', 'class': 'logging.StreamHandler', 'stream': '
> ext://sys.stdout'}, 'rotate': {'level': 'DEBUG', 'formatter': 'standard',
> 'class': 'logging.handlers.RotatingFileHandler', 'filename':
> '/tmp/weewx.log', 'maxBytes': '1000', 'backupCount': '2'}},
> 'formatters': {'simple': {'format': '%(levelname)s %(message)s'},
> 'standard': {'format': 'weewx[%(process)d] %(levelname)s %(name)s:
> %(message)s'}, 'verbose': {'format': '%(asctime)s  weewx[%(process)d]
> %(levelname)s %(name)s: %(message)s', 'datefmt': '%Y-%m-%d %H:%M:%S'}}}
>
>
> cheers
>
> On 2 May 2020, at 10:42 pm, Tom Keffer  wrote:
>
> Logging from Python under MacOS High Sierra and later is a complete
> mystery. I have been unable to get it to work and, it seems, neither have
> other
> 
>  users
> 
> .
>
> Wish I could be of more help...
>
> -tk
>
> On Sat, May 2, 2020 at 5:26 AM Graham Eddy  wrote:
>
>> i reported this incorrectly. instead of giveing me an unchanged logger
>> format, it gives me no lines at all (from the point the weewx.conf log
>> format is parsed).  even the following does the same (no logger output).

[weewx-user] maxSolarRad not calculated since switching to Python 3

Hi,
I've just detected that maxSolarRadiation isn't calculated since I've 
switched to the Python 3 version of Weewx.
Before switching to Python 3, I already had the Python 2 version of 4.0.0 
installed for a couple of hours. maxSolarRad got calculated during that 
time.

Any idea what the issue could be? 

maxSolarRad is included in the weewx.conf.
I've tried the prefer_hardware and software option.

[StdWXCalculate]


[[Calculations]]

# How to calculate derived quantities.  Possible values are:

#  hardware- use the value provided by hardware

#  software- use the value calculated by weewx

#  prefer_hardware - use value provide by hardware if available,

#  otherwise use value calculated by weewx


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

windrun = prefer_hardware

appTemp = prefer_hardware

cloudbase = prefer_hardware

humidex = prefer_hardware

ET = prefer_hardware

-- 
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/c1744cac-b0ab-4d71-bda3-bbfe438ddf42%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Pete Geenhuizen

OK I guess I'll have to give it a shot and hope like hell that it works.

Thanks

On 2020-05-02 13:36, Tom Keffer wrote:

It should. I'm not sure how thoroughly it as been tested under Python 3.

On Sat, May 2, 2020 at 9:17 AM Pete Geenhuizen > wrote:

Oops my bad i got confused by the similar driver name, I'm using
the wx23xx driver which is working just fine under V3 so will it
work in V4?

On 5/2/20 11:47 AM, Tom Keffer wrote:

wh23xx is not a supported weather station under WeeWX V3 or V4.
No plans to change that.

However, I will see what I can do about getting the wh23xx 3rd
party extension updated.

-tk

On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen
mailto:p...@geenhuizen.net>> wrote:
--
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/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com

--
This message has been scanned for viruses and

dangerous content by *MailScanner*
, and is
believed to be clean.

--
Unencumbered by the thought process.

-- Click and Clack the Tappet brothers

--
This message has been scanned for viruses and

dangerous content by *MailScanner* ,
and is
believed to be clean.

--
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/CAPq0zEB2YtYHWcGUcKXCAr2%3DTDkXNTaQe1Z%3D1NmrZYn9bFy8ng%40mail.gmail.com
.

--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean.

--
Unencumbered by the thought process.
-- Click and Clack the Tappet brothers

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/733f185a-8d2d-874e-ee58-f42e09e6e772%40geenhuizen.net.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

On Saturday, May 2, 2020 at 10:01:39 AM UTC-4, Tom Keffer wrote:
>
> The weewx usage map  shows 26 
> installations (out of 1471 registered stations), or less than 2%. That's 
> not enough usage to justify the work. Get your friends to use it!
>
> Still, I'll see what I can do...
>
>>
>>
tom,

i'll take care of it - its one of my drivers.  but its over 50F for the 
first time in weeks, so it will have to wait until after sunset US eastern 
time :)

m 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9533ea63-6ad3-4684-bb81-9adf4f7446e6%40googlegroups.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

There must have been some reason you were using software record generation.
You may "fix" this, but break something else!

On Sat, May 2, 2020 at 11:00 AM Hyrules  wrote:

> That must be it. The setting record_generation was software changed it to
> hardware in weewx.conf. Waiting for a archive packet.
>
> On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>>
>> Are you using software record generation?
>>
>> If so, weewx will not retrieve the archive record from the logger and,
>> instead, calculates the archive record in software. The logger is what
>> supplies the number of wind samples, so it is only available if you
>> download an archive record.
>>
>> -tk
>>
>> On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:
>>
>>> Well that's not it. I ahve reflashed with the wireless version and still
>>> not seeing the rxCheckPercent and Wind Samples
>>>
>>> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:

 Crap I think I have and Idea what is happening I might have flashed the
 cabled version firmware. Will try to reflash the wireless version because
 my station is wireless.

 On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>
> Hi everyone,
>
> I have a vantage pro 2 and was wondering what might be the issue of
> the following my rc_CheckPercent is always at zero. I have a point in my
> sql data when I temporarily got some value but at the moment it's zero.
> This is happening in Weewx 4.0 but was also happening in Weewx 3.9.x
> Also is it possible to get the number of wind sample ? The skin that
> i'm creating requires it and i have hard time finding any info on it in 
> the
> documentation.
>
> Anyone has any input.
>
> 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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/43011f58-be98-44a2-8e71-3dd1711be9bf%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/CAPq0zECWctOQ2a8xjaAkV%3DxJ9VWcjKzJZ%2B_N83As_qYqgB%2BmDQ%40mail.gmail.com.

Re: [weewx-user] Re: Installing weewx on Centos 8

OK.

HTML pages look as expected for me when using Firefox. Can you post an HTML
file that does this? Or, give an URL to one?

-tk

On Sat, May 2, 2020 at 11:17 AM Mike Doneske  wrote:

> This was a new install on an OS that never had WeeWx installed. Only files
> copied from old machine was weewx.sdb and weewx.conf
>
> On Friday, May 1, 2020 at 5:03:57 PM UTC-5, Tom Keffer wrote:
>>
>> Skins are not touched by an upgrade, so what you're looking at is your
>> old skin.
>>
>> On Fri, May 1, 2020 at 1:46 PM Mike Doneske  wrote:
>>
>>> Followed new installation instructions and everything worked as
>>> expected. Only issue identified so far is default index.html doesn't
>>> display as before on Fire fox. Graphs have all moved to the bottom of the
>>> display and a lot of white space to the right of the text at the top.
>>>
>>> On Wednesday, April 29, 2020 at 3:19:55 PM UTC-5, Mike Doneske wrote:



 On Wednesday, April 29, 2020 at 2:57:45 PM UTC-5, vince wrote:
>
> On Wednesday, April 29, 2020 at 12:02:51 PM UTC-7, Mike Doneske wrote:
>>
>> On Wednesday, April 29, 2020 at 1:54:05 PM UTC-5, Mike Doneske wrote:
>>
>>> Trying to install weewx on Centos 8 following the instructions in
>>> the compatibility matrix. I'm trying to install the b18 version Python3.
>>> All works OK until I get to the *dnf install weewx* step. I get a
>>> message: *no match for argument weewx* I'm using
>>> epel-release-8-8.el8.noarch. Did I miss a step? Am I using the right r
>>>
>>
>>
>>
> If you can hold out for a day or two (hopefully max), Matthew is
> 'really' close to releasing the rpms for weewx v4 and associated 
> procedure.
>
> I've tested it on a centos8 vm and the procedure works great.   So if
> you can hang tight for a 'little' bit then it'll be very very
> straightforward...
>

 It's a new install so I can hold off for a bit... 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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/998cb272-46bd-4599-9b63-d3a259b50512%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/5f00b3ca-2e42-4da7-9da0-bd6f9ef1c56a%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/CAPq0zEDk%2B922ETNb6mrP8bqoK16d1nCmxb2M2vTuuWk659sW4w%40mail.gmail.com.

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

That seems reasonable. Try this version



On Sat, May 2, 2020 at 9:10 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:

> Shouldnt it be taking in api_key in test mode too? Is that intentional?
>
> On Sat, 2 May 2020 at 20:52, Tom Keffer  wrote:
>
>> Thanks for catching the problem with json.load(). Fixed in commit c05f76b
>> 
>>
>> As you discovered, I think the api_key code is working properly.
>>
>> On Sat, May 2, 2020 at 8:04 AM Praveen Chandrasekaran <
>> praveen.c...@gmail.com> wrote:
>>
>>> I think I figured out API key issue. It's not read if in test mode and
>>> hence causes error. Attached snippet
>>>
>>> On Sat, 2 May 2020, 19:40 Praveen Chandrasekaran, <
>>> praveen.c...@gmail.com> wrote:
>>>
 I didnt attached console output because i just ran wunderfixer at
 shell. I was getting HTTP 401 error. printed api_key from within
 wunderfixer it was "None". Then edited wunderfixer with the api key
 locally and that fixed that issue

 On Sat, 2 May 2020 at 19:32, Tom Keffer  wrote:

> Log? Console output?
>
> On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
> praveen.c...@gmail.com> wrote:
>
>> 2 issues:
>>
>> 1) API key not getting passed. Hacked wunderfixer with local api key
>> instead of passing
>> 2) After 1 I get error  that  JSON object must be str not bytes.
>>
>> On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran
>> wrote:
>>>
>>> Hi,
>>>
>>> My wunderfixer was working till yesterday (I know for sure because I
>>> have used it to fill missing data often recently)
>>>
>>> After updating to v4, the wunderfixer stopped working. The API key
>>> looks fine but I am getting HTTP 401 FORBIDDEN ERROR.
>>>
>>> Regards,
>>> Praveen
>>>
>> --
>> 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/e6608887-e63e-4844-955b-da4437b2f662%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/PSemiQmyCt0/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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%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+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWjPPZX-B9eZsU1VscKP9j1fMQ0d9iEOhf9UwPKMO%2B3Cg%40mail.gmail.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/PSemiQmyCt0/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/CAPq0zEAB22_VgJ%3DS9i7ZABuffq%2B2f48ri%2BektbMpJQOQgWcdPg%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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWvHUz1hSTxNY8rQcXQJV-fTP_0mXwx02sNiPBDUSqPNA%40mail.gmail.com
> 
> .
>

-- 
You

Re: [weewx-user] Re: Installing weewx on Centos 8

2020-05-02 Thread Mike Doneske

This was a new install on an OS that never had WeeWx installed. Only files 
copied from old machine was weewx.sdb and weewx.conf

On Friday, May 1, 2020 at 5:03:57 PM UTC-5, Tom Keffer wrote:
>
> Skins are not touched by an upgrade, so what you're looking at is your old 
> skin.
>
> On Fri, May 1, 2020 at 1:46 PM Mike Doneske  > wrote:
>
>> Followed new installation instructions and everything worked as expected. 
>> Only issue identified so far is default index.html doesn't display as 
>> before on Fire fox. Graphs have all moved to the bottom of the display and 
>> a lot of white space to the right of the text at the top.
>>
>> On Wednesday, April 29, 2020 at 3:19:55 PM UTC-5, Mike Doneske wrote:
>>>
>>>
>>>
>>> On Wednesday, April 29, 2020 at 2:57:45 PM UTC-5, vince wrote:

 On Wednesday, April 29, 2020 at 12:02:51 PM UTC-7, Mike Doneske wrote:
>
> On Wednesday, April 29, 2020 at 1:54:05 PM UTC-5, Mike Doneske wrote:
>
>> Trying to install weewx on Centos 8 following the instructions in the 
>> compatibility matrix. I'm trying to install the b18 version Python3. All 
>> works OK until I get to the *dnf install weewx* step. I get a 
>> message: *no match for argument weewx* I'm using 
>> epel-release-8-8.el8.noarch. Did I miss a step? Am I using the right r
>>
>
>
>
 If you can hold out for a day or two (hopefully max), Matthew is 
 'really' close to releasing the rpms for weewx v4 and associated procedure.

 I've tested it on a centos8 vm and the procedure works great.   So if 
 you can hang tight for a 'little' bit then it'll be very very 
 straightforward... 

>>>
>>> It's a new install so I can hold off for a bit... 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/998cb272-46bd-4599-9b63-d3a259b50512%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/5f00b3ca-2e42-4da7-9da0-bd6f9ef1c56a%40googlegroups.com.

[weewx-user] Re: Weewx will only work for a week then stops

2020-05-02 Thread Luc Theoret

Hi,

 I have removed cmon. It seeems to be working.

As far is outTemp is that is the main temperature and it is populated in 
the database and graphed in weewx.
I get an error for the min max outTemp.

Luc

On Saturday, May 2, 2020 at 11:44:42 AM UTC-6, Luc Theoret wrote:
>
> Hi Luc,
>
> I have updated to the version of cmon provide in your link.
>
> I did a wee_extension weewx-cmon-master.zip
> everthing i think went OK, but now weewx wont start I get this error:
>
> May  2 11:37:21 weewx-pi systemd[1]: Started Session c3 of user pi.
> May  2 11:37:24 weewx-pi weewx[556]: sdr: MainThread: timed out waiting 
> for stderr-thread
> May  2 11:37:24 weewx-pi weewx[556]: engine: Caught unrecoverable 
> exception in engine:
> May  2 11:37:24 weewx-pi weewx[556]:   No module named builtins
> May  2 11:37:24 weewx-pi weewx[556]:   Traceback (most recent call 
> last):
> May  2 11:37:24 weewx-pi weewx[556]: File 
> "/usr/share/weewx/weewx/engine.py", line 888, in main
> May  2 11:37:24 weewx-pi weewx[556]:   engine = 
> engine_class(config_dict)
> May  2 11:37:24 weewx-pi weewx[556]: File 
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> May  2 11:37:24 weewx-pi weewx[556]:   
> self.loadServices(config_dict)
> May  2 11:37:24 weewx-pi weewx[556]: File 
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> May  2 11:37:24 weewx-pi weewx[556]:   
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> May  2 11:37:24 weewx-pi weewx[556]: File 
> "/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object
> May  2 11:37:24 weewx-pi weewx[556]:   mod = __import__(module)
> May  2 11:37:24 weewx-pi weewx[556]: File 
> "/usr/share/weewx/user/cmon.py", line 124, in 
> May  2 11:37:24 weewx-pi weewx[556]:   from builtins import 
> input
> May  2 11:37:24 weewx-pi weewx[556]:   ImportError: No module 
> named builtins
> May  2 11:37:24 weewx-pi weewx[556]:   Exiting.
>
> Luc
>  
>
> On Saturday, May 2, 2020 at 7:47:18 AM UTC-6, Luc Heijst wrote:
>>
>> Hi Luc,
>>
>> The error:
>> ValueError: accum: ScalarStats.addHiLo expected float or int, got type 
>> '' ('4552332')
>> is caused by an old version of weewx_cmon. The latest version (0.20) 
>> solves this, See: https://github.com/matthewwall/weewx-cmon
>>
>> Also your syslog show several errors with outTemp, like:
>> cheetahgenerator:  Reason: Unknown daily summary type outTemp
>>
>> Check your database if you have a value outTemp. 
>> If not, check your skin files for the use of outTemp.
>>
>> Luc Heijst
>>
>> On Saturday, 2 May 2020 02:33:45 UTC-3, Luc Theoret wrote:
>>>
>>> Hi,
>>>
>>> I have been trying to get weewx to record my acurite data using sdr 
>>> RTL_433 for about a year now.
>>> The system I have almost running is a raspberry pi 3 running on respbian 
>>> stretch. it has an external real time clock attached.
>>> weewx runs consistently for a week then stops. I was finally find the 
>>> log entry for the stop, see attached file.
>>> In the file is the last successful update, then the error and the exit. 
>>> I also included the config file.
>>>
>>>
>>> I have tried to reinstall on new SD card with Buster but cannot get the 
>>> radio to work. tried blackballing stuff blindly (not knowing what doing).
>>> Then I went back to this SD card. changed a couple of things and it ran. 
>>> But as usual after a week like clockwork it stopped.
>>>
>>> Luc
>>>
>>

-- 
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/76dbc906-144e-49bf-84e2-63dcef65fb17%40googlegroups.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

That must be it. The setting record_generation was software changed it to 
hardware in weewx.conf. Waiting for a archive packet.

On Saturday, May 2, 2020 at 1:35:43 PM UTC-4, Tom Keffer wrote:
>
> Are you using software record generation?
>
> If so, weewx will not retrieve the archive record from the logger and, 
> instead, calculates the archive record in software. The logger is what 
> supplies the number of wind samples, so it is only available if you 
> download an archive record.
>
> -tk
>
> On Sat, May 2, 2020 at 10:27 AM Hyrules > 
> wrote:
>
>> Well that's not it. I ahve reflashed with the wireless version and still 
>> not seeing the rxCheckPercent and Wind Samples
>>
>> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>>>
>>> Crap I think I have and Idea what is happening I might have flashed the 
>>> cabled version firmware. Will try to reflash the wireless version because 
>>> my station is wireless.
>>>
>>> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:

 Hi everyone,

 I have a vantage pro 2 and was wondering what might be the issue of the 
 following my rc_CheckPercent is always at zero. I have a point in my sql 
 data when I temporarily got some value but at the moment it's zero. This 
 is 
 happening in Weewx 4.0 but was also happening in Weewx 3.9.x
 Also is it possible to get the number of wind sample ? The skin that 
 i'm creating requires it and i have hard time finding any info on it in 
 the 
 documentation.

 Anyone has any input.

 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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/43011f58-be98-44a2-8e71-3dd1711be9bf%40googlegroups.com.

Re: [weewx-user] weewx 4.0 fails connecting to Vantage Vue

2020-05-02 Thread Andre C

I first tried wee_device --dump in order to salvage the logger data. This 
failed due to a CRC16 error.
So as a last resort I cleared the memory.
As a net result i'm missing archive record fot about a day and a half.
The goood news is that the console output is monitored again!!!

thanks a lot for your help,

Andre

Op zaterdag 2 mei 2020 19:45:26 UTC+2 schreef Tom Keffer:
>
> I've seen this a few times. Try clearing the logger memory:
>
> wee_device --clear-memory
>
> -tk
>
> On Sat, May 2, 2020 at 10:03 AM Andre C > 
> wrote:
>
>> After shutting down power, re-install the WeatherLink-IP and re-powering, 
>> the Vantage Vue console is now detected again!
>> However, another error message arises:
>>
>> May  2 18:50:14 Domo weewx[12892] DEBUG weewx.drivers.vantage: Getting 
>> archive packets since 2020-05-01 11:35:00 CEST (1588325700)
>> May  2 18:50:15 Domo weewx[12892] DEBUG weewx.drivers.vantage: Gentle 
>> wake up of console successful
>> May  2 18:50:16 Domo weewx[12892] DEBUG weewx.drivers.vantage: Retrieving 
>> 3 page(s); starting index= 0
>> May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine: Internal error 
>> detected. Catchup abandoned
>> May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine:  Unknown 
>> archive type = 0xdd
>>
>> The starting point of weewx reflects the last record in the archive table 
>> (I assume the 2-hour time difference is due to the delta between localtime 
>> and UTC):
>> sqlite3 /var/lib/weewx/weewx.sdb
>> sqlite>SELECT datetime(dateTime,'unixepoch') FROM archive ORDER BY 
>> dateTime DESC LIMIT 1;
>> 2020-05-01 09:35:00
>>
>> Is this "Unknown archivetpe = 0xDD" a known issue ?
>>
>> Andre
>>
>>
>> Op zaterdag 2 mei 2020 06:54:58 UTC+2 schreef Andre C:
>>>
>>> Attached the tcpdump output from the communication between weewx running 
>>> on a raspberry PI and the vantage Vue console.
>>> There is communication, but no data transfer.
>>>
>>> Running telnet:
>>>
>>> Trying 192.168.178.10...
>>> Connected to 192.168.178.10.
>>> Escape character is '^]'.VER
>>>
>>> OK
>>> RXTEST
>>>
>>> OK
>>> RXCHECK
>>>
>>> OK
>>>
>>> I hope this helps.
>>>
>>> Andre
>>>
>>> Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:

 If you open up a telnet session to the Vue, can you communicate with it?

 Use the connectivity test 
 ,
  
 except use telnet. 

 On Fri, May 1, 2020 at 12:31 PM Andre C  wrote:

> After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes 
> the Vantage Vue console.
>
> The console has a serial to IP link, so weewx communicates over 
> Ethernet.
> Below the output from syslog:
>
> May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
> May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx 
> version 4.0.0
> May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3 
> (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
> May  1 21:20:35 Domo weewx[420] INFO __main__: Platform 
> Linux-4.19.97-v7+-armv7l-with-debian-10.3
> May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
> May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is 
> /var/run/weewx.pid
> May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
> May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
> May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver 
> version is 3.2.0
> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up 
> ethernet host 192.168.178.10 on port 2. timeout=4.0, 
> tcp_send_delay=0.5
> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No  
> received from console
> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: 
> _determine_hardware; retry #0
> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No  
> received from console
> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: 
> _determine_hardware; retry #1
> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No  
> received from console
> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: 
> _determine_hardware; retry #2
> May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No  
> received from console
> May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage: 
> _determine_hardware; retry #3
> May  1

Re: [weewx-user] Re: Weewx will only work for a week then stops

I would guess that cmon is using an undocumented prerequisite: future.

Under Python 2, try

*pip install future*

-tk

On Sat, May 2, 2020 at 10:44 AM Luc Theoret  wrote:

> Hi Luc,
>
> I have updated to the version of cmon provide in your link.
>
> I did a wee_extension weewx-cmon-master.zip
> everthing i think went OK, but now weewx wont start I get this error:
>
> May  2 11:37:21 weewx-pi systemd[1]: Started Session c3 of user pi.
> May  2 11:37:24 weewx-pi weewx[556]: sdr: MainThread: timed out waiting
> for stderr-thread
> May  2 11:37:24 weewx-pi weewx[556]: engine: Caught unrecoverable
> exception in engine:
> May  2 11:37:24 weewx-pi weewx[556]:   No module named builtins
> May  2 11:37:24 weewx-pi weewx[556]:   Traceback (most recent call
> last):
> May  2 11:37:24 weewx-pi weewx[556]: File
> "/usr/share/weewx/weewx/engine.py", line 888, in main
> May  2 11:37:24 weewx-pi weewx[556]:   engine =
> engine_class(config_dict)
> May  2 11:37:24 weewx-pi weewx[556]: File
> "/usr/share/weewx/weewx/engine.py", line 78, in __init__
> May  2 11:37:24 weewx-pi weewx[556]: 
> self.loadServices(config_dict)
> May  2 11:37:24 weewx-pi weewx[556]: File
> "/usr/share/weewx/weewx/engine.py", line 142, in loadServices
> May  2 11:37:24 weewx-pi weewx[556]: 
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
> May  2 11:37:24 weewx-pi weewx[556]: File
> "/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object
> May  2 11:37:24 weewx-pi weewx[556]:   mod = __import__(module)
> May  2 11:37:24 weewx-pi weewx[556]: File
> "/usr/share/weewx/user/cmon.py", line 124, in 
> May  2 11:37:24 weewx-pi weewx[556]:   from builtins import
> input
> May  2 11:37:24 weewx-pi weewx[556]:   ImportError: No module
> named builtins
> May  2 11:37:24 weewx-pi weewx[556]:   Exiting.
>
> Luc
>
>
> On Saturday, May 2, 2020 at 7:47:18 AM UTC-6, Luc Heijst wrote:
>>
>> Hi Luc,
>>
>> The error:
>> ValueError: accum: ScalarStats.addHiLo expected float or int, got type
>> '' ('4552332')
>> is caused by an old version of weewx_cmon. The latest version (0.20)
>> solves this, See: https://github.com/matthewwall/weewx-cmon
>>
>> Also your syslog show several errors with outTemp, like:
>> cheetahgenerator:  Reason: Unknown daily summary type outTemp
>>
>> Check your database if you have a value outTemp.
>> If not, check your skin files for the use of outTemp.
>>
>> Luc Heijst
>>
>> On Saturday, 2 May 2020 02:33:45 UTC-3, Luc Theoret wrote:
>>>
>>> Hi,
>>>
>>> I have been trying to get weewx to record my acurite data using sdr
>>> RTL_433 for about a year now.
>>> The system I have almost running is a raspberry pi 3 running on respbian
>>> stretch. it has an external real time clock attached.
>>> weewx runs consistently for a week then stops. I was finally find the
>>> log entry for the stop, see attached file.
>>> In the file is the last successful update, then the error and the exit.
>>> I also included the config file.
>>>
>>>
>>> I have tried to reinstall on new SD card with Buster but cannot get the
>>> radio to work. tried blackballing stuff blindly (not knowing what doing).
>>> Then I went back to this SD card. changed a couple of things and it ran.
>>> But as usual after a week like clockwork it stopped.
>>>
>>> Luc
>>>
>> --
> 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/3e75cbad-1eb4-4a83-b58a-f805ea48ce4a%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/CAPq0zEDHcfbLns4tizYNekWnxXrTWAwy%2B0t00fdbxFC4p-TQQw%40mail.gmail.com.

Re: [weewx-user] weewx 4.0 fails connecting to Vantage Vue

I've seen this a few times. Try clearing the logger memory:

wee_device --clear-memory

-tk

On Sat, May 2, 2020 at 10:03 AM Andre C  wrote:

> After shutting down power, re-install the WeatherLink-IP and re-powering,
> the Vantage Vue console is now detected again!
> However, another error message arises:
>
> May  2 18:50:14 Domo weewx[12892] DEBUG weewx.drivers.vantage: Getting
> archive packets since 2020-05-01 11:35:00 CEST (1588325700)
> May  2 18:50:15 Domo weewx[12892] DEBUG weewx.drivers.vantage: Gentle wake
> up of console successful
> May  2 18:50:16 Domo weewx[12892] DEBUG weewx.drivers.vantage: Retrieving
> 3 page(s); starting index= 0
> May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine: Internal error
> detected. Catchup abandoned
> May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine:  Unknown archive
> type = 0xdd
>
> The starting point of weewx reflects the last record in the archive table
> (I assume the 2-hour time difference is due to the delta between localtime
> and UTC):
> sqlite3 /var/lib/weewx/weewx.sdb
> sqlite>SELECT datetime(dateTime,'unixepoch') FROM archive ORDER BY
> dateTime DESC LIMIT 1;
> 2020-05-01 09:35:00
>
> Is this "Unknown archivetpe = 0xDD" a known issue ?
>
> Andre
>
>
> Op zaterdag 2 mei 2020 06:54:58 UTC+2 schreef Andre C:
>>
>> Attached the tcpdump output from the communication between weewx running
>> on a raspberry PI and the vantage Vue console.
>> There is communication, but no data transfer.
>>
>> Running telnet:
>>
>> Trying 192.168.178.10...
>> Connected to 192.168.178.10.
>> Escape character is '^]'.VER
>>
>> OK
>> RXTEST
>>
>> OK
>> RXCHECK
>>
>> OK
>>
>> I hope this helps.
>>
>> Andre
>>
>> Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:
>>>
>>> If you open up a telnet session to the Vue, can you communicate with it?
>>>
>>> Use the connectivity test
>>> ,
>>> except use telnet.
>>>
>>> On Fri, May 1, 2020 at 12:31 PM Andre C  wrote:
>>>
 After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes the
 Vantage Vue console.

 The console has a serial to IP link, so weewx communicates over
 Ethernet.
 Below the output from syslog:

 May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
 May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx
 version 4.0.0
 May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3
 (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
 May  1 21:20:35 Domo weewx[420] INFO __main__: Platform
 Linux-4.19.97-v7+-armv7l-with-debian-10.3
 May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
 May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is
 /var/run/weewx.pid
 May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration file
 /etc/weewx/weewx.conf
 May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
 May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station type
 Vantage (weewx.drivers.vantage)
 May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
 May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
 May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver
 version is 3.2.0
 May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up
 ethernet host 192.168.178.10 on port 2. timeout=4.0, tcp_send_delay=0.5
 May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle
 wake up of console successful
 May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #0
 May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #1
 May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #2
 May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #3
 May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: Unable to
 read hardware type; raise WeeWxIOError
 May  1 21:20:38 Domo weewx[443] ERROR weewx.engine: Import of driver
 failed: Unable to read hardware type ()
 May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
 Traceback (most recent call last):
 May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
 "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
 May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:

[weewx-user] Re: Weewx will only work for a week then stops

2020-05-02 Thread Luc Theoret

Hi Luc,

I have updated to the version of cmon provide in your link.

I did a wee_extension weewx-cmon-master.zip
everthing i think went OK, but now weewx wont start I get this error:

May  2 11:37:21 weewx-pi systemd[1]: Started Session c3 of user pi.
May  2 11:37:24 weewx-pi weewx[556]: sdr: MainThread: timed out waiting for 
stderr-thread
May  2 11:37:24 weewx-pi weewx[556]: engine: Caught unrecoverable exception 
in engine:
May  2 11:37:24 weewx-pi weewx[556]:   No module named builtins
May  2 11:37:24 weewx-pi weewx[556]:   Traceback (most recent call 
last):
May  2 11:37:24 weewx-pi weewx[556]: File 
"/usr/share/weewx/weewx/engine.py", line 888, in main
May  2 11:37:24 weewx-pi weewx[556]:   engine = 
engine_class(config_dict)
May  2 11:37:24 weewx-pi weewx[556]: File 
"/usr/share/weewx/weewx/engine.py", line 78, in __init__
May  2 11:37:24 weewx-pi weewx[556]:   
self.loadServices(config_dict)
May  2 11:37:24 weewx-pi weewx[556]: File 
"/usr/share/weewx/weewx/engine.py", line 142, in loadServices
May  2 11:37:24 weewx-pi weewx[556]:   
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, config_dict))
May  2 11:37:24 weewx-pi weewx[556]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1107, in _get_object
May  2 11:37:24 weewx-pi weewx[556]:   mod = __import__(module)
May  2 11:37:24 weewx-pi weewx[556]: File 
"/usr/share/weewx/user/cmon.py", line 124, in 
May  2 11:37:24 weewx-pi weewx[556]:   from builtins import 
input
May  2 11:37:24 weewx-pi weewx[556]:   ImportError: No module named 
builtins
May  2 11:37:24 weewx-pi weewx[556]:   Exiting.

Luc
 

On Saturday, May 2, 2020 at 7:47:18 AM UTC-6, Luc Heijst wrote:
>
> Hi Luc,
>
> The error:
> ValueError: accum: ScalarStats.addHiLo expected float or int, got type 
> '' ('4552332')
> is caused by an old version of weewx_cmon. The latest version (0.20) 
> solves this, See: https://github.com/matthewwall/weewx-cmon
>
> Also your syslog show several errors with outTemp, like:
> cheetahgenerator:  Reason: Unknown daily summary type outTemp
>
> Check your database if you have a value outTemp. 
> If not, check your skin files for the use of outTemp.
>
> Luc Heijst
>
> On Saturday, 2 May 2020 02:33:45 UTC-3, Luc Theoret wrote:
>>
>> Hi,
>>
>> I have been trying to get weewx to record my acurite data using sdr 
>> RTL_433 for about a year now.
>> The system I have almost running is a raspberry pi 3 running on respbian 
>> stretch. it has an external real time clock attached.
>> weewx runs consistently for a week then stops. I was finally find the log 
>> entry for the stop, see attached file.
>> In the file is the last successful update, then the error and the exit. 
>> I also included the config file.
>>
>>
>> I have tried to reinstall on new SD card with Buster but cannot get the 
>> radio to work. tried blackballing stuff blindly (not knowing what doing).
>> Then I went back to this SD card. changed a couple of things and it ran. 
>> But as usual after a week like clockwork it stopped.
>>
>> Luc
>>
>

-- 
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/3e75cbad-1eb4-4a83-b58a-f805ea48ce4a%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

It should. I'm not sure how thoroughly it as been tested under Python 3.

On Sat, May 2, 2020 at 9:17 AM Pete Geenhuizen  wrote:

> Oops my bad i got confused by the similar driver name, I'm using the
> wx23xx driver which is working just fine under V3 so will it work in V4?
>
> On 5/2/20 11:47 AM, Tom Keffer wrote:
>
> wh23xx is not a supported weather station under WeeWX V3 or V4. No plans
> to change that.
>
> However, I will see what I can do about getting the wh23xx 3rd party
> extension updated.
>
> -tk
>
> On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen 
> wrote:
> --
> 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/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com
> 
> .
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* , and is
> believed to be clean.
>
>
> --
> Unencumbered by the thought process.
>  -- Click and Clack the Tappet brothers
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* , and is
> believed to be clean.
>

-- 
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/CAPq0zEB2YtYHWcGUcKXCAr2%3DTDkXNTaQe1Z%3D1NmrZYn9bFy8ng%40mail.gmail.com.

Re: [weewx-user] Re: rxCheckPercent always zero and number of wind samples

Are you using software record generation?

If so, weewx will not retrieve the archive record from the logger and,
instead, calculates the archive record in software. The logger is what
supplies the number of wind samples, so it is only available if you
download an archive record.

-tk

On Sat, May 2, 2020 at 10:27 AM Hyrules  wrote:

> Well that's not it. I ahve reflashed with the wireless version and still
> not seeing the rxCheckPercent and Wind Samples
>
> On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>>
>> Crap I think I have and Idea what is happening I might have flashed the
>> cabled version firmware. Will try to reflash the wireless version because
>> my station is wireless.
>>
>> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>>
>>> Hi everyone,
>>>
>>> I have a vantage pro 2 and was wondering what might be the issue of the
>>> following my rc_CheckPercent is always at zero. I have a point in my sql
>>> data when I temporarily got some value but at the moment it's zero. This is
>>> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>>> Also is it possible to get the number of wind sample ? The skin that i'm
>>> creating requires it and i have hard time finding any info on it in the
>>> documentation.
>>>
>>> Anyone has any input.
>>>
>>> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%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/CAPq0zEDvwef%2BOo%2B8%3DbNTiYgGw2mbgLh2-7W1%3DaObqEoxQT-anQ%40mail.gmail.com.

[weewx-user] Re: rxCheckPercent always zero and number of wind samples

Well that's not it. I ahve reflashed with the wireless version and still 
not seeing the rxCheckPercent and Wind Samples

On Saturday, May 2, 2020 at 12:18:08 PM UTC-4, Hyrules wrote:
>
> Crap I think I have and Idea what is happening I might have flashed the 
> cabled version firmware. Will try to reflash the wireless version because 
> my station is wireless.
>
> On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>>
>> Hi everyone,
>>
>> I have a vantage pro 2 and was wondering what might be the issue of the 
>> following my rc_CheckPercent is always at zero. I have a point in my sql 
>> data when I temporarily got some value but at the moment it's zero. This is 
>> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
>> Also is it possible to get the number of wind sample ? The skin that i'm 
>> creating requires it and i have hard time finding any info on it in the 
>> documentation.
>>
>> Anyone has any input.
>>
>> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/de51f119-74a6-4b4b-a7fb-bb8b68e3f6fe%40googlegroups.com.

Re: [weewx-user] weewx 4.0 fails connecting to Vantage Vue

2020-05-02 Thread Andre C

After shutting down power, re-install the WeatherLink-IP and re-powering, 
the Vantage Vue console is now detected again!
However, another error message arises:

May  2 18:50:14 Domo weewx[12892] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2020-05-01 11:35:00 CEST (1588325700)
May  2 18:50:15 Domo weewx[12892] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful
May  2 18:50:16 Domo weewx[12892] DEBUG weewx.drivers.vantage: Retrieving 3 
page(s); starting index= 0
May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine: Internal error 
detected. Catchup abandoned
May  2 18:50:17 Domo weewx[12892] ERROR weewx.engine:  Unknown archive 
type = 0xdd

The starting point of weewx reflects the last record in the archive table 
(I assume the 2-hour time difference is due to the delta between localtime 
and UTC):
sqlite3 /var/lib/weewx/weewx.sdb
sqlite>SELECT datetime(dateTime,'unixepoch') FROM archive ORDER BY dateTime 
DESC LIMIT 1;
2020-05-01 09:35:00

Is this "Unknown archivetpe = 0xDD" a known issue ?

Andre


Op zaterdag 2 mei 2020 06:54:58 UTC+2 schreef Andre C:
>
> Attached the tcpdump output from the communication between weewx running 
> on a raspberry PI and the vantage Vue console.
> There is communication, but no data transfer.
>
> Running telnet:
>
> Trying 192.168.178.10...
> Connected to 192.168.178.10.
> Escape character is '^]'.VER
>
> OK
> RXTEST
>
> OK
> RXCHECK
>
> OK
>
> I hope this helps.
>
> Andre
>
> Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:
>>
>> If you open up a telnet session to the Vue, can you communicate with it?
>>
>> Use the connectivity test 
>> ,
>>  
>> except use telnet. 
>>
>> On Fri, May 1, 2020 at 12:31 PM Andre C  wrote:
>>
>>> After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes the 
>>> Vantage Vue console.
>>>
>>> The console has a serial to IP link, so weewx communicates over Ethernet.
>>> Below the output from syslog:
>>>
>>> May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx 
>>> version 4.0.0
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3 
>>> (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Platform 
>>> Linux-4.19.97-v7+-armv7l-with-debian-10.3
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration file 
>>> /etc/weewx/weewx.conf
>>> May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
>>> May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station type 
>>> Vantage (weewx.drivers.vantage)
>>> May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
>>> May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
>>> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver 
>>> version is 3.2.0
>>> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up 
>>> ethernet host 192.168.178.10 on port 2. timeout=4.0, tcp_send_delay=0.5
>>> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle wake 
>>> up of console successful
>>> May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No  
>>> received from console
>>> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: 
>>> _determine_hardware; retry #0
>>> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No  
>>> received from console
>>> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: 
>>> _determine_hardware; retry #1
>>> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No  
>>> received from console
>>> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage: 
>>> _determine_hardware; retry #2
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No  
>>> received from console
>>> May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage: 
>>> _determine_hardware; retry #3
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: Unable to 
>>> read hardware type; raise WeeWxIOError
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.engine: Import of driver 
>>> failed: Unable to read hardware type ()
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:   
>>> Traceback (most recent call last):
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File 
>>> "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:   
>>> self.console = loader_function(config_dict, self)
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File 
>>> "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>>> May  1 21:20:38 Domo weewx[443] CRITICAL

[weewx-user] Re: need to modify daily rain in weewx.sdb

On Saturday, May 2, 2020 at 8:50:45 AM UTC-7, Bob Grattan wrote:
>
> 1.  An easy way to modify weewx.sdb when I need to modify the rain amount. 
> I have used DB Browser (SQLite) in the past but am not certain this is the 
> easiest. If possible, I want to avoid the SQL search/modify mode as my 
> skills are limited.
>
> 2. Once the "rain" amount in weewx.sdb is modified, how do I get the 
> system to incorporate the new total in the various displays such as for 
> month and year? In wview I was able to erase certain indexes and they were 
> recreated using the new values from the db; however, I'm not sure how this 
> works in weewx.
>
>
>
See https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data for the 
procedure

I would recommend you 'do' use sqlite3 search/modify commands 'and' try to 
extend your skills.  The time will be well spent.   It's very 
straightforward once you get over the fear/uncertainty hurdle.

Definitely work off of a copy of your weewx database to become comfortable 
with the few steps in the procedure.


 

-- 
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/0ef94d12-96dd-44c6-afed-cd9585aa466b%40googlegroups.com.

[weewx-user] Re: rxCheckPercent always zero and number of wind samples

Crap I think I have and Idea what is happening I might have flashed the 
cabled version firmware. Will try to reflash the wireless version because 
my station is wireless.

On Saturday, May 2, 2020 at 11:11:31 AM UTC-4, Hyrules wrote:
>
> Hi everyone,
>
> I have a vantage pro 2 and was wondering what might be the issue of the 
> following my rc_CheckPercent is always at zero. I have a point in my sql 
> data when I temporarily got some value but at the moment it's zero. This is 
> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
> Also is it possible to get the number of wind sample ? The skin that i'm 
> creating requires it and i have hard time finding any info on it in the 
> documentation.
>
> Anyone has any input.
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9aae5ca-398c-438f-bddf-4f63d19d6759%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Pete Geenhuizen

Oops my bad i got confused by the similar driver name, I'm using the 
wx23xx driver which is working just fine under V3 so will it work in V4?


On 5/2/20 11:47 AM, Tom Keffer wrote:
wh23xx is not a supported weather station under WeeWX V3 or V4. No 
plans to change that.


However, I will see what I can do about getting the wh23xx 3rd party 
extension updated.


-tk

On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen > wrote:

--
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/CAPq0zEDvXyyw-Le12K8mWVqGRsNkEXgfcd%2Behyji7xYv2ew9Dw%40mail.gmail.com 
.


--
This message has been scanned for viruses and
dangerous content by *MailScanner* , and is
believed to be clean. 


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

--
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/a554794f-6025-9fca-b898-f9b9a1d25a03%40geenhuizen.net.

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

Shouldnt it be taking in api_key in test mode too? Is that intentional?

On Sat, 2 May 2020 at 20:52, Tom Keffer  wrote:

> Thanks for catching the problem with json.load(). Fixed in commit c05f76b
> 
>
> As you discovered, I think the api_key code is working properly.
>
> On Sat, May 2, 2020 at 8:04 AM Praveen Chandrasekaran <
> praveen.c...@gmail.com> wrote:
>
>> I think I figured out API key issue. It's not read if in test mode and
>> hence causes error. Attached snippet
>>
>> On Sat, 2 May 2020, 19:40 Praveen Chandrasekaran, 
>> wrote:
>>
>>> I didnt attached console output because i just ran wunderfixer at shell.
>>> I was getting HTTP 401 error. printed api_key from within wunderfixer it
>>> was "None". Then edited wunderfixer with the api key locally and that fixed
>>> that issue
>>>
>>> On Sat, 2 May 2020 at 19:32, Tom Keffer  wrote:
>>>
 Log? Console output?

 On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
 praveen.c...@gmail.com> wrote:

> 2 issues:
>
> 1) API key not getting passed. Hacked wunderfixer with local api key
> instead of passing
> 2) After 1 I get error  that  JSON object must be str not bytes.
>
> On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran
> wrote:
>>
>> Hi,
>>
>> My wunderfixer was working till yesterday (I know for sure because I
>> have used it to fill missing data often recently)
>>
>> After updating to v4, the wunderfixer stopped working. The API key
>> looks fine but I am getting HTTP 401 FORBIDDEN ERROR.
>>
>> Regards,
>> Praveen
>>
> --
> 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/e6608887-e63e-4844-955b-da4437b2f662%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/PSemiQmyCt0/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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWjPPZX-B9eZsU1VscKP9j1fMQ0d9iEOhf9UwPKMO%2B3Cg%40mail.gmail.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/PSemiQmyCt0/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/CAPq0zEAB22_VgJ%3DS9i7ZABuffq%2B2f48ri%2BektbMpJQOQgWcdPg%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWvHUz1hSTxNY8rQcXQJV-fTP_0mXwx02sNiPBDUSqPNA%40mail.gmail.com.

Re: [weewx-user] rxCheckPercent always zero and number of wind samples

Hi Tom,

1) yes sorry exactly.

2) yes with heidi sql I have explored the database. made a select on the 
archive_day_rxCheckPercent table.

3) Here is the output of a loop and a record. 

REC:2020-05-02 11:58:00 EDT (1588435080) altimeter: 29.9361792613, 
appTemp: 56.9873572311, bar_calibration: -0.032, barometer: 29.9380645161, 
bar_reduction: 0.002, cloudbase: 5220.57597677, consBatteryVoltage: None, 
dateTime: 1588435080, dayET: 0.0, dayRain: 0.0, dewpoint: 39.4244525587, ET: 
None, extraAlarm1: 0.0, extraAlarm2: 0.0, extraAlarm3: 0.0, extraAlarm4: 0.0
, extraAlarm5: 0.0, extraAlarm6: 0.0, extraAlarm7: 0.0, extraAlarm8: 0.0, 
forecastIcon: 6.0, forecastRule: 45.0, heatindex: 60.3258064516, hourRain: 
0.0, humidex: 61.7387096774, inDewpoint: 46.0149745351, inHumidity: 48.0, 
insideAlarm: 0.0, inTemp: 66.3, interval: 1, leafWet4: 0.0, maxSolarRad: 
872.308269831, monthET: 0.0, monthRain: 0.29, outHumidity: 44.1612903226, 
outsideAlarm1: 0.0, outsideAlarm2: 0.0, outTemp: 61.7387096774, pressure: 
29.708654238, pressure_raw: 29.7080625, rain: 0.0, rain15: 0.0, rain24: 0.01
, rainAlarm: 0.0, rainRate: 0.0, soilLeafAlarm1: 0.0, soilLeafAlarm2: 0.0, 
soilLeafAlarm3: 0.0, soilLeafAlarm4: 0.0, stormRain: 0.0, sunrise: 
1588414608.0, sunset: 1588465056.0, trendIcon: -20.0, txBatteryStatus: None, 
usUnits: 1, windchill: 61.8741935484, windDir: 207.502892677, windGust: 8.0, 
windGust10: 0.8, windGustDir: 138.0, windGustDir10: 225.0, windrun: 
0.0731182795699, windSpeed: 4.38709677419, windSpeed10: 3.2, windSpeed2: 4.7
, yearET: 0.0, yearRain: 8.07
LOOP:   2020-05-02 11:58:17 EDT (1588435097) altimeter: 29.9393849737, 
appTemp: 56.2444565315, barometer: 29.939, cloudbase: 5111.7782065, 
consBatteryVoltage: 4.54, dateTime: 1588435097, dayET: 0.0, dayRain: 0.0, 
dewpoint: 40.2321758914, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 
0, forecastIcon: 6, forecastRule: 45, heatindex: 61.8, humidex: 61.8, 
inDewpoint: 46.0149745351, inHumidity: 48.0, insideAlarm: 0, inTemp: 66.3, 
leafWet4: 0.0, maxSolarRad: 873.09899593, monthET: 0.0, monthRain: 0.29, 
outHumidity: 45.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 61.8, 
pressure: 29.7102273392, rain: 0.0, rainAlarm: 0, rainRate: 0.0, 
soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, 
stormRain: 0.0, sunrise: 1588414608.0, sunset: 1588465056.0, txBatteryStatus
: 0, usUnits: 1, windchill: 61.8, windDir: 218.0, windGust: 8.0, windGustDir
: 267.0, windSpeed: 6.0, windSpeed10: 3.0, yearET: 0.0, yearRain: 8.07
LOOP:   2020-05-02 11:58:18 EDT (1588435098) altimeter: 29.935, appTemp: 
56.2444565315, bar_calibration: -0.032, barometer: 29.939, bar_reduction: 
0.002, cloudbase: 5111.7782065, dateTime: 1588435098, dayET: 0.0, dayRain: 
0.0, dewpoint: 40.0, heatindex: 59.0, hourRain: 0.0, humidex: 61.8, 
inDewpoint: 46.0149745351, inHumidity: 48.0, inTemp: 66.3, maxSolarRad: 
873.115761147, outHumidity: 45.0, outTemp: 61.8, pressure: 29.709, 
pressure_raw: 29.709, rain: 0.0, rain15: 0.0, rain24: 0.01, rainRate: 0.0, 
stormRain: 0.0, trendIcon: -20, usUnits: 1, windchill: 62.0, windDir: 218.0, 
windGust: 8.0, windGust10: 0.8, windGustDir: 267.0, windGustDir10: 225.0, 
windSpeed: 6.0, windSpeed10: 3.2, windSpeed2: 5.0

4) Here is the output. It seems in order.
Davis Vantage EEPROM settings:

CONSOLE TYPE:   Vantage Pro2

CONSOLE FIRMWARE:
  Date: Sep 11 2017
  Version:  3.80

CONSOLE SETTINGS:
  Archive interval: 900 (seconds)
  Altitude: 210 (foot)
  Wind cup type:large
  Rain bucket type: 0.01 inches
  Rain year start:  1
  Onboard time: 2020-05-02 11:40:22

CONSOLE DISPLAY UNITS:
  Barometer:mbar
  Temperature:  degree_10C
  Rain: mm
  Wind: km_per_hour

CONSOLE STATION INFO:
  Latitude (onboard):   +45.5
  Longitude (onboard):  -75.6
  Use manual or auto DST?   AUTO
  DST setting:  N/A
  Use GMT offset or zone code?  ZONE_CODE
  Time zone code:   10
  GMT offset:   N/A
  Temperature logging:  LAST
  Retransmit channel:   OFF (0)

TRANSMITTERS:
  Channel   Receive   Repeater  Type
 1  inactivenone(N/A)
 2  inactivenone(N/A)
 3  inactivenone(N/A)
 4  inactivenone(N/A)
 5  inactivenone(N/A)
 6  inactivenone(N/A)
 7  active  noneiss
 8  inactivenone(N/A)

RECEPTION STATS:
  Total packets received:   14085
  Total packets missed: 185
  Number of resynchronizations: 3

Re: [weewx-user] weewx 4.0 fails connecting to Vantage Vue

2020-05-02 Thread Andre Abepol

I have a WeatherLink IP connected to theVantage Vue console.
Since about 6 weeks a Vantage Pro2 ISS is installed. At the same time I
moved from the old wview softwareto weewx, which worked like a charm.
Until last week. First I was getting error messages like 'received
unexpected 0xDD".
I found some tips, this might be due to clock drift and/or old software in
the console.
Therefore I upgraded the console to the latest software ()1.15). The
upgrade however did not solve the "0xDD" error messages. And now even these
message are gone  and the whole communications is stuck.
Something between the WeatherLink IP and the console ??

Andre


Op za 2 mei 2020 om 14:08 schreef Tom Keffer :

> Thanks.
>
> Can you give us some details about your hardware setup? From your
> description that "the console has a serial to IP link" I had assumed that
> your Vantage Vue had a normal WeatherLink serial logger
> ,
> which you were accessing via some sort of serial-to-IP converter. Is that
> the case?
>
> Or, are you using the (now discontinued) Vantage WeatherlinkIP logger
> 
> ?
>
> Or, something else?
>
> -tk
>
> On Fri, May 1, 2020 at 9:55 PM Andre C  wrote:
>
>> Attached the tcpdump output from the communication between weewx running
>> on a raspberry PI and the vantage Vue console.
>> There is communication, but no data transfer.
>>
>> Running telnet:
>>
>> Trying 192.168.178.10...
>> Connected to 192.168.178.10.
>> Escape character is '^]'.VER
>>
>> OK
>> RXTEST
>>
>> OK
>> RXCHECK
>>
>> OK
>>
>> I hope this helps.
>>
>> Andre
>>
>> Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:
>>>
>>> If you open up a telnet session to the Vue, can you communicate with it?
>>>
>>> Use the connectivity test
>>> ,
>>> except use telnet.
>>>
>>> On Fri, May 1, 2020 at 12:31 PM Andre C  wrote:
>>>
 After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes the
 Vantage Vue console.

 The console has a serial to IP link, so weewx communicates over
 Ethernet.
 Below the output from syslog:

 May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
 May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx
 version 4.0.0
 May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3
 (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
 May  1 21:20:35 Domo weewx[420] INFO __main__: Platform
 Linux-4.19.97-v7+-armv7l-with-debian-10.3
 May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
 May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is
 /var/run/weewx.pid
 May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration file
 /etc/weewx/weewx.conf
 May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
 May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station type
 Vantage (weewx.drivers.vantage)
 May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
 May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
 May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver
 version is 3.2.0
 May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up
 ethernet host 192.168.178.10 on port 2. timeout=4.0, tcp_send_delay=0.5
 May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle
 wake up of console successful
 May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #0
 May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #1
 May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #2
 May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No 
 received from console
 May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage:
 _determine_hardware; retry #3
 May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: Unable to
 read hardware type; raise WeeWxIOError
 May  1 21:20:38 Domo weewx[443] ERROR weewx.engine: Import of driver
 failed: Unable to read hardware type ()
 May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
 Traceback (most recent call last):
 May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
 "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
 May  1 21:20:38 Domo weewx[443] CRITICAL

[weewx-user] need to modify daily rain in weewx.sdb

2020-05-02 Thread Bob Grattan

Hello,
I have a constant battle with my VP2 tipping bucket rain gauge as it often 
gets clogged with trash. I check it against an accurate manual gauge to 
make sure it's reasonable since I know tipping buckets have problems.
I would like suggestions for the following:

1.  An easy way to modify weewx.sdb when I need to modify the rain amount. 
I have used DB Browser (SQLite) in the past but am not certain this is the 
easiest. If possible, I want to avoid the SQL search/modify mode as my 
skills are limited.

2. Once the "rain" amount in weewx.sdb is modified, how do I get the system 
to incorporate the new total in the various displays such as for month and 
year? In wview I was able to erase certain indexes and they were recreated 
using the new values from the db; however, I'm not sure how this works in 
weewx.

I am running weewx 3.x.x (latest using "setup") on Ubuntu 18 and my station 
is a Davis VP2+.

Thanks for your help. Please take care and stay safe in these difficult 
times.

Bob
grattans.org/wx

-- 
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/d8d97b91-622a-4e68-b261-3a6b38d340f0%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

wh23xx is not a supported weather station under WeeWX V3 or V4. No plans to
change that.

However, I will see what I can do about getting the wh23xx 3rd party
extension updated.

-tk

On Sat, May 2, 2020 at 8:42 AM Pete Geenhuizen  wrote:

> OK so now I'm a little confused, is/will V4 support WH23xx?  I'm using it
> now and if it won't work under V4 then I should forgo my planned upgrade to
> V4 right?
> On 2020-05-02 11:30, Tom Keffer wrote:
>
> Believe me, I'm mighty tempted to trim the list of supported weather
> stations!
>
> On Sat, May 2, 2020 at 7:29 AM Jever Hägen 
> wrote:
>
>> Thanks for thinking about of doing that work.
>>
>> yes, there are not very much wh23xx stations registered beside mine.
>> But overall they are on rank 9 ;-)
>> 1 Vantage 537
>> 2 FineOffsetUSB 274
>> 3 AcuRite 147
>> 4 Interceptor 87
>> 5 TE923 67
>> 6 WMR100 40
>> 7 SDR 33
>> 8 WMR200 29
>> *9* *WH23xx* *26*
>> 10 WS23xx 24
>> 11 WS28xx 24
>> 12 netatmo 17
>> 13 Ultimeter 15
>> 14 WeatherFlowUDP 14
>> 15 WMR300 14
>> 16 FileParse 11
>> 17 Simulator 11
>>
>> Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:
>>>
>>> The weewx usage map  shows 26
>>> installations (out of 1471 registered stations), or less than 2%. That's
>>> not enough usage to justify the work. Get your friends to use it!
>>>
>>> Still, I'll see what I can do...
>>>
>>> -tk
>>>
>>> On Sat, May 2, 2020 at 5:30 AM Jever Hägen  wrote:
>>>
 Hi Tom,

 yes I know, but wouldn't it be possible for you or some of the guys out
 there to integrate the driver into weewx v4?

 Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>
> It looks like the wh23xx driver has not been ported to Python 3 and
> weewx V4 (it's not actually part of weewx).
>
> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин 
> wrote:
>
>> I had the same problem today, when weewx updated to 4. The station is
>> WH2310. I made a little analyze of problem and found that import of
>> log_traceback in the ws23xx driver no more valid, because of changings in
>> weewx.
>> Try to replace
>> the string in the file wh23xx.py:
>> from weeutil.weeutil import timestamp_to_string, log_traceback
>>
>> to:
>> from weeutil.weeutil import timestamp_to_string
>> from weeutil.log log_traceback
>>
>> This is solved my problem.
>> I made pull request to the sources of this driver, hope that it will
>> be accepted.
>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to weewx...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%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/CAPq0zEDxnKzss%2BsgcJeoFasbaLkOjB8mi5VqEA4%3DFp0ubbP%3DWw%40mail.gmail.com
> 
> .
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* , and is
> believed to be clean.
>
> --
> Unencumbered by the thought process.
>  -- Click and Clack the Tappet brothers
>
>
> --
> This message has been scanned for viruses and
> dangerous content

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Pete Geenhuizen

OK so now I'm a little confused, is/will V4 support WH23xx? I'm using
it now and if it won't work under V4 then I should forgo my planned
upgrade to V4 right?

On 2020-05-02 11:30, Tom Keffer wrote:
Believe me, I'm mighty tempted to trim the list of supported weather
stations!

On Sat, May 2, 2020 at 7:29 AM Jever Hägen > wrote:

Thanks for thinking about of doing that work.

yes, there are not very much wh23xx stations registered beside mine.
But overall they are on rank 9 ;-)
1 Vantage 537
2 FineOffsetUSB 274
3 AcuRite 147
4 Interceptor 87
5 TE923 67
6 WMR100 40
7 SDR 33
8 WMR200 29
*9* *WH23xx**26*
10 WS23xx 24
11 WS28xx 24
12 netatmo 17
13 Ultimeter 15
14 WeatherFlowUDP 14
15 WMR300 14
16 FileParse 11
17 Simulator 11

Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:

The weewx usage map shows 26
installations (out of 1471 registered stations), or less than
2%. That's not enough usage to justify the work. Get your
friends to use it!

Still, I'll see what I can do...

-tk

On Sat, May 2, 2020 at 5:30 AM Jever Hägen
wrote:

Hi Tom,

yes I know, but wouldn't it be possible for you or some of
the guys out there to integrate the driver into weewx v4?

Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:

It looks like the wh23xx driver has not been ported to
Python 3 and weewx V4 (it's not actually part of weewx).

On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин
wrote:

I had the same problem today, when weewx updated
to 4. The station is WH2310. I made a little
analyze of problem and found that import of
log_traceback in the ws23xx driver no more valid,
because of changings in weewx.
Try to replace
the string in the file wh23xx.py:
|
fromweeutil.weeutil
importtimestamp_to_string,log_traceback
|

to:
|
fromweeutil.weeutil importtimestamp_to_string
fromweeutil.log log_traceback
|

This is solved my problem.
I made pull request to the sources of this driver,
hope that it will be accepted.
--
You received this message because you are

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

https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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...@googlegroups.com.
To view this discussion on the web visit

https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%40googlegroups.com

Re: [weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread p q

I upgraded from 3.5. Remarkably painless. Took maybe 15 minutes. 

Thanks!

I had previously set up a duplicate site on a VM and migrated that to 3.9 
and then to 4.0. Doing all the prep work and testing took way longer than 
doing the actual upgrade.

Next job - upgrade Raspian from Stretch to Buster and then move the site to 
Python 3. I expect I'll have a few hiccoughs there due to some custom 
Python 2 code. But I've migrated other apps from 2 to 3, and I wrote the 
custom code to begin with.

On Saturday, May 2, 2020 at 8:08:45 AM UTC-7, vince wrote:
>
> On Friday, May 1, 2020 at 10:26:31 PM UTC-7, Gert Andersen wrote:
>>
>> E: Unable to correct problems, you have held broken packages.
>>
>>
>>
> Please google that exact message and you will find dozens of hits with 
> methods for how to clean this up.  Unfortunately, that particular mesage 
> can be a bit painful to clean up, and occasionally comes with some risk.
>
> FWIW, if you are on a raspberry pi, you 'might' find it simpler to put a 
> new SD card in and simply build a clean system.
>
> is not available but is referred to by another package.
>> This may mean that the package is missing, has been obsoleted, or
>> is only available from another source
>>
>> Again, if you google 'this' message you will get many hits describing 
> what is going on.
>
>  
>

-- 
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/2dfa3994-2980-4094-8974-c495f32e117f%40googlegroups.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

Believe me, I'm mighty tempted to trim the list of supported weather
stations!

On Sat, May 2, 2020 at 7:29 AM Jever Hägen  wrote:

> Thanks for thinking about of doing that work.
>
> yes, there are not very much wh23xx stations registered beside mine.
> But overall they are on rank 9 ;-)
> 1 Vantage 537
> 2 FineOffsetUSB 274
> 3 AcuRite 147
> 4 Interceptor 87
> 5 TE923 67
> 6 WMR100 40
> 7 SDR 33
> 8 WMR200 29
> *9* *WH23xx* *26*
> 10 WS23xx 24
> 11 WS28xx 24
> 12 netatmo 17
> 13 Ultimeter 15
> 14 WeatherFlowUDP 14
> 15 WMR300 14
> 16 FileParse 11
> 17 Simulator 11
>
> Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:
>>
>> The weewx usage map  shows 26
>> installations (out of 1471 registered stations), or less than 2%. That's
>> not enough usage to justify the work. Get your friends to use it!
>>
>> Still, I'll see what I can do...
>>
>> -tk
>>
>> On Sat, May 2, 2020 at 5:30 AM Jever Hägen  wrote:
>>
>>> Hi Tom,
>>>
>>> yes I know, but wouldn't it be possible for you or some of the guys out
>>> there to integrate the driver into weewx v4?
>>>
>>> Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:

 It looks like the wh23xx driver has not been ported to Python 3 and
 weewx V4 (it's not actually part of weewx).

 On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин 
 wrote:

> I had the same problem today, when weewx updated to 4. The station is
> WH2310. I made a little analyze of problem and found that import of
> log_traceback in the ws23xx driver no more valid, because of changings in
> weewx.
> Try to replace
> the string in the file wh23xx.py:
> from weeutil.weeutil import timestamp_to_string, log_traceback
>
> to:
> from weeutil.weeutil import timestamp_to_string
> from weeutil.log log_traceback
>
> This is solved my problem.
> I made pull request to the sources of this driver, hope that it will
> be accepted.
>
> --
> You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%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/CAPq0zEDxnKzss%2BsgcJeoFasbaLkOjB8mi5VqEA4%3DFp0ubbP%3DWw%40mail.gmail.com.

Re: [weewx-user] rxCheckPercent always zero and number of wind samples

A few more details, please

1. By "rc_CheckPercent" I assume you mean "rxCheckPercent"?

2. You said you have "a point in my sql data" where you got some value.
Does this mean you checked the database (using some sort of SELECT)
statement?

3. If you run weewxd from the command line, what values do you see for
rxCheckPercent?

4. If you run the command "wee_device --info", what do you get? In
particular, what does it list for "CONSOLE TYPE"?

-tk

On Sat, May 2, 2020 at 8:11 AM Hyrules  wrote:

> Hi everyone,
>
> I have a vantage pro 2 and was wondering what might be the issue of the
> following my rc_CheckPercent is always at zero. I have a point in my sql
> data when I temporarily got some value but at the moment it's zero. This is
> happening in Weewx 4.0 but was also happening in Weewx 3.9.x
> Also is it possible to get the number of wind sample ? The skin that i'm
> creating requires it and i have hard time finding any info on it in the
> documentation.
>
> Anyone has any input.
>
> 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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/db059f47-103e-406c-a342-7bddf07ec536%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/CAPq0zEAiHA%2BZT0FP_NtBBYz3g8j_jYRxxm_%3D0gTupmR3C1-PcQ%40mail.gmail.com.

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

Thanks for catching the problem with json.load(). Fixed in commit c05f76b


As you discovered, I think the api_key code is working properly.

On Sat, May 2, 2020 at 8:04 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:

> I think I figured out API key issue. It's not read if in test mode and
> hence causes error. Attached snippet
>
> On Sat, 2 May 2020, 19:40 Praveen Chandrasekaran, 
> wrote:
>
>> I didnt attached console output because i just ran wunderfixer at shell.
>> I was getting HTTP 401 error. printed api_key from within wunderfixer it
>> was "None". Then edited wunderfixer with the api key locally and that fixed
>> that issue
>>
>> On Sat, 2 May 2020 at 19:32, Tom Keffer  wrote:
>>
>>> Log? Console output?
>>>
>>> On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
>>> praveen.c...@gmail.com> wrote:
>>>
 2 issues:

 1) API key not getting passed. Hacked wunderfixer with local api key
 instead of passing
 2) After 1 I get error  that  JSON object must be str not bytes.

 On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran wrote:
>
> Hi,
>
> My wunderfixer was working till yesterday (I know for sure because I
> have used it to fill missing data often recently)
>
> After updating to v4, the wunderfixer stopped working. The API key
> looks fine but I am getting HTTP 401 FORBIDDEN ERROR.
>
> Regards,
> Praveen
>
 --
 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/e6608887-e63e-4844-955b-da4437b2f662%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/PSemiQmyCt0/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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWjPPZX-B9eZsU1VscKP9j1fMQ0d9iEOhf9UwPKMO%2B3Cg%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAB22_VgJ%3DS9i7ZABuffq%2B2f48ri%2BektbMpJQOQgWcdPg%40mail.gmail.com.

[weewx-user] rxCheckPercent always zero and number of wind samples

Hi everyone,

I have a vantage pro 2 and was wondering what might be the issue of the 
following my rc_CheckPercent is always at zero. I have a point in my sql 
data when I temporarily got some value but at the moment it's zero. This is 
happening in Weewx 4.0 but was also happening in Weewx 3.9.x
Also is it possible to get the number of wind sample ? The skin that i'm 
creating requires it and i have hard time finding any info on it in the 
documentation.

Anyone has any input.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/db059f47-103e-406c-a342-7bddf07ec536%40googlegroups.com.

Re: [weewx-user] Re: Version 4.0 is (finally) here!

On Friday, May 1, 2020 at 10:26:31 PM UTC-7, Gert Andersen wrote:
>
> E: Unable to correct problems, you have held broken packages.
>
>
>
Please google that exact message and you will find dozens of hits with 
methods for how to clean this up.  Unfortunately, that particular mesage 
can be a bit painful to clean up, and occasionally comes with some risk.

FWIW, if you are on a raspberry pi, you 'might' find it simpler to put a 
new SD card in and simply build a clean system.

is not available but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
>
> Again, if you google 'this' message you will get many hits describing what 
is going on.

 

-- 
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/3805d6ea-1f00-4a87-8df5-cd480113019c%40googlegroups.com.

Re: [weewx-user] Re: 4.x logging format

i think we all agree that syslog on macos is a lost cause.
the corollary is that pointing python logging at syslog (via 
logging.handlers.SysLogHandler) is doomed

i accept that syslog works fine on most platforms, but it is not feasible for 
macos
but there is the simple alternative for macos users of using a different 
handler:

i patched log_dict in bin/weeutil/logger.py to add a 
logging.handlers.RotatingFileHandler and it worked fine.
adding it via weewx.conf gives a type conversion error that seems simple to fix.
with the fix, i would suggest this be added to the macos installation 
instructions for user to add to weewx.conf (or make it part of the installation 
process)

details follow...

weewx.conf (yes, using that ‘root’ hack introduced to work around a ConfigObj 
limitation):

[Logging]
  [[loggers]]
[[[root]]]
  level = DEBUG
  propogate = True
  handlers = syslog, rotate
  [[handlers]]
[[[rotate]]]
  level = DEBUG
  formatter = standard
  class = logging.handlers.RotatingFileHandler
  filename = /tmp/weewx.log
  maxBytes = 1000
  backupCount = 2

gives the following error, which on the face of it would take a simple fix of 
type conversions:

Traceback (most recent call last):
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
 line 563, in configure
handler = self.configure_handler(handlers[name])
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
 line 736, in configure_handler
result = factory(**kwargs)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/handlers.py",
 line 146, in __init__
if maxBytes > 0:
TypeError: '>' not supported between instances of 'str' and ‘int’ < - - - SEE 
HERE

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "bin/weewxd", line 261, in 
main()
  File "bin/weewxd", line 136, in main
weeutil.logger.setup(options.log_label, config_dict)
  File "/opt/weewx/bin/weeutil/logger.py", line 203, in setup
logging.config.dictConfig(log_dict)
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
 line 800, in dictConfig
dictConfigClass(config).configure()
  File 
"/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/logging/config.py",
 line 571, in configure
'%r' % name) from e
ValueError: Unable to configure handler 'rotate'

the log_dict it produces before crashing seems correct:

{'version': 1, 'disable_existing_loggers': False, 'loggers': {'': {'level': 
'DEBUG', 'propagate': True, 'handlers': ['syslog'], 'propogate': 'True'}}, 
'handlers': {'syslog': {'level': 'DEBUG', 'formatter': 'standard', 'class': 
'logging.handlers.SysLogHandler', 'address': '/var/run/syslog', 'facility': 
'local1'}, 'console': {'level': 'DEBUG', 'formatter': 'verbose', 'class': 
'logging.StreamHandler', 'stream': 'ext://sys.stdout'}, 'rotate': {'level': 
'DEBUG', 'formatter': 'standard', 'class': 
'logging.handlers.RotatingFileHandler', 'filename': '/tmp/weewx.log', 
'maxBytes': '1000', 'backupCount': '2'}}, 'formatters': {'simple': 
{'format': '%(levelname)s %(message)s'}, 'standard': {'format': 
'weewx[%(process)d] %(levelname)s %(name)s: %(message)s'}, 'verbose': 
{'format': '%(asctime)s  weewx[%(process)d] %(levelname)s %(name)s: 
%(message)s', 'datefmt': '%Y-%m-%d %H:%M:%S'}}}

cheers

> On 2 May 2020, at 10:42 pm, Tom Keffer  wrote:
> 
> Logging from Python under MacOS High Sierra and later is a complete mystery. 
> I have been unable to get it to work and, it seems, neither have other 
> 
>  users 
> .
> 
> Wish I could be of more help...
> 
> -tk
> 
> On Sat, May 2, 2020 at 5:26 AM Graham Eddy  > wrote:
> i reported this incorrectly. instead of giveing me an unchanged logger 
> format, it gives me no lines at all (from the point the weewx.conf log format 
> is parsed).  even the following does the same (no logger output). commenting 
> out the “format” line reverts to lines being produced, in original format of 
> course
> 
> [Logging]
>   [[formatters]]
> [[[standard]]]
>   format = '%(message)s'

-- 
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/85C23BE1-912C-4EAA-80AC-F7E81F8EE021%40gmail.com.

[weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Gert Andersen

Hi Jaap

Did and this message:

ubuntu@Kamatera:~$ sudo pip3 install cheetah3
The directory '/home/ubuntu/.cache/pip/http' or its parent directory is not 
owned by the current user and the cache has been disabled. Please check the 
permissions and owner of that directory. If executing pip with sudo, you 
may want sudo's -H flag.
The directory '/home/ubuntu/.cache/pip' or its parent directory is not 
owned by the current user and caching wheels has been disabled. check the 
permissions and owner of that directory. If executing pip with sudo, you 
may want sudo's -H flag.
Requirement already satisfied: cheetah3 in 
/usr/local/lib/python3.6/dist-packages

Gert

On Saturday, May 2, 2020 at 9:26:56 AM UTC+2, Jaap de Munck wrote:
>
> @Gert: Try to install cheetah via pip3.
> http://www.weewx.com/docs/setup.htm
> Follow Ubuntu 16.04-17.10
> python3-cheetah is not available for Ubuntu 18.04 (the exception)
>
> //Jaap
>
> Op zaterdag 2 mei 2020 07:40:00 UTC+2 schreef Greg from Oz:
>>
>> Does /etc/apt/sources.list.d/weewx.list
>> look like this?
>> deb [arch=all] http://weewx.com/apt/ squeeze main
>>
>> That is what mine looks like.
>> I just did 
>> sudo apt update
>> then it informed me there was a new versionof weewx and then I did:
>> sudo apt dist-upgrade
>> and that was it.
>>
>> https://weather.ubeaut.work/
>>
>> On Friday, 1 May 2020 03:09:47 UTC+10, Tom Keffer wrote:
>>>
>>> After months of waiting, Version 4 has finally arrived! The major new 
>>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>>
>>> It took a long time to get the packaging right but now, thanks to 
>>> Matthew Wall, WeeWX is easier than ever to install. Be sure to read the 
>>> installation instructions for your specific operating system 
>>> . As always, a setup.py install method is 
>>> also supported.
>>>
>>> Generally, the package installers will use Python 3, if its available. 
>>> On older systems, the installers will use Python 2.
>>>
>>>
>>> CHANGE LOG
>>> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, 
>>> as well
>>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>>
>>> New facility for creating new user-defined derived types. See the Wiki 
>>> article
>>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>>
>>> WeeWX now uses the Python 'logging' facility. This means log, formats, 
>>> and other
>>> things can now be customized. Fixes issue #353.
>>>
>>> Strings appearing in the data stream no longer cause a TypeError if they 
>>> can be
>>> converted to a number.
>>>
>>> Strings can now be accumulated and extracted in the accumulators, making 
>>> it
>>> possible to include them in the database schemas.
>>>
>>> The utility wee_reports now loads services, allowing it to use 
>>> user-supplied
>>> extensions. Fixes issue #95.
>>>
>>> New default schema ("wview_extended") that offers many new types. The 
>>> old schema
>>> is still supported. Fixes issue #115.
>>>
>>> Optional, more flexible, way of specifying schemas for the daily 
>>> summaries. The
>>> old way is still supported.
>>>
>>> The install process now offers to register a user's station with 
>>> weewx.com.
>>>
>>> The package MySQL-python, which we used previously, is not always 
>>> available on
>>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>>> alternative.
>>>
>>> The default for WOW no longer throttles posting frequency (the default 
>>> used to
>>> be no more than once every 15 minutes).
>>>
>>> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>>>
>>> Unit group group_distance is now a first-class group.
>>>
>>> Added new tag $python_version.
>>>
>>> Ported to Python2-PyMySQL package on OpenSUSE.
>>>
>>> Added new aggregation types 'first' (similar to 'last'), 'diff' (the 
>>> difference
>>> between last and first value in the aggregation interval), and 'tderiv' 
>>> (the
>>> difference divided by the time difference).
>>>
>>> Created new unit group 'group_energy2', defined as watt-seconds. Useful 
>>> for high
>>> resolution energy monitors.
>>>
>>> An observation type known to the system, but not in a record, will now 
>>> return a
>>> proper ValueTuple, rather than UnknownType.
>>>
>>> Type "stormStart" was added to the unit system. Fixes issue #380.
>>>
>>> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 
>>> 'cooldeg', it
>>> measures growing degree-days. Basically, cooldeg, but with a different 
>>> base.
>>> Fixes issue #367. Thanks to user Clay Jackson for guidance!
>>>
>>> Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!
>>>
>>> Catch SSL certificate errors in uploaders. Retry after an hour. Fixes 
>>> issue
>>> #413.
>>>
>>> Wunderfixer has been ported to the new WU API. This API requires an API 
>>> key,
>>> which you can get from the WU. Put it in weewx.conf. Added option 
>>> --upload-only.
>>> Thanks to user Leon Shaner! Fixes issues #414 and #445.
>>>
>>>

[weewx-user] Re: Version 4.0 is (finally) here!

2020-05-02 Thread Gert Andersen

Hi Greg from Oz

No my file looks like this:
deb [arch=all] http://weewx.com/apt/python3 buster main

Gert

On Saturday, May 2, 2020 at 7:40:00 AM UTC+2, Greg from Oz wrote:
>
> Does /etc/apt/sources.list.d/weewx.list
> look like this?
> deb [arch=all] http://weewx.com/apt/ squeeze main
>
> That is what mine looks like.
> I just did 
> sudo apt update
> then it informed me there was a new versionof weewx and then I did:
> sudo apt dist-upgrade
> and that was it.
>
> https://weather.ubeaut.work/
>
> On Friday, 1 May 2020 03:09:47 UTC+10, Tom Keffer wrote:
>>
>> After months of waiting, Version 4 has finally arrived! The major new 
>> feature is that WeeWX will not run under either Python 2 or Python 3.
>>
>> It took a long time to get the packaging right but now, thanks to Matthew 
>> Wall, WeeWX is easier than ever to install. Be sure to read the 
>> installation instructions for your specific operating system 
>> . As always, a setup.py install method is 
>> also supported.
>>
>> Generally, the package installers will use Python 3, if its available. On 
>> older systems, the installers will use Python 2.
>>
>>
>> CHANGE LOG
>> Ported to Python 3. WeeWX should now run under Python 3.5 and greater, as 
>> well
>> as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.
>>
>> New facility for creating new user-defined derived types. See the Wiki 
>> article
>> https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types
>>
>> WeeWX now uses the Python 'logging' facility. This means log, formats, 
>> and other
>> things can now be customized. Fixes issue #353.
>>
>> Strings appearing in the data stream no longer cause a TypeError if they 
>> can be
>> converted to a number.
>>
>> Strings can now be accumulated and extracted in the accumulators, making 
>> it
>> possible to include them in the database schemas.
>>
>> The utility wee_reports now loads services, allowing it to use 
>> user-supplied
>> extensions. Fixes issue #95.
>>
>> New default schema ("wview_extended") that offers many new types. The old 
>> schema
>> is still supported. Fixes issue #115.
>>
>> Optional, more flexible, way of specifying schemas for the daily 
>> summaries. The
>> old way is still supported.
>>
>> The install process now offers to register a user's station with 
>> weewx.com.
>>
>> The package MySQL-python, which we used previously, is not always 
>> available on
>> Python 3. Ported the MySQL code to use the package mysqlclient as an
>> alternative.
>>
>> The default for WOW no longer throttles posting frequency (the default 
>> used to
>> be no more than once every 15 minutes).
>>
>> Added new aggregate types minsum, minsumtime, sum_le. PR #382.
>>
>> Unit group group_distance is now a first-class group.
>>
>> Added new tag $python_version.
>>
>> Ported to Python2-PyMySQL package on OpenSUSE.
>>
>> Added new aggregation types 'first' (similar to 'last'), 'diff' (the 
>> difference
>> between last and first value in the aggregation interval), and 'tderiv' 
>> (the
>> difference divided by the time difference).
>>
>> Created new unit group 'group_energy2', defined as watt-seconds. Useful 
>> for high
>> resolution energy monitors.
>>
>> An observation type known to the system, but not in a record, will now 
>> return a
>> proper ValueTuple, rather than UnknownType.
>>
>> Type "stormStart" was added to the unit system. Fixes issue #380.
>>
>> Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 'cooldeg', 
>> it
>> measures growing degree-days. Basically, cooldeg, but with a different 
>> base.
>> Fixes issue #367. Thanks to user Clay Jackson for guidance!
>>
>> Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!
>>
>> Catch SSL certificate errors in uploaders. Retry after an hour. Fixes 
>> issue
>> #413.
>>
>> Wunderfixer has been ported to the new WU API. This API requires an API 
>> key,
>> which you can get from the WU. Put it in weewx.conf. Added option 
>> --upload-only.
>> Thanks to user Leon Shaner! Fixes issues #414 and #445.
>>
>> Wee_import can now import Weather Display monthly log files.
>>
>> Fixed problem where sub-sections DegreeDays and Trend were located under 
>> the
>> wrong weewx.conf section. Fixes issue #432. Thanks to user mph for 
>> spotting
>> this!
>>
>> Added new parameters to the Weather Underground uploader. Fixes issue 
>> #435.
>>
>> Added new air quality types pm1_0, pm2_5, and pm10_0 to the unit system. 
>> Added
>> new unit microgram_per_meter_cubed. Added new unit group, 
>> group_concentration.
>>
>> Plist for the Mac launcher now includes a log file for stderr.
>>
>> Night-day transition in plots now uses shortest travel distance around 
>> color
>> wheel to minimize extra colors. Fixes issue #457. Thanks to user Alex 
>> Edwards!
>>
>> Fixed bug that causes plots to fail when both min and max are zero. Fixes 
>> issue
>> #463.
>>
>> Fixed problem with sqlite driver that can lead to memory growth. See PR 
>> #467.
>>

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Jever Hägen

Thanks for thinking about of doing that work.

yes, there are not very much wh23xx stations registered beside mine.
But overall they are on rank 9 ;-)
1 Vantage 537 
2 FineOffsetUSB 274 
3 AcuRite 147 
4 Interceptor 87 
5 TE923 67 
6 WMR100 40 
7 SDR 33 
8 WMR200 29 
*9* *WH23xx* *26* 
10 WS23xx 24 
11 WS28xx 24 
12 netatmo 17 
13 Ultimeter 15 
14 WeatherFlowUDP 14 
15 WMR300 14 
16 FileParse 11 
17 Simulator 11 

Am Samstag, 2. Mai 2020 16:01:39 UTC+2 schrieb Tom Keffer:
>
> The weewx usage map  shows 26 
> installations (out of 1471 registered stations), or less than 2%. That's 
> not enough usage to justify the work. Get your friends to use it!
>
> Still, I'll see what I can do...
>
> -tk
>
> On Sat, May 2, 2020 at 5:30 AM Jever Hägen  > wrote:
>
>> Hi Tom,
>>
>> yes I know, but wouldn't it be possible for you or some of the guys out 
>> there to integrate the driver into weewx v4?
>>
>> Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>>>
>>> It looks like the wh23xx driver has not been ported to Python 3 and 
>>> weewx V4 (it's not actually part of weewx).
>>>
>>> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин  wrote:
>>>
 I had the same problem today, when weewx updated to 4. The station is 
 WH2310. I made a little analyze of problem and found that import of 
 log_traceback in the ws23xx driver no more valid, because of changings in 
 weewx.
 Try to replace
 the string in the file wh23xx.py: 
 from weeutil.weeutil import timestamp_to_string, log_traceback

 to:
 from weeutil.weeutil import timestamp_to_string
 from weeutil.log log_traceback

 This is solved my problem. 
 I made pull request to the sources of this driver, hope that it will be 
 accepted.

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/7a79fd32-daf7-4965-9af4-cb5b9160d2b4%40googlegroups.com.

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

I didnt attached console output because i just ran wunderfixer at shell. I
was getting HTTP 401 error. printed api_key from within wunderfixer it was
"None". Then edited wunderfixer with the api key locally and that fixed
that issue

On Sat, 2 May 2020 at 19:32, Tom Keffer  wrote:

> Log? Console output?
>
> On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
> praveen.c...@gmail.com> wrote:
>
>> 2 issues:
>>
>> 1) API key not getting passed. Hacked wunderfixer with local api key
>> instead of passing
>> 2) After 1 I get error  that  JSON object must be str not bytes.
>>
>> On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran wrote:
>>>
>>> Hi,
>>>
>>> My wunderfixer was working till yesterday (I know for sure because I
>>> have used it to fill missing data often recently)
>>>
>>> After updating to v4, the wunderfixer stopped working. The API key looks
>>> fine but I am getting HTTP 401 FORBIDDEN ERROR.
>>>
>>> Regards,
>>> Praveen
>>>
>> --
>> 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/e6608887-e63e-4844-955b-da4437b2f662%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/PSemiQmyCt0/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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmWEOe6xLFUY0pwRCDOhFoWwx6os7RELirYq7QU9M8faJQ%40mail.gmail.com.

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

Fixed it locally at my end. api_key not getting passed is a mystery yet.

Need to decode the response to utf-8 to get it working properly. Attached
modified wunderfixer file (search for v4)

On Sat, 2 May 2020 at 19:32, Tom Keffer  wrote:

> Log? Console output?
>
> On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
> praveen.c...@gmail.com> wrote:
>
>> 2 issues:
>>
>> 1) API key not getting passed. Hacked wunderfixer with local api key
>> instead of passing
>> 2) After 1 I get error  that  JSON object must be str not bytes.
>>
>> On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran wrote:
>>>
>>> Hi,
>>>
>>> My wunderfixer was working till yesterday (I know for sure because I
>>> have used it to fill missing data often recently)
>>>
>>> After updating to v4, the wunderfixer stopped working. The API key looks
>>> fine but I am getting HTTP 401 FORBIDDEN ERROR.
>>>
>>> Regards,
>>> Praveen
>>>
>> --
>> 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/e6608887-e63e-4844-955b-da4437b2f662%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/PSemiQmyCt0/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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CA%2BW%3DTmXXNvtMt9TBZwxW7jdvqPG30MDfUJt9jTgxHnet2khtXg%40mail.gmail.com.


wunderfixer
Description: Binary data

Re: [weewx-user] Re: Wunderfixer stopped working after v4 update

Log? Console output?

On Sat, May 2, 2020 at 6:18 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:

> 2 issues:
>
> 1) API key not getting passed. Hacked wunderfixer with local api key
> instead of passing
> 2) After 1 I get error  that  JSON object must be str not bytes.
>
> On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran wrote:
>>
>> Hi,
>>
>> My wunderfixer was working till yesterday (I know for sure because I have
>> used it to fill missing data often recently)
>>
>> After updating to v4, the wunderfixer stopped working. The API key looks
>> fine but I am getting HTTP 401 FORBIDDEN ERROR.
>>
>> Regards,
>> Praveen
>>
> --
> 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/e6608887-e63e-4844-955b-da4437b2f662%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/CAPq0zEB_L-AwoN0DpQSqEjSSCn43oiuH5fZe8TPLcLBqajbQfQ%40mail.gmail.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

The weewx usage map  shows 26 installations
(out of 1471 registered stations), or less than 2%. That's not enough usage
to justify the work. Get your friends to use it!

Still, I'll see what I can do...

-tk

On Sat, May 2, 2020 at 5:30 AM Jever Hägen  wrote:

> Hi Tom,
>
> yes I know, but wouldn't it be possible for you or some of the guys out
> there to integrate the driver into weewx v4?
>
> Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>>
>> It looks like the wh23xx driver has not been ported to Python 3 and weewx
>> V4 (it's not actually part of weewx).
>>
>> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин  wrote:
>>
>>> I had the same problem today, when weewx updated to 4. The station is
>>> WH2310. I made a little analyze of problem and found that import of
>>> log_traceback in the ws23xx driver no more valid, because of changings in
>>> weewx.
>>> Try to replace
>>> the string in the file wh23xx.py:
>>> from weeutil.weeutil import timestamp_to_string, log_traceback
>>>
>>> to:
>>> from weeutil.weeutil import timestamp_to_string
>>> from weeutil.log log_traceback
>>>
>>> This is solved my problem.
>>> I made pull request to the sources of this driver, hope that it will be
>>> accepted.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%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/CAPq0zEDLge6kqMyr3Su%2B5YbzKVQwOoSPMBXbDRnqmw_Q_mJdVQ%40mail.gmail.com.

[weewx-user] Re: Weewx will only work for a week then stops

2020-05-02 Thread Luc Heijst

Hi Luc,

The error:
ValueError: accum: ScalarStats.addHiLo expected float or int, got type 
'' ('4552332')
is caused by an old version of weewx_cmon. The latest version (0.20) solves 
this, See: https://github.com/matthewwall/weewx-cmon

Also your syslog show several errors with outTemp, like:
cheetahgenerator:  Reason: Unknown daily summary type outTemp

Check your database if you have a value outTemp. 
If not, check your skin files for the use of outTemp.

Luc Heijst

On Saturday, 2 May 2020 02:33:45 UTC-3, Luc Theoret wrote:
>
> Hi,
>
> I have been trying to get weewx to record my acurite data using sdr 
> RTL_433 for about a year now.
> The system I have almost running is a raspberry pi 3 running on respbian 
> stretch. it has an external real time clock attached.
> weewx runs consistently for a week then stops. I was finally find the log 
> entry for the stop, see attached file.
> In the file is the last successful update, then the error and the exit. 
> I also included the config file.
>
>
> I have tried to reinstall on new SD card with Buster but cannot get the 
> radio to work. tried blackballing stuff blindly (not knowing what doing).
> Then I went back to this SD card. changed a couple of things and it ran. 
> But as usual after a week like clockwork it stopped.
>
> Luc
>

-- 
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/9aee7de0-73d0-4290-8c36-2b99c2cc28eb%40googlegroups.com.

[weewx-user] Re: wee_import Weather Underground HTTP Error 401: Unauthorized

2020-05-02 Thread Clint Parrish

Gary,

I think wee_import is working as it should.  I was able to get the records to 
import successfully this morning. WU must have some kind of daily restriction 
on API or access to the data somehow.  For now I am doing monthly imports as 
suggested in the guide.  I think annual imports are too much and WU ends up 
cutting me off.

For what it’s worth, wunderfixer acts the same way so this must be a WU problem.

I will investigate further and update.

Thanks,

Clint

-- 
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/5a995564-24ca-4fa5-a1d8-c556d68724d7%40googlegroups.com.

[weewx-user] Re: Wunderfixer stopped working after v4 update

2 issues:

1) API key not getting passed. Hacked wunderfixer with local api key 
instead of passing
2) After 1 I get error  that  JSON object must be str not bytes.

On Saturday, 2 May 2020 17:56:50 UTC+5:30, Praveen Chandrasekaran wrote:
>
> Hi,
>
> My wunderfixer was working till yesterday (I know for sure because I have 
> used it to fill missing data often recently)
>
> After updating to v4, the wunderfixer stopped working. The API key looks 
> fine but I am getting HTTP 401 FORBIDDEN ERROR.
>
> Regards,
> Praveen
>

-- 
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/e6608887-e63e-4844-955b-da4437b2f662%40googlegroups.com.

Re: [weewx-user] Wunderfixer stopped working after v4 update

For some reason, api_key not getting passed from conf to wunderfixer.

On Sat, 2 May 2020 at 17:56, Praveen Chandrasekaran 
wrote:

> Hi,
>
> My wunderfixer was working till yesterday (I know for sure because I have
> used it to fill missing data often recently)
>
> After updating to v4, the wunderfixer stopped working. The API key looks
> fine but I am getting HTTP 401 FORBIDDEN ERROR.
>
> Regards,
> Praveen
>
> --
> 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/PSemiQmyCt0/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/26dc7321-1e8b-454b-a11b-6c2bd9f1b9fc%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/CA%2BW%3DTmWr%3D4mzpV00qSajQNiPpCutOrnOf0Wix1XBXgoKoBR7GQ%40mail.gmail.com.

Re: [weewx-user] Re: 4.x logging format

Logging from Python under MacOS High Sierra and later is a complete
mystery. I have been unable to get it to work and, it seems, neither have
other

 users

.

Wish I could be of more help...

-tk

On Sat, May 2, 2020 at 5:26 AM Graham Eddy  wrote:

> i reported this incorrectly. instead of giveing me an unchanged logger
> format, it gives me no lines at all (from the point the weewx.conf log
> format is parsed).  even the following does the same (no logger output).
> commenting out the “format” line reverts to lines being produced, in
> original format of course
>
> [Logging]
>   [[formatters]]
> [[[standard]]]
>   format = '%(message)s'
>
>
> On 2 May 2020, at 10:02 pm, Graham Eddy  wrote:
>
> i am trying to change the weewx log format. i have added the following to
> my weewx.conf, but it has no effect. how should i do it? (weewx 4.0.0 on
> macos 10.13.6 high sierra). and can i use { style?
>
> [Logging]
>   [[formatters]]
> [[[verbose]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
> [[[standard]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
> [[[simple]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
>
>
> but it gives me the weewx default
>
> May  2 21:59:44 pebble weewx[1663] INFO __main_] : Platform
> Darwin-17.7.0-x86_64-i386-64bit
>
>
>
> --
> 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/55F10FED-0D65-4010-9D74-D61203848291%40gmail.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/CAPq0zEDxB6XB6HRk56EnZw6ONyt_r9T6SMEhCFFfxe4Kv1PD7A%40mail.gmail.com.

Re: [weewx-user] Re: weewx-wh23xx - Weewx breaks starting/running after upgrade from 3.9.2 to 4.0

2020-05-02 Thread Jever Hägen

Hi Tom,

yes I know, but wouldn't it be possible for you or some of the guys out 
there to integrate the driver into weewx v4?

Am Freitag, 1. Mai 2020 23:54:16 UTC+2 schrieb Tom Keffer:
>
> It looks like the wh23xx driver has not been ported to Python 3 and weewx 
> V4 (it's not actually part of weewx).
>
> On Fri, May 1, 2020 at 9:57 AM Богдан Пилюгин  > wrote:
>
>> I had the same problem today, when weewx updated to 4. The station is 
>> WH2310. I made a little analyze of problem and found that import of 
>> log_traceback in the ws23xx driver no more valid, because of changings in 
>> weewx.
>> Try to replace
>> the string in the file wh23xx.py: 
>> from weeutil.weeutil import timestamp_to_string, log_traceback
>>
>> to:
>> from weeutil.weeutil import timestamp_to_string
>> from weeutil.log log_traceback
>>
>> This is solved my problem. 
>> I made pull request to the sources of this driver, hope that it will be 
>> accepted.
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2e71df79-aa5c-40be-9d91-0231c192d70e%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/e19dd0d2-f97f-4a3a-a7a9-d14b020b1dab%40googlegroups.com.

Re: [weewx-user] Weewx will only work for a week then stops

Either the sdr or, more likely, cmon, is emitting a type 'long', which the
accumulators are not prepared to accept.

Which version of cmon are you using? I believe latest versions avoid this
by explicitly converting to type 'int'.

-tk

On Fri, May 1, 2020 at 10:33 PM Luc Theoret  wrote:

> Hi,
>
> I have been trying to get weewx to record my acurite data using sdr
> RTL_433 for about a year now.
> The system I have almost running is a raspberry pi 3 running on respbian
> stretch. it has an external real time clock attached.
> weewx runs consistently for a week then stops. I was finally find the log
> entry for the stop, see attached file.
> In the file is the last successful update, then the error and the exit.
> I also included the config file.
>
>
> I have tried to reinstall on new SD card with Buster but cannot get the
> radio to work. tried blackballing stuff blindly (not knowing what doing).
> Then I went back to this SD card. changed a couple of things and it ran.
> But as usual after a week like clockwork it stopped.
>
> Luc
>
> --
> 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/eae081d7-9287-4667-8f21-01836b385002%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/CAPq0zEAYjoRR5BhjTyACqja1qf9cRPcEaSt4XEK2iqKKLoOevw%40mail.gmail.com.

[weewx-user] Wunderfixer stopped working after v4 update

Hi,

My wunderfixer was working till yesterday (I know for sure because I have 
used it to fill missing data often recently)

After updating to v4, the wunderfixer stopped working. The API key looks 
fine but I am getting HTTP 401 FORBIDDEN ERROR.

Regards,
Praveen

-- 
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/26dc7321-1e8b-454b-a11b-6c2bd9f1b9fc%40googlegroups.com.

[weewx-user] Re: 4.x logging format

i reported this incorrectly. instead of giveing me an unchanged logger format, 
it gives me no lines at all (from the point the weewx.conf log format is 
parsed).  even the following does the same (no logger output). commenting out 
the “format” line reverts to lines being produced, in original format of course

[Logging]
  [[formatters]]
[[[standard]]]
  format = '%(message)s'


> On 2 May 2020, at 10:02 pm, Graham Eddy  wrote:
> 
> i am trying to change the weewx log format. i have added the following to my 
> weewx.conf, but it has no effect. how should i do it? (weewx 4.0.0 on macos 
> 10.13.6 high sierra). and can i use { style?
> 
> [Logging]
>   [[formatters]]
> [[[verbose]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
> [[[standard]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
> [[[simple]]]
>   format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
>   datefmt = %Y-%m-%d %H:%M:%S
> 
> but it gives me the weewx default
> May  2 21:59:44 pebble weewx[1663] INFO __main_] : Platform 
> Darwin-17.7.0-x86_64-i386-64bit
> 

-- 
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/55F10FED-0D65-4010-9D74-D61203848291%40gmail.com.

Re: [weewx-user] weewx 4.0 fails connecting to Vantage Vue

Thanks.

Can you give us some details about your hardware setup? From your
description that "the console has a serial to IP link" I had assumed that
your Vantage Vue had a normal WeatherLink serial logger
,
which you were accessing via some sort of serial-to-IP converter. Is that
the case?

Or, are you using the (now discontinued) Vantage WeatherlinkIP logger

?

Or, something else?

-tk

On Fri, May 1, 2020 at 9:55 PM Andre C  wrote:

> Attached the tcpdump output from the communication between weewx running
> on a raspberry PI and the vantage Vue console.
> There is communication, but no data transfer.
>
> Running telnet:
>
> Trying 192.168.178.10...
> Connected to 192.168.178.10.
> Escape character is '^]'.VER
>
> OK
> RXTEST
>
> OK
> RXCHECK
>
> OK
>
> I hope this helps.
>
> Andre
>
> Op zaterdag 2 mei 2020 00:01:05 UTC+2 schreef Tom Keffer:
>>
>> If you open up a telnet session to the Vue, can you communicate with it?
>>
>> Use the connectivity test
>> ,
>> except use telnet.
>>
>> On Fri, May 1, 2020 at 12:31 PM Andre C  wrote:
>>
>>> After upgrading weewx from 3.9.2 to 4.0, weewx no longer recognizes the
>>> Vantage Vue console.
>>>
>>> The console has a serial to IP link, so weewx communicates over Ethernet.
>>> Below the output from syslog:
>>>
>>> May  1 21:20:33 Domo systemd[1]: Starting LSB: weewx weather system...
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Initializing weewx
>>> version 4.0.0
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Using Python 3.7.3
>>> (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Platform
>>> Linux-4.19.97-v7+-armv7l-with-debian-10.3
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: Locale is 'nl_NL@euro'
>>> May  1 21:20:35 Domo weewx[420] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> May  1 21:20:35 Domo weewx[443] INFO __main__: Using configuration file
>>> /etc/weewx/weewx.conf
>>> May  1 21:20:35 Domo weewx[443] DEBUG __main__: Initializing engine
>>> May  1 21:20:35 Domo weewx[443] INFO weewx.engine: Loading station type
>>> Vantage (weewx.drivers.vantage)
>>> May  1 21:20:35 Domo weewx[332]: Starting weewx weather system: weewx.
>>> May  1 21:20:35 Domo systemd[1]: Started LSB: weewx weather system.
>>> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Driver
>>> version is 3.2.0
>>> May  1 21:20:35 Domo weewx[443] DEBUG weewx.drivers.vantage: Opened up
>>> ethernet host 192.168.178.10 on port 2. timeout=4.0, tcp_send_delay=0.5
>>> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage: Gentle wake
>>> up of console successful
>>> May  1 21:20:36 Domo weewx[443] ERROR weewx.drivers.vantage: No 
>>> received from console
>>> May  1 21:20:36 Domo weewx[443] DEBUG weewx.drivers.vantage:
>>> _determine_hardware; retry #0
>>> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
>>> received from console
>>> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
>>> _determine_hardware; retry #1
>>> May  1 21:20:37 Domo weewx[443] ERROR weewx.drivers.vantage: No 
>>> received from console
>>> May  1 21:20:37 Domo weewx[443] DEBUG weewx.drivers.vantage:
>>> _determine_hardware; retry #2
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: No 
>>> received from console
>>> May  1 21:20:38 Domo weewx[443] DEBUG weewx.drivers.vantage:
>>> _determine_hardware; retry #3
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.drivers.vantage: Unable to
>>> read hardware type; raise WeeWxIOError
>>> May  1 21:20:38 Domo weewx[443] ERROR weewx.engine: Import of driver
>>> failed: Unable to read hardware type ()
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
>>> Traceback (most recent call last):
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
>>> "/usr/share/weewx/weewx/engine.py", line 103, in setupStation
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
>>> self.console = loader_function(config_dict, self)
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
>>> "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
>>> return VantageService(engine, config_dict)
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
>>> "/usr/share/weewx/weewx/drivers/vantage.py", line 1897, in __init__
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: 
>>> Vantage.__init__(self, **config_dict[DRIVER_NAME])
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine: File
>>> "/usr/share/weewx/weewx/drivers/vantage.py", line 514, in __init__
>>> May  1 21:20:38 Domo weewx[443] CRITICAL weewx.engine:

[weewx-user] 4.x logging format

i am trying to change the weewx log format. i have added the following to my 
weewx.conf, but it has no effect. how should i do it? (weewx 4.0.0 on macos 
10.13.6 high sierra). and can i use { style?

[Logging]
  [[formatters]]
[[[verbose]]]
  format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
  datefmt = %Y-%m-%d %H:%M:%S
[[[standard]]]
  format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
  datefmt = %Y-%m-%d %H:%M:%S
[[[simple]]]
  format = '%(asctime)s %(levelname)s %(name)s|%(message)s'
  datefmt = %Y-%m-%d %H:%M:%S

but it gives me the weewx default
May  2 21:59:44 pebble weewx[1663] INFO __main_] : Platform 
Darwin-17.7.0-x86_64-i386-64bit

-- 
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/1F53A625-F718-4EFB-A250-43D8F6DB%40gmail.com.

Re: [weewx-user] Re: How to force weeex to run on python 3

Ok, Had to change in /etc/default/weewx. That did the trick.

On Sat, 2 May 2020 at 16:43, Praveen Chandrasekaran 
wrote:

> However I run it as daemon
>
> /etc/init.d/weewx. How to change the python version when pi starts up?
> Without having to setup a cron job.
>
>
>
> On Sat, 2 May 2020 at 16:16, gjr80  wrote:
>
>> Already asked and answered. Have a look at this post
>> https://groups.google.com/d/msg/weewx-user/v-WEKHOIRiI/YZl28Kj-BQAJ
>>
>> Gary
>>
>> On Saturday, 2 May 2020 20:41:40 UTC+10, Praveen Chandrasekaran  wrote:
>> > This maybe a dumb question. How to force weewx to use python 3. The
>> default python on my pi is 2.7. Python3 is python 3.5.3. In log I see weewx
>> v4 still starting on python 2.7.
>>
>> --
>> 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/2XNvSgAKUGI/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/dcc7b109-b9b0-46c2-981d-64af635d8339%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/CA%2BW%3DTmW%3DWsDyE4SBty1c83SLjDZsFP_Q-gkDQR07vT%2BgzzC8wQ%40mail.gmail.com.

Re: [weewx-user] Re: How to force weeex to run on python 3

However I run it as daemon

/etc/init.d/weewx. How to change the python version when pi starts up?
Without having to setup a cron job.



On Sat, 2 May 2020 at 16:16, gjr80  wrote:

> Already asked and answered. Have a look at this post
> https://groups.google.com/d/msg/weewx-user/v-WEKHOIRiI/YZl28Kj-BQAJ
>
> Gary
>
> On Saturday, 2 May 2020 20:41:40 UTC+10, Praveen Chandrasekaran  wrote:
> > This maybe a dumb question. How to force weewx to use python 3. The
> default python on my pi is 2.7. Python3 is python 3.5.3. In log I see weewx
> v4 still starting on python 2.7.
>
> --
> 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/2XNvSgAKUGI/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/dcc7b109-b9b0-46c2-981d-64af635d8339%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/CA%2BW%3DTmV2oe2rb6yDqjg-cmKgpkd1E1cqAhHNkp53%2BzTPRbioqA%40mail.gmail.com.

[weewx-user] Re: How to force weeex to run on python 3