date:20210116

Try removing the line

rain = prefer_hardware

It's what's causing the StdWXCalculate service to try and calculate a value.

I wonder where that line came from. I don't recall it ever being part of
weewx.conf

-tk

On Sat, Jan 16, 2021 at 4:58 PM Clay Jackson  wrote:

> I'm using an Accurite 5n1 - this has been working since early 3.x; just
> stopped in 4.3,  I AM using my 4.2 config files and skins.
>
> [StdWXCalculate]
>
> [[Calculations]]
> # Derived quantities are calculated by this service. Possible
> values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
>
> pressure = prefer_hardware
> barometer = prefer_hardware
> altimeter = software
> windchill = software
> heatindex = software
> dewpoint = software
> inDewpoint = prefer_hardware
> rainRate = prefer_hardware
> rain = prefer_hardware
> ET = software
> maxSolarRad = prefer_hardware
> cloudbase = prefer_hardware
> humidex = prefer_hardware
> appTemp = prefer_hardware
> windrun = prefer_hardware
>
>
> On Sat, Jan 16, 2021 at 4:45 PM Tom Keffer  wrote:
>
>> Normally, the driver does it, but if asked, WeeWX can calculate 'rain'
>> from cumulative quantities such as totalRain, by taking a difference.
>>
>> Your configuration file seems to be asking to do so, but totalRain is not
>> available. As for why it's asking, that's not clear.
>>
>> What does the section [StdWXCalculate] in your file weewx.conf look like?
>>
>>
>> On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson 
>> wrote:
>>
>>> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
>>> seeing the following error.
>>> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system:
>>> weewx.
>>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration
>>> file /etc/weewx/weewx.conf
>>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
>>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station
>>> type SDR (user.sdr)
>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is
>>> 0.78
>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
>>> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
>>> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
>>> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
>>> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
>>> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
>>> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
>>> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
>>> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
>>> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
>>> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
>>> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
>>> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
>>> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
>>> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
>>> u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2':
>>> u'temperature.1:0.AmbientF007THPacket', u'extraTemp3':
>>> u'temperature.2:0.AmbientF007THPacket', u'extraTemp4':
>>> u'temperature.3:0.AmbientF007THPacket', u'extraHumid2':
>>> u'humidity.3:0.AmbientF007THPacket'}
>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is
>>> {u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
>>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process
>>> 'rtl_433 -M utc -F json'
>>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert
>>> target unit is 0x1
>>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use
>>> data binding wx_binding
>>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record
>>> generation will be attempted in 'hardware'
>>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive
>>> interval of 300 seconds (specified in weewx configuration)
>>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS:
>>> Data for station KWAPROSS22 will be posted
>>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for
>>> station N7QNM-13 will be posted
>>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is
>>> 0.23
>>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
>>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
>>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be
>>> uploaded to mqtt://@localhost:1883/
>>> Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up

[weewx-user] How does battery and signal observation works/proccess?

2021-01-16 Thread jmc...@gmail.com

Hi!
How does these two observations works?
I mean: for battery, I have "0-100" (%) for "inTempBatteryStatus" 
field.but in reports page, I'm getting "LOW".

For signal (signal1, signal2, etc..), I have link-quality (0-255) and dBm 
(negative values). I'm not using any right now, but I would like to 
useI just don't know how it is proccesed/displayed.



-- 
You received this message because you are subscribed to the Google 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/84b20f94-de94-4f23-84b3-f724b8b2ad69n%40googlegroups.com.

Re: [weewx-user] Errors in 4.3

2021-01-16 Thread Clay Jackson

I'm using an Accurite 5n1 - this has been working since early 3.x; just
stopped in 4.3,  I AM using my 4.2 config files and skins.

[StdWXCalculate]

[[Calculations]]
# Derived quantities are calculated by this service. Possible
values are:
#  hardware- use the value provided by hardware
#  software- use the value calculated by weewx
#  prefer_hardware - use value provide by hardware if available,
#  otherwise use value calculated by weewx

pressure = prefer_hardware
barometer = prefer_hardware
altimeter = software
windchill = software
heatindex = software
dewpoint = software
inDewpoint = prefer_hardware
rainRate = prefer_hardware
rain = prefer_hardware
ET = software
maxSolarRad = prefer_hardware
cloudbase = prefer_hardware
humidex = prefer_hardware
appTemp = prefer_hardware
windrun = prefer_hardware


On Sat, Jan 16, 2021 at 4:45 PM Tom Keffer  wrote:

> Normally, the driver does it, but if asked, WeeWX can calculate 'rain'
> from cumulative quantities such as totalRain, by taking a difference.
>
> Your configuration file seems to be asking to do so, but totalRain is not
> available. As for why it's asking, that's not clear.
>
> What does the section [StdWXCalculate] in your file weewx.conf look like?
>
>
> On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson  wrote:
>
>> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
>> seeing the following error.
>> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
>> /var/run/weewx.pid
>> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system:
>> weewx.
>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration
>> file /etc/weewx/weewx.conf
>> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station
>> type SDR (user.sdr)
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is 0.78
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
>> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
>> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
>> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
>> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
>> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
>> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
>> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
>> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
>> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
>> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
>> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
>> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
>> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
>> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
>> u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2':
>> u'temperature.1:0.AmbientF007THPacket', u'extraTemp3':
>> u'temperature.2:0.AmbientF007THPacket', u'extraTemp4':
>> u'temperature.3:0.AmbientF007THPacket', u'extraHumid2':
>> u'humidity.3:0.AmbientF007THPacket'}
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is
>> {u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
>> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process
>> 'rtl_433 -M utc -F json'
>> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert target
>> unit is 0x1
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use
>> data binding wx_binding
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record generation
>> will be attempted in 'hardware'
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive
>> interval of 300 seconds (specified in weewx configuration)
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS:
>> Data for station KWAPROSS22 will be posted
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for
>> station N7QNM-13 will be posted
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is
>> 0.23
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
>> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be
>> uploaded to mqtt://@localhost:1883/
>> Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up weewx
>> version 4.3.0
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using binding
>> 'wx_binding' to database 'weewx'
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.manager: Starting
>> backfill of daily summaries
>> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Starting main
>> packet loop.
>> Jan 16 15:59:34 Weather weewx[17291] INFO weewx.engine: Main loop
>> exiting.

Re: [weewx-user] Errors in 4.3

Normally, the driver does it, but if asked, WeeWX can calculate 'rain' from
cumulative quantities such as totalRain, by taking a difference.

Your configuration file seems to be asking to do so, but totalRain is not
available. As for why it's asking, that's not clear.

What does the section [StdWXCalculate] in your file weewx.conf look like?


On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson  wrote:

> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
> seeing the following error.
> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
> /var/run/weewx.pid
> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system: weewx.
> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration
> file /etc/weewx/weewx.conf
> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station
> type SDR (user.sdr)
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is 0.78
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
> u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2':
> u'temperature.1:0.AmbientF007THPacket', u'extraTemp3':
> u'temperature.2:0.AmbientF007THPacket', u'extraTemp4':
> u'temperature.3:0.AmbientF007THPacket', u'extraHumid2':
> u'humidity.3:0.AmbientF007THPacket'}
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is
> {u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process
> 'rtl_433 -M utc -F json'
> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert target
> unit is 0x1
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use
> data binding wx_binding
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record generation
> will be attempted in 'hardware'
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive
> interval of 300 seconds (specified in weewx configuration)
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS:
> Data for station KWAPROSS22 will be posted
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for
> station N7QNM-13 will be posted
> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is
> 0.23
> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
> Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be uploaded
> to mqtt://@localhost:1883/
> Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up weewx
> version 4.3.0
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using binding
> 'wx_binding' to database 'weewx'
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.manager: Starting backfill
> of daily summaries
> Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Starting main
> packet loop.
> Jan 16 15:59:34 Weather weewx[17291] INFO weewx.engine: Main loop exiting.
> Shutting engine down.
> Jan 16 15:59:34 Weather weewx[17291] INFO user.sdr: shutdown process
> rtl_433 -M utc -F json
> Jan 16 15:59:45 Weather weewx[17291] ERROR user.sdr: process did not
> respond to kill, shutting down anyway
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: Caught
> unrecoverable exception:
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: 
> 'totalRain'
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: 
> Traceback (most recent call last):
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File
> "/usr/share/weewx/weewxd", line 154, in main
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: 
> engine.run()
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 210, in run
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: 
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
> Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File
> "/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
> Jan 16 15:59:45 Weather

[weewx-user] Errors in 4.3

2021-01-16 Thread Clay Jackson

I just upgraded (through apt update, using raspbian) to 4.3.0 and am seeing 
the following error. 
Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system: weewx.
Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading station 
type SDR (user.sdr)
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is 0.78
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is 
{u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed': 
u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp': 
u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity': 
u'humidity.04C9.Acurite5n1PacketV2', u'rain_total': 
u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus': 
u'battery.04C9.Acurite5n1PacketV2', u'inTemp': 
u'temperature.4:0.AmbientF007THPacket', u'inHumidity': 
u'humidity.4:0.AmbientF007THPacket', u'lightning_distance': 
u'distance.002B.AcuriteLightningPacket', u'soilTemp1': 
u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5': 
u'temperature.0F66.Acurite00275MPacket', u'extraHumid3': 
u'humidity.0F66.Acurite00275MPacket', u'extraTemp1': 
u'temperature.002B.AcuriteLightningPacket', u'extraHumid1': 
u'humidity.002B.AcuriteLightningPacket', u'strikes_total': 
u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2': 
u'temperature.1:0.AmbientF007THPacket', u'extraTemp3': 
u'temperature.2:0.AmbientF007THPacket', u'extraTemp4': 
u'temperature.3:0.AmbientF007THPacket', u'extraHumid2': 
u'humidity.3:0.AmbientF007THPacket'}
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: deltas is 
{u'lightning_strike_count': u'strikes_total', u'rain': u'rain_total'}
Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: startup process 
'rtl_433 -M utc -F json'
Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: Wunderground-PWS: 
Data for station KWAPROSS22 will be posted
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.restx: CWOP: Data for 
station N7QNM-13 will be posted
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: service version is 0.23
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: binding to archive
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: topic is temps
Jan 16 15:59:13 Weather weewx[17291] INFO user.mqtt: data will be uploaded 
to mqtt://@localhost:1883/
Jan 16 15:59:13 Weather weewx[17291] INFO __main__: Starting up weewx 
version 4.3.0
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx'
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.manager: Starting backfill 
of daily summaries
Jan 16 15:59:13 Weather weewx[17291] INFO weewx.engine: Starting main 
packet loop.
Jan 16 15:59:34 Weather weewx[17291] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jan 16 15:59:34 Weather weewx[17291] INFO user.sdr: shutdown process 
rtl_433 -M utc -F json
Jan 16 15:59:45 Weather weewx[17291] ERROR user.sdr: process did not 
respond to kill, shutting down anyway
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: Caught 
unrecoverable exception:
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
'totalRain'
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   Traceback 
(most recent call last):
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewxd", line 154, in main
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
engine.run()
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 210, in run
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
callback(event)
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:   
self.do_calculations(event.packet)
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__: File 
"/usr/share/weewx/weewx/wxservices.py", line 66, in do_calculations
Jan 16 15:59:45 Weather weewx[17291] CRITICAL __main__:

Re: [weewx-user] Data errors preventing report generation

It looks like you may have two instances of weewxd running.

On Sat, Jan 16, 2021 at 11:12 AM icoj...@gmail.com 
wrote:

> Hi,
>
> Aercus WeatherRanger (Fine Offset HP1000)
> Weewx 4.3.0 on Raspian 10
> Setup.py installation
>
> My weewx setup stopped generating reports on 5th January.  Nothing I tried
> fixed it.  I reinstalled on a different microSD card and I'm seeing exactly
> the same thing.  The syslog shows lots of unique constraint errors and the
> reporting loop never triggers.
>
> The unique constraint errors are always for the same days, September 2020,
> whenever I look at the log the errors are always from that same few weeks.
> I have no idea what the cause is.  I did absolutely nothing to it and it
> simply stopped working last week.
>
> Please can someone who understands the log interpret it and suggest what
> the issue is?  It's driving me insane!
>
> Many thanks,
>
> Matt
>
> Jan 16 19:00:48 weatherpi weewx[849] INFO root: HP100: Timed out too many
> times
> Jan 16 19:01:13 weatherpi weewx[849] INFO root: HP100: Timed out too many
> times
> Jan 16 19:01:19 weatherpi weewx[849] INFO root: HP100: Connected to
> address ('192.168.86.35', 60038)
> Jan 16 19:01:20 weatherpi weewx[849] INFO root: HP100: Established contact
> at 16/01/21 19:01:20
> Jan 16 19:01:20 weatherpi weewx[849] INFO root: HP100: Retrieving startup
> records
> Jan 16 19:01:31 weatherpi weewx[849] INFO weewx.manager: Added record
> 2021-01-16 18:55:15 GMT (1610823315) to database 'weewx.sdb'
> Jan 16 19:01:31 weatherpi weewx[849] INFO weewx.manager: Added record
> 2021-01-16 18:55:15 GMT (1610823315) to daily summary in 'weewx.sdb'
> Jan 16 19:01:31 weatherpi nmbd[533]: [2021/01/16 19:01:31.554850, 0]
> ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
> Jan 16 19:01:31 weatherpi nmbd[533]: query_name_response: Multiple (2)
> responses received for a query on subnet 192.168.86.40 for name WORKGROUP$
> Jan 16 19:01:31 weatherpi nmbd[533]: This response was from IP
> 192.168.86.26, reporting an IP address of 192.168.86.26.
> Jan 16 19:01:32 weatherpi weewx[849] INFO weewx.engine: Main loop exiting.
> Shutting engine down.
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: Caught OSError:
> [Errno 5] Input/output error
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  Traceback
> (most recent call last):
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "./bin/weewxd", line 154, in main
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  engine.run()
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 178, in run
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> self.dispatchEvent(weewx.Event(weewx.STARTUP))
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> callback(event)
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 567, in startup
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> self._catchup(self.engine.console.genStartupRecords)
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 682, in _catchup
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> origin='hardware'))
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> callback(event)
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File
> "/home/weewx/bin/weewx/engine.py", line 787, in new_archive_record
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: 
> to_sorted_string(event.record))
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  OSError:
> [Errno 5] Input/output error
> Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  Waiting 10
> seconds then retrying...
> Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: retrying...
> Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: Using configuration
> file /home/weewx/weewx.conf
> Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: Debug is 1
> Jan 16 19:01:42 weatherpi weewx[849] DEBUG __main__: Initializing engine
> Jan 16 19:01:42 weatherpi weewx[849] INFO weewx.engine: Loading station
> type HP1000 (user.HP1000)
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: HP1000 Starting
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Using user-defined
> broadcast mask - 192.168.86.35
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Address Mask =
> 192.168.86.35
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Retry count =
> 5.00
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Socket timeout =
> 5.00
> Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Loop

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread galfert

Yes the best method when using the Interceptor is to use the Customized 
server settings. The path doesn't matter. But in some firmware versions it 
just couldn't be left blank or it wouldn't send. So just put in index.php? 
for the path.


On Saturday, January 16, 2021 at 3:49:17 PM UTC-5 sjr4...@gmail.com wrote:

> OK. So i am homing in a little closer here. 
> I have configured the console to wunderground and it is working. 
>
> Now i need to adjust weewx.conf with the following, but as the weewx 
> server is on a different subnet, i will need to use listen mode. 
>
> [Interceptor]
> driver = user.interceptor
> device_type = wu-client 
>
> If i understand, i can point the console with a custom config to my 
> server, and then publish from my server to wunderground right?
>
> if i do that, what will the path on weewx for the console? 
>
> host:  weewx.local.lan
> Path: ?
> ID:   xx
> Key:xx
>
> also, on a side note. I can't find the log in freebsd. 
>
> On Saturday, January 16, 2021 at 9:17:02 PM UTC+1 galfert wrote:
>
>> What I understand you are saying is that you have a WH2910 and you want 
>> to interface it with WeeWX. Since you don't have an Ambient version you do 
>> have the ability to easily use the Interceptor driver. Ambient WS-2902 
>> can't without a lot of extra work. You, with the WH2910 can simply install 
>> the WeeWX Interceptor driver and make sure your WeeWX config is set to use 
>> the Interceptor driver with the correct WU client settings:
>> [Interceptor]
>> driver = user.interceptor
>> device_type = wu-client  
>>
>> ...or you can add the Ecowitt GW1000 driver and the instead use the 
>> GW1000 API driver instead of the Interceptor driver. This will allow you to 
>> add more sensors.
>>
>>
>> On Saturday, January 16, 2021 at 2:54:09 PM UTC-5 sjr4...@gmail.com 
>> wrote:
>>
>>>
>>> actually, mine is equivalent to the WH2910 - it is not a case of 
>>> getting, i already have
>>> On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:
>>>
 You have dug up quite an old thread. A lot has changed since. The 
 recommendation now is to just acquire the Ecowitt GW1000 and use the WeeWX 
 GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
 doesn't talk to the display console...as it is its own console). You'll 
 get 
 a much nicer experience with the GW1000, which will also let you add extra 
 sensors.
 https://github.com/gjr80/weewx-gw1000


 On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com 
 wrote:

> were you able to get this to work in the end. can you share the weewx 
> details please
>
> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com 
> wrote:
>
>> I see that weewx is said to support the FINE OFFSET WH2900 , I was 
>> wondering if anyone could share with me the protocol and port 
>> information 
>> that is in the driver? I
>>
>

-- 
You received this message because you are subscribed to the Google 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/9ffc8d40-0683-439b-99ae-177157df776cn%40googlegroups.com.

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-16 Thread Garry A Lockyer

Thanks, will do but later today.

Regards,

Garry Lockyer
C: +1.250.689.0686
E: ga...@lockyer.ca


> On Jan 16, 2021, at 11:09, bell...@gmail.com  wrote:
> 
> 
> Garry,
> If you want me to run something, just make it available and give me some 
> instructions.
> rich
>> On Saturday, 16 January 2021 at 12:25:33 UTC-5 garrya...@gmail.com wrote:
>> I've added the mem extension.  My test station, with a large number of feeds 
>> selected, is at: https://lockyer.ca/weather/OsoyoosLakeNorthEast
>> 
>> mem graphs are at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem
>> 
>> Regards,
>> 
>> Garry
>> 
>>> On Saturday, January 16, 2021 at 8:42:09 AM UTC-8 garrya...@gmail.com wrote:
>>> Brief Update: January 16, 2021:
>>> 
>>> I've pretty much finished moving my extension to a service.
>>> 
>>> I started WeeWX at about midnight and at about 8:20 AM, memory usage has 
>>> grown to over 941MB!  Allocated blocks was at 4,245,722.
>>> 
>>> So growing memory usage problem exists.
>>> 
>>> Bill indicated above he ran my test code on Ubuntu so I set up a Ubuntu 
>>> Raspberry Pi Desktop system:
>>> 
>>> RPi 4 - 6 GB
>>> Ubuntu Raspberry Pi OS 20.10
>>> Python3 - 3.8.6
>>> WeeWX 4.3
>>> Belchertown 1.2
>>> 
>>> Later today I intend to add the mem extension.  Will report back soonest!  
>>> I will also run things on Raspberrry Pi OS (but I have to build a new one!).
>>> 
>>> Regards,
>>> 
>>> Garry
>>> PS: I *think* I'm going to continue all development on Ubuntu as it seems 
>>> more current - it has a later linux kernel and more current Python - but 
>>> I'm not sure it's otherwise better than Raspberry Pi OS.  Both OS's have 
>>> wireless mouse lag problems, fixed somewhat by changing 'mousepoll' 
>>> setting.  Installation of Ubuntu was easy and I managed to get it to boot 
>>> from a USB SSD.  In the first 8 hours or so, Ubuntu froze a couple of 
>>> times, so now I keep an ssh session open so that I can reboot.
>>> 
 On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com wrote:
 My experience is that when I recreate an include file for Belchertown on 
 each archive cycle, as an extension to Belchertown or as a service, memory 
 usage increases with each cycle and eventually errors start.  I’ve seen 
 the error I reported in this string and unresponsive systems.  So, yes, I 
 think there’s a problem.
 
 The memory test service I provided starts out at about 45 MB and increases 
 at about 3 MB per cycle.  I’ve seen WeeWx memory usage grow to over 1 GB!
 
 I’m working on a new version of my extension, as a service, and will 
 report back on its memory usage, hopefully within only a couple of days.
 
 Thanks for all your help!
 
 
 Regards,
 
 Garry Lockyer
 C: +1.250.689.0686
 E: ga...@lockyer.ca
 
 
>> On Jan 9, 2021, at 19:11, vince  wrote:
>> 
> If your memory usage is stable, is there a problem ?
 
> It's pretty typical after a weewx startup for the usage to go up a bit 
> then level off nicely.
> 
>> On Saturday, January 9, 2021 at 4:41:51 PM UTC-8 bell...@gmail.com wrote:
>> Garry,
>> I ran your test extension for a bit in my Ubuntu VM.  Doesn't appear to 
>> be leaking.
>>  16:42:24 {'mem_size': 338.53515625, 'mem_rss': 32.953125, 'mem_share': 
>> 11.28125}
>>  16:47:38 {'mem_size': 423.80859375, 'mem_rss': 47.75, 'mem_share': 
>> 11.796875}
>>  16:52:53 {'mem_size': 424.4140625, 'mem_rss': 48.2265625, 'mem_share': 
>> 11.796875}
>>  16:57:24 {'mem_size': 426.46875, 'mem_rss': 50.19921875, 'mem_share': 
>> 11.796875}
>>  17:02:32 {'mem_size': 426.46875, 'mem_rss': 50.21875, 'mem_share': 
>> 11.796875}
>>  17:07:20 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:12:27 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:17:26 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:22:24 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:27:19 {'mem_size': 424.6640625, 'mem_rss': 48.71875, 'mem_share': 
>> 11.796875}
>>  17:32:27 {'mem_size': 424.6640625, 'mem_rss': 48.71875, 'mem_share': 
>> 11.796875}
>>  17:37:17 {'mem_size': 424.5859375, 'mem_rss': 48.7109375, 'mem_share': 
>> 11.796875}
>>  17:42:21 {'mem_size': 424.58203125, 'mem_rss': 48.70703125, 
>> 'mem_share': 11.796875}
>>  17:47:24 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>> 11.796875}
>>  17:52:21 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>> 11.796875}
>>  17:57:15 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
>> 'mem_share': 11.796875}
>>  18:02:11 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
>> 'mem_share': 11.796875}
>>  18:07:13 {'mem_size': 425.1171875, 'mem_rss': 49.3359375,

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread S R

OK. So i am homing in a little closer here. 
I have configured the console to wunderground and it is working. 

Now i need to adjust weewx.conf with the following, but as the weewx server 
is on a different subnet, i will need to use listen mode. 

[Interceptor]
driver = user.interceptor
device_type = wu-client 

If i understand, i can point the console with a custom config to my server, 
and then publish from my server to wunderground right?

if i do that, what will the path on weewx for the console? 

host:  weewx.local.lan
Path: ?
ID:   xx
Key:xx

also, on a side note. I can't find the log in freebsd. 

On Saturday, January 16, 2021 at 9:17:02 PM UTC+1 galfert wrote:

> What I understand you are saying is that you have a WH2910 and you want to 
> interface it with WeeWX. Since you don't have an Ambient version you do 
> have the ability to easily use the Interceptor driver. Ambient WS-2902 
> can't without a lot of extra work. You, with the WH2910 can simply install 
> the WeeWX Interceptor driver and make sure your WeeWX config is set to use 
> the Interceptor driver with the correct WU client settings:
> [Interceptor]
> driver = user.interceptor
> device_type = wu-client  
>
> ...or you can add the Ecowitt GW1000 driver and the instead use the GW1000 
> API driver instead of the Interceptor driver. This will allow you to add 
> more sensors.
>
>
> On Saturday, January 16, 2021 at 2:54:09 PM UTC-5 sjr4...@gmail.com wrote:
>
>>
>> actually, mine is equivalent to the WH2910 - it is not a case of getting, 
>> i already have
>> On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:
>>
>>> You have dug up quite an old thread. A lot has changed since. The 
>>> recommendation now is to just acquire the Ecowitt GW1000 and use the WeeWX 
>>> GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
>>> doesn't talk to the display console...as it is its own console). You'll get 
>>> a much nicer experience with the GW1000, which will also let you add extra 
>>> sensors.
>>> https://github.com/gjr80/weewx-gw1000
>>>
>>>
>>> On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com 
>>> wrote:
>>>
 were you able to get this to work in the end. can you share the weewx 
 details please

 On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com 
 wrote:

> I see that weewx is said to support the FINE OFFSET WH2900 , I was 
> wondering if anyone could share with me the protocol and port information 
> that is in the driver? I
>


-- 
You received this message because you are subscribed to the Google 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/0962cbf9-35dd-4112-a18b-37d9a34e8d1bn%40googlegroups.com.

[weewx-user] Re: error 401 with import WU

2021-01-16 Thread Sébastien F4GQK

Hello,

[image: error401.jpg]


My version Weewx is : 4.3.0

Thanks

Sebastien - F4GQK 

Le mardi 12 janvier 2021 à 20:30:37 UTC+1, gjr80 a écrit :

> Hi,
>
> Can you please post the exact output you are seeing when wee_import fails. 
> Also what version of WeeWX are you running?
>
> Gary
> On Wednesday, 13 January 2021 at 03:52:44 UTC+10 f4...@f4gqk.fr wrote:
>
>> Hello,
>>
>> I am going to the following command:
>>
>>
>>
>> * wee_import --config=/etc/weewx/weewx.conf 
>> --import-config=/var/tmp/wu.conf  *
>>
>> and I have a 401 error.
>>
>> *HTTP Error 401, Unauthorized*
>>
>> My station ID is OK on wunderground and my password is OK too.
>>
>> Does anyone have the same problem?
>>
>> Thank you and happy new year
>>
>> Sebastien 
>>
>>
>>

-- 
You received this message because you are subscribed to the Google 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/8bf2ae79-39b8-4dfa-b696-0dee468d7e82n%40googlegroups.com.

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread galfert

What I understand you are saying is that you have a WH2910 and you want to 
interface it with WeeWX. Since you don't have an Ambient version you do 
have the ability to easily use the Interceptor driver. Ambient WS-2902 
can't without a lot of extra work. You, with the WH2910 can simply install 
the WeeWX Interceptor driver and make sure your WeeWX config is set to use 
the Interceptor driver with the correct WU client settings:
[Interceptor]
driver = user.interceptor
device_type = wu-client  

...or you can add the Ecowitt GW1000 driver and the instead use the GW1000 
API driver instead of the Interceptor driver. This will allow you to add 
more sensors.

On Saturday, January 16, 2021 at 2:54:09 PM UTC-5 sjr4...@gmail.com wrote:

>
> actually, mine is equivalent to the WH2910 - it is not a case of getting, 
> i already have
> On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:
>
>> You have dug up quite an old thread. A lot has changed since. The 
>> recommendation now is to just acquire the Ecowitt GW1000 and use the WeeWX 
>> GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
>> doesn't talk to the display console...as it is its own console). You'll get 
>> a much nicer experience with the GW1000, which will also let you add extra 
>> sensors.
>> https://github.com/gjr80/weewx-gw1000
>>
>>
>> On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com 
>> wrote:
>>
>>> were you able to get this to work in the end. can you share the weewx 
>>> details please
>>>
>>> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com 
>>> wrote:
>>>
 I see that weewx is said to support the FINE OFFSET WH2900 , I was 
 wondering if anyone could share with me the protocol and port information 
 that is in the driver? I

>>>

-- 
You received this message because you are subscribed to the Google 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/a918a7b5-e20a-47a4-92bf-bec00e114ac3n%40googlegroups.com.

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread Rainer Lang

I don't think you properly understood what galfert was saying resp. what
he wanted to say:

what he meant was that an _additional_ Ecowitt GW1000 displayless
console (+/- 36 USD) would do the best job. If you don't know the piece,
I recommend to look it up at ecowitt.com. It's a matchbox size USB port
powered console.

With it you can receive (and process in weewx) all the sensors of your
WH2900 sensor array plus all extra sensors Ecowitt or Ambient or other
Fine Offset clone resellers offer

if you decide to purchase them by the help of the weewx GW1000 API driver.

WH2910 indicates to me that it is not an Ambient but an Ecowitt or other
FIne Offset clone device you are talking about/own.
Then you could (but that's rather old fashioned and has got several
caveats) also use the weewx Interceptor driver and the customized server
push data functionality of your WH2910 console.

On 16.01.2021 20:54, S R wrote:

actually, mine is equivalent to the WH2910 - it is not a case of
getting, i already have

On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:

You have dug up quite an old thread. A lot has changed since. The
recommendation now is to just acquire the Ecowitt GW1000 and use
the WeeWX GW1000 API driver. The GW1000 will directly pick up your
sensor data (it doesn't talk to the display console...as it is its
own console). You'll get a much nicer experience with the GW1000,
which will also let you add extra sensors.
https://github.com/gjr80/weewx-gw1000

On Saturday, January 16, 2021 at 2:43:44 AM UTC-5
sjr4...@gmail.com wrote:

were you able to get this to work in the end. can you share
the weewx details please

On Saturday, April 1, 2017 at 4:37:01 PM UTC+2
44085w...@gmail.com wrote:

I see that weewx is said to support the FINE OFFSET WH2900
, I was wondering if anyone could share with me the
protocol and port information that is in the driver? I

--
You received this message because you are subscribed to the Google
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/853cc4c5-709d-491f-97b8-3fec2a1548d9n%40googlegroups.com
.

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/5197005a-48fd-9c65-dcd3-bb932cf98df8%40gmail.com.

Re: [weewx-user] Re: skin Belchertown " earth Quake"

If this is your website:

http://jurassikpat.ddns.net/weewx/belchertown/

Then you don't have installed the skin version that a gave the link to.

Op zaterdag 16 januari 2021 om 20:39:58 UTC+1 schreef sali...@gmail.com:

> Hi
>
> I used already the master, "weewx-belchertown-master.zip", but there is 
> more errors before !!!
>
> bye
>
> patrick
> Le 16/01/2021 à 19:31, Arend a écrit :
>
> Thank you Vince for pointing this out. 
>
> He needs the unreleased master: 
> https://github.com/poblabs/weewx-belchertown/archive/master.zip
>
> Arend
>
> Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:
>
>> On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:
>>
>>> That belchertown.py file is an old 1.2 version. The problem right now is 
>>> that there are multiple Belchertown versions out there which all bear the 
>>> version number 1.2. This is because at the moment changes are all merged 
>>> into the Belchertown 1.2 master without changes to the version numbers.
>>
>>
>> Um - not quite.   There is no such thing as 'Belchertown 1.2 master'. 
>>   There is the released v1.2 and there is a rolling  'unreleased' master of 
>> whatever might come next.
>>
>> A quick look says that there have been 137 commits to master after 1.2 
>> was released in September, so if you simply run off a git clone of master 
>> there is some risk until Pat releases a new tested version.  You can get 
>> the 'released' versions from 
>> https://github.com/poblabs/weewx-belchertown/releases
>>
>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/95d5d647-c8d2-427f-9484-f7908843d877n%40googlegroups.com
>  
> 
> .
>
>

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

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread S R


actually, mine is equivalent to the WH2910 - it is not a case of getting, i 
already have
On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:

> You have dug up quite an old thread. A lot has changed since. The 
> recommendation now is to just acquire the Ecowitt GW1000 and use the WeeWX 
> GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
> doesn't talk to the display console...as it is its own console). You'll get 
> a much nicer experience with the GW1000, which will also let you add extra 
> sensors.
> https://github.com/gjr80/weewx-gw1000
>
>
> On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com wrote:
>
>> were you able to get this to work in the end. can you share the weewx 
>> details please
>>
>> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com wrote:
>>
>>> I see that weewx is said to support the FINE OFFSET WH2900 , I was 
>>> wondering if anyone could share with me the protocol and port information 
>>> that is in the driver? I
>>>
>>

-- 
You received this message because you are subscribed to the Google 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/853cc4c5-709d-491f-97b8-3fec2a1548d9n%40googlegroups.com.

Re: [weewx-user] Re: skin Belchertown " earth Quake"

I used already the master, "weewx-belchertown-master.zip", but there is
more errors before !!!

bye

patrick

Le 16/01/2021 à 19:31, Arend a écrit :

Thank you Vince for pointing this out.

He needs the unreleased master:
https://github.com/poblabs/weewx-belchertown/archive/master.zip

Arend

Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:

On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:

That belchertown.py file is an old 1.2 version. The problem
right now is that there are multiple Belchertown versions out
there which all bear the version number 1.2. This is because
at the moment changes are all merged into the Belchertown 1.2
master without changes to the version numbers.

Um - not quite. There is no such thing as 'Belchertown 1.2
master'. There is the released v1.2 and there is a rolling
'unreleased' master of whatever might come next.

A quick look says that there have been 137 commits to master after
1.2 was released in September, so if you simply run off a git
clone of master there is some risk until Pat releases a new tested
version. You can get the 'released' versions from
https://github.com/poblabs/weewx-belchertown/releases

--
You received this message because you are subscribed to the Google
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/95d5d647-c8d2-427f-9484-f7908843d877n%40googlegroups.com
.

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/d771fb20-e6c2-2043-2fb6-ea35791212c4%40gmail.com.

Re: [weewx-user] aeris weather

hi,

the issue resolved, it was an issue on their servers.

bye

Patrick

Le 16/01/2021 à 18:59, Tom Keffer a écrit :
I have been having similar errors for the last 10 hours. Something
going on at the PWSWeather site, I guess. This has happened before.

On Sat, Jan 16, 2021 at 9:44 AM sali...@gmail.com
> wrote:

hi,

I have this error "Jan 16 18:42:59 raspberrypi weewx[22190] ERROR
weewx.restx: PWSWeather: Failed to publish record 2021-01-16
18:42:00 CET (1610818920): Failed upload after 3 tries"

but when I connect me on the website with my login it is OK !
an idea

thanks

Patrick
--
You received this message because you are subscribed to the Google

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/da0a9026-f926-42a6-98fd-7d1c1e820c52n%40googlegroups.com

--
You received this message because you are subscribed to the Google
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to weewx-user+unsubscr...@googlegroups.com
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBscvNOXkzdxKUNg_pp-PpeyYntCqyWc1dweNLhB%3D0SfQ%40mail.gmail.com
.

--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/b5d34231-1a76-7626-e64c-4ded07e95483%40gmail.com.

[weewx-user] Data errors preventing report generation

2021-01-16 Thread icoj...@gmail.com

Hi,

Aercus WeatherRanger (Fine Offset HP1000)
Weewx 4.3.0 on Raspian 10
Setup.py installation

My weewx setup stopped generating reports on 5th January.  Nothing I tried 
fixed it.  I reinstalled on a different microSD card and I'm seeing exactly 
the same thing.  The syslog shows lots of unique constraint errors and the 
reporting loop never triggers.

The unique constraint errors are always for the same days, September 2020, 
whenever I look at the log the errors are always from that same few weeks.  
I have no idea what the cause is.  I did absolutely nothing to it and it 
simply stopped working last week.

Please can someone who understands the log interpret it and suggest what 
the issue is?  It's driving me insane!

Many thanks,

Matt

Jan 16 19:00:48 weatherpi weewx[849] INFO root: HP100: Timed out too many 
times
Jan 16 19:01:13 weatherpi weewx[849] INFO root: HP100: Timed out too many 
times
Jan 16 19:01:19 weatherpi weewx[849] INFO root: HP100: Connected to address 
('192.168.86.35', 60038)
Jan 16 19:01:20 weatherpi weewx[849] INFO root: HP100: Established contact 
at 16/01/21 19:01:20
Jan 16 19:01:20 weatherpi weewx[849] INFO root: HP100: Retrieving startup 
records
Jan 16 19:01:31 weatherpi weewx[849] INFO weewx.manager: Added record 
2021-01-16 18:55:15 GMT (1610823315) to database 'weewx.sdb'
Jan 16 19:01:31 weatherpi weewx[849] INFO weewx.manager: Added record 
2021-01-16 18:55:15 GMT (1610823315) to daily summary in 'weewx.sdb'
Jan 16 19:01:31 weatherpi nmbd[533]: [2021/01/16 19:01:31.554850, 0] 
../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Jan 16 19:01:31 weatherpi nmbd[533]: query_name_response: Multiple (2) 
responses received for a query on subnet 192.168.86.40 for name WORKGROUP$
Jan 16 19:01:31 weatherpi nmbd[533]: This response was from IP 
192.168.86.26, reporting an IP address of 192.168.86.26.
Jan 16 19:01:32 weatherpi weewx[849] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__: Caught OSError: 
[Errno 5] Input/output error
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  Traceback 
(most recent call last):
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"./bin/weewxd", line 154, in main
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  engine.run()
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 178, in run
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  
self.dispatchEvent(weewx.Event(weewx.STARTUP))
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  callback(event)
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 567, in startup
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  
self._catchup(self.engine.console.genStartupRecords)
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 682, in _catchup
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  
origin='hardware'))
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  callback(event)
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  File 
"/home/weewx/bin/weewx/engine.py", line 787, in new_archive_record
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  
to_sorted_string(event.record))
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  OSError: 
[Errno 5] Input/output error
Jan 16 19:01:32 weatherpi weewx[849] CRITICAL __main__:  Waiting 10 
seconds then retrying...
Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: retrying...
Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: Using configuration 
file /home/weewx/weewx.conf
Jan 16 19:01:42 weatherpi weewx[849] INFO __main__: Debug is 1
Jan 16 19:01:42 weatherpi weewx[849] DEBUG __main__: Initializing engine
Jan 16 19:01:42 weatherpi weewx[849] INFO weewx.engine: Loading station 
type HP1000 (user.HP1000)
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: HP1000 Starting
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Using user-defined 
broadcast mask - 192.168.86.35
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Address Mask = 
192.168.86.35
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Retry count = 
5.00
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Socket timeout = 
5.00
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Loop delay = 
15.00
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Retry Wait = 5.00
Jan 16 19:01:42 weatherpi weewx[849] INFO root: HP100: Max Retry = 3.00
Jan 16 19:01:42 weatherpi weewx[849] DEBUG weewx.engine: Loading service

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-16 Thread bell...@gmail.com


Garry,
If you want me to run something, just make it available and give me some 
instructions.
rich
On Saturday, 16 January 2021 at 12:25:33 UTC-5 garrya...@gmail.com wrote:

> I've added the mem extension.  My test station, with a large number of 
> feeds selected, is at: https://lockyer.ca/weather/OsoyoosLakeNorthEast
>
> mem graphs are at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem
>
> Regards,
>
> Garry
>
> On Saturday, January 16, 2021 at 8:42:09 AM UTC-8 garrya...@gmail.com 
> wrote:
>
>> Brief Update: January 16, 2021:
>>
>> I've pretty much finished moving my extension to a service.
>>
>> I started WeeWX at about midnight and at about 8:20 AM, memory usage has 
>> grown to over 941MB!  Allocated blocks was at 4,245,722.
>>
>> So growing memory usage problem exists.
>>
>> Bill indicated above he ran my test code on Ubuntu so I set up a Ubuntu 
>> Raspberry Pi Desktop system:
>>
>> RPi 4 - 6 GB
>> Ubuntu Raspberry Pi OS 20.10
>> Python3 - 3.8.6
>> WeeWX 4.3
>> Belchertown 1.2
>>
>> Later today I intend to add the mem extension.  Will report back 
>> soonest!  I will also run things on Raspberrry Pi OS (but I have to build a 
>> new one!).
>>
>> Regards,
>>
>> Garry
>> PS: I *think* I'm going to continue all development on Ubuntu as it seems 
>> more current - it has a later linux kernel and more current Python - but 
>> I'm not sure it's otherwise better than Raspberry Pi OS.  Both OS's have 
>> wireless mouse lag problems, fixed somewhat by changing 'mousepoll' 
>> setting.  Installation of Ubuntu was easy and I managed to get it to boot 
>> from a USB SSD.  In the first 8 hours or so, Ubuntu froze a couple of 
>> times, so now I keep an ssh session open so that I can reboot.
>>
>> On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com 
>> wrote:
>>
>>> My experience is that when I recreate an include file for Belchertown on 
>>> each archive cycle, as an extension to Belchertown or as a service, memory 
>>> usage increases with each cycle and eventually errors start.  I’ve seen the 
>>> error I reported in this string and unresponsive systems.  So, yes, I think 
>>> there’s a problem.
>>>
>>> The memory test service I provided starts out at about 45 MB and 
>>> increases at about 3 MB per cycle.  I’ve seen WeeWx memory usage grow to 
>>> over 1 GB!
>>>
>>> I’m working on a new version of my extension, as a service, and will 
>>> report back on its memory usage, hopefully within only a couple of days.
>>>
>>> Thanks for all your help!
>>>
>>>
>>> Regards,
>>>
>>> Garry Lockyer
>>> C: +1.250.689.0686 <(250)%20689-0686>
>>> E: ga...@lockyer.ca
>>>
>>>
>>> On Jan 9, 2021, at 19:11, vince  wrote:
>>>
>>> If your memory usage is stable, is there a problem ?
>>>
>>> It's pretty typical after a weewx startup for the usage to go up a bit 
>>> then level off nicely.
>>>
>>> On Saturday, January 9, 2021 at 4:41:51 PM UTC-8 bell...@gmail.com 
>>> wrote:
>>>
 Garry,
 I ran your test extension for a bit in my Ubuntu VM.  Doesn't appear to 
 be leaking.
  16:42:24 {'mem_size': 338.53515625, 'mem_rss': 32.953125, 'mem_share': 
 11.28125}
  16:47:38 {'mem_size': 423.80859375, 'mem_rss': 47.75, 'mem_share': 
 11.796875}
  16:52:53 {'mem_size': 424.4140625 <(424)%20414-0625>, 'mem_rss': 
 48.2265625, 'mem_share': 11.796875}
  16:57:24 {'mem_size': 426.46875, 'mem_rss': 50.19921875, 'mem_share': 
 11.796875}
  17:02:32 {'mem_size': 426.46875, 'mem_rss': 50.21875, 'mem_share': 
 11.796875}
  17:07:20 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
 11.796875}
  17:12:27 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
 11.796875}
  17:17:26 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
 11.796875}
  17:22:24 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
 11.796875}
  17:27:19 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
 48.71875, 'mem_share': 11.796875}
  17:32:27 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
 48.71875, 'mem_share': 11.796875}
  17:37:17 {'mem_size': 424.5859375 <(424)%20585-9375>, 'mem_rss': 
 48.7109375, 'mem_share': 11.796875}
  17:42:21 {'mem_size': 424.58203125, 'mem_rss': 48.70703125, 
 'mem_share': 11.796875}
  17:47:24 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
 11.796875}
  17:52:21 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
 11.796875}
  17:57:15 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
 'mem_share': 11.796875}
  18:02:11 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
 'mem_share': 11.796875}
  18:07:13 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
 11.796875}
  18:12:14 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
 11.796875}
  18:17:12 {'mem_size': 425.21875, 'mem_rss': 49.4375, 'mem_share': 
 11.796875}
  18:22:10

Re: [weewx-user] Recording External Temperatures

2021-01-16 Thread Mike Revitt

I tend to use Cloud Formation with a User Data script. If I can get it 
working I will share the template on here

On Saturday, January 16, 2021 at 6:04:27 PM UTC vince wrote:

> On Saturday, January 16, 2021 at 5:55:11 AM UTC-8 mi...@cougar.eu.com 
> wrote:
>
>> I used to use Virtual Box all the time but these days tend to spin up EC2 
>> hosts, but hadn't even thought of that for WeeWX testing, so definitely 
>> going to give that a go
>>
>
> Yup.  You could probably use the provisioner scripts I have in my repo as 
> a userdata script in EC2 or Lightsail.   I'd do it via Terraform but there 
> are many ways of course.
>
> Nice thing about Vagrant/VirtualBox is that once you have those two 
> packages installed and have cloned my repo, it's just "vagrant up" to 
> boot+configure a VM, and "vagrant destroy" to delete them. 
>

-- 
You received this message because you are subscribed to the Google 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/0e9cd604-46e1-43be-b0aa-b2929db23d62n%40googlegroups.com.

[weewx-user] Problem in forecast extension using darsky as source

2021-01-16 Thread Anders Fosgerau



For the record: In using the modified forecast extension posted earlier on 
the list as I'm running under python3, mysql and a metric database. But I 
guess this is a more generic problem than just me deviating from standard 
configuration.

The problem appears "periodically" when using the forecast extension with 
Darsky as source for the forecast module. The short version is that a 
metric/US conversion without float rounding seems to cause a database 
schema "violation".

This is the log:

Jan 16 18:10:17 hjernen weewx[8513] INFO user.forecast: DSThread: DS: 
downloading forecast from 
'https://api.darksky.net/forecast/6bb8/55.71275,12.395433?exclude=currently,minutely,hourly,alerts,flags=en=us'
Jan 16 18:10:18 hjernen weewx[8513] INFO user.forecast: DSThread: DS: got 8 
forecast records
Jan 16 18:10:18 hjernen weewx[8513] INFO weewx.manager: Added record 
2021-01-16 18:10:18 CET (1610817018) to database 'weewx_forecast'
Jan 16 18:10:18 hjernen weewx[8513] ERROR user.forecast: DSThread: DS: save 
failed (attempt 1 of 3): (1406, "Data too long for column 'qsf' at row 1")
Jan 16 18:10:28 hjernen weewx[8513] INFO weewx.manager: Added record 
2021-01-16 18:10:18 CET (1610817018) to database 'weewx_forecast'
Jan 16 18:10:28 hjernen weewx[8513] ERROR user.forecast: DSThread: DS: save 
failed (attempt 2 of 3): (1406, "Data too long for column 'qsf' at row 1")
Jan 16 18:10:38 hjernen weewx[8513] INFO weewx.manager: Added record 
2021-01-16 18:10:18 CET (1610817018) to database 'weewx_forecast'
Jan 16 18:10:38 hjernen weewx[8513] ERROR user.forecast: DSThread: DS: save 
failed (attempt 3 of 3): (1406, "Data too long for column 'qsf' at row 1")
Jan 16 18:10:48 hjernen weewx[8513] ERROR user.forecast: DSThread: DS: 
forecast failure: save failed after 3 attempts, dbm_dict: {'manager': 
'weewx.manager.Manager', 'schema': [('method', 'VARCHAR(10) NOT NULL'), 
('usUnits', 'INTEGER NOT NULL'), ('dateTime', 'INTEGER NOT NULL'), 
('issued_ts', 'INTEGER NOT NULL'), ('event_ts', 'INTEGER NOT NULL'), 
('duration', 'INTEGER'), ('location', 'VARCHAR(64)'), ('desc', 
'VARCHAR(256)'), ('zcode', 'CHAR(1)'), ('hour', 'INTEGER'), ('tempMin', 
'REAL'), ('tempMax', 'REAL'), ('temp', 'REAL'), ('dewpoint', 'REAL'), 
('humidity', 'REAL'), ('windDir', 'VARCHAR(3)'), ('windSpeed', 'REAL'), 
('windGust', 'REAL'), ('windChar', 'VARCHAR(2)'), ('clouds', 'VARCHAR(2)'), 
('pop', 'REAL'), ('qpf', 'VARCHAR(8)'), ('qsf', 'VARCHAR(5)'), ('rain', 
'VARCHAR(2)'), ('rainshwrs', 'VARCHAR(2)'), ('tstms', 'VARCHAR(2)'), 
('drizzle', 'VARCHAR(2)'), ('snow', 'VARCHAR(2)'), ('snowshwrs', 
'VARCHAR(2)'), ('flurries', 'VARCHAR(2)'), ('sleet', 'VARCHAR(2)'), 
('frzngrain', 'VARCHAR(2)'), ('frzngdrzl', 'VARCHAR(2)'), ('hail', 
'VARCHAR(2)'), ('obvis', 'VARCHAR(3)'), ('windChill', 'REAL'), 
('heatIndex', 'REAL'), ('uvIndex', 'INTEGER'), ('airQuality', 'INTEGER'), 
('hilo', 'CHAR(1)'), ('offset', 'REAL'), ('waveheight', 'REAL'), 
('waveperiod', 'REAL')], 'table_name': 'archive', 'database_dict': 
{'database_name': 'weewx_forecast', 'driver': 'weedb.mysql', 'host': 
'localhost', 'user': 'weewx', 'password': 'weewx'}}

The DS forecast retrieved was:
{"latitude":55.71275,"longitude":12.395433,"timezone":"Europe/Copenhagen","daily":{"summary":"Light
 
rain on Monday through 
Friday.","icon":"rain","data":[{"time":1610751600,"summary":"Clear 
throughout the 
day.","icon":"clear-day","sunriseTime":1610782200,"sunsetTime":1610809980,"moonPhase":0.12,"precipIntensity":0,"precipIntensityMax":0.0002,"precipIntensityMaxTime":1610820540,"precipProbability":0.02,"temperatureHigh":29.65,"temperatureHighTime":1610795280,"temperatureLow":24.04,"temperatureLowTime":1610858700,"apparentTemperatureHigh":23.98,"apparentTemperatureHighTime":1610795220,"apparentTemperatureLow":19.81,"apparentTemperatureLowTime":1610863200,"dewPoint":19.52,"humidity":0.79,"pressure":1023.3,"windSpeed":4.61,"windGust":8.64,"windGustTime":1610820900,"windBearing":337,"cloudCover":0.22,"uvIndex":0,"uvIndexTime":1610796000,"visibility":10,"ozone":334.4,"temperatureMin":20.57,"temperatureMinTime":1610759820,"temperatureMax":29.65,"temperatureMaxTime":1610795280,"apparentTemperatureMin":14.84,"apparentTemperatureMinTime":1610759640,"apparentTemperatureMax":23.98,"apparentTemperatureMaxTime":1610795220},{"time":1610838000,"summary":"Mostly
 
cloudy throughout the

Re: [weewx-user] Re: skin Belchertown " earth Quake"

Thank you Vince for pointing this out.

He needs the unreleased master: 
https://github.com/poblabs/weewx-belchertown/archive/master.zip

Arend

Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:

> On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:
>
>> That belchertown.py file is an old 1.2 version. The problem right now is 
>> that there are multiple Belchertown versions out there which all bear the 
>> version number 1.2. This is because at the moment changes are all merged 
>> into the Belchertown 1.2 master without changes to the version numbers.
>
>
> Um - not quite.   There is no such thing as 'Belchertown 1.2 master'. 
>   There is the released v1.2 and there is a rolling  'unreleased' master of 
> whatever might come next.
>
> A quick look says that there have been 137 commits to master after 1.2 was 
> released in September, so if you simply run off a git clone of master there 
> is some risk until Pat releases a new tested version.  You can get the 
> 'released' versions from 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
>

-- 
You received this message because you are subscribed to the Google 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/95d5d647-c8d2-427f-9484-f7908843d877n%40googlegroups.com.

Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-16 Thread vince

On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:

> That belchertown.py file is an old 1.2 version. The problem right now is 
> that there are multiple Belchertown versions out there which all bear the 
> version number 1.2. This is because at the moment changes are all merged 
> into the Belchertown 1.2 master without changes to the version numbers.

Um - not quite.   There is no such thing as 'Belchertown 1.2 master'.   
There is the released v1.2 and there is a rolling  'unreleased' master of 
whatever might come next.

A quick look says that there have been 137 commits to master after 1.2 was 
released in September, so if you simply run off a git clone of master there 
is some risk until Pat releases a new tested version.  You can get the 
'released' versions 
from https://github.com/poblabs/weewx-belchertown/releases

-- 
You received this message because you are subscribed to the Google 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/65f33e9c-ec17-47b6-a196-d52ea0a2fc1fn%40googlegroups.com.

Re: [weewx-user] Recording External Temperatures

2021-01-16 Thread vince

On Saturday, January 16, 2021 at 5:55:11 AM UTC-8 mi...@cougar.eu.com wrote:

> I used to use Virtual Box all the time but these days tend to spin up EC2 
> hosts, but hadn't even thought of that for WeeWX testing, so definitely 
> going to give that a go
>

Yup.  You could probably use the provisioner scripts I have in my repo as a 
userdata script in EC2 or Lightsail.   I'd do it via Terraform but there 
are many ways of course.

Nice thing about Vagrant/VirtualBox is that once you have those two 
packages installed and have cloned my repo, it's just "vagrant up" to 
boot+configure a VM, and "vagrant destroy" to delete them. 

-- 
You received this message because you are subscribed to the Google 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/55522bc6-ae5a-48ed-a95d-bbbd6f1f1891n%40googlegroups.com.

Re: [weewx-user] Re: skin Belchertown " earth Quake"

That belchertown.py file is an old 1.2 version. The problem right now is 
that there are multiple Belchertown versions out there which all bear the 
version number 1.2. This is because at the moment changes are all merged 
into the Belchertown 1.2 master without changes to the version numbers.

My advice would be to upgrade your skin from the Belchertown repo with the 
latest "1.2". That way you are sure your skin will get updated with many 
new features and fixes including the earthquakedistance unit fix. If you 
choose to do this, make sure you backup your current skin.conf and 
graphs,conf files before your upgrade.

Op zaterdag 16 januari 2021 om 18:30:52 UTC+1 schreef sali...@gmail.com:

> I am come back with my origin version " release 1.2 of skin" , that works 
> well; but I have always the same error with eart quake.
>
> I join my belchertown.py file.
>
> thanks
>
> Patrick
> Le 16/01/2021 à 17:16, salinois a écrit :
>
> hi again me,
>
>  I found some errors from me but now I have others errors:
>
> Jan 16 17:10:29 raspberrypi weewx[18631] INFO user.belchertown: New 
> forecast file downloaded to 
> /var/www/html/weewx/belchertown/json/forecast.json
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: Caught 
> unrecoverable exception in generator 
> 'weewx.cheetahgenerator.CheetahGenerator'
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   'CheetahGenerator' object has no attribute 'group_unit_dict'
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   obj.start()
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   self.run()
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 149, in run
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   ngen = self.generate(gen_dict[section_name], self.gen_ts)
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in 
> generate
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   ngen += self.generate(section[subsection], gen_ts)
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in 
> generate
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   ngen += self.generate(section[subsection], gen_ts)
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 308, in 
> generate
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   default_binding)
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 379, in 
> _getSearchList
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   searchList += obj.get_extension_list(timespan, db_lookup)
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
> File "/usr/share/weewx/user/belchertown.py", line 1059, in 
> get_extension_list
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   distance_unit = self.generator.group_unit_dict["group_distance"]
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   AttributeError: 'CheetahGenerator' object has no attribute 
> 'group_unit_dict'
> Jan 16 17:10:29 raspberrypi weewx[18631] ERROR weewx.reportengine: 
>   Generator terminated
>
> I put for you my file "belchertown.py"
>
>
> Le 16/01/2021 à 17:01, salinois a écrit :
>
> hi, Arend,
>
> I am with skin belchertown 1.2.
>
> I done this modifications inside belchertown.py
>
> [
>
> *Additional context*
>
> Fixes:
>
> Changed in belchertown.py:
>
> distance_unit = converter.group_unit_dict["group_distance"]
>
> into
>
> distance_unit = self.generator.converter.group_unit_dict["group_distance"]
>
> And:
>
> eqdistance = eq_distance_round % eqdistance_bearing[0]
>
> into
>
> eqdistance = locale.format("%g", float(eq_distance_round % 
> eqdistance_bearing[0]) )
>
> And:
>
> eqmag = eqdata["features"][0]["properties"]["mag"]
>
> into
>
> eqmag = locale.format("%g", float(eqdata["features"][0]["properties"]["mag"]) 
> )
>
> And:
>
> eqmag =

Re: [weewx-user] aeris weather

I have been having similar errors for the last 10 hours. Something going on
at the PWSWeather site, I guess. This has happened before.

On Sat, Jan 16, 2021 at 9:44 AM sali...@gmail.com 
wrote:

>
> hi,
>
> I have this error "Jan 16 18:42:59 raspberrypi weewx[22190] ERROR
> weewx.restx: PWSWeather: Failed to publish record 2021-01-16 18:42:00 CET
> (1610818920): Failed upload after 3 tries"
>
> but when I connect me on the website with my login it is OK !
> an idea
>
> thanks
>
> Patrick
>
> --
> You received this message because you are subscribed to the Google 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/da0a9026-f926-42a6-98fd-7d1c1e820c52n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBscvNOXkzdxKUNg_pp-PpeyYntCqyWc1dweNLhB%3D0SfQ%40mail.gmail.com.

[weewx-user] Re: Netatmo station - help needed for read some observation

2021-01-16 Thread ve2se

Neowx  skin  works fine  with Netatmo 
translated in  french :  http://ve2se.noip.me:8008//weewx/index.html

Le samedi 16 janvier 2021 à 03 h 35 min 05 s UTC-5, johansso...@outlook.com 
a écrit :

>
> Now it works :) Many MANY thanks for you help and time you give me to fix 
> this!
>
> *Connectivity*
> WiFi Signal 58 dB
> Outdoor Module Signal 65 dB
> Anemometer Signal 67 dB
> Rain Gauge Signal 63 dB
>
> *Battery Status*
> Anemometer Battery 94%
> Rain Gauge Battery 100%
> Outdoor Module Battery 93%
> lördag 16 januari 2021 kl. 08:21:49 UTC+1 skrev gjr80:
>
>> Ah, that was my mistake, I deleted a few lines I should not have. Try 
>> this sensors.txt; same deal, download, rename and save as 
>> /etc/weewx/skins/Seasons/sensors.inc. No need to restart WeeWx this 
>> time, just wait for the report cycle to complete.
>>
>> Gary
>>
>> On Saturday, 16 January 2021 at 16:52:28 UTC+10 johansso...@outlook.com 
>> wrote:
>>
>>> i think it works now.
>>> I dont know what i did but i use the early sensor.inc code you gave me 
>>> and the readings is now this
>>>
>>> Connectivity
>>> WiFi Signal
>>> (57 dB)
>>> Outdoor Module Signal
>>> (66 dB)
>>> Anemometer Signal
>>> (69 dB)
>>> Rain Gauge Signal
>>> (62 dB)
>>>
>>> Battery Status
>>> Anemometer Battery
>>> (95%)
>>> Rain Gauge Battery
>>> (100%)
>>> Outdoor Module Battery
>>> (93%)
>>>
>>> lördag 16 januari 2021 kl. 07:35:56 UTC+1 skrev Rebecka Johansson:
>>>
 I do as you described :)

 But got errors after i replaced the new sensors.inc code

 The log error shows this

 "Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 Generate failed with exception ''
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
  Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
  Reason: #012#012Some #directives are missing their corresponding #end 
 ___ tag: if, if#012Line 153, column 7 in file 
 /etc/weewx/skins/Seasons/sensors.inc#012#012Line|Cheetah 
 Code#012|-#012150
  
 |  #012151 |#012152 |#012153 |#end if#012   ^
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   Traceback (most recent call last):
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in 
 generate
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   unicode_string = compiled_template.respond()
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "_etc_weewx_skins_Seasons_index_html_tmpl.py", line 225, in 
 respond
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
 1685, in _handleCheetahInclude
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   file=file)
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
 775, in compile
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   compiler.compile()
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/lib/python3/dist-packages/Cheetah/Compiler.py", line 
 1799, in compile
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   self._parser.parse()
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/lib/python3/dist-packages/Cheetah/Parser.py", line 
 1554, 
 in parse
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   self.assertEmptyOpenDirectivesStack()
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
 File "/usr/lib/python3/dist-packages/Cheetah/Parser.py", line 
 2778, 
 in assertEmptyOpenDirectivesStack
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   raise ParseError(self, msg=errorMsg)
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   Cheetah.Parser.ParseError: 
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   Some #directives are missing their corresponding #end ___ tag: if, if
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   Line 153, column 7 in file /etc/weewx/skins/Seasons/sensors.inc
 Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
   
 Jan 16 07:33:21 Raspi

[weewx-user] aeris weather

2021-01-16 Thread sali...@gmail.com


hi,

I have this error "Jan 16 18:42:59 raspberrypi weewx[22190] ERROR 
weewx.restx: PWSWeather: Failed to publish record 2021-01-16 18:42:00 CET 
(1610818920): Failed upload after 3 tries"

but when I connect me on the website with my login it is OK !
an idea

thanks

Patrick

-- 
You received this message because you are subscribed to the Google 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/da0a9026-f926-42a6-98fd-7d1c1e820c52n%40googlegroups.com.

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-16 Thread garrya...@gmail.com

I've added the mem extension.  My test station, with a large number of 
feeds selected, is at: https://lockyer.ca/weather/OsoyoosLakeNorthEast

mem graphs are at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem

Regards,

Garry

On Saturday, January 16, 2021 at 8:42:09 AM UTC-8 garrya...@gmail.com wrote:

> Brief Update: January 16, 2021:
>
> I've pretty much finished moving my extension to a service.
>
> I started WeeWX at about midnight and at about 8:20 AM, memory usage has 
> grown to over 941MB!  Allocated blocks was at 4,245,722.
>
> So growing memory usage problem exists.
>
> Bill indicated above he ran my test code on Ubuntu so I set up a Ubuntu 
> Raspberry Pi Desktop system:
>
> RPi 4 - 6 GB
> Ubuntu Raspberry Pi OS 20.10
> Python3 - 3.8.6
> WeeWX 4.3
> Belchertown 1.2
>
> Later today I intend to add the mem extension.  Will report back soonest!  
> I will also run things on Raspberrry Pi OS (but I have to build a new one!).
>
> Regards,
>
> Garry
> PS: I *think* I'm going to continue all development on Ubuntu as it seems 
> more current - it has a later linux kernel and more current Python - but 
> I'm not sure it's otherwise better than Raspberry Pi OS.  Both OS's have 
> wireless mouse lag problems, fixed somewhat by changing 'mousepoll' 
> setting.  Installation of Ubuntu was easy and I managed to get it to boot 
> from a USB SSD.  In the first 8 hours or so, Ubuntu froze a couple of 
> times, so now I keep an ssh session open so that I can reboot.
>
> On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com 
> wrote:
>
>> My experience is that when I recreate an include file for Belchertown on 
>> each archive cycle, as an extension to Belchertown or as a service, memory 
>> usage increases with each cycle and eventually errors start.  I’ve seen the 
>> error I reported in this string and unresponsive systems.  So, yes, I think 
>> there’s a problem.
>>
>> The memory test service I provided starts out at about 45 MB and 
>> increases at about 3 MB per cycle.  I’ve seen WeeWx memory usage grow to 
>> over 1 GB!
>>
>> I’m working on a new version of my extension, as a service, and will 
>> report back on its memory usage, hopefully within only a couple of days.
>>
>> Thanks for all your help!
>>
>>
>> Regards,
>>
>> Garry Lockyer
>> C: +1.250.689.0686 <(250)%20689-0686>
>> E: ga...@lockyer.ca
>>
>>
>> On Jan 9, 2021, at 19:11, vince  wrote:
>>
>> If your memory usage is stable, is there a problem ?
>>
>> It's pretty typical after a weewx startup for the usage to go up a bit 
>> then level off nicely.
>>
>> On Saturday, January 9, 2021 at 4:41:51 PM UTC-8 bell...@gmail.com wrote:
>>
>>> Garry,
>>> I ran your test extension for a bit in my Ubuntu VM.  Doesn't appear to 
>>> be leaking.
>>>  16:42:24 {'mem_size': 338.53515625, 'mem_rss': 32.953125, 'mem_share': 
>>> 11.28125}
>>>  16:47:38 {'mem_size': 423.80859375, 'mem_rss': 47.75, 'mem_share': 
>>> 11.796875}
>>>  16:52:53 {'mem_size': 424.4140625 <(424)%20414-0625>, 'mem_rss': 
>>> 48.2265625, 'mem_share': 11.796875}
>>>  16:57:24 {'mem_size': 426.46875, 'mem_rss': 50.19921875, 'mem_share': 
>>> 11.796875}
>>>  17:02:32 {'mem_size': 426.46875, 'mem_rss': 50.21875, 'mem_share': 
>>> 11.796875}
>>>  17:07:20 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>>> 11.796875}
>>>  17:12:27 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>>> 11.796875}
>>>  17:17:26 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>>> 11.796875}
>>>  17:22:24 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>>> 11.796875}
>>>  17:27:19 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
>>> 48.71875, 'mem_share': 11.796875}
>>>  17:32:27 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
>>> 48.71875, 'mem_share': 11.796875}
>>>  17:37:17 {'mem_size': 424.5859375 <(424)%20585-9375>, 'mem_rss': 
>>> 48.7109375, 'mem_share': 11.796875}
>>>  17:42:21 {'mem_size': 424.58203125, 'mem_rss': 48.70703125, 
>>> 'mem_share': 11.796875}
>>>  17:47:24 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>>> 11.796875}
>>>  17:52:21 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>>> 11.796875}
>>>  17:57:15 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
>>> 'mem_share': 11.796875}
>>>  18:02:11 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 
>>> 'mem_share': 11.796875}
>>>  18:07:13 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
>>> 11.796875}
>>>  18:12:14 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
>>> 11.796875}
>>>  18:17:12 {'mem_size': 425.21875, 'mem_rss': 49.4375, 'mem_share': 
>>> 11.796875}
>>>  18:22:10 {'mem_size': 425.09765625, 'mem_rss': 49.31640625, 
>>> 'mem_share': 11.796875}
>>>  18:27:13 {'mem_size': 425.0390625, 'mem_rss': 49.2578125, 'mem_share': 
>>> 11.796875}
>>>  18:32:15 {'mem_size': 425.0390625, 'mem_rss': 49.2578125, 'mem_share': 
>>> 11.796875}
>>>  18:37:15 {'mem_size': 425.03125, 'mem_rss': 49.25,

Re: [weewx-user] Re: Confusion installing Forecast

2021-01-16 Thread John Kline

As a general rule, downloading head on a github repository is not equivalent to 
getting the latest release.  Head may contain changes not yet released (and 
perhaps not yet fully tested).

In this case, you can see here:
https://github.com/chaunceygardiner/weewx-forecast/commits/master
that nothing was submitted after the latest release.  That is, in this case, 
they are the same.

> On Jan 16, 2021, at 8:28 AM, Kevin Davis  wrote:
> 
> 
> I think I'm tracking now.  From this fork: 
> https://github.com/chaunceygardiner/weewx-forecast
> 
> If I download weewx-forecast-master.zip from there, it is the latest release, 
> which in this case IS 3.4.0b11.
> 
> Had I needed a specific release, I can go to the Release link on the right 
> side. 
> 
> Sorry it took me a bit to get spun up. 
> 
> 
> 
> 
> 
> 
>> On Sat, Jan 16, 2021 at 5:29 AM John Kline  wrote:
>> What he was missing is that he was downloading head and not the release.
>> 
 On Jan 15, 2021, at 10:27 PM, gjr80  wrote:
 
>>> 
>>> OK, granted John's repo (the second repo link) refers to a different .zip 
>>> file name compared to Matthews repo (the WeeWX wiki linked repo), but the 
>>> name of the .zip file is not important, what is important is that the name 
>>> of the file that you get when you download the repo is the same as the file 
>>> you use to install with wee_extension. So if your downloaded file is 
>>> weewx-forecast.zip then that is what you use with wee_extension to install.
>>> 
>>> Gary
>>> 
 On Saturday, 16 January 2021 at 16:06:28 UTC+10 blu...@gmail.com wrote:
 The file provided by the Zip download on the fork Gary linked, 
 https://github.com/chaunceygardiner/weewx-forecast, is called 
 weewx-forecast-master.zip not weewx-forecast-3.4.0b11.zip
 
 What am I missing?
 
> On Fri, Jan 15, 2021 at 8:26 PM John Kline  wrote:
> Use the instructions in the second link Gary provided.
> 
> wee_extension --install weewx-forecast-3.4.0b11.zip
> 
> 
>>> On Jan 15, 2021, at 7:46 PM, Kevin Davis  wrote:
>>> 
>> 
>> I'm working off the branch you sent, but the one I initially was working 
>> off does ref the tgz not zip
>> 
>> 1) run the installer:
>> 
>> wee_extension --install weewx-forecast.tgz
>> 
>>> On Fri, Jan 15, 2021 at 7:37 PM gjr80  wrote:
>>> Yes, that is the repo I linked to in my previous post that is mentioned 
>>> in the WeeWX wiki. But as I said I see no mention there of .tgz only 
>>> .zip. The download instructions tell you how to get the zip and the 
>>> install instructions tell you how to install from it. But you probably 
>>> won’t have much success with that repo when it comes to running the 
>>> forecast extension, better to use the second repo I linked. The same 
>>> download/install instructions should work for the second repo.
>>> 
>>> Gary
>>> 
 On Saturday, 16 January 2021 at 13:22:47 UTC+10 blu...@gmail.com wrote:
 Oh ok! 
 
 I ended up on this git repo.
 
 https://github.com/matthewwall/weewx-forecast
 
> On Fri, Jan 15, 2021 at 7:04 PM gjr80  wrote:
> Hi,
> 
> You haven’t said what instructions on git you are following but as 
> far as I can tell the download and install instructions for the 
> forecasting extension in the WeeWX wiki only refer to .zip. That 
> being said there are some some issues (runtime not install) with the 
> forecasting extension in the wiki; however, I believe this fork is 
> working.
> 
> In terms of running install.py, it was never going to work, 
> install.py is meant to be called by wee_extension not executed 
> directly by the user.
> 
> Gary
> 
>>> On Saturday, 16 January 2021 at 12:49:53 UTC+10 blu...@gmail.com 
>>> wrote:
>>> I know I'm being dense, but the instructions on git for installing 
>>> forecast say to point at wee_extension @ weewx-forecast.tgz
>>> 
>>> Where do I get this file?  Only download option I see is for .zip.
>>> 
>>> And, if I do a git clone and run install.py manually, I get an 
>>> error.
>>> 
>>> Traceback (most recent call last):
>>>   File "install.py", line 5, in 
>>> from weecfg.extension import ExtensionInstaller
>>> ModuleNotFoundError: No module named 'weecfg'
>>> 
>> 
> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, 
> send an email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/9d19ba30-9561-4f40-a735-55f04466553an%40googlegroups.com.

[weewx-user] Re: Weewx upgrade 3.9.1 to 4.3.0 reports no more - Error generating report

2021-01-16 Thread sbar...@gmail.com

Fixed it by removing accented char ( à ) from comment in weewx.conf file.

On Saturday, January 16, 2021 at 12:07:59 PM UTC+1 sbar...@gmail.com wrote:

> Ok,
>
> I tried running as app and not as daemon, and I got the following stack 
> trace error :
> Exception in thread ReportThread:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
> self.run()
>   File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
> skin_dict = self._build_skin_dict(report)
>   File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
> _build_skin_dict
> merge_dict = 
> weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
> new_dict.main)
>   File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
> new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
> new_dict.main)
>   File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
> new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe0' in 
> position 9: ordinal not in range(128)
>
> Any idea where I should look to get this fixed?
>
> Thank you,
>
> On Saturday, January 16, 2021 at 10:24:31 AM UTC+1 sbar...@gmail.com 
> wrote:
>
>> Hello,
>>
>> I decided to upgrade my weewx this morning from 3.9.1 to 4.3.
>> I upgraded via webmin and resulted a in a default conf.
>>
>> I manually reapplied the conf from a backup, and now: 
>>   - data aquisition from SDR seems OK 
>>   - Wunderground reporting is OK
>>   - Station registry is OK
>>
>> But there does not seem to be any generated report.
>> My local website does not get updated
>> My remote website that was updated via FTP does not get updated either
>>
>> I set debug=1, and see it in the log startup  that it should be taken 
>> into account:
>>
>> However I see no error in the log, not any DEBUG message.
>>
>> Running on rapsbian 9.9 I used the pyhton2 package.
>>
>> Any hint as to were I may have messed up?
>>
>> Regards,
>>
>> Below is a part of the weewx log from start-up:
>> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Initializing weewx 
>> version 4.3.0
>> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Using Python 2.7.13 
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Locale is 
>> 'en_GB.UTF-8'
>> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Debug is 1
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Loading station 
>> type SDR (user.sdr)
>> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: driver version is 
>> 0.14rc1
>> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: sensor map is 
>> {u'windGust': u'wind_gust.0:*.OSWGR800Packet', u'windSpeed': 
>> u'wind_speed.0:*.OSWGR800Packet', u'windBatteryStatus': 
>> u'battery.0:*.OSWGR800Packet', u'windDir': u'wind_dir.0:*.OSWGR800Packet', 
>> u'outHumidity': u'humidity.1:*.OSTHGR810Packet', u'outTemp': 
>> u'temperature.1:*.OSTHGR810Packet', u'outTempBatteryStatus': 
>> u'battery.1:*.OSTHGR810Packet', u'rain_total': 
>> u'rain_total.0:*.OSPCR800Packet', u'rainBatteryStatus': 
>> u'battery.0:*.OSPCR800Packet', u'extraTemp1': 
>> u'temperature.1:14.RubicsonTempPacket', u'UV': 
>> u'uv_index.1:*.OSUV800Packet', u'pressure': 
>> u'pressure.1:*.OSBTHGN129Packet', u'inTemp': 
>> u'temperature.1:*.OSBTHGN129Packet', u'inHumidity': 
>> u'humidity.1:*.OSBTHGN129Packet', u'inTempBatteryStatus': 
>> u'battery.1:*.OSBTHGN129Packet'}
>> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: deltas is {'strikes': 
>> 'strikes_total', 'rain': 'rain_total'}
>> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: startup process 
>> '/usr/local/bin/rtl_433 -q -U'
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Jan 16 09:40:49 weatherpi kernel: [40068.515685] r820t 4-001a: destroying 
>> instance
>> Jan 16 09:40:49 weatherpi kernel: [40068.520517] dvb_usb_v2: 'Realtek 
>> RTL2832U reference design:1-1.4' successfully deinitialized and disconnected
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Archive will use 
>> data binding wx_binding
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Using archive 
>> interval of 60 seconds (specified in weewx configuration)
>> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: StationRegistry: 
>> Station will be

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-16 Thread garrya...@gmail.com

Brief Update: January 16, 2021:

I've pretty much finished moving my extension to a service.

I started WeeWX at about midnight and at about 8:20 AM, memory usage has 
grown to over 941MB!  Allocated blocks was at 4,245,722.

So growing memory usage problem exists.

Bill indicated above he ran my test code on Ubuntu so I set up a Ubuntu 
Raspberry Pi Desktop system:

RPi 4 - 6 GB
Ubuntu Raspberry Pi OS 20.10
Python3 - 3.8.6
WeeWX 4.3
Belchertown 1.2

Later today I intend to add the mem extension.  Will report back soonest!  
I will also run things on Raspberrry Pi OS (but I have to build a new one!).

Regards,

Garry
PS: I *think* I'm going to continue all development on Ubuntu as it seems 
more current - it has a later linux kernel and more current Python - but 
I'm not sure it's otherwise better than Raspberry Pi OS.  Both OS's have 
wireless mouse lag problems, fixed somewhat by changing 'mousepoll' 
setting.  Installation of Ubuntu was easy and I managed to get it to boot 
from a USB SSD.  In the first 8 hours or so, Ubuntu froze a couple of 
times, so now I keep an ssh session open so that I can reboot.

On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com wrote:

> My experience is that when I recreate an include file for Belchertown on 
> each archive cycle, as an extension to Belchertown or as a service, memory 
> usage increases with each cycle and eventually errors start.  I’ve seen the 
> error I reported in this string and unresponsive systems.  So, yes, I think 
> there’s a problem.
>
> The memory test service I provided starts out at about 45 MB and increases 
> at about 3 MB per cycle.  I’ve seen WeeWx memory usage grow to over 1 GB!
>
> I’m working on a new version of my extension, as a service, and will 
> report back on its memory usage, hopefully within only a couple of days.
>
> Thanks for all your help!
>
>
> Regards,
>
> Garry Lockyer
> C: +1.250.689.0686 <(250)%20689-0686>
> E: ga...@lockyer.ca
>
>
> On Jan 9, 2021, at 19:11, vince  wrote:
>
> If your memory usage is stable, is there a problem ?
>
> It's pretty typical after a weewx startup for the usage to go up a bit 
> then level off nicely.
>
> On Saturday, January 9, 2021 at 4:41:51 PM UTC-8 bell...@gmail.com wrote:
>
>> Garry,
>> I ran your test extension for a bit in my Ubuntu VM.  Doesn't appear to 
>> be leaking.
>>  16:42:24 {'mem_size': 338.53515625, 'mem_rss': 32.953125, 'mem_share': 
>> 11.28125}
>>  16:47:38 {'mem_size': 423.80859375, 'mem_rss': 47.75, 'mem_share': 
>> 11.796875}
>>  16:52:53 {'mem_size': 424.4140625 <(424)%20414-0625>, 'mem_rss': 
>> 48.2265625, 'mem_share': 11.796875}
>>  16:57:24 {'mem_size': 426.46875, 'mem_rss': 50.19921875, 'mem_share': 
>> 11.796875}
>>  17:02:32 {'mem_size': 426.46875, 'mem_rss': 50.21875, 'mem_share': 
>> 11.796875}
>>  17:07:20 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:12:27 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:17:26 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:22:24 {'mem_size': 427.1796875, 'mem_rss': 50.9921875, 'mem_share': 
>> 11.796875}
>>  17:27:19 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
>> 48.71875, 'mem_share': 11.796875}
>>  17:32:27 {'mem_size': 424.6640625 <(424)%20664-0625>, 'mem_rss': 
>> 48.71875, 'mem_share': 11.796875}
>>  17:37:17 {'mem_size': 424.5859375 <(424)%20585-9375>, 'mem_rss': 
>> 48.7109375, 'mem_share': 11.796875}
>>  17:42:21 {'mem_size': 424.58203125, 'mem_rss': 48.70703125, 'mem_share': 
>> 11.796875}
>>  17:47:24 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>> 11.796875}
>>  17:52:21 {'mem_size': 424.984375, 'mem_rss': 49.140625, 'mem_share': 
>> 11.796875}
>>  17:57:15 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 'mem_share': 
>> 11.796875}
>>  18:02:11 {'mem_size': 425.05078125, 'mem_rss': 49.26953125, 'mem_share': 
>> 11.796875}
>>  18:07:13 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
>> 11.796875}
>>  18:12:14 {'mem_size': 425.1171875, 'mem_rss': 49.3359375, 'mem_share': 
>> 11.796875}
>>  18:17:12 {'mem_size': 425.21875, 'mem_rss': 49.4375, 'mem_share': 
>> 11.796875}
>>  18:22:10 {'mem_size': 425.09765625, 'mem_rss': 49.31640625, 'mem_share': 
>> 11.796875}
>>  18:27:13 {'mem_size': 425.0390625, 'mem_rss': 49.2578125, 'mem_share': 
>> 11.796875}
>>  18:32:15 {'mem_size': 425.0390625, 'mem_rss': 49.2578125, 'mem_share': 
>> 11.796875}
>>  18:37:15 {'mem_size': 425.03125, 'mem_rss': 49.25, 'mem_share': 
>> 11.796875}
>>  18:42:24 {'mem_size': 425.01953125, 'mem_rss': 49.2578125, 'mem_share': 
>> 11.796875}
>>  18:47:14 {'mem_size': 425.0078125, 'mem_rss': 49.24609375, 'mem_share': 
>> 11.796875}
>>  18:52:13 {'mem_size': 425.0078125, 'mem_rss': 49.24609375, 'mem_share': 
>> 11.796875}
>>  18:57:15 {'mem_size': 425.61328125, 'mem_rss': 49.8515625, 'mem_share': 
>> 11.796875}
>>  19:02:19 {'mem_size': 425.0078125, 'mem_rss': 49.2734375,

Re: [weewx-user] Re: Confusion installing Forecast

2021-01-16 Thread Kevin Davis

I think I'm tracking now.  From this fork:
https://github.com/chaunceygardiner/weewx-forecast

If I download weewx-forecast-master.zip from there, it is the latest
release, which in this case IS 3.4.0b11.

Had I needed a specific release, I can go to the Release link on the right
side.

Sorry it took me a bit to get spun up.






On Sat, Jan 16, 2021 at 5:29 AM John Kline  wrote:

> What he was missing is that he was downloading head and not the release.
>
> On Jan 15, 2021, at 10:27 PM, gjr80  wrote:
>
> 
> OK, granted John's repo (the second repo link) refers to a different .zip
> file name compared to Matthews repo (the WeeWX wiki linked repo), but the
> name of the .zip file is not important, what is important is that the name
> of the file that you get when you download the repo is the same as the file
> you use to install with wee_extension. So if your downloaded file is
> weewx-forecast.zip then that is what you use with wee_extension to
> install.
>
> Gary
>
> On Saturday, 16 January 2021 at 16:06:28 UTC+10 blu...@gmail.com wrote:
>
>> The file provided by the Zip download on the fork Gary linked,
>> https://github.com/chaunceygardiner/weewx-forecast, is called
>> weewx-forecast-master.zip not weewx-forecast-3.4.0b11.zip
>>
>> What am I missing?
>>
>> On Fri, Jan 15, 2021 at 8:26 PM John Kline  wrote:
>>
>>> Use the instructions in the second link Gary provided.
>>>
>>>
>>> wee_extension --install weewx-forecast-3.4.0b11.zip
>>>
>>>
>>>
>>> On Jan 15, 2021, at 7:46 PM, Kevin Davis  wrote:
>>>
>>> 
>>> I'm working off the branch you sent, but the one I initially was working
>>> off does ref the tgz not zip
>>>
>>> 1) run the installer:
>>>
>>> wee_extension --install weewx-forecast.tgz
>>>
>>>
>>> On Fri, Jan 15, 2021 at 7:37 PM gjr80  wrote:
>>>
 Yes, that is the repo I linked to in my previous post that is mentioned
 in the WeeWX wiki. But as I said I see no mention there of .tgz only .zip.
 The download instructions
  tell you
 how to get the zip and the install instructions
  tell
 you how to install from it. But you probably won’t have much success with
 that repo when it comes to running the forecast extension, better to use
 the second repo I linked. The same download/install instructions should
 work for the second repo.

 Gary

 On Saturday, 16 January 2021 at 13:22:47 UTC+10 blu...@gmail.com wrote:

> Oh ok!
>
> I ended up on this git repo.
>
> https://github.com/matthewwall/weewx-forecast
>
> On Fri, Jan 15, 2021 at 7:04 PM gjr80  wrote:
>
>> Hi,
>>
>> You haven’t said what instructions on git you are following but as
>> far as I can tell the download
>>  and
>> install
>> 
>> instructions for the forecasting extension in the WeeWX wiki
>>  only refer to
>> .zip. That being said there are some some issues (runtime not install) 
>> with
>> the forecasting extension in the wiki; however, I believe this fork
>>  is working.
>>
>> In terms of running install.py, it was never going to work,
>> install.py is meant to be called by wee_extension not executed directly 
>> by
>> the user.
>>
>> Gary
>>
>> On Saturday, 16 January 2021 at 12:49:53 UTC+10 blu...@gmail.com
>> wrote:
>>
>>> I know I'm being dense, but the instructions on git for installing
>>> forecast say to point at wee_extension @ weewx-forecast.tgz
>>>
>>> Where do I get this file?  Only download option I see is for .zip.
>>>
>>> And, if I do a git clone and run install.py manually, I get an error.
>>>
>>> Traceback (most recent call last):
>>>   File "install.py", line 5, in 
>>> from weecfg.extension import ExtensionInstaller
>>> ModuleNotFoundError: No module named 'weecfg'
>>>
>>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/9d19ba30-9561-4f40-a735-55f04466553an%40googlegroups.com
>> 
>> .
>>
> --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to

Re: [weewx-user] Re: skin Belchertown " earth Quake"


hi, Arend,

I am with skin belchertown 1.2.

I done this modifications inside belchertown.py

[

*Additional context*

Fixes:

Changed in belchertown.py:

|distance_unit = converter.group_unit_dict["group_distance"] into 
distance_unit = self.generator.converter.group_unit_dict["group_distance"] |


And:

|eqdistance = eq_distance_round % eqdistance_bearing[0] into eqdistance 
= locale.format("%g", float(eq_distance_round % eqdistance_bearing[0]) ) |


And:

|eqmag = eqdata["features"][0]["properties"]["mag"] into eqmag = 
locale.format("%g", float(eqdata["features"][0]["properties"]["mag"]) ) |


And:

|eqmag = round(eqdata["features"][0]["properties"]["magnitude"],1) into 
eqmag = locale.format("%g", 
float(round(eqdata["features"][0]["properties"]["magnitude"],1)) ) |


After applying these changes:]

but I have some errors in logs:

Jan 16 16:55:21 raspberrypi weewx[17349] ERROR weewx.reportengine: 
Unable to instantiate generator 'user.belchert own.HighchartsJsonGenerator'
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   invalid syntax 
(belchertown.py,    line 1136)
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   Traceback (most recent call 
last   ):
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:     File "/usr/share/weewx/weewx/r 
eportengine.py", line 179, in run
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   obj = weeutil.weeutil.get_ob 
ject(generator)(
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:     File "/usr/share/weewx/weeutil 
/weeutil.py", line 1093, in get_object
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   mod = __import__(module)
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:     File "/usr/share/weewx/user/be 
lchertown.py", line 1136
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   elif self.generator.skin_dic 
t['Extras']['earthquake_server'] == "GeoNet":
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:  ^
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   SyntaxError: invalid syntax
Jan 16 16:55:21 raspberrypi weewx[17349] ERROR 
weewx.reportengine:   Generator ignored


Patrick

Le 16/01/2021 à 15:48, Arend a écrit :

Hi Patrick,

Can you upload the belchertown.py file you are currently using?

Regards, Arend

Op zaterdag 16 januari 2021 om 12:15:34 UTC+1 schreef sali...@gmail.com:

hello

I done that but it is always the same thing !!!

I don't understand before it was good

Patrick

Le 11/01/2021 à 04:00, Greg from Oz a écrit :

You just need to delete the earthquake.json file and it recreates
next cycle.

On Monday, 11 January 2021 at 13:55:46 UTC+11 pedal...@gmail.com
wrote:

Yeah, apparently I needed to wait for the next refresh. It is
functioning properly now.

Thanks for checking though.

On Sun, Jan 10, 2021, 1:56 PM Colin Larsen
 wrote:



I just looked at your site and the distance is in miles
as I would expect for the US. What part do you think is
buggy?

Colin

On Mon, 11 Jan 2021 at 03:48, John Mora
 wrote:

I am following these threads with interest as my
Belchertown "Earthquake" is working but not as I
desire it to work. The skin installed without a hitch
and is running but the Eathquake  distance is in km
instead of miles and I also tried to change the
earthquake_maxradiuskm setting from 1000 to 2000 and
the changes aren't being reflected in the output.

I've tried making changes to belchertown.py
(https://github.com/poblabs/weewx-belchertown/issues/422
)
and changing the skin.conf by setting the
belchertown_locale from auto to en_US.UTF-8 and doing
the locale-gen command to no avail.

I will continue to follow this thread hoping that
there is some final solution as to why the Earthquake
is "buggy". Thanks to all who post, you have been a
great help in trying to figure this anomaly out.

my site: http://weather.codetales.com





On Saturday, January 9, 2021 at 7:34:41 PM UTC-5 Greg
from Oz wrote:

Yes I did that to but it made no difference.

You can change the locale = (in the belchertown
skin.conf) to

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-16 Thread galfert

You have dug up quite an old thread. A lot has changed since. The 
recommendation now is to just acquire the Ecowitt GW1000 and use the WeeWX 
GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
doesn't talk to the display console...as it is its own console). You'll get 
a much nicer experience with the GW1000, which will also let you add extra 
sensors.
https://github.com/gjr80/weewx-gw1000

On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com wrote:

> were you able to get this to work in the end. can you share the weewx 
> details please
>
> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com wrote:
>
>> I see that weewx is said to support the FINE OFFSET WH2900 , I was 
>> wondering if anyone could share with me the protocol and port information 
>> that is in the driver? I
>>
>

-- 
You received this message because you are subscribed to the Google 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/362aa4d0-8128-4351-8213-36fd04d92505n%40googlegroups.com.

Re: [weewx-user] Re: skin Belchertown " earth Quake"

Hi Patrick,

Can you upload the belchertown.py file you are currently using?

Regards, Arend

Op zaterdag 16 januari 2021 om 12:15:34 UTC+1 schreef sali...@gmail.com:

> hello
>
> I done that but it is always the same thing !!!
>
> I don't understand before it was good
>
> Patrick
> Le 11/01/2021 à 04:00, Greg from Oz a écrit :
>
> You just need to delete the earthquake.json file and it recreates next 
> cycle.
>
> On Monday, 11 January 2021 at 13:55:46 UTC+11 pedal...@gmail.com wrote:
>
>> Yeah, apparently I needed to wait for the next refresh. It is functioning 
>> properly now. 
>>
>> Thanks for checking though. 
>>
>> On Sun, Jan 10, 2021, 1:56 PM Colin Larsen  wrote:
>>
>>>
>>>
>>> I just looked at your site and the distance is in miles as I would 
>>> expect for the US. What part do you think is buggy?
>>>
>>> Colin
>>>
>>> On Mon, 11 Jan 2021 at 03:48, John Mora  wrote:
>>>
 I am following these threads with interest as my Belchertown 
 "Earthquake" is working but not as I desire it to work. The skin installed 
 without a hitch and is running but the Eathquake  distance is in km 
 instead 
 of miles and I also tried to change the earthquake_maxradiuskm setting 
 from 
 1000 to 2000 and the changes aren't being reflected in the output.

 I've tried making changes to belchertown.py (
 https://github.com/poblabs/weewx-belchertown/issues/422) and changing 
 the skin.conf by setting the belchertown_locale from auto to en_US.UTF-8 
 and doing the locale-gen command to no avail.

 I will continue to follow this thread hoping that there is some final 
 solution as to why the Earthquake is "buggy". Thanks to all who post, you 
 have been a great help in trying to figure this anomaly out.

 my site: http://weather.codetales.com




 On Saturday, January 9, 2021 at 7:34:41 PM UTC-5 Greg from Oz wrote:

> Yes I did that to but it made no difference. 
>
> You can change the locale = (in the belchertown skin.conf) to 
> "*en_AU.UTF-8" 
> *and that works  but if you leave it as auto and do the regen then it 
> works as expected.
>
>
> On Sunday, 10 January 2021 at 10:12:38 UTC+11 colin@gmail.com 
> wrote:
>
>> My simple fix for this was to make sure that in weewx.conf (or 
>> skin.conf if you prefer) you have under the stanza
>>
>> [[belchertown]]
>> [[[units]]]
>> groups
>>
>> An entry that says 
>>
>> group_distance = km
>>
>>
>>
>> On Sun, 10 Jan 2021 at 11:12, Greg from Oz  wrote:
>>
>>> Run the command: locale 
>>>
>>> See if *LC_MEASUREMENT *is in your units
>>>
>>> If it is like this: *LC_MEASUREMENT="en_US.UTF-8" *the the 
>>> measurement units will be in US (miles)
>>>
>>> To regenerate all your locale settings run: *locale-gen*
>>>
>>> There is a lot of discussion here: 
>>> https://groups.google.com/g/weewx-user/c/BckKUHu2_DQ/m/30YJPrKkBwAJ
>>>
>>>
>>> On Sunday, 10 January 2021 at 06:48:26 UTC+11 sali...@gmail.com 
>>> wrote:
>>>
 hello,
 in which file, can I modify miles in kilometers.

 inside joint file

 thanks

 Patrick

 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, 
>>> send an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/06af1676-3a27-4989-945d-af379f5b1647n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/544e2f70-aecc-4199-87bd-f8cd0940d371n%40googlegroups.com
  
 
 .

>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/CACjxfUt9vbjdz4AYF-hNQ2BSHGGcK22BfrGX0uTLuHxkZ43Q8A%40mail.gmail.com
>>>  
>>>

Re: [weewx-user] Recording External Temperatures

2021-01-16 Thread Mike Revitt

Great idea Vince,

I used to use Virtual Box all the time but these days tend to spin up EC2 
hosts, but hadn't even thought of that for WeeWX testing, so definitely 
going to give that a go

And as I know a few have asked, I have finished documenting what I did here
https://www.cougar.eu.com/useful-guides/weewx-guides/rasberry-pi/add-ecowitt/index.html


On Friday, January 15, 2021 at 5:41:03 PM UTC vince wrote:

> On Friday, January 15, 2021 at 1:56:13 AM UTC-8 mi...@cougar.eu.com wrote:
>
>> One thing I am keen to try is using the config file to define the 
>> directory as you show above Vince, but that will have to wait till I have 
>> time to experiment on my "spare" raspberry Pi. Not trying that on my live 
>> system. So for the time being the directory is defined as a constant
>>
>>
> This is a good example of why running a virtualized weewx is great.   You 
> could spin up a quick Vagrant/VirtualBox VM using the Simulator driver and 
> add your draft extension to it.   No need for a spare pi.   Get everything 
> working and then add/update your custom code on your production (so to 
> speak) pi.
>
> My Vagrant configs for centos7/8, debian10, ubuntu1804/2004 are on GitHub 
>  if you wanted those for 
> either pre-packaged or setup.py variants.   The provisioner scripts can 
> also be used standalone to add weewx to a base os of that flavor.  Might be 
> worth a look.
>
>
>

-- 
You received this message because you are subscribed to the Google 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/32c47c25-3901-441c-8a85-9b62b5f7544fn%40googlegroups.com.

Re: [weewx-user] Re: Confusion installing Forecast

2021-01-16 Thread John Kline

What he was missing is that he was downloading head and not the release.

> On Jan 15, 2021, at 10:27 PM, gjr80  wrote:
> 
> 
> OK, granted John's repo (the second repo link) refers to a different .zip 
> file name compared to Matthews repo (the WeeWX wiki linked repo), but the 
> name of the .zip file is not important, what is important is that the name of 
> the file that you get when you download the repo is the same as the file you 
> use to install with wee_extension. So if your downloaded file is 
> weewx-forecast.zip then that is what you use with wee_extension to install.
> 
> Gary
> 
>> On Saturday, 16 January 2021 at 16:06:28 UTC+10 blu...@gmail.com wrote:
>> The file provided by the Zip download on the fork Gary linked, 
>> https://github.com/chaunceygardiner/weewx-forecast, is called 
>> weewx-forecast-master.zip not weewx-forecast-3.4.0b11.zip
>> 
>> What am I missing?
>> 
>>> On Fri, Jan 15, 2021 at 8:26 PM John Kline  wrote:
>>> Use the instructions in the second link Gary provided.
>>> 
>>> wee_extension --install weewx-forecast-3.4.0b11.zip
>>> 
>>> 
> On Jan 15, 2021, at 7:46 PM, Kevin Davis  wrote:
> 
 
 I'm working off the branch you sent, but the one I initially was working 
 off does ref the tgz not zip
 
 1) run the installer:
 
 wee_extension --install weewx-forecast.tgz
 
> On Fri, Jan 15, 2021 at 7:37 PM gjr80  wrote:
> Yes, that is the repo I linked to in my previous post that is mentioned 
> in the WeeWX wiki. But as I said I see no mention there of .tgz only 
> .zip. The download instructions tell you how to get the zip and the 
> install instructions tell you how to install from it. But you probably 
> won’t have much success with that repo when it comes to running the 
> forecast extension, better to use the second repo I linked. The same 
> download/install instructions should work for the second repo.
> 
> Gary
> 
>> On Saturday, 16 January 2021 at 13:22:47 UTC+10 blu...@gmail.com wrote:
>> Oh ok! 
>> 
>> I ended up on this git repo.
>> 
>> https://github.com/matthewwall/weewx-forecast
>> 
>>> On Fri, Jan 15, 2021 at 7:04 PM gjr80  wrote:
>>> Hi,
>>> 
>>> You haven’t said what instructions on git you are following but as far 
>>> as I can tell the download and install instructions for the forecasting 
>>> extension in the WeeWX wiki only refer to .zip. That being said there 
>>> are some some issues (runtime not install) with the forecasting 
>>> extension in the wiki; however, I believe this fork is working.
>>> 
>>> In terms of running install.py, it was never going to work, install.py 
>>> is meant to be called by wee_extension not executed directly by the 
>>> user.
>>> 
>>> Gary
>>> 
> On Saturday, 16 January 2021 at 12:49:53 UTC+10 blu...@gmail.com 
> wrote:
> I know I'm being dense, but the instructions on git for installing 
> forecast say to point at wee_extension @ weewx-forecast.tgz
> 
> Where do I get this file?  Only download option I see is for .zip.
> 
> And, if I do a git clone and run install.py manually, I get an error.
> 
> Traceback (most recent call last):
>   File "install.py", line 5, in 
> from weecfg.extension import ExtensionInstaller
> ModuleNotFoundError: No module named 'weecfg'
> 
 
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/9d19ba30-9561-4f40-a735-55f04466553an%40googlegroups.com.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/8faedb72-5b5c-4282-9190-3482eda163e6n%40googlegroups.com.
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/CAHiQ_B3ef6LO6_y8yNDtFXw7joJed68gA8tRQhpPu3pngtY9Kw%40mail.gmail.com.
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to weewx-user+...@googlegroups.com.
>> 
>>> To view

Re: [weewx-user] Re: skin Belchertown " earth Quake"

hello

I done that but it is always the same thing !!!

I don't understand before it was good

Patrick

Le 11/01/2021 à 04:00, Greg from Oz a écrit :
You just need to delete the earthquake.json file and it recreates next
cycle.

On Monday, 11 January 2021 at 13:55:46 UTC+11 pedal...@gmail.com wrote:

Yeah, apparently I needed to wait for the next refresh. It is
functioning properly now.

Thanks for checking though.

On Sun, Jan 10, 2021, 1:56 PM Colin Larsen
wrote:

I just looked at your site and the distance is in miles as I
would expect for the US. What part do you think is buggy?

Colin

On Mon, 11 Jan 2021 at 03:48, John Mora
wrote:

I am following these threads with interest as my
Belchertown "Earthquake" is working but not as I desire it
to work. The skin installed without a hitch and is running
but the Eathquake distance is in km instead of miles and
I also tried to change the earthquake_maxradiuskm setting
from 1000 to 2000 and the changes aren't being reflected
in the output.

I've tried making changes to belchertown.py
(https://github.com/poblabs/weewx-belchertown/issues/422
)
and changing the skin.conf by setting the
belchertown_locale from auto to en_US.UTF-8 and doing the
locale-gen command to no avail.

I will continue to follow this thread hoping that there is
some final solution as to why the Earthquake is "buggy".
Thanks to all who post, you have been a great help in
trying to figure this anomaly out.

my site: http://weather.codetales.com

On Saturday, January 9, 2021 at 7:34:41 PM UTC-5 Greg from
Oz wrote:

Yes I did that to but it made no difference.

You can change the locale = (in the belchertown
skin.conf) to "*en_AU.UTF-8" *and that works but if
you leave it as auto and do the regen then it works as
expected.

On Sunday, 10 January 2021 at 10:12:38 UTC+11
colin@gmail.com wrote:

My simple fix for this was to make sure that in
weewx.conf (or skin.conf if you prefer) you have
under the stanza

[[belchertown]]
[[[units]]]
groups

An entry that says

group_distance = km

On Sun, 10 Jan 2021 at 11:12, Greg from Oz
wrote:

Run the command: locale

See if *LC_MEASUREMENT *is in your units

If it is like this:
*LC_MEASUREMENT="en_US.UTF-8" *the the
measurement units will be in US (miles)

To regenerate all your locale settings run:
*locale-gen*
*
*
There is a lot of discussion here:

https://groups.google.com/g/weewx-user/c/BckKUHu2_DQ/m/30YJPrKkBwAJ

On Sunday, 10 January 2021 at 06:48:26 UTC+11
sali...@gmail.com wrote:

hello,
in which file, can I modify miles in
kilometers.

inside joint file

thanks

Patrick

--
You received this message because you are

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

https://groups.google.com/d/msgid/weewx-user/06af1676-3a27-4989-945d-af379f5b1647n%40googlegroups.com

--
You received this message because you are subscribed to

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

[weewx-user] Re: Weewx upgrade 3.9.1 to 4.3.0 reports no more - Error generating report

2021-01-16 Thread sbar...@gmail.com

Ok,

I tried running as app and not as daemon, and I got the following stack 
trace error :
Exception in thread ReportThread:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
  File "/usr/share/weewx/weewx/reportengine.py", line 141, in run
skin_dict = self._build_skin_dict(report)
  File "/usr/share/weewx/weewx/reportengine.py", line 249, in 
_build_skin_dict
merge_dict = 
weeutil.config.deep_copy(self.config_dict)['StdReport']['Defaults']
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 251, in deep_copy
new_value = deep_copy(old_value, new_dict, new_dict.depth+1, 
new_dict.main)
  File "/usr/share/weewx/weeutil/config.py", line 262, in deep_copy
new_dict.comments[entry] = [str(x) for x in old_dict.comments[entry]]
UnicodeEncodeError: 'ascii' codec can't encode character u'\xe0' in 
position 9: ordinal not in range(128)

Any idea where I should look to get this fixed?

Thank you,

On Saturday, January 16, 2021 at 10:24:31 AM UTC+1 sbar...@gmail.com wrote:

> Hello,
>
> I decided to upgrade my weewx this morning from 3.9.1 to 4.3.
> I upgraded via webmin and resulted a in a default conf.
>
> I manually reapplied the conf from a backup, and now: 
>   - data aquisition from SDR seems OK 
>   - Wunderground reporting is OK
>   - Station registry is OK
>
> But there does not seem to be any generated report.
> My local website does not get updated
> My remote website that was updated via FTP does not get updated either
>
> I set debug=1, and see it in the log startup  that it should be taken into 
> account:
>
> However I see no error in the log, not any DEBUG message.
>
> Running on rapsbian 9.9 I used the pyhton2 package.
>
> Any hint as to were I may have messed up?
>
> Regards,
>
> Below is a part of the weewx log from start-up:
> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Initializing weewx 
> version 4.3.0
> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Using Python 2.7.13 
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Locale is 
> 'en_GB.UTF-8'
> Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: PID file is 
> /var/run/weewx.pid
> Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Debug is 1
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Loading station 
> type SDR (user.sdr)
> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: driver version is 
> 0.14rc1
> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: sensor map is 
> {u'windGust': u'wind_gust.0:*.OSWGR800Packet', u'windSpeed': 
> u'wind_speed.0:*.OSWGR800Packet', u'windBatteryStatus': 
> u'battery.0:*.OSWGR800Packet', u'windDir': u'wind_dir.0:*.OSWGR800Packet', 
> u'outHumidity': u'humidity.1:*.OSTHGR810Packet', u'outTemp': 
> u'temperature.1:*.OSTHGR810Packet', u'outTempBatteryStatus': 
> u'battery.1:*.OSTHGR810Packet', u'rain_total': 
> u'rain_total.0:*.OSPCR800Packet', u'rainBatteryStatus': 
> u'battery.0:*.OSPCR800Packet', u'extraTemp1': 
> u'temperature.1:14.RubicsonTempPacket', u'UV': 
> u'uv_index.1:*.OSUV800Packet', u'pressure': 
> u'pressure.1:*.OSBTHGN129Packet', u'inTemp': 
> u'temperature.1:*.OSBTHGN129Packet', u'inHumidity': 
> u'humidity.1:*.OSBTHGN129Packet', u'inTempBatteryStatus': 
> u'battery.1:*.OSBTHGN129Packet'}
> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: deltas is {'strikes': 
> 'strikes_total', 'rain': 'rain_total'}
> Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: startup process 
> '/usr/local/bin/rtl_433 -q -U'
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Jan 16 09:40:49 weatherpi kernel: [40068.515685] r820t 4-001a: destroying 
> instance
> Jan 16 09:40:49 weatherpi kernel: [40068.520517] dvb_usb_v2: 'Realtek 
> RTL2832U reference design:1-1.4' successfully deinitialized and disconnected
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Archive will use 
> data binding wx_binding
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Record generation 
> will be attempted in 'hardware'
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Using archive 
> interval of 60 seconds (specified in weewx configuration)
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: StationRegistry: 
> Station will be registered.
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: Wunderground-PWS: 
> Data for station IRHNEALP38 will be posted
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: PWSweather: 
> Posting not enabled.
> Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: CWOP:

[weewx-user] Weewx upgrade 3.9.1 to 4.3.0 reports no more :(

2021-01-16 Thread sbar...@gmail.com

Hello,

I decided to upgrade my weewx this morning from 3.9.1 to 4.3.
I upgraded via webmin and resulted a in a default conf.

I manually reapplied the conf from a backup, and now: 
  - data aquisition from SDR seems OK 
  - Wunderground reporting is OK
  - Station registry is OK

But there does not seem to be any generated report.
My local website does not get updated
My remote website that was updated via FTP does not get updated either

I set debug=1, and see it in the log startup  that it should be taken into 
account:

However I see no error in the log, not any DEBUG message.

Running on rapsbian 9.9 I used the pyhton2 package.

Any hint as to were I may have messed up?

Regards,

Below is a part of the weewx log from start-up:
Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Initializing weewx 
version 4.3.0
Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Using Python 2.7.13 
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: Locale is 'en_GB.UTF-8'
Jan 16 09:40:48 weatherpi weewx[2920] INFO __main__: PID file is 
/var/run/weewx.pid
Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Debug is 1
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Loading station 
type SDR (user.sdr)
Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: driver version is 0.14rc1
Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: sensor map is 
{u'windGust': u'wind_gust.0:*.OSWGR800Packet', u'windSpeed': 
u'wind_speed.0:*.OSWGR800Packet', u'windBatteryStatus': 
u'battery.0:*.OSWGR800Packet', u'windDir': u'wind_dir.0:*.OSWGR800Packet', 
u'outHumidity': u'humidity.1:*.OSTHGR810Packet', u'outTemp': 
u'temperature.1:*.OSTHGR810Packet', u'outTempBatteryStatus': 
u'battery.1:*.OSTHGR810Packet', u'rain_total': 
u'rain_total.0:*.OSPCR800Packet', u'rainBatteryStatus': 
u'battery.0:*.OSPCR800Packet', u'extraTemp1': 
u'temperature.1:14.RubicsonTempPacket', u'UV': 
u'uv_index.1:*.OSUV800Packet', u'pressure': 
u'pressure.1:*.OSBTHGN129Packet', u'inTemp': 
u'temperature.1:*.OSBTHGN129Packet', u'inHumidity': 
u'humidity.1:*.OSBTHGN129Packet', u'inTempBatteryStatus': 
u'battery.1:*.OSBTHGN129Packet'}
Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: deltas is {'strikes': 
'strikes_total', 'rain': 'rain_total'}
Jan 16 09:40:49 weatherpi weewxd: sdr: MainThread: startup process 
'/usr/local/bin/rtl_433 -q -U'
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: StdConvert target 
unit is 0x1
Jan 16 09:40:49 weatherpi kernel: [40068.515685] r820t 4-001a: destroying 
instance
Jan 16 09:40:49 weatherpi kernel: [40068.520517] dvb_usb_v2: 'Realtek 
RTL2832U reference design:1-1.4' successfully deinitialized and disconnected
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Archive will use 
data binding wx_binding
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Using archive 
interval of 60 seconds (specified in weewx configuration)
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: StationRegistry: 
Station will be registered.
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: Wunderground-PWS: 
Data for station IRHNEALP38 will be posted
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: PWSweather: Posting 
not enabled.
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: CWOP: Posting not 
enabled.
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: WOW: Posting not 
enabled.
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.restx: AWEKAS: Posting not 
enabled.
Jan 16 09:40:49 weatherpi weewx[2934] INFO __main__: Starting up weewx 
version 4.3.0
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx'
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.manager: Starting backfill 
of daily summaries
Jan 16 09:40:49 weatherpi weewx[2934] INFO weewx.engine: Starting main 
packet loop.
Jan 16 09:40:52 weatherpi weewxd: sdr: MainThread: unparsed: []


-- 
You received this message because you are subscribed to the Google 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/7f79653b-90ea-4801-94ab-d783888e9a54n%40googlegroups.com.

[weewx-user] Re: Netatmo station - help needed for read some observation

2021-01-16 Thread Rebecka Johansson


Now it works :) Many MANY thanks for you help and time you give me to fix 
this!

*Connectivity*
WiFi Signal 58 dB
Outdoor Module Signal 65 dB
Anemometer Signal 67 dB
Rain Gauge Signal 63 dB

*Battery Status*
Anemometer Battery 94%
Rain Gauge Battery 100%
Outdoor Module Battery 93%
lördag 16 januari 2021 kl. 08:21:49 UTC+1 skrev gjr80:

> Ah, that was my mistake, I deleted a few lines I should not have. Try this 
> sensors.txt; same deal, download, rename and save as 
> /etc/weewx/skins/Seasons/sensors.inc. No need to restart WeeWx this time, 
> just wait for the report cycle to complete.
>
> Gary
>
> On Saturday, 16 January 2021 at 16:52:28 UTC+10 johansso...@outlook.com 
> wrote:
>
>> i think it works now.
>> I dont know what i did but i use the early sensor.inc code you gave me 
>> and the readings is now this
>>
>> Connectivity
>> WiFi Signal
>> (57 dB)
>> Outdoor Module Signal
>> (66 dB)
>> Anemometer Signal
>> (69 dB)
>> Rain Gauge Signal
>> (62 dB)
>>
>> Battery Status
>> Anemometer Battery
>> (95%)
>> Rain Gauge Battery
>> (100%)
>> Outdoor Module Battery
>> (93%)
>>
>> lördag 16 januari 2021 kl. 07:35:56 UTC+1 skrev Rebecka Johansson:
>>
>>> I do as you described :)
>>>
>>> But got errors after i replaced the new sensors.inc code
>>>
>>> The log error shows this
>>>
>>> "Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> Generate failed with exception ''
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>  Ignoring template /etc/weewx/skins/Seasons/index.html.tmpl
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>  Reason: #012#012Some #directives are missing their corresponding #end 
>>> ___ tag: if, if#012Line 153, column 7 in file 
>>> /etc/weewx/skins/Seasons/sensors.inc#012#012Line|Cheetah 
>>> Code#012|-#012150
>>>  
>>> |  #012151 |#012152 |#012153 |#end if#012   ^
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   Traceback (most recent call last):
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 323, in 
>>> generate
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   unicode_string = compiled_template.respond()
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "_etc_weewx_skins_Seasons_index_html_tmpl.py", line 225, in 
>>> respond
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>>> 1685, in _handleCheetahInclude
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   file=file)
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 
>>> 775, in compile
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   compiler.compile()
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/lib/python3/dist-packages/Cheetah/Compiler.py", line 
>>> 1799, in compile
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   self._parser.parse()
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/lib/python3/dist-packages/Cheetah/Parser.py", line 1554, 
>>> in parse
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   self.assertEmptyOpenDirectivesStack()
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>> File "/usr/lib/python3/dist-packages/Cheetah/Parser.py", line 2778, 
>>> in assertEmptyOpenDirectivesStack
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   raise ParseError(self, msg=errorMsg)
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   Cheetah.Parser.ParseError: 
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   Some #directives are missing their corresponding #end ___ tag: if, if
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   Line 153, column 7 in file /etc/weewx/skins/Seasons/sensors.inc
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   Line|Cheetah Code
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   |-
>>> Jan 16 07:33:21 Raspi wee_reports[12432] ERROR weewx.cheetahgenerator: 
>>>   150 |  
>>> Jan 16

Re: [weewx-user] Re: Belchertown 1.2 and Danish Charaters