Re: [weewx-user] Re: Version 4.3.0 released

[Per Edström]

How do I install the extension?

What is the difference between Python2 and Python3? Does it matter on
Raspbian 10/Buster?


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Jan 8, 2021 at 9:21 PM Tom Keffer  wrote:

> The wmr200 driver is no longer included in the regular distribution. It's
> now a separate extension .
>
> If you upgrade, there will be no wmr200 driver, so you would have to
> install the extension.
>
> Older versions have to be installed manually.
>
> -tk
>
> On Fri, Jan 8, 2021 at 11:54 AM peredst...@gmail.com <
> peredstrom@gmail.com> wrote:
>
>> Ok, so what is the difference between the unsupported WMR200-version and
>> the last supported driver? As I have three WMR200 I'm quite interested in
>> keeping it running and they are now at 4.2.0
>>
>> I guess I need to remove Weewx from the source.list so that the newest
>> version don't get installed during upgrade.
>>
>> How to install older versions? Need to to that manually?
>>
>> tisdag 5 januari 2021 kl. 00:28:30 UTC+1 skrev tke...@gmail.com:
>>
>>> This release fixes a bug in V4.2 that caused average values to be 
>>> calculated incorrectly if the archive interval changes.
>>>
>>>
>>> 4.3.0 01/04/2020
>>>
>>> Version 4.2.0 had a bug, which caused the sums in the daily summary to be
>>> incorrectly calculated. This version includes a patch to fix the problem. It
>>> runs once at startup. Fixes issue #623.
>>>
>>> The WMR200 driver is no longer supported. An unsupported version can be 
>>> found
>>> at https://github.com/weewx/weewx-wmr200. Support for LaCrosse WS23xx and
>>> Oregon WMR300 will continue.
>>>
>>> Service weewx.wxxtypes.StdDelta was inadvertently left out of the list of
>>> services to be run. Fortunately, it is not used. Yet. Added it back in.
>>>
>>> Added the "old" NWS algorithm as an option for calculating heat index.
>>>
>>> Changed how various undocumented parameters in [StdWXCalculate] are 
>>> specified.
>>> The only one people are likely to have used is 'ignore_zero_wind'. Its name 
>>> has
>>> changed to 'force_null', and it has been moved. See the Upgrading Guide.
>>>
>>> Documented the various [StdWXCalculate] options.
>>>
>>> Fixed corner case for windDir when using software record generation,
>>> ignore_zero_wind=True, and windSpeed=0 for entire record interval. Now emits
>>> last windDir value.
>>>
>>> Fixed problem when looking up stars with more than one word in their name.
>>> Fixes issue #620.
>>>
>>> Fixed problem where wind gust direction is not available when using software
>>> record generation.
>>>
>>> Added --no-prompt action to wee_import allowing wee_import to be run 
>>> unattended.
>>>
>>> Fixed problem that prevented option `observations` from being used in the
>>> simulator. Thanks to user Graham!
>>>
>>> Fixed problem where wind chill was calculated incorrectly for METRICWX
>>> databases. PR #627. Thanks to user edi-x!
>>>
>>> Allow wind vectors to be converted to unit of beaufort. Fixes issue #629.
>>>
>>> Option log_failure under [StdReport] is set to True by the upgrade process.
>>> See the Upgrading Guide.
>>>
>>> --
>> You received this message because you are 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/5a842cf3-a449-4899-bb8a-f526eecaee1en%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/7UhFHHUNmX8/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/CAPq0zECHSybxYk7uPzLBo%3D2xRUbJdN_eQgxg38k4m%2BdC1OmFig%40mail.gmail.com
> 
> .
>


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
You received this message because you are 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] WMR200-driver reports UV-sensor value as 255 when h'FF = no sensor installed

[Per Edström]

The wmr200.py should not report h'ff as a value out of range as there is no 
value from the UV-sensor as there is no sensor installed. Alternative 
report is record out of order, sensor lost or sensor not installed.

Debug and archive log info:

Sep 27 06:00:35 RPi-3Bp-Arelien weewx[16407] DEBUG weewx.drivers.wmr200:   UV 
index:255
Sep 27 06:00:36 RPi-3Bp-Arelien weewx[16407] WARNING weewx.qc: 2020-09-27 
06:00:08 CEST (1601179208) Archive value 'UV' 255 outside limits (0.0, 6.0)

Raw data from console:

Sep 27 06:00:35 RPi-3Bp-Arelien weewx[16407] DEBUG weewx.drivers.wmr200: 
Packet raw:d2 70 07 05 1b 09 14 00 00 00 00 19 00 bb 41 00 0c 01 01 07 06 
0c 0f 60 01 86 01 ff cd 43 cd 33 0a 00 e8 00 19 14 00 00 00 00 40 1d 3c 00 
00 04 e1 00 29 5a 00 00 00 00 40 30 14 80 00 00 e9 00 15 00 00 00 0f 02 5e 
56 46 80 00 08 01 55 52 5a 80 00 01 33 00 46 00 00 00 00 00 40 0f 50 80 00 
00 00 40 25 3c 00 00 07 c5 00 23 28 00 00 50 12

Information on the D2-data:
https://www.bashewa.com/wmr200-protocol.php

*D5 UV 
*
   Byte 27: (xI) Reports value of [#ff] in history [D2] records when out of 
order, not
 installed or sensor is lost.
 (x) byte(27:H) .. unknown / always [#0] .. maybe alarm or sensor 
absent?
 (I) byte(27:L) .. UVI 0-15
 ... (0-2 low / 3-5 moderate / 6-7 high / 8-10 very high / 11+ 
extremely high)

-- 
You received this message because you are 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/20860b37-a03f-4566-aacc-d2b83f3c110co%40googlegroups.com.

[weewx-user] "UV"-debug causing unrecoverable exception in wmr200.py (4.1.1)

[Per Edström]

During debug of sensors (DEBUG_.. = 1 in wmr200.py):

Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: Caught 
unrecoverable exception:
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__:   
'UV'
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__:   
Traceback (most recent call last):
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewxd", line 154, in main
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  engine.run()
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 158, in run
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  self.dispatchEvent(weewx.Event(weewx.STARTUP))
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  callback(event)
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 530, in startup
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  self._catchup(self.engine.console.genStartupRecords)
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/engine.py", line 638, in _catchup
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  for record in generator(lastgood_ts):
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/drivers/wmr200.py", line 1858, in 
genStartupRecords
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  self._process_packet_complete()
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/drivers/wmr200.py", line 1712, in 
_process_packet_complete
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  self._pkt.packet_process()
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/drivers/wmr200.py", line 672, in packet_process
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  self._record.update(decode_uvi(self,  self._pkt_data[27:28]))
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
File "/usr/share/weewx/weewx/drivers/wmr200.py", line 863, in decode_uvi
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__: 
  log.debug("  UV index:%s\n" % record['UV'])
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__:   
KeyError: 
'UV'
Sep 26 17:00:35 RPi-3Bp-Arelien weewx[3203] CRITICAL __main__:   
Exiting.


Current code:

def decode_uvi(pkt, pkt_data):
"""Decode the uvi portion of a wmr200 packet."""
try:
record = {'uv': pkt_data[0 & 0x0f]}
if DEBUG_PACKETS_UVI:
log.debug("  UV index:%s\n" % record['UV'])
return record

Suggested change:

def decode_uvi(pkt, pkt_data):
"""Decode the uvi portion of a wmr200 packet."""
try:
record = {'uv': pkt_data[0 & 0x0f]}
if DEBUG_PACKETS_UVI:
log.debug("  UV index:%s\n" % record['uv'])
return record





-- 
You received this message because you are 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/4dc338b5-9684-4cc0-8a0b-bf300c5ffbcco%40googlegroups.com.

[weewx-user] WMR200: Strange values from temp/humid-sensors (not in use)

[Per Edström]

Made a new Weewx-install (3.8.2) as the upgrade caused problems (WMR200 was 
not found on USB).

Now it seems that there are two ID 0-sensors (internal temp/humid in WMR200)

Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:0 24.1 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:0 23% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:0: 2.0 C
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:0 0.0 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:0 29% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:0: 6.0 C
:
Also, ID 0 seems to change value rapidly:

Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:0 0.0 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:0 48% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:0: -2.0 C
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:0 23.3 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:0 21% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:0: 0.0 C

Next we have ID:s not in use (as far as I know), I only use 0 to 7 here 
(and sensor 15 can't exist om WMR200 - only 0-10):

Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:15 358.6 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:15 86% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:15: -7.0 C
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Temperature 
id:8 128.1 C trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Humidity 
id:8 82% trend: Stable
Jan  4 18:31:19 RPi1B-Arelien weewx[6557]: wmr200: MainThread: D   Dew 
point id:8: -9.0 C
:

Looking through the code in driver/wmr200.py I can't see other than that 
the sensor ID is derived from the data string received from WMR200 so it 
must be faulty input to weewx - so that data must be corrupt in some way..

def decode_temp(pkt, pkt_data):
"""Decode the temperature portion of a wmr200 packet."""
try:
record = {}
# The historic data can contain data from multiple sensors. I'm not
# sure if the 0xD7 frames can do too. I've never seen a frame with
# multiple sensors. But historic data bundles data for multiple
# sensors.
# Byte 0: low nibble contains sensor ID. 0 for base station.
sensor_id = pkt_data[0] & 0x0f


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Failed: Adding new sensors to DB

[Per Edström]

Found the fault. There was a double entry in weewx.conf - line 269..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Error when adding more sensors to DB

[Per Edström]

WMR200 can have up to 10 extra sensors (in practice channel 1 is the 
outdoor sensor = extraTemp1).

Anyway, the DB does not have entries for all these sensors so I tried to 
add them by creating a new user/schema.py
but something is wrong somewhere but I can't figure out what/where from 
this..

root@RPi1B-Arelien:/home/folke/weewx# wee_database /etc/weewx/weewx.conf 
--reconfigure
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 793, in 
main()
  File "/usr/bin/wee_database", line 133, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1230, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1320, in _load
raise error
configobj.DuplicateError: Duplicate section name at line 269.
root@RPi1B-Arelien:/home/folke/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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR200-driver shutdown directly after startup

[Per Edström]

I don't seem to have that 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR200-driver shutdown directly after startup

[Per Edström]

Noone?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Negative rain-value. Need quality-control?

[Per Edström]

Ok, so UV might be different but temperature, humidity, wind, rain etc 
should be the same for all.

Those who do not want quality control can just comment it out..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR200-driver shutdown directly after startup

[Per Edström]

There seems to be a mismatch between a working system:






*root@RPi3B-Roses:/etc/weewx/skins/Standard# lsusbBus 001 Device 004: ID 
0fde:ca01 Oregon Scientific WMRS200 weather stationBus 001 Device 005: ID 
0951:1666 Kingston Technology DataTraveler G4Bus 001 Device 003: ID 
0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet 
AdapterBus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 
HubBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub*

and the one not working (where the "name" is missing on the USB):






*root@RPi1B-Arelien:~# lsusbBus 001 Device 002: ID 0424:9512 Standard 
Microsystems Corp.Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 
root hubBus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.Bus 001 
Device 004: ID 1781:0c31 Multiple Vendors Telldus TellStick DuoBus 001 
Device 005: ID 0fde:ca01*

Reboot doesn't reset the USB enough.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Easier way to change barometer => pressure ?

[Per Edström]

My WMR200 is presenting local airpressure ("pressure") on the display but 
Weewx have default setting to present sea-lever pressure ("barmometer").

I don't find sea-level-pressure useful as it differs from what the WMR200 
is showing. It is also more acurate. 

Changing this requires editing "barometer" => "pressure" in a lot of files 
and there in many places (and just replacing "barometer" with "pressure" 
will change too much e.g. pure text on web page):
- weex.conf
- skin.conf
- index.html.tmpl
- week.html.tmpl
- month.html.tmpl
- year.html.tmpl
- smartphone/index.html.tmpl
- smartphone/barometer.html.tmpl

Can this be done in one place instead? Like changing just in weewx.conf

*airpressure = barometer/pressure*


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] What happens on upgrade when choosing to keep old files?

[Per Edström]

I have been using Weewx since version, well.. probably 2.someting.

On every upgrade I have selected to keep weewx.conf etc as there are 
changes in them that I don't want to loose but now many versions later I 
note that the weewx.conf on a brand new installation is quite different 
from my old ones.

Are they still compatible?

Is there a need to "clean up" old files and migrate own changes to the new 
version?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WMR200-driver shutdown directly after startup

[Per Edström]

Suddenly yesterday my WMR200 stopped talking to Weewx.

It happened after multiple parsing errors when generating HTML-pages (yes - 
my bad). I don't know if the engine gave up due to this or if the engine 
shutdown is related to the WMR200-driver quitting..




































*Nov 10 22:20:38 RPi1B-Arelien weewx[5304]:   ParseError:Nov 10 
22:20:38 RPi1B-Arelien weewx[5304]: Nov 10 22:20:38 RPi1B-Arelien 
weewx[5304]:   #end found, but nothing to endNov 10 22:20:38 
RPi1B-Arelien weewx[5304]:   Line 519, column 1 in file 
/etc/weewx/skins/Standard/week.html.tmplNov 10 22:20:38 RPi1B-Arelien 
weewx[5304]: Nov 10 22:20:38 RPi1B-Arelien weewx[5304]:   
Line|Cheetah CodeNov 10 22:20:38 RPi1B-Arelien weewx[5304]:   
|-Nov 10 
22:20:38 RPi1B-Arelien weewx[5304]:   516 |  Nov 10 
22:20:38 RPi1B-Arelien weewx[5304]:   517 |Nov 10 22:20:38 
RPi1B-Arelien weewx[5304]:   518 |  #end ifNov 10 22:20:38 
RPi1B-Arelien weewx[5304]:   519 |  Nov 10 22:20:38 
RPi1B-Arelien weewx[5304]:    ^Nov 10 22:20:38 RPi1B-Arelien 
weewx[5304]:   520 |  #if $month.UV.has_dataNov 10 22:20:38 
RPi1B-Arelien weewx[5304]:   521 |  Nov 10 22:20:38 
RPi1B-Arelien weewx[5304]:   522 |Nov 10 22:20:38 RPi1B-Arelien weewx[5304]: Nov 10 
22:20:44 RPi1B-Arelien weewx[5304]: cheetahgenerator: Generated 13 files 
for report StandardReport in 21.06 secondsNov 10 22:21:01 RPi1B-Arelien 
weewx[5304]: imagegenerator: Generated 21 images for StandardReport in 
17.31 secondsNov 10 22:21:01 RPi1B-Arelien weewx[5304]: copygenerator: 
copied 0 files to /var/www/weewxNov 10 22:21:04 RPi1B-Arelien weewx[5304]: 
wmr200: MainThread: W Clock time unsynchronizedNov 10 22:21:20 
RPi1B-Arelien weewx[5304]: ftpgenerator: ftp'd 34 files in 19.26 secondsNov 
10 22:21:29 RPi1B-Arelien weewx[5304]: engine: Shutting down StdReport 
threadNov 10 22:21:29 RPi1B-Arelien weewx[5304]: wmr200: Thread-2: I USB 
polling device thread exitingNov 10 22:21:29 RPi1B-Arelien weewx[5304]: 
wmr200: MainThread: I USB polling thread expiredNov 10 22:21:29 
RPi1B-Arelien weewx[5304]: wmr200: Thread-1: I Watchdog received 
shutdownNov 10 22:21:29 RPi1B-Arelien weewx[5304]: wmr200: Thread-1: I 
Watchdog thread exitingNov 10 22:21:29 RPi1B-Arelien weewx[5304]: wmr200: 
MainThread: I Watchdog thread expiredNov 10 22:21:29 RPi1B-Arelien 
weewx[5304]: wmr200: MainThread: I Received packet count live:9408 
archive:7 control:487Nov 10 22:21:29 RPi1B-Arelien weewx[5304]: wmr200: 
MainThread: I Received bytes:1163488 sent bytes:11432Nov 10 22:21:29 
RPi1B-Arelien weewx[5304]: wmr200: MainThread: I Packet archive queue len:7 
live queue len:0Nov 10 22:21:29 RPi1B-Arelien weewx[5304]: wmr200: 
MainThread: W Exiting with packets still in archive queue cnt:7Nov 10 
22:21:29 RPi1B-Arelien weewx[5304]: wmr200: MainThread: I Driver gracefully 
exitingNov 10 22:21:36 RPi1B-Arelien weewx[18912]: engine: Initializing 
weewx version 3.8.2Nov 10 22:21:36 RPi1B-Arelien weewx[18912]: engine: 
Using Python 2.7.3 (default, Nov 24 2017, 21:13:24) #012[GCC 4.6.3]Nov 10 
22:21:36 RPi1B-Arelien weewx[18912]: engine: Platform 
Linux-4.1.19+-armv6l-with-debian-7.11*
Now the driver quits directly efter startup, everything within 2 seconds. 
Did the driver really try to pull the WMR200?

























*Nov 11 09:37:47 RPi1B-Arelien weewx[21588]: engine: Initializing weewx 
version 3.8.2Nov 11 09:37:47 RPi1B-Arelien weewx[21588]: engine: Using 
Python 2.7.3 (default, Nov 24 2017, 21:13:24) #012[GCC 4.6.3]Nov 11 
09:37:47 RPi1B-Arelien weewx[21588]: engine: Platform 
Linux-4.1.19+-armv6l-with-debian-7.11Nov 11 09:37:47 RPi1B-Arelien 
weewx[21588]: engine: Locale is 'C'Nov 11 09:37:47 RPi1B-Arelien 
weewx[21588]: engine: pid file is /var/run/weewx.pidNov 11 09:37:47 
RPi1B-Arelien weewx[21592]: engine: Using configuration file 
/etc/weewx/weewx.confNov 11 09:37:47 RPi1B-Arelien weewx[21592]: engine: 
Loading station type WMR200 (weewx.drivers.wmr200)Nov 11 09:37:47 
RPi1B-Arelien weewx[21592]: wmr200: MainThread: I driver version is 
3.3.5Nov 11 09:37:47 RPi1B-Arelien weewx[21592]: wmr200: MainThread: I 
sensor map is {'outTempBatteryStatus': 'battery_status_out', 'extraTemp10': 
'temperature_10', 'outHumidity': 'humidity_1', 'rainRate': 'rain_rate', 
'extraHumid8': 'humidity_8', 'heatindex4': 'heatindex_4', 'rainTotal': 
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6': 
'heatindex_6', 'extraTemp5': 'temperature_5', 'uvFault': 'uv_fault', 
'extraTemp2': 'temperature_2', 'heatindex': 'heatindex_1', 'rain24': 
'rain_24', 'inHeatindex': 'heatindex_0', 'inTemp': 'temperature_0', 
'extraHumid9': 'humidity_9', 'hourRain': 'rain_hour', 'windFault': 
'wind_fault', 'extraHumid10': 'humidity_10', 'windchill': 'windchill', 
'clockUnsynchronized': 'clock_unsynchronized', 

[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached

[Per Edström]

Ok..

So it seems like this part resets the settings made at the top of the 
wmr200.py file. If DEBUG is needed then one needs to set "1" here too..





































*# Restart counter when driver crashes and is restarted by 
the# weewx engine.global STAT_RESTARTSTAT_RESTART 
+= 1if STAT_RESTART > 1:logwar(('Restart count: %d') % 
STAT_RESTART)# Reset any other state during startup or after a 
crash.PacketArchiveData.rain_total_last = None# Debugging 
flagsglobal DEBUG_WRITESDEBUG_WRITES = 
int(stn_dict.get('debug_writes', 0))global DEBUG_COMM
DEBUG_COMM = int(stn_dict.get('debug_comm', 0))global 
DEBUG_CONFIG_DATADEBUG_CONFIG_DATA = 
int(stn_dict.get('debug_config_data', 1))global 
DEBUG_PACKETS_RAWDEBUG_PACKETS_RAW = 
int(stn_dict.get('debug_packets_raw', 1))global 
DEBUG_PACKETS_COOKEDDEBUG_PACKETS_COOKED = 
int(stn_dict.get('debug_packets_cooked', 0))global 
DEBUG_PACKETS_ARCHIVEDEBUG_PACKETS_ARCHIVE = 
int(stn_dict.get('debug_packets_archive', 0))global 
DEBUG_PACKETS_TEMPDEBUG_PACKETS_TEMP = 
int(stn_dict.get('debug_packets_temp', 0))global 
DEBUG_PACKETS_RAINDEBUG_PACKETS_RAIN = 
int(stn_dict.get('debug_packets_rain', 0))global 
DEBUG_PACKETS_WINDDEBUG_PACKETS_WIND = 
int(stn_dict.get('debug_packets_wind', 0))global 
DEBUG_PACKETS_STATUSDEBUG_PACKETS_STATUS = 
int(stn_dict.get('debug_packets_status', 0))global 
DEBUG_PACKETS_PRESSUREDEBUG_PACKETS_PRESSURE = 
int(stn_dict.get('debug_packets_pressure', 0))global 
DEBUG_CHECKSUMDEBUG_CHECKSUM = int(stn_dict.get('debug_checksum', 
0))global DEBUG_MAPPINGDEBUG_MAPPING = 
int(stn_dict.get('debug_mapping', 0))*

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows

[Per Edström]

So this is no longer a suggestion about new function, it is a fault report 
about functions not working as it should..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached

[Per Edström]

I change in the wmr200.py file but it doesn't have any effect on the 
if-statements e.g.







*# weewx configurable flags for enabling/disabling debug verbosity.# Prints 
processed packets with context from console.DEBUG_PACKETS_COOKED = 0# 
Prints raw pre-processed packets from console.DEBUG_PACKETS_RAW = 1# Prints 
respective packets individually.*
*:*








*def _process_packet_complete(self):"""Process a completed 
packet from the wmr200 console."""#PEED#if 
DEBUG_PACKETS_RAW:logdbg(self._pkt.to_string_raw('Packet 
raw:'))# This will raise exception if checksum fails.
self._pkt.verify_checksum()*

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows

[Per Edström]

Oh I have been playing around with the file now..

Apparently the DEBUG-settings in wmr200.py doesn't work. The "if DEBUG_xxx: 
" don't work but the DEBUG_PACKETS_RAW is what I have been looking for. I 
had to # the if-statement in order to make it work..

*wmr200: MainThread: D Packet raw:d7 10 24 15 0a 0b 12 40 fe 00 27 6e 00 00 
1a 03*

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] driver/wmr200.py - DEBUG_PACKETS_TEMP is never reached

[Per Edström]

If I set:

*DEBUG_PACKETS_TEMP = 1*

weewx will still never enter this part of the code:











*if DEBUG_PACKETS_TEMP:logdbg('peed')
logdbg('  Temperature id:%d %.1f C trend: %s'   % 
(sensor_id, temp, TRENDS[temp_trend]))logdbg('  Humidity id:%d 
%d%% trend: %s'   % (sensor_id, humidity, 
TRENDS[hum_trend]))logdbg(('  Dew point id:%d: %.1f C' % 
(sensor_id, dew_point)))if heat_index is not 
None:logdbg('  Heat id:%d index:%d' % (sensor_id, 
heat_index))return record*

But if I remove the DEBUG-condition then the code is executed:












*#PEED#if DEBUG_PACKETS_TEMP:logdbg('peed')
logdbg('  Temperature id:%d %.1f C trend: %s' % (sensor_id, temp, 
TRENDS[temp_trend]))#   % (sensor_id, temp, 
TRENDS[temp_trend]))logdbg('  Humidity id:%d %d%% trend: %s' % 
(sensor_id, humidity, TRENDS[hum_trend]))#   % (sensor_id, 
humidity, TRENDS[hum_trend]))logdbg(('  Dew point id:%d: %.1f C' % 
(sensor_id, dew_point)))if heat_index is not None:
logdbg('  Heat id:%d index:%d' % (sensor_id, heat_index))return 
record*

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Suggestion: Debug-format - sensor packet on one row instead of multiple rows

[Per Edström]

I'm not that skilled in Python but I guess the code to adjust might be this:
(wmr200.py)

 



*   if DEBUG_READS:buf = ''for byte 
in report[1:report[0] + 1]:buf += '%02x ' % 
bytelogdbg('read_device(): %s' % buf)*

Maybe it doesn't loop properly before writing to syslog?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Suggestion: Debug-format - sensor packet on one row instead of multiple rows

[Per Edström]

I'm trying to find the battery status from the extra sensors on WMR200 and 
maybe there already a way to do this as described below..

When using the debug settings the data is written in a not too userfriendly 
format. One data packet is written not only over multiple rows but also 
with varying number of bytes per row.
Like this (D7-packet from WMR200):

*> Time/Date> TEMP/HUM/DEW---> CHSUM**00 01 02 03 04 05 06 07 08 09 
10 11 12 13 14 15* ...byte nr*ID LL mm-hh dd-mm-yy tS TT-sT HU DD-sD HI cL-cH* 
...notation*- -- -- - -- - -- -**d7 10 2f 0d 06 0c 
0a 91 22 01 1b 14 80 52 8a 02* ...data

*---*









*Nov 10 16:17:13 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:21 live_queue_len:21Nov 10 16:17:15 RPi3B-Roses weewx[2547]: 
wmr200: Thread-2: D read_device(): d7Nov 10 16:17:15 RPi3B-Roses 
weewx[2547]: wmr200: Thread-2: D read_device(): 10Nov 10 16:17:15 
RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 11 10Nov 10 
16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 0a 0b 
12Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D 
read_device(): 52 af 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: 
Thread-2: D read_device(): 47 82 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: 
wmr200: Thread-2: D read_device(): 00 f9 02*















*Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:22 live_queue_len:22Nov 10 16:17:15 RPi3B-Roses weewx[2547]: 
wmr200: Thread-2: D read_device(): d7Nov 10 16:17:15 RPi3B-Roses 
weewx[2547]: wmr200: Thread-2: D read_device(): 10Nov 10 16:17:15 
RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 11 10Nov 10 
16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 0aNov 
10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 
0bNov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D 
read_device(): 12 00Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: 
Thread-2: D read_device(): fcNov 10 16:17:15 RPi3B-Roses weewx[2547]: 
wmr200: Thread-2: D read_device(): 00Nov 10 16:17:15 RPi3B-Roses 
weewx[2547]: wmr200: Thread-2: D read_device(): 25Nov 10 16:17:15 
RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 64Nov 10 
16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00Nov 
10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D read_device(): 00 
b4Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: Thread-2: D 
read_device(): 02*

*Nov 10 16:17:16 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:23 live_queue_len:23*


I would find it more readable and searchable if the packets above was 
written in one line like this:


*Nov 10 16:17:13 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:21 live_queue_len:21*

*wmr200: Thread-2: D read_device():d7 10 11 10 0a 0b 12 52 af 00 47 82 00 
00 f9 02 (B7:L = 2 => extraTemp2 + extraHumid2)*

*Nov 10 16:17:15 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:22 live_queue_len:22*

*wmr200: Thread-2: D read_device():d7 10 11 10 0a 0b 12 00 fc 00 25 64 00 
00 b4 02 (B7:L = 0 => inTemp + inHumidity)*
*Nov 10 16:17:16 RPi3B-Roses weewx[2547]: wmr200: MainThread: D   Queuing 
live packet rx:23 live_queue_len:23*

It is then easy to grep on the log (for ":d7 10" and directly compare the 
content.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Negative rain-value. Need quality-control?

[Per Edström]

I would also suggest that all extra sensors are pre-added in the quality 
control. If they are not used by the weather station or the user then I 
guess that there is no harm done anyway. 

Oregon WMR200 can have a total of 10 sensors (where channel = 1 is the 
outdoor sensor but it can be replaced with e.g. THGR-810 set on channel 1). 
As we don't know where the user might place the extra sensors we might have 
to extend the quality range to outdoor usage:

[[MinMax]]
barometer = 26, 32.5, inHg
outTemp = -40, 120, degree_F
inTemp = 10, 120, degree_F
extraTemp2 = -40, 120, degree_F
extraTemp3 = -40, 120, degree_F
extraTemp4 = -40, 120, degree_F
extraTemp5 = -40, 120, degree_F
extraTemp6 = -40, 120, degree_F
extraTemp7 = -40, 120, degree_F
extraTemp8 = -40, 120, degree_F
extraTemp9 = -40, 120, degree_F
extraTemp10 = -40, 120, degree_F
outHumidity = 0, 100
inHumidity = 0, 100
extraHumid2 = 0, 100
extraHumid3 = 0, 100
extraHumid4 = 0, 100
extraHumid5 = 0, 100
extraHumid6 = 0, 100
extraHumid7 = 0, 100
extraHumid8 = 0, 100
extraHumid9 = 0, 100
extraHumid10 = 0, 100
windSpeed = 0, 120, mile_per_hour
UV = 0, 6
rain = 0, 6, inch
pressure = 24, 34.5, inHg

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Negative rain-value. Need quality-control?

[Per Edström]

Also, there is not quality control för the UV-sensor (Oregon UV ranges 
0-4). I seem to have that entry in some older weewx.conf. Not sure if I 
added it myself..

I suggest that 

UV = 0, 6

is added too..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

[Per Edström]

I loaded the suggested engine.py and now there is only a record saved every 
5 minutes:

Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Loading service 
weewx.engine.StdArchive
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Archive will use data 
binding wx_binding
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Record generation will be 
attempted in 'software'
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using archive interval of 
300 seconds (software record generation)
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Use LOOP data in hi/low 
calculations: 1
Nov  5 22:34:21 RPi3_L5E weewx[25497]: manager: Daily summary version is 1.0
Nov  5 22:34:21 RPi3_L5E weewx[25497]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb'

But stille the WMR200 is providing sensor values every minute. Which value 
is used for the 5-minute-storage? An average or the latest? Or is the 
WMR200 pulled once every 5 minutes?
There is still quite a busy log here:

Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:53 live_queue_len:1
Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:56
Nov  5 22:37:14 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:54 live_queue_len:1
Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:57
Nov  5 22:37:15 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:55 live_queue_len:1
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D genLoop() 
Yielding live queued packet id:58
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   adjust_rain 
rain_total:31.90 Rain.rain_total_last:31.90 rain_interval:0.00
Nov  5 22:37:16 RPi3_L5E weewx[25497]: wmr200: MainThread: D   Queuing live 
packet rx:56 live_queue_len:1

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

[Per Edström]

Sorry about that - here it is..

It seems like the config-value (300) is overridden by the WMR200-value (60).


Nov  4 20:49:26 RPi-3B_Skalet systemd[1]: Starting LSB: weewx weather 
system...
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Initializing weewx 
version 3.8.2
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Platform 
Linux-4.14.70-v7+-armv7l-with-debian-9.4
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: Locale is 'en_GB.UTF-8'
Nov  4 20:49:26 RPi-3B_Skalet weewx[17619]: engine: pid file is 
/var/run/weewx.pid
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Using configuration 
file /etc/weewx/weewx.conf
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Debug is 1
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Initializing engine
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: engine: Loading station type 
WMR200 (weewx.drivers.wmr200)
Nov  4 20:49:26 RPi-3B_Skalet weewx[17608]: Starting weewx weather system: 
weewx.
Nov  4 20:49:26 RPi-3B_Skalet systemd[1]: Started LSB: weewx weather system.
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I driver 
version is 3.3.5
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I sensor 
map is {'outTempBatteryStatus': 'battery_status_out', 'extraTemp10': 
'temperature_10', 'outHumidity': 'humidity_1', 'rainRate': 'rain_rate', 
'extraHumid8': 'humidity_8', 'heatindex4': 'heatindex_4', 'rainTotal': 
'rain_total', 'rainBatteryStatus': 'battery_status_rain', 'heatindex6': 
'heatindex_6', 'extraTemp5': 'temperature_5', 'uvFault': 'uv_fault', 
'extraTemp2': 'temperature_2', 'heatindex': 'heatindex_1', 'rain24': 
'rain_24', 'inHeatindex': 'heatindex_0', 'inTemp': 'temperature_0', 
'extraHumid9': 'humidity_9', 'hourRain': 'rain_hour', 'windFault': 
'wind_fault', 'extraHumid10': 'humidity_10', 'windchill': 'windchill', 
'clockUnsynchronized': 'clock_unsynchronized', 'extraTemp7': 
'temperature_7', 'rain': 'rain', 'forecastIcon': 'forecast_icon', 
'pressure': 'pressure', 'extraHumid4': 'humidity_4', 'extraHumid5': 
'humidity_5', 'extraHumid2': 'humidity_2', 'extraHumid3': 'humidity_3', 
'extraTemp8': 'temperature_8', 'extraTemp9': 'temperature_9', 'extraTemp6': 
'temperature_6', 'heatindex5': 'heatindex_5', 'extraTemp4': 
'temperature_4', 'heatindex7': 'heatindex_7', 'altimeter': 'altimeter', 
'extraTemp3': 'temperature_3', 'heatindex2': 'heatindex_2', 'heatindex3': 
'heatindex_3', 'extraHumid6': 'humidity_6', 'extraHumid7': 'humidity_7', 
'windBatteryStatus': 'battery_status_wind', 'UV': 'uv', 'rainFault': 
'rain_fault', 'windDir': 'wind_dir', 'outTemp': 'temperature_1', 
'windSpeed': 'wind_speed', 'inHumidity': 'humidity_0', 'outTempFault': 
'out_fault', 'windGust': 'wind_gust', 'uvBatteryStatus': 
'battery_status_uv', 'heatindex8': 'heatindex_8', 'heatindex10': 
'heatindex_10', 'heatindex9': 'heatindex_9'}
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created 
watchdog thread to poke for live data every 30 seconds
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Created 
USB polling thread to read block on device
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB polling 
device thread for live data launched
Nov  4 20:49:26 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: I Reset 
console device
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-2: I USB polling 
device thread signaled to start
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D 
Configuration setup
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: Thread-1: I Started 
watchdog thread live data
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Log 
sensor faults: True
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Using 
PC Time: True
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Erase 
archive data: False
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Archive 
interval: 60
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: wmr200: MainThread: D   Archive 
threshold: 604800
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdTimeSynch
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdTimeSynch
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdConvert
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: StdConvert target unit 
is 0x1
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdConvert
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdCalibrate
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Finished loading 
service weewx.engine.StdCalibrate
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: engine: Loading service 
weewx.engine.StdQC
Nov  4 20:49:27 RPi-3B_Skalet weewx[17623]: 

Re: [weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

[Per Edström]

>
> DEBUG = 1 does not give that much new information..


Nov  4 09:34:07 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:415
Nov  4 09:34:07 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D   Queuing
live packet rx:393 live_queue_len:1
Nov  4 09:34:08 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:416
Nov  4 09:34:16 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D   Queuing
live packet rx:394 live_queue_len:1
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:417
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record
2018-11-04 09:34:00 CET (1541320440) to database 'weewx.sdb'
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: manager: Added record
2018-11-04 09:34:00 CET (1541320440) to daily summary in 'weewx.sdb'
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running reports
for latest time in the database.
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
phase getting live packets
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report
StandardReport
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Standard/skin.conf for report
StandardReport
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report
StandardReport skipped due to report_timing setting
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report FTP
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report FTP
skipped due to report_timing setting
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Running report
RSYNC
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Found
configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Nov  4 09:34:17 RPi-3B_Skalet weewx[15362]: reportengine: Report RSYNC
skipped due to report_timing setting
Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: W Skipped
bytes before resync:1
Nov  4 09:34:21 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D   Queuing
live packet rx:396 live_queue_len:1
Nov  4 09:34:22 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D genLoop()
Yielding live queued packet id:419
Nov  4 09:34:24 RPi-3B_Skalet weewx[15362]: wmr200: MainThread: D
 Acknowledged control packet rx:24


Actually, I have noted that in order to get really useful debug information
one needs to set various DEBUG_ parameters = 1 in drivers/wmr200.py

But maybe that is how it should work? the DEBUG in weewx.conf is maybe only
for the engines and not "everything"?


Virus-free.
www.avg.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Suggestion: Re-fill DB if sensor data is missing

[Per Edström]

No, I have 300 seconds = 5 minutes as archive interval but the WMR200 
overrides it.

I tried software generation but Weewx still stores every minute (I guess 
the HW-interval can not be overridden in weewx.conf):

Nov  3 10:20:36 RPi-3B_Skalet weewx[9980]: ftpgenerator: ftp'd 33 files in 
13.16 seconds
Nov  3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:21:00 CET (1541236860) to database 'weewx.sdb'
Nov  3 10:21:16 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:21:00 CET (1541236860) to daily summary in 'weewx.sdb'
Nov  3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:22:00 CET (1541236920) to database 'weewx.sdb'
Nov  3 10:22:16 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:22:00 CET (1541236920) to daily summary in 'weewx.sdb'
Nov  3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:23:00 CET (1541236980) to database 'weewx.sdb'
Nov  3 10:23:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:23:00 CET (1541236980) to daily summary in 'weewx.sdb'
Nov  3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:24:00 CET (1541237040) to database 'weewx.sdb'
Nov  3 10:24:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:24:00 CET (1541237040) to daily summary in 'weewx.sdb'
Nov  3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:25:00 CET (1541237100) to database 'weewx.sdb'
Nov  3 10:25:17 RPi-3B_Skalet weewx[9980]: manager: Added record 2018-11-03 
10:25:00 CET (1541237100) to daily summary in 'weewx.sdb'
Nov  3 10:25:18 RPi-3B_Skalet weewx[9980]: cheetahgenerator: Generated 15 
files for report StandardReport in 1.18 seconds

I would prefer that the DB-writing was made more seldom i.e. at the archive 
interval. Weewx could keep these 1-minute-values in memory until DB is to 
be written.

Also, as this thread was started as, I would prefer Weewx to take the last 
received sensor value if there is one expected but missing i.e. the WMR200 
is not presenting it in the 1-minute-pull..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Suggestion: Re-fill DB if sensor data is missing

[Per Edström]

Sensor data is quite often missing from my WMR200-stations. Data is pulled 
every minute (hardware control) but from time to time some data is missing. 

This causes the webpage to present "N/A" and dropouts in diagrams. Somewhat 
annouying and not really neccesary.

Not that many sensor values are changed rapidly and I'd rather have an old 
value than none at all.

So, it is possible to have a setting in e.g. weewx.conf

[db_refill]
   missing = 10

So that up to 10 missing sensor values can be replaced by the last value 
received. In my case that would be 10 minutes. 10 missing sensor data in a 
row is not that common..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Oregon Scientific WMR300 issues reading outside temperature and humidity into weewx

[Per Edström]

Do a restart at midnight via Cronjob. Something like..

00 00 * * * "service weewx restart"



Den torsdag 4 oktober 2018 kl. 16:49:01 UTC+2 skrev Cameron D:
>
>  
> Markus,
> check this post 
> for 
> a driver with extra debugging that might help understanding this problem.
>
> Cameron.
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Negative rain-value. Need quality-control?

[Per Edström]

New installation 3.8.2.
RPi 3B+
WMR200

I have never seen negative value, and that big numbers, on rain-meter.
Any idea how this could have happened?

Now I added in weewx.conf

[StdQC]
[[MinMax]]
:
rain = 0, 100

[image: dayrain.png]

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: WMR200-reception can not be improved - What station should I replace it with?

[Per Edström]

Google can translate web pages.

How much better reception did you get?

Does the WMR200 provide +3VDC to the receiver? Or 5VDC?

It is odd that the WMR200 can't run on the USB-power alone..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: After migrating to a Raspberry Pi - cheetahgenerator: Generate failed with exception ''

[Per Edström]

I suspect it is the degree-sign in e.g.

Today's min: $day.outTemp.min at $day.outTemp.mintime

Today's min: 22.4°C at 17:58

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] After migrating to a Raspberry Pi - cheetahgenerator: Generate failed with exception ''

[Per Edström]

Not really sure why it complains..

Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator: Generate failed 
with exception ''
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Standard/week.html.tmpl
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator:  Reason: 
'utf8' codec can't decode byte 0xe4 in position 507: invalid continuation 
byte
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   Traceback (most recent call 
last):
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 328, in generate
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   
filtersLib=weewx.cheetahgenerator)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1259, in 
__init__
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   self._compile(source, 
file, compilerSettings=compilerSettings)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1553, in 
_compile
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   
keepRefToGeneratedCode=True)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 740, in compile
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   
settings=(compilerSettings or {}))
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Compiler.py", line 1577, in 
__init__
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   source = 
source.decode(encoding)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/encodings/utf_8.py", line 16, in decode
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   return 
codecs.utf_8_decode(input, errors, True)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   UnicodeDecodeError: 'utf8' 
codec can't decode byte 0xe4 in position 507: invalid continuation byte
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator: Generate failed 
with exception ''
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Standard/smartphone/temp_outside.html.tmpl
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: cheetahgenerator:  Reason: 
'ascii' codec can't encode character u'\xb0' in position 3: ordinal not in 
range(128)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   Traceback (most recent call 
last):
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   print >> _file, 
compiled_template
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   rc = getattr(self, 
mainMethName)()
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"_etc_weewx_skins_Standard_smartphone_temp_outside_html_tmpl.py", line 108, 
in respond
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 621, in filter
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   filtered = str(val)
Sep 11 23:21:22 RPi-3B_L5E weewx[8516]:   UnicodeEncodeError: 'ascii' 
codec can't encode character u'\xb0' in position 3: ordinal not in 
range(128)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: I cant ftpupload FTPS

[Per Edström]

How is FTPS setup in weewx.conf?


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WMR200 range improvement - rebuild inside..

[Per Edström]

I found this description on how to change the radiomodule in the WMR200. It 
should improve reception from the sensors.
Now, the manual says that a 3.3V-module should be used. It this correct? 
Should it not be 5V?

https://rothlive.de/de/content/oregon-scientific-wmr-200-empfang-verbessern-erh%C3%B6hen

Further more, it is possible to convert the WMR200 to use power from the 
USB-cable instead of the external power source? It seems as poor design not 
to use USB if available..

If I change the receiver, would it not be a good idea to mount a 
SMA-connector for an external antenna? The built-in one is not optimal..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] WMR200-reception can not be improved - What station should I replace it with?

[Per Edström]

If you get some really small ferrie core blocks then these might reduce 
interference over USB-cable. Not much space to fit them though.

Also, if possible, clock-down the RPi CPU. It might help (unless it is the 
USB-circuit that causes it)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] WMR200-reception can not be improved - What station should I replace it with?

[Per Edström]

I also added this "mechanical" antenna amplifier:

http://www.the-lighthouse.se/eng/teknik/antenn-amp/antenn-amp.html

It is in swedish but just take some solid copper wire and remove the 
isolation. It improved my reception a bit more but looks ugly. Now, my 
motto is "Form follows function" so it is Ok..

As my "PC" (Ebox 3350) is sending interference (at least that is what I 
suspect) through the USB-wire, I added a 10m USB repeater. It also improved 
reception somewhat.
(My theory is that the PC-CPU is running at 933MHz so there might be an 
"undertone" of around 433MHz propagating down the USB-line into WMR200 thus 
blocking out the 433MHz-signal from the sensors. When using RPi I have a 
lot less issues with reception but maybe newer RPi will cause interference?)

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR88 (WMR100): Get notification in syslog of low.batt from temp.sensors

[Per Edström]

Well, I guess there is no contradiction in saving to DB and writing to 
syslog. I don't know why I commented the DB-line..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WMR88 (WMR100): Get notification in syslog of low.batt from temp.sensors

[Per Edström]

1. Go to: /usr/share/weewx/weewx/drivers

2. Edit wmr100.py

3. Find section and insert (bold text):

elif channel >= 2:
# If additional temperature sensors exist (channel>=2), then
# use observation types 'extraTemp1', 'extraTemp2', etc.
_record['extraTemp%d'  % (channel-1)] = T
_record['extraHumid%d' % (channel-1)] = R




*#PEED   #_record['extraBatteryStatus%d' % (channel)] = (packet[0] 
& 0x40) >> 6B = (packet[0] & 0x40) >> 6if B == 
1:syslog.syslog(syslog.LOG_DEBUG, "extraBatteryStatus%d:  
Low battery" % channel)*

return _record

4. Restart 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: WMR200: Help me to find "low batt."-bits in the d9-packet

[Per Edström]

Well, this is a running system and some sensors are placed in 
hard-to-get-places so I don't want to mess with them right now.
Maybe if I change my WMR928 for a new WMR200..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Selection of USB/RS232 device to RPI. To control WMR 928

[Per Edström]

Well, I don't have RPi3 but an eBox 3350 but I don't see why it shouldn't 
work on RPi3..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Selection of USB/RS232 device to RPI. To control WMR 928

[Per Edström]

I have WMR928 with a RS232-to-USB and it works fine. Have been running for 
many years.
I run Ubuntu 10.04.
Sometimes the /dev/ttyUSB0 changes to /dev/ttyUSB1 so Weewx lost contact 
but I solved that by adding a device-link that points to the current 
USB-device..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] WMR200: Help me to find "low batt."-bits in the d9-packet

[Per Edström]

On my WMR88 (WMR100-driver) I managed to get the battery status from the 
data packages read from the console. But on the WMR200 it is not that 
obvious. I have tried with two temp.sensors going low on battery but I 
can't figure out what WMR200 is doing with that information. Maybe someone 
here have an idea?

The protocol-information is here: http://www.bashewa.com/wmr200-protocol.php

This is what I get with debug-mode when I change channel on a sensor with 
low battery (current temp.sensors with good battery are Ch.1+2+3+5) :

: *(Added Ch.4)*
Feb 27 16:46:07 eBox3350 weewx[28036]: wmr200: MainThread: D Packet raw:d9 
08 50 10 84 00 c5 01
Feb 27 16:48:07 eBox3350 weewx[28036]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 00 c5 01
: *(Added Ch.6)*
Feb 27 19:25:05 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 00 c5 01
Feb 27 19:26:04 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 00 c5 01
: *(Changed Ch.6 => Ch.10)*
Feb 27 19:54:04 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 00 c5 01
Feb 27 19:55:03 eBox3350 weewx[31196]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 08 cd 01
*: (No change, did the system note that ch.6 is missing** when scan-period 
is over? So this is Ch.4+6+10 on low batt?)*
Feb 27 20:09:04 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 10 d4 08 cd 01
Feb 27 20:09:28 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 08 cd 01
: *(Changed Ch.10 => Ch.7)*
Feb 27 20:13:04 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 08 cd 01
Feb 27 20:13:38 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 10 94 09 ce 01

*: (No change, did the system note that ch.10 is missing when scan-period 
is over? So this is Ch.4+7+10 on low batt?)*Feb 27 20:28:03 eBox3350 
weewx[32260]: wmr200: MainThread: D Packet raw:d9 08 40 10 94 09 ce 01
Feb 27 20:28:49 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 18 94 01 ce 01
*: (Changed Ch.7 => Ch.6)*
Feb 27 20:43:03 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 40 18 94 01 ce 01
Feb 27 20:44:03 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 18 d4 01 ce 01

*: (No change, did the system note that ch.10 is missing when scan-period 
is over? So this is Ch.4+6+7 on low batt?)*Feb 27 20:57:02 eBox3350 
weewx[32260]: wmr200: MainThread: D Packet raw:d9 08 00 18 d4 01 ce 01
Feb 27 20:57:42 eBox3350 weewx[32260]: wmr200: MainThread: D Packet raw:d9 
08 00 19 d4 00 ce 01
*: (Note that this SHOULD be as above i.e.  *

*MainThread: D Packet raw:d9 08 00 10 d4 00 c5 01  when running Ch4+6 with 
low batt, but it is not!)*Now, does anyone see any pattern here?

















































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































































-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] FTP-fault: type object 'set' has no attribute 'append'

[Per Edström]

I renamed #FTP.last to FOO.last and restarted Weewx. (The file is readable 
but I don't know what fault to look for..)

Now it works. So the file was blocking the upload (the files were in 
/var/www/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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] FTP-fault: type object 'set' has no attribute 'append'

[Per Edström]

I can't remember changing anything but one (I hace two) FTP-session have 
stopped working. Now, what is this due to?

Feb 11 13:49:23 eBox3350 weewx[7904]: reportengine: ftp'd 26 files in 2.31 
seconds
Feb 11 13:49:23 eBox3350 weewx[7904]: reportengine: Caught unrecoverable 
exception in generator weewx.reportengine.FtpGenerator
Feb 11 13:49:23 eBox3350 weewx[7904]:   type object 'set' has 
no attribute 'append'
Feb 11 13:49:23 eBox3350 weewx[7904]:   Traceback (most recent 
call last):
Feb 11 13:49:23 eBox3350 weewx[7904]: File 
"/usr/share/weewx/weewx/reportengine.py", line 238, in run
Feb 11 13:49:23 eBox3350 weewx[7904]:   obj.start()
Feb 11 13:49:23 eBox3350 weewx[7904]: File 
"/usr/share/weewx/weewx/reportengine.py", line 271, in start
Feb 11 13:49:23 eBox3350 weewx[7904]:   self.run()
Feb 11 13:49:23 eBox3350 weewx[7904]: File 
"/usr/share/weewx/weewx/reportengine.py", line 322, in run
Feb 11 13:49:23 eBox3350 weewx[7904]:   n = ftp_data.run()
Feb 11 13:49:23 eBox3350 weewx[7904]: File 
"/usr/share/weewx/weeutil/ftpupload.py", line 82, in run
Feb 11 13:49:23 eBox3350 weewx[7904]:   (timestamp, 
fileset) = self.getLastUpload()
Feb 11 13:49:23 eBox3350 weewx[7904]: File 
"/usr/share/weewx/weeutil/ftpupload.py", line 191, in getLastUpload
Feb 11 13:49:23 eBox3350 weewx[7904]:   fileset   = 
cPickle.load(f)
Feb 11 13:49:23 eBox3350 weewx[7904]:   AttributeError: type 
object 'set' has no attribute 'append'
Feb 11 13:49:23 eBox3350 weewx[7904]:   Generator terminated
Feb 11 13:49:27 eBox3350 weewx[7904]: wmr200: MainThread: W Rain sensor 
fault

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: How to backup weewx data and restore it after a new OS installation

[Per Edström]

I guess you could copy all fiels and directories under 
/etc/weewx/ (user settings)
/var/lib/weewx/ (database)
/usr/share/weewx/ (the "programfiles")
then just restore it on the new installation.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx stop reporting (or crash?) few time per day ????

[Per Edström]

Apparently my USB-to-COM-port converter is not stable hence causing weewx 
to stop (when the device changes). SO  I made a link to the current device 
for use in weewx.conf (details in a new thread here in the forum).
It seems to work for 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Fix USB-device to usable dev-link

[Per Edström]

To my Oregon WMR928 I have a USB-to-COM-port converter. That one seems to 
change device for unknown reason. It can happen during reboot or 
spontaneously. If it changes from /dev/ttyUSB0 to /dev/ttyUSB1 then Weewx 
stops. So I need to have a fixed device to use in weewx.conf

This page describes how to do it:
http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/

What I did was check the settings using "lsusb":
root@Ebox3350.Roses:~# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 1781:0c31 Multiple Vendors
Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible 
Power Supply
*Bus 001 Device 005: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial 
Port*
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I created the file* /etc/udev/rules.d/99-usb-serial.rules* with the content:
SUBSYSTEM=="tty", ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", 
SYMLINK+="wmr928"

(In the description they have "serial" too but I could not get that to work 
so I skipped it and it seems to do the trick anyway)

The new device (link) will be */dev/wmr928* so change 
*/etc/weewx/weewx.conf* for your station.

Reboot

Check that the new device is created and that Weewx works..

Reboot.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Monitor battery status in (extra) sensors

[Per Edström]

I know there is a lowbattery.py that will send email every hour but is 
there not just a syslog-notification available?

Are extraBatteriStatus used yet or a future feature? So one can print the 
current value of the extraBatteruStatus ..

I note that the drivers seems to be quite different in their 
implementation. In the wmr100.py there is a check on the indoor and outdoor 
sensors battery status but not on the extra ones, so I did a small change 
just to check if the battery status is there:

elif channel >= 2:
# If additional temperature sensors exist (channel>=2), then
# use observation types 'extraTemp1', 'extraTemp2', etc.
_record['extraTemp%d'  % (channel-1)] = T
_record['extraHumid%d' % (channel-1)] = R
#PEED
   #_record['extraBatteryStatus%d' % (channel)] = (packet[0] & 
0x40) >> 6
B = (packet[0] & 0x40) >> 6
if B == 1:
syslog.syslog(syslog.LOG_DEBUG, "extraBatteryStatus%d:  Low 
battery" % channel)

return _record

Resulting printout..

Jan  8 21:07:31 eBox3350 weewx[31392]: * could not detach kernel driver 
from interface 0: No data available
Jan  8 21:07:36 eBox3350 weewx[31392]: extraBatteryStatus2:  Low battery
Jan  8 21:08:00 eBox3350 weewx[31392]: wmr100: Bad USB report received.

But I can't seem to get the same information from WMR200..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: spikes in rain data

[Per Edström]

In the future, does entries in */etc/weewx/weewx.conf* prevent extreme data 
to be added to DB? Or does it just prevent it from showing?
Does "rainRate" have to be added to this list?

[StdQC]

[[MinMax]]
barometer = 24, 34.5, inHg
outTemp = -40, 120, degree_F
inTemp = 10, 120, degree_F
outHumidity = 0, 100
inHumidity = 0, 100
windSpeed = 0, 60, mile_per_hour
windGust = 0, 100, mile_per_hour
*rain = 0, 6, inch*
pressure = 24, 34.5, inHg

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] How does Weewx work?

[Per Edström]

Is there any document describing, in a rather simple overview way, how 
Weewx works?
I.e. what files are used, where to change the content to fit the user 
needs, how to access and check DB data, data format, what syntax to use etc


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Well, there are a lot of things around Weewx that I don't know and others 
that I don't understand. I thought that the default mapping should mirror 
what the console could actually provide and if the user wants other data to 
be stored in the same DB then the user have to make own configurations. The 
other "standard"-fields should be #-out so if the WMR100-user wants to use 
extraTemp4 as CPU-temp then he/she can comment it out. (Is this really 
common?).

The difference with WMR200 compared to all other WMR-stations is that the 
outdoor-channel can be used for another model of T/H-sensor and hence this 
is a very possible configuration (my "Mushroom-sensor broke when the 
roof-guys damaged the mounting and the sensor got hanging in the 
solarpanel-wire so that the rain flooded the sensor. Instead of buying a 
new "Mushroom" I could have bought another sensor and set it to channel 1).
So the mapping, in my view, should show (yellow) that as "outTemp" doesn't 
have to be a sensor for outdoor usage but can be an indoor sensor on 
channel 1:

wmr200:

'inTemp': 'temperature_0',
'outTemp': 'temperature_1', # 'extraTemp1': 'temperature_1',
'extraTemp2': 'temperature_2', #Ch.2
'extraTemp3': 'temperature_3',
'extraTemp4': 'temperature_4',
'extraTemp5': 'temperature_5',
'extraTemp6': 'temperature_6',
'extraTemp7': 'temperature_7',
'extraTemp8': 'temperature_8',
'extraTemp9': 'temperature_9',
'extraTemp10': 'temperature_10', # Ch.10
'inHumidity': 'humidity_0',
'outHumidity': 'humidity_1', # 'extraHumid1': 'humidity_1',
'extraHumid2': 'humidity_2', # Ch.2
'extraHumid3': 'humidity_3',
'extraHumid4': 'humidity_4',
'extraHumid5': 'humidity_5',
'extraHumid6': 'humidity_6',
'extraHumid7': 'humidity_7',
'extraHumid8': 'humidity_8',
'extraHumid9': 'humidity_9',
'extraHumid10': 'humidity_10',

In any case, WMR200 need two more extraTemp/extraHumid (green) in the 
standard configuration/DB.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

I have looked through the code and I can't find the collection of battery 
status from extra sensors anywhere. Looking on the WMR200-protocol I guess 
there is no clear place where the information is available:
http://www.bashewa.com/wmr200-protocol.php

Now, enabling the debug reveals that my WMR200 (with 5 extra sensors 
THGR810) sends status package:
Sensor packet:d9 08 00 10 d4 00 c5 01
where
B02: 00 
B03: 10 = 0001 
B04: d4 = 1101 0100
B05: 00
 
B06: c5 # checksum
B07: 01 # checksum

If I match my data with the procotol reverse engineering I get 
(high-lighted = 1):

   Byte 02:  (H) [1... ] = [#80]
 [.1.. ] = [#40]
 [..1. ] = [#20]
 [...1 ] = [#10]
 (L) [ 1...] = [#08]
 [ .1..] = [#04]
 [ ..1.] = [#02] Sensor fault: Sensor 1 (temp/hum outdoor) 
# Correct
 [ ...1] = [#01] Sensor fault: Wind (---) # Correct

 Byte 03:  (H) [1... ] = [#80]
 [.1.. ] = [#40]
 [..1. ] = [#20] Sensor fault: UV   (--) # Correct
 [...1 ] = [#10] Sensor fault: Rain (---) #Correct
 (L) [ 1...] = [#08]
 [ .1..] = [#04]
 [ ..1.] = [#02]
 [ ...1] = [#01]

   Byte 04:  (H) [1... ] = [#80] RF Signal Weak: Console Clock (time not 
synchronized) #This is true. The signal from Frankfurt is too week for my 
station..
 [.1.. ] = [#40] # This should mean something as it is = 1
 [..1. ] = [#20]
 [...1 ] = [#10] # This should mean something as it is = 1
 (L) [ 1...] = [#08]
 [ .1..] = [#04] # This should mean something as it is = 1
 [ ..1.] = [#02] Battery Low: Sensor 1 (temp/hum outdoor)
 [ ...1] = [#01] Battery Low: Wind ... to be confirmed)

   Byte 05:  (H) [1... ] = [#80]
 [.1.. ] = [#40]
 [..1. ] = [#20] Battery Low: UV . (below 2.4v out of 
3.0v)
 [...1 ] = [#10] Battery Low: Rain ... to be confirmed)
 (L) [ 1...] = [#08]
 [ .1..] = [#04]
 [ ..1.] = [#02]
 [ ...1] = [#01]


Now, I just replaced batteries on most of the extra sensors but the one on 
channel 4,as it is places in a remote/inaccessible place, but it should too 
be low on battery. It seems though as three sensors could be low on battery 
(if there is one bit per sensor). Maybe I should insert "bad" batteries in 
one extra sensor, change the channel and see if any bit changes and moves 
in byte 4 and 5..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Why don't WMR200 have:

'extraBatteryStatus1': 'battery_status_2', #Channel 2
'extraBatteryStatus2': 'battery_status_3',
'extraBatteryStatus3': 'battery_status_4',
'extraBatteryStatus4': 'battery_status_5',
'extraBatteryStatus5': 'battery_status_6',
'extraBatteryStatus6': 'battery_status_7',
'extraBatteryStatus7': 'battery_status_8',
+
'extraBatteryStatus8': 'battery_status_9',
'extraBatteryStatus9': 'battery_status_10', # Channel 10


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

The code in wmr200.py should be changed so the original outdoor sensor 
could be swapped out for another sensor, as stated in my code-example 
earlier.

Although I don't think many WMR200-users have a need to swap the outdoor 
sensor or use 10 extra sensors, there might be someone that need that 
feature and the change seems minimal.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Yes, different drivers for the WMR200 and WMR9x8 as there is a 
HW-difference but they need to handle the extraSensors in the same way i.e. 
having the channel number as numbering of the extraTemp.

As I described it earlier: it should be read as "extraTemp[channel]" and 
not as the sequence of extra sensors in the system. If you consider the 
outdoor sensor on WMR200 as an extra sensor, as it is using one of the 
channels, it might be more clear what I mean.
This is how it is implemented in the wmr9x8.py and how it was implemented 
in wmr200.py until the "-1" was introduced in 3.6.1.

Out of curiosity, and I tried to understand the issue 164: Why was the 
previous implementation seen as a problem? Lack of understanding on how 
WMR200 are using channel 1 compared to other WMR-models?

I note that the same "-1"-change, but in another way, is made in the WMR300 
but guess it too uses channel 1 as outdoor sensor.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Because I have the following Oregon-stations running:
1x WMR100
2x WMR200
1x WMR928

I need to have some consistency between them i.e. that the numbering of the 
extraSensors are related to the channel used or else fault finding, 
changing of the web templates etc will be more difficult. The extraSensor 
THGR810 displays the channel number on its display so with the current 
change I have to think "OK, this is a WMR200-system so this sensor on 
channel 3 is extraTemp2..or was it extraTemp4..? But if I'm on the 
WMR100-system then if would be extraTemp3..". 

So, if the "-1"-change in the WMR200-driver will remain then I have to keep 
changing it back on every driver-update. I don't need the problem described 
above!

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

The WMR200 is a bit special as it is using channel 1 for the original 
outdoor sensor. The good thing about this is that if the original outdoor 
sensor is broken then a "standard" extra sensor set on channel 1 can be 
used, but this is also why the change was not correctly made.

On e.g. WMR928 the outdoor sensor has its own "internal" channel that can't 
be used for extra sensors and here you can't replace it with a "standard" 
sensor e.g. THGR810 but you will need the original replacement sensor.

On WMR200 the display says (channel) [1] for the outdoor sensor but on the 
WMR928 is says [ ] i.e. an empty channel field.

So, on WMR200 the "extraTemp2" should not be read as "the second extraTemp" 
but rather "the extraTemp on channel 2" as this is how it is read on the 
display. This is how the naming should be interpreted on the WMR928 too, as 
related to the WMR-channel used/shown on the display.

The current change is causing a confusion as "extraTemp1" will be found on 
channel 2 on WMR200 but on channel 1 on WMR928. Really not logical.
Note that if you don't have the original outdoor sensor it is possible to 
use channel 1 on WMR200 for another sensor, as described above, but it 
requires the driver to be modified and also a setting in weewx.conf (under 
[wmr200]-section):

(I'm not a programmer so the code is not correct in syntax but I hope you 
understand my thinking here)



*wmr200.py*if sensor_id == 0:
# Indoor temperature sensor.
record['inTemp'] = temp
record['inHumidity'] = humidity
elif sensor_id == 1:
# Outdoor temperature sensor.
if (parameter-in-weewx.conf) # This will be extraTemp1 / 
extraHumid1 if not using the original outdoor sensor
  record['extraTemp%d' % (sensor_id)] = temp
  record['extraHumid%d' % (sensor_id)] = humidity
else # Using the original outdoor sensor (The Mushroom)
  record['outTemp'] = temp
  record['outHumidity'] = humidity
  record['heatindex'] = heat_index
elif sensor_id >= 2:
# Extra temperature sensors.
# If additional temperature sensors exist (channel>=2), then
# use observation types 'extraTemp1', 'extraTemp2', etc.
record['extraTemp%d' % (sensor_id)] = temp # the "-1" is 
removed/restored to as it was before
record['extraHumid%d' % (sensor_id)] = humidity # the "-1" is 
removed/restored to as it was before

if DEBUG_PACKETS_TEMP:

With the implementation now in place a new sensor on channel 1 on WMR200 
will be "extraTemp0" or channel 1 is left unsuable. Was that the intention?
On the WMR928 it is a different story as channel 1 is the first usable 
channel for extra sensors. Here is makes sense to name it "extraTemp1" as 
it is on channel 1.

The change made for WMR200 was not thought through as there is a 
significant hardware difference between the WMR-models.
I recommend it is reverted and a change as described above is made. This 
change will not affect the weewx currently running with WMR200 i.e. the 
ones that have been running weewx prior to 3.6.1.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx Uptime > Server Uptime

[Per Edström]

No, it is not a problem for me. I just noted that there is difference, if 
anyone felt like looking into it..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Well, it was a quick fix to remove that "improvement"..

Just edit this file, seach for "extraTemp", remove the yellow-marked "-1", 
save and restart Weewx..

/usr/share/weewx/weewx/drivers/wmr200.py

elif sensor_id >= 2:
# Extra temperature sensors.
# If additional temperature sensors exist (channel>=2), then
# use observation types 'extraTemp1', 'extraTemp2', etc.
record['extraTemp%d' % (sensor_id)-1] = temp
record['extraHumid%d' % (sensor_id)-1] = humidity

if DEBUG_PACKETS_TEMP:

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Weewx Uptime > Server Uptime

[Per Edström]

Yes, it states that Weewx have been running some 20 minutes MORE than the 
OS. That I don't understand..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Public IP-address

[Per Edström]

The web server is not under my control hence I can't check..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Public IP-address

[Per Edström]

Well, if I were on site this would not be a problem but the site is some 
100km away.
Weewx is FTP'ing files to the web server so there is a connection but as 
DynDNS haven't updated (unknown reason), I have no clue what the IP is. 
That is why I would like it on the web site. I know it doesn't fix the 
problem but it is a work-around until is it solved..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] After 3.6.2-upgrade: ExtraSensors have "moved" one channel/index (WMR200)

[Per Edström]

Were there a new WMR200-driver introduced in Weewx 3.6.2?
Is it 3.1.1?

I have 5 THGR810 sensors. 

skin.conf
extraTemp2 = Temperatur - Kallare (5E)
extraHumid2= Luftfuktighet - Kallare (5E)
extraTemp3 = Temperatur - Vind (5E)
extraHumid3= Luftfuktighet - Vind (5E)
extraTemp4 = Temperatur - Vind (5F)
extraHumid4= Luftfuktighet - Vind (5F)
extraTemp5 = Temperatur - Skyddsrum (L5)
extraHumid5= Luftfuktighet - Skyddsrum (L5)
extraTemp6 = Temperatur - Kanal6 (L5)
extraHumid6= Luftfuktighet - Kanal6 (L5)

But they have all steped one channel in the software i.e. the value of the 
sensor set on ch.3 will show up as extraTemp2 = ch.2, the ch.5-sensor is 
extraTemp4 in Weewx web page etc. The ch.6-sensor in N/A although it is 
"online" with WMR200.

Now, when I debug there is no extraTemp6 but extraTemp1 have emerged. It 
should not exist. I guess this is part of the problem but why did the index 
change to start on 1 instead of 2 (ch.1 is the "original" outdoor sensor on 
WMR200).

Jan  5 13:00:37 eBox3350 weewx[3827]: wmr200: MainThread: D  Packet cooked: 
id:14 Archive Data 2017-01-05 12:59:09 CET (1483617549) len:98 fields:33 
{'interval': 1, 'windchill': None, 'outHumidity': 75, 'rainRate': 0.0, 
'rain': 0.0, 'forecastIcon': 3, 'pressure': 992.0, 'extraHumid4': 23, 
'extraHumid5': 23, 'extraHumid2': 53, 'extraHumid3': 65, 'extraHumid1': 28, 
'totalRainLast': None, 'extraTemp4': 18.399, 'extraTemp5': 
21.601, 'altimeter': 992.0, 'extraTemp3': -9.3007, 
'usUnits': 16, 'extraTemp1': 21.801, 'totalRain': 
75.7428003, 'extraTemp2': -5.9004, 'heatindex': None, 
'UV': 0, 'dateTime': 1483617549.0, 'windDir': None, 'outTemp': 
-20.199, 'windSpeed': 0.0, 'inHumidity': 22, 'inTemp': 24.0, 
'rain24': 0.0, 'windGust': 0.0, 'hourRain': 0.0, 'windGustDir': None}


I see a similar problem on my other WMR200 (see picture), note the change..


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Public IP-address

[Per Edström]

For some reason is my ISP changing the public IP-address. That is not 
really a problem but it seems that DynDNS doesn't update.
Is it possible to have Weewx show the public IP-address on the weather 
page? Is there any pre-defined parameter for this?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Wind chill, dewpoint and heat index

[Per Edström]

This one have:
[Outdoor] [RH outdoor]
[Wind chill/HEat index] [Dewpoint]
The loss of windchill is due to low wind (I guess)..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Wind chill, dewpoint and heat index

[Per Edström]

I don't really know that information that is needed. This screenshot has:
[Outdoor/Dewpoint] [RH outdoor]
[Wind chill/Heat index] [ Dewpoint]


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx stop reporting (or crash?) few time per day ????

[Per Edström]

My Weewx tend to stop for various reasons so I restart Weewx every hour by 
a cronjob:

# m h  dom mon dow   command
59 * * * * /etc/init.d/weewx stop
0 * * * * /etc/init.d/weewx start

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Passive antenna amplifier for WMR200

[Per Edström]

I made one after this description and it made a difference. It would have 
been better to have a connector for an external antenna (Ground-plane) but 
this is easier to make..

http://www.the-lighthouse.se/eng/teknik/antenn-amp/antenn-amp.html

In swedish but maybe Google Translate can be of assistance.. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Wind chill, dewpoint and heat index

[Per Edström]

I have 4 (different) Oregon stations connected to Weewx (on different HW 
too).
One have stable readings/calculation on these three values but not the 
other ones. Some stations have sporadic notations on some of these.
I checked wxformulas.py on how they are calculated and what I can see they 
don't require 12hrs temp.data as the barometer-calculation does.

So, why doesn't I get these calculations right on all stations? 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Lost barometer on WMR200 and WMR88

[Per Edström]

.. I also have to modify all .tmpl files that create the web pages. Quite 
messy..
There should be a local variable that does this globally i.e. change in 
skin.conf only..

air_pressure = barometer
or
air_pressure = pressure
or
air_pressure = altimeter

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Lost barometer on WMR200 and WMR88

[Per Edström]

Apparently the "Barometer"-reading requires 12 hrs of temperature data. As 
my sensors/the station don't manage to collect all data the 
barometer-calculation fails.

But I realize I'm not that interested in barometer-readings: "*This is the 
pressure corrected for altitude, temperature, and (frequently) humidity. 
Pilots call this QFF. This is the value displayed by the standard skin*."

I think pressure-reading i.e. the local air-pressure is of more interest: 
"*This 
is the absolute, raw pressure as measured by your instrument. It is not 
corrected for altitude or pressure. Pilots call this QFE*."

So, I changed "barometer" in skin.conf for "pressure" and this did the 
trick! Now I have the readings I want..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Lost barometer on WMR200 and WMR88

[Per Edström]

..but it is working on WMR928.
I have not really noticed as temperature is the main focus. Looking back in 
history it has been lost for more than a year (as far as I can seen on 
GUI/web).

Both WMR-stations have barometer-sensor built-in but WMR928 have extrernal 
sensor (in the indoor-sensor). Is that related?

Is this a known issue?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Alarm on loss of sensor or low temperature?

[Per Edström]

I have one temperature sensor in another (small) building/house (2 sq.m) 
where the water filter is located. Now, there are serveral issues there:
1. The sensor consumes batteries very rapidly. I have to change once a 
month when it should last a year. I don't know why this is but the sensor 
is out of stock (end-of-life) so it can't be replaced.
2. The heater got an electrical fault causing the RCD (residual current 
device) to cut the power and shutting down the heater => everything froze 
solid and broke stuff.

So, I would like to monitor:
1. When contact with the temp-sensor is lost for more than e.g. 6 hrs
2. When temperature drops below +4C (indicating that the heater is out of 
order for some reason).

Is it possible to get and alert-email when the above happens? How? 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Create backup image of the running system

[Per Edström]

Actually, there is not that much info available..

Isof says one user when Weewx is running but none when Weewx is stopped.

A reboot did solve the Lock-problem but I have to stop Weewx on this unit, 
not the other one..

folke@eBox3350.L5E:~$ sqlite3 /var/lib/weewx/weewx.sdb ".backup 
/home/folke/weewx.sdb.bak"
Error: database is locked
folke@eBox3350.L5E:~$ sudo reboot

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] USB-reset changes /dev/ttyUSB0 to /dev/ttyUSB1

[Per Edström]

This is probably related to my HW i.e. the Ebox3350 and the 
RS232-to-USB-unit )PL2303). But maybe other Weewx-users have experienced a 
change in USB-device?

Questions:
- Why is the USB reset?
- Why does it change device number?
- Is there any way to lock the PL2303 to /dev/ttyUSB0 so it doesn't change?

After a reboot it is back to /dev/ttyUSB0

"
Dec 28 03:49:14 Ebox3350 kernel: [43641.405860] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:16 Ebox3350 weewx[3202]: wmr9x8: Received WMR9x8 data packet.
Dec 28 03:49:19 Ebox3350 kernel: [43646.533834] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:24 Ebox3350 kernel: [43651.465190] *usb 1-2: USB disconnect, 
address 2*
Dec 28 03:49:24 Ebox3350 kernel: [43651.465211] usb 1-2.1: USB disconnect, 
address 3
Dec 28 03:49:24 Ebox3350 kernel: [43651.465929] usb 1-2.3: USB disconnect, 
address 4
Dec 28 03:49:24 Ebox3350 kernel: [43651.485257] *usb 1-2.4: USB disconnect, 
address 5*
Dec 28 03:49:24 Ebox3350 kernel: [43651.485679] *usb 1-2: clear tt 4 (9053) 
error -19*
Dec 28 03:49:24 Ebox3350 kernel: [43651.527638] *pl2303 ttyUSB0: pl2303 
converter now disconnected from ttyUSB0*
Dec 28 03:49:24 Ebox3350 kernel: [43651.527996] pl2303 1-2.4:1.0: device 
disconnected
Dec 28 03:49:24 Ebox3350 kernel: [43651.817456] usb 1-2: new high speed USB 
device using ehci_hcd and address 6
Dec 28 03:49:24 Ebox3350 kernel: [43651.941412] usb 1-2: New USB device 
found, idVendor=1a40, idProduct=0101
Dec 28 03:49:24 Ebox3350 kernel: [43651.941436] usb 1-2: New USB device 
strings: Mfr=0, Product=1, SerialNumber=0
Dec 28 03:49:24 Ebox3350 kernel: [43651.941453] usb 1-2: Product: USB 2.0 
Hub [MTT]
Dec 28 03:49:24 Ebox3350 kernel: [43651.946294] hub 1-2:1.0: USB hub found
Dec 28 03:49:24 Ebox3350 kernel: [43651.946695] hub 1-2:1.0: 4 ports 
detected
Dec 28 03:49:24 Ebox3350 kernel: [43652.214202] usb 1-2.1: new full speed 
USB device using ehci_hcd and address 7
Dec 28 03:49:24 Ebox3350 kernel: [43652.304159] usb 1-2.1: New USB device 
found, idVendor=1781, idProduct=0c31
Dec 28 03:49:24 Ebox3350 kernel: [43652.304183] usb 1-2.1: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
Dec 28 03:49:24 Ebox3350 kernel: [43652.304200] usb 1-2.1: Product: 
TellStick Duo
Dec 28 03:49:24 Ebox3350 kernel: [43652.304213] usb 1-2.1: Manufacturer: 
Telldus
Dec 28 03:49:24 Ebox3350 kernel: [43652.304226] usb 1-2.1: SerialNumber: 
A501IW2P
Dec 28 03:49:25 Ebox3350 kernel: [43652.380956] usb 1-2.3: new low speed 
USB device using ehci_hcd and address 8
Dec 28 03:49:25 Ebox3350 kernel: [43652.510039] usb 1-2.3: New USB device 
found, idVendor=051d, idProduct=0002
Dec 28 03:49:25 Ebox3350 kernel: [43652.510062] usb 1-2.3: New USB device 
strings: Mfr=3, Product=1, SerialNumber=2
Dec 28 03:49:25 Ebox3350 kernel: [43652.510080] usb 1-2.3: Product: 
Back-UPS ES 700 FW:829.D2 .I USB FW:D2
Dec 28 03:49:25 Ebox3350 kernel: [43652.510096] usb 1-2.3: Manufacturer: APC
Dec 28 03:49:25 Ebox3350 kernel: [43652.510109] usb 1-2.3: SerialNumber: 
5B0823T19645
Dec 28 03:49:25 Ebox3350 kernel: [43652.864594] generic-usb 
0003:051D:0002.0002: hiddev96,hidraw0: USB HID v1.10 Device [APC Back-UPS 
ES 700 FW:829.D2 .I USB FW:D2 ] on usb-:00:0a.1-2.3/input0
Dec 28 03:49:25 Ebox3350 kernel: [43652.940824] usb 1-2.4: new full speed 
USB device using ehci_hcd and address 9
Dec 28 03:49:25 Ebox3350 kernel: [43653.025405] usb 1-2.4: New USB device 
found, idVendor=067b, idProduct=2303
Dec 28 03:49:25 Ebox3350 kernel: [43653.025428] usb 1-2.4: New USB device 
strings: Mfr=1, Product=2, SerialNumber=0
Dec 28 03:49:25 Ebox3350 kernel: [43653.025446] usb 1-2.4: Product: 
USB-Serial Controller D
Dec 28 03:49:25 Ebox3350 kernel: [43653.025460] usb 1-2.4: Manufacturer: 
Prolific Technology Inc.
Dec 28 03:49:25 Ebox3350 kernel: [43653.031091] *pl2303 1-2.4:1.0: pl2303 
converter detected*
Dec 28 03:49:25 Ebox3350 kernel: [43653.034439] *usb 1-2.4: pl2303 
converter now attached to ttyUSB1*
Dec 28 03:49:25 Ebox3350 kernel: [43653.119773] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:26 Ebox3350 modem-manager: (ttyUSB1) opening serial device...
Dec 28 03:49:26 Ebox3350 modem-manager: (ttyUSB1): probe requested by 
plugin 'Generic'
Dec 28 03:49:29 Ebox3350 kernel: [43656.783741] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:34 Ebox3350 kernel: [43661.911701] usb 1-2.3: input irq status 
-75  received
Dec 28 03:49:38 Ebox3350 modem-manager: (ttyUSB1) closing serial device...

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Recover corrupt DB

[Per Edström]

I tried to start sqlite3 with the dumpfile but that did not work, do I have 
to import it using the syntax you gave me?
How to I import in into the new running system? Is it too the syntax above?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Create backup image of the running system

[Per Edström]

I run my Weewx on Raspberry Pi and on a  "PC" (Ebox 3350 and Ubuntu 10). 
Both have the OS on an SD/SDHC-card.

Now, I find it messy to create a backup image:
1. Halt system
2. Power down
3. Remove SD-card
4. Put in laptop and create an image to file (5-10 min)
5. Insert SD-card in taget again and power up.
6. Write image file to new SD-card (15-20 min).

(NB! I have noted that not all 16GB SD-card have the exact same size, it 
varies quite a lot. This became an issue the trying to find a new SD-card 
for the one that failed..)

This procedure takes time and requires quite a lot of physical intervention.

Is there any way of to create or maintain an updated image from the running 
system. Maybe it's Ok to just backup some files (user installed)?

Also, it would be nice to have this "backup SD" as an alternative boot 
SD-card in case the primary one fails. I don't know if that is possible..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Recover corrupt DB

[Per Edström]

I was lazy and did not make any backup or image of my installation. (Yes - 
Bad sysadmin!)  Last week my SD-card gave up and very few files are not 
affected (and can be copied). The weewx.sdb-file is only readable by 80% 
and the rest is zeros now.

Is it possible to recover the first 80% and import it to the "new" database 
that my new installation is creating? I can dump the first 80% to a file 
but that is just all the INSERT that weewx have made. How do I import it?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.