[weewx-user] aqi_backfill gives error

[Rahul Bedi]

Hi,

I tried running the "aqi_backfill" script which is part of the aqi 
extension on a weewx 4.1.1 install and get the following error.

Looks like way to pull the config seems to have changes since the time this 
script was written.

Any ideas?

- Rahul


pi@PrideWeatherStation:/usr/share/weewx $ sudo ./aqi_backfill weewx.conf
Traceback (most recent call last):
  File "./aqi_backfill", line 34, in 
config = weewx.engine.getConfiguration(args.config_file)
AttributeError: 'module' object has no attribute 'getConfiguration'



pi@PrideWeatherStation:/usr/share/weewx $ sudo ./aqi_backfill 
/etc/weewx/weewx.conf
Traceback (most recent call last):
  File "./aqi_backfill", line 34, in 
config = weewx.engine.getConfiguration(args.config_file)
AttributeError: 'module' object has no attribute 'getConfiguration'

-- 
You received this message because you are subscribed 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/1a24a46a-c69f-47d9-90da-c8e0222a2e09o%40googlegroups.com.

Re: [weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[Constantine Samaklis]

Thanks Gary. I have an application that reads the console values which are
pushed to a Mosquitto MQTT server in real time so this will address the
issue until the update is out.

On Wed, Jul 1, 2020 at 01:20 gjr80  wrote:

> Just to close this off I installed the updated vantage driver on my system
> and sunrise/sunset from the console is spot on today. If the anomaly
> bothers you and you can't wait for 4.1.2 to be released you can download
> the patched vantage driver here
> .
> Just use
>
> $ wget -P /var/tmp https://
> raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
>
> to download to /var/tmp and then copy in place of the existing driver (
> /home/weewx/bin/weewx/drivers/vantage.py or
> /usr/share/weewx/weewx/drivers/vantage.py) and restart WeeWX. You will
> need to run WeeWX directly and observer the sunrise/sunset values in the
> loop packets or use some other means to view the loop data as WeeWX does
> not normally display/use the console provided sunrise/sunset times.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/5IZfZge3RxU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/672bf2e7-4403-47d9-8bef-5a763ae618f1o%40googlegroups.com
> 
> .
>

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

[weewx-user] Weewx 4.1 or later mqtt client

[gjr80]

Hi,

The mqtt uploader on the wiki home page (https://github.com/weewx/weewx/wiki) 
has a green tick next to it indicating it will work under WeeWX v4 and python 3 
(and I believe python 2).

Gary

-- 
You received this message because you are subscribed 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/9d7e41f6-3b6a-448e-9027-e2159b528726o%40googlegroups.com.

[weewx-user] Re: Sunrise/Sunset times off on Vantage Pro 2

[Constantine Samaklis]

Thanks for taking the time and putting in the effort to troubleshoot.

On Tuesday, June 30, 2020 at 8:47:25 AM UTC-4, Jacques Terrettaz wrote:
>
> HI,
>
> I checked with my Davis station and I am observing exactly the same kind 
> of differences. I think the problem is coming from the vantage weewx driver 
> :
>
> Here are my data concerning sunrise :
>
>- the console displays 05:46 for sunrise. This is correct
>- the raw loop data for sunrise, as received by Weewx , is 546 
>- weewx vantage driver is converting the raw loop data into seconds 
>using this function 
>'sunrise' : lambda p, k: 3600 * (p[k] / 100) + 60 * (p[k] % 100
>),
> giving :  3600 * (546/100) + 60 * 46 =* 22416*.   This is wrong, it 
>should be 3600 * (*500*/100) + 60 * 46 = *20760*
>
> Should the right formulas be :
> 'sunrise' : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
> 'sunset'  : lambda p, k: 3600 * (p[k] // 100) + 60 * (p[k] % 100),
>
>
> ?
>
>
> Le mardi 30 juin 2020 13:03:37 UTC+2, Constantine Samaklis a écrit :
>>
>> I did what you suggested (settings where fine to begin with) but still 
>> getting 20min discrepancies which are not explained by the loss of accuracy 
>> on the lon/lat.
>>
>> Wondering what to try next.
>>
>> On Tuesday, June 30, 2020 at 6:44:53 AM UTC-4, gjr80 wrote:
>>>
>>> No problems, it's just that sunrise/sunset can come from up to three 
>>> different sources and you need to to know which source is the problem in 
>>> order to troubleshoot.
>>>
>>> You are right that the sunrise/sunset in loop packets comes from the 
>>> console.  So in this case pyephem does not come into play nor does the 
>>> lat/long settings in weewx.conf. You need to check/set the lat/long 
>>> settings in your console, either via the console buttons or through use of 
>>> the wee_device  
>>> utility (note the if using wee_device you need to stop WeeWX first). From 
>>> memory the console (via buttons or wee_device) accepts decimal degrees with 
>>> a max resolution of 0.1 degree. Not sure a 0.1 degree resolution should 
>>> result in an inaccuracy of 20+ minutes though. 
>>>
>>> Gary
>>>
>>> On Tuesday, 30 June 2020 20:19:21 UTC+10, Constantine Samaklis wrote:

 My bad, I should have been more thorough with details. I was under the 
 impression that the sunrise/sunset times were provided directly by the 
 Davis console and not calculated.

 The values I am getting are coming from the LOOP when running weewxd

 LOOP:   2020-06-30 06:07:56 EDT (1593511676) altimeter: 
 29.887106231687923, barometer: 29.88, cloudbase: 1238.2237428350452, 
 consBatteryVoltage: 3.75, dateTime: 1593511676, dayET: 0.0, dayRain: 0.0, 
 dewpoint: 64.5434155315258, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 
 0, 
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
 extraAlarm8: 0, forecastIcon: 6, forecastRule: 45, heatindex: 69.6, 
 inDewpoint: 45.1326136300073, inHumidity: 53.0, insideAlarm: 0, inTemp: 
 62.5, leafWet4: 0.0, monthET: 0.0, monthRain: 1.89, outHumidity: 84.0, 
 outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 69.6, pressure: 
 29.788405301826174, rain: 0.0, rainAlarm: 0, rainRate: 0.0, 
 soilLeafAlarm1: 
 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 
 0.0, 
 sunrise: 1593510480.0, sunset: 1593564480.0, txBatteryStatus: 0, 
 usUnits: 1, windchill: 69.6, windDir: None, windGust: 0.0, windGustDir: 
 None, windSpeed: 0.0, windSpeed10: 1.0, yearET: 0.0, yearRain: 14.08

 I do have the following version of ephem: python3-ephem 
3.7.6.0-7+b1 

 Weewx is running on Python 3.7 

 # Latitude and longitude in decimal degrees
 latitude = 40.624573
 longitude = -74.012931

 On Monday, June 29, 2020 at 10:23:36 PM UTC-4, gjr80 wrote:
>
> Hi,
>
> I think we need to sort the apples from the oranges and bananas. 
> Exactly what are you showing us? Is that the sunrise/sunset times as 
> displayed on the console or as displayed in loop packet/archive record or 
> as returned by a tag in a report? What latitude/longitude do you have set 
> in your console and in weewx.conf? Do you have pyephem installed for 
> the version of python that WeeWX is being run under?
>
> Sorry for the questions, but it's a bit like the 'pressures'; there 
> are a number of moving parts to this and unless you know exactly what is 
> being looked at it is hard to give a meaningful answer.
>
> Gary
>
>
>
>
> On Tuesday, 30 June 2020 11:16:33 UTC+10, Constantine Samaklis wrote:
>>
>> Wondering if anyone is having the same issue. In the last 3-4 days my 
>> Vantage pro is showing the wrong sunrise and sunset times. I am in NY 
>> and 
>> the console is set to 

Re: [weewx-user] Decimal comma in xml files bug?

[Tom Keffer]

WeeWX formats numbers using Python's locale.format() facility, which
typically uses your "default" locale. In your case, that locale must use
commas as the decimal separator.

To change, either change your locale with environment variable LANG
 to
something that uses periods as decimal separators, or override the
formatting.

To override the formatting, set option localize to False:

$current.outTemp.format(localize=False)

-tk





On Tue, Jun 30, 2020 at 10:41 PM Michael Meyer  wrote:

> Hello, I'm running weewx 4.1.1 on Rpi 3b installed with setup.py.  To get
> a clean installation I installed buster from scratch.
> Before I had installed version 3xxx on the same Rpi with Jessie running.
> With a xml.tmpl I grabed the datas to work with them on my smart home
> system Domoticz.
> With the new installation a problem popped up. The xml file have decimal
> comma instead of decimal points. It's not just my template is also eg.
> /home/weewx/public_html/rss.xml.
> As I read in www decimal point for xml is necessary. My question is it a
> bug or is there something wrong within my system what I can change.
> Any help appreciate
> Michael
>
> --
> You received this message because you are subscribed 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/2544a5c5-d34d-426d-b5ad-d544cc5b6792n%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/CAPq0zEDPZJOYwr4UnxKb5Q-NjH%2BBDh4N2vV2bGPKMnmi-ovY9A%40mail.gmail.com.

Re: [weewx-user] Decimal comma in xml files bug?

[Michael Meyer]

Got it thanks.

tke...@gmail.com schrieb am Mittwoch, 1. Juli 2020 um 14:15:28 UTC+2:

> WeeWX formats numbers using Python's locale.format() facility, which 
> typically uses your "default" locale. In your case, that locale must use 
> commas as the decimal separator. 
>
> To change, either change your locale with environment variable LANG 
>  to 
> something that uses periods as decimal separators, or override the 
> formatting.
>
> To override the formatting, set option localize to False:
>
> $current.outTemp.format(localize=False)
>
> -tk
>
>
>
>
>
> On Tue, Jun 30, 2020 at 10:41 PM Michael Meyer  wrote:
>
>> Hello, I'm running weewx 4.1.1 on Rpi 3b installed with setup.py.  To get 
>> a clean installation I installed buster from scratch. 
>> Before I had installed version 3xxx on the same Rpi with Jessie running.
>> With a xml.tmpl I grabed the datas to work with them on my smart home 
>> system Domoticz.
>> With the new installation a problem popped up. The xml file have decimal 
>> comma instead of decimal points. It's not just my template is also eg. 
>> /home/weewx/public_html/rss.xml.
>> As I read in www decimal point for xml is necessary. My question is it a 
>> bug or is there something wrong within my system what I can change.
>> Any help appreciate
>> Michael
>>
>> -- 
>> You received this message because you are subscribed 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/2544a5c5-d34d-426d-b5ad-d544cc5b6792n%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/c011df9b-3c98-48c0-9de7-5a9b88b1d571n%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

@John: This is the error message, where do I have to search?

reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>

complete line:
Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
[['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
[sender] io timeout after 1 seconds -- exiting. rsync error: timeout in 
data send/receive (code 30) at io.c(204) [sender=3.1.3]


Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>
> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
> int.
>
> I didn’t catch this as I was not specifying a port.  This should now be 
> fixed in 1.3.1.  Would you please give it a try?
>
> On Jun 30, 2020, at 1:32 AM, Geni 0815 > 
> wrote:
>
> 
>>
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>>
>> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>>
>> @John: I have the following entry in the syslog, what is not suitable?
>>
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> barometer_rate_secs: 10800
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_secs : 86400
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_points   : 16
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   Traceback (most recent call last):
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.compose_and_write_packet(pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>>> compose_and_write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.write_packet(selective_pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.rsync_data(pkt['dateTime'])
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   rsync_upload.run()
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   if self.port is not None and len(self.port.strip()) > 0:
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   AttributeError: 'int' object has no attribute 'strip'
>>>
>>> [image: belch09.jpg]
>>  
>>
>> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>>
>>> I just now updated this extension to 1.1.  I would try it before 
>>> resorting to a clean install.
>>>
>>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  

[weewx-user] Re: Wmr200: read_device() USB Error Reason:[Errno 110] Operation timed out

[Jason Ingraham]

Heres my log : 

Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Finished loading 
service weewx.restx.StdAWEKAS
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Loading service 
weewx.engine.StdPrint
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdPrint
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Loading service 
weewx.engine.StdReport
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Finished loading 
service weewx.engine.StdReport
Jul  1 11:19:37 WxPI weewx[1949] INFO __main__: Starting up weewx version 
4.1.1
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.engine: Station does not 
support reading the time
Jul  1 11:19:37 WxPI weewx[1949] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jul  1 11:19:37 WxPI weewx[1949] INFO weewx.manager: Starting backfill of 
daily summaries
Jul  1 11:19:37 WxPI weewx[1949] DEBUG weewx.manager: Daily summary version 
is 2.0
Jul  1 11:19:52 WxPI weewx[1949] ERROR weewx.drivers.wmr200: read_device() 
USB Error Reason:[Errno 110] Operation timed out
Jul  1 11:19:52 WxPI weewx[1949] ERROR weewx.drivers.wmr200: USB device 
read error
Jul  1 11:20:02 WxPI weewx[1949] INFO weewx.manager: Processed 1363 records 
to backfill 2 day summaries in 25.04 seconds
Jul  1 11:20:02 WxPI weewx[1949] DEBUG weewx.drivers.wmr200: genStartup() 
phase getting archive packets since 2020-07-01 00:02:00 ADT (1593572520)
Jul  1 11:20:02 WxPI weewx[1949] ERROR weewx.drivers.wmr200: USB polling 
thread unexpectedly terminated
Jul  1 11:20:02 WxPI weewx[1949] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Jul  1 11:20:02 WxPI weewx[1949] DEBUG weewx.restx: Shut down 
Wunderground-PWS thread.
Jul  1 11:20:02 WxPI weewx[1949] INFO weewx.drivers.wmr200: USB polling 
thread expired
Jul  1 11:20:02 WxPI weewx[1949] CRITICAL __main__: Caught WeeWxIOError: 
USB polling thread unexpectedly terminated
Jul  1 11:20:02 WxPI weewx[1949] CRITICAL __main__:   Waiting 60 
seconds then retrying...
Jul  1 11:21:02 WxPI weewx[1949] INFO __main__: retrying...
Jul  1 11:21:02 WxPI weewx[1949] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Jul  1 11:21:02 WxPI weewx[1949] INFO __main__: Debug is 1
Jul  1 11:21:02 WxPI weewx[1949] DEBUG __main__: Initializing engine
Jul  1 11:21:02 WxPI weewx[1949] INFO weewx.engine: Loading station type 
WMR200 (weewx.drivers.wmr200)
Jul  1 11:21:02 WxPI weewx[1949] INFO weewx.drivers.wmr200: driver version 
is 3.5.0
Jul  1 11:21:02 WxPI weewx[1949] INFO weewx.drivers.wmr200: sensor map is 
{'altimeter': 'altimeter', 'pressure': 'pressure', 'windSpeed': 
'wind_speed', 'windDir': 'wind_dir', 'windGust': 'wind_gust', 
'windBatteryStatus': 'battery_status_wind', 'inTemp': 'temperature_0', 
'outTemp': 'temperature_1', 'extraTemp1': 'temperature_2', 'extraTemp2': 
'temperature_3', 'extraTemp3': 'temperature_4', 'extraTemp4': 
'temperature_5', 'extraTemp5': 'temperature_6', 'extraTemp6': 
'temperature_7', 'extraTemp7': 'temperature_8', 'inHumidity': 'humidity_0', 
'outHumidity': 'humidity_1', 'extraHumid1': 'humidity_2', 'extraHumid2': 
'humidity_3', 'extraHumid3': 'humidity_4', 'extraHumid4': 'humidity_5', 
'extraHumid5': 'humidity_6', 'extraHumid6': 'humidity_7', 'extraHumid7': 
'humidity_8', 'inHeatindex': 'heatindex_0', 'heatindex': 'heatindex_1', 
'heatindex1': 'heatindex_2', 'heatindex2': 'heatindex_3', 'heatindex3': 
'heatindex_4', 'heatindex4': 'heatindex_5', 'heatindex5': 'heatindex_6', 
'heatindex6': 'heatindex_7', 'heatindex7': 'heatindex_8', 
'outTempBatteryStatus': 'battery_status_out', 'rain': 'rain', 'rainTotal': 
'rain_total', 'rainRate': 'rain_rate', 'hourRain': 'rain_hour', 'rain24': 
'rain_24', 'rainBatteryStatus': 'battery_status_rain', 'UV': 'uv', 
'uvBatteryStatus': 'battery_status_uv', 'windchill': 'windchill', 
'forecastIcon': 'forecast_icon', 'outTempFault': 'out_fault', 'windFault': 
'wind_fault', 'uvFault': 'uv_fault', 'rainFault': 'rain_fault', 
'clockUnsynchronized': 'clock_unsynchronized'}
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.drivers.wmr200: 
open_device() Unable to claim USB interface. Reason: [Errno 16] Resource 
busy
Jul  1 11:21:02 WxPI weewx[1949] ERROR weewx.engine: Import of driver 
failed: [Errno 16] Resource busy ()
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine:   Traceback 
(most recent call last):
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/wmr200.py", line 193, in open_device
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine:   
self.handle.claimInterface(self.interface)
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine: File 
"/usr/lib/python3/dist-packages/usb/legacy.py", line 230, in claimInterface
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine:   
util.claim_interface(self.dev, interface)
Jul  1 11:21:02 WxPI weewx[1949] CRITICAL weewx.engine: File 

[weewx-user] Re: Wmr200: read_device() USB Error Reason:[Errno 110] Operation timed out

[Jason Ingraham]

I'm getting the same error here as well with my WMR200 and Rpi


On Saturday, 20 June 2020 08:06:10 UTC-3, Alessandro wrote:
>
> Hello all,
> firstly thanks so much for your work!
>
> As newbie, I'm having a problem running Weewx on Raspi 4 and Wmr200 as 
> weather station.
>
> I installed weewx 3 days ago, and already I have received the error 
> (attached below) twice, that has blocked weewx.
>
> I have solved rebooting the Raspi, but I hope there is a smarter solution. 
> Now I have also changed the usb cable...
>
>
> Some infomation:
> Raspbian version:
> PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="10"
> VERSION="10 (buster)"
> VERSION_CODENAME=buster
>
> Weewx version:
> Weewx version 4.1.1
> Installed following http://www.weewx.com/docs/debian.htm
>
> Thanks for any hints,
> Alessandro
>
> Jun 20 06:44:21 raspberrypi weewx[2902] DEBUG weewx.manager: Daily summary 
> version is 2.0
> Jun 20 06:44:22 raspberrypi weewx[2902] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 0.81 seconds
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.manager: Daily summary 
> version is 2.0
> Jun 20 06:44:22 raspberrypi weewx[2902] INFO weewx.imagegenerator: 
> Generated 15 images for report SeasonsReport in 0.81 seconds
> Jun 20 06:44:22 raspberrypi weewx[2902] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.reportengine: Report 
> 'StandardReport' not enabled. Skipping.
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.reportengine: Report 
> 'FTP' not enabled. Skipping.
> Jun 20 06:44:22 raspberrypi weewx[2902] DEBUG weewx.reportengine: Report 
> 'RSYNC' not enabled. Skipping.
> Jun 20 06:44:30 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7252 live_queue_len:1
> Jun 20 06:44:31 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8050
> Jun 20 06:44:36 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7253 live_queue_len:1
> Jun 20 06:44:37 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8051
> Jun 20 06:44:38 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  adjust_rain rain_total:4.55 Rain.rain_total_last:4.55 rain_interval:0.00
> Jun 20 06:44:38 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7254 live_queue_len:1
> Jun 20 06:44:39 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8052
> Jun 20 06:44:39 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7255 live_queue_len:1
> Jun 20 06:44:40 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8053
> Jun 20 06:44:49 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7256 live_queue_len:1
> Jun 20 06:44:50 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8054
> Jun 20 06:44:50 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7257 live_queue_len:1
> Jun 20 06:44:51 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8055
> Jun 20 06:44:57 raspberrypi weewx[2902] WARNING weewx.drivers.wmr200: 
> Clock time unsynchronized
> Jun 20 06:44:57 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7258 live_queue_len:1
> Jun 20 06:44:58 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8056
> Jun 20 06:44:59 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7259 live_queue_len:1
> Jun 20 06:45:00 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8057
> Jun 20 06:45:03 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7260 live_queue_len:1
> Jun 20 06:45:04 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8058
> Jun 20 06:45:04 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7261 live_queue_len:1
> Jun 20 06:45:05 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8059
> Jun 20 06:45:09 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Queuing live packet rx:7262 live_queue_len:1
> Jun 20 06:45:10 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200: 
> genLoop() Yielding live queued packet id:8060
> Jun 20 06:45:12 raspberrypi weewx[2902] DEBUG weewx.drivers.wmr200:  
>  Acknowledged control packet rx:488
> Jun 20 06:45:15 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I added this section to the README:

Rsync "errors" in the log:

If one is using rsync, especially if the loop interval is short (e.g., 2s), it 
is expected that

there will be log entries for connection timeouts, data timeouts and skipped 
packets.

By default only one second is allowed to connect or transmit the data. Also, by 
default,

if the loop data is older than 3s, it is skipped. With these settings, the 
remote server

may miss receiving some loop-data packets, but it won't get caught behind 
trying to

send a backlog of old loop data.



Following are examples of a connection timeout, a data transmission timeout and 
a

skipped packet. These errors are fine in moderation. If too many packets are 
timing out,

one might try changing the connection timeout or timeout values (depending on 
whether

the timeouts are in the connection or the transmission).

Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
'--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
'/home/weewx/gauge-data/loop-data.txt', 
'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] reported 
errors: ssh: connect to host www.paloaltoweather.com port 22: Connection timed 
out. rsync: connection unexpectedly closed (0 bytes received so far) [sender]. 
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.3]
Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
'--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
'/home/weewx/gauge-data/loop-data.txt', 
'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] reported 
errors: [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in 
data send/receive (code 30) at io.c(204) [sender=3.1.3]
Jun 21 19:16:23 charlemagne weewx[8170] INFO user.rtgd: rsync_data: skipping 
packet (2020-06

> On Jul 1, 2020, at 10:20 AM, John Kline  wrote:
> 
> 
> It is normal to have some timeouts as the timeout is set to 1s.
> 
> For example, today so far I’ve had 5 connection timeouts on loop-data.  I’ve 
> also had 3 gauge-data timeouts (I contributed the rsync code for rtgd).
> 
>rsync: gauge-data: connection timeouts 3
>rsync: loop-data: connection timeouts5
> 
> How many of these error messages are you seeing?
> 
> John
> 
>>> On Jul 1, 2020, at 10:03 AM, Geni 0815  wrote:
>>> 
>> 
>> 
>> @John: This is the error message, where do I have to search?
>> 
>>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>> 
>> complete line:
>> Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
>> ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
>> 'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
>> [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in data 
>> send/receive (code 30) at io.c(204) [sender=3.1.3]
>> 
>> 
>> Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>>> 
>>> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
>>> int.
>>> 
>>> I didn’t catch this as I was not specifying a port.  This should now be 
>>> fixed in 1.3.1.  Would you please give it a try?
>>> 
> On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
> 
 
> 
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in 
> process_queue
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in 
> write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   if 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

It is normal to have some timeouts as the timeout is set to 1s.

For example, today so far I’ve had 5 connection timeouts on loop-data.  I’ve 
also had 3 gauge-data timeouts (I contributed the rsync code for rtgd).

   rsync: gauge-data: connection timeouts 3
   rsync: loop-data: connection timeouts5

How many of these error messages are you seeing?

John

> On Jul 1, 2020, at 10:03 AM, Geni 0815  wrote:
> 
> 
> 
> @John: This is the error message, where do I have to search?
> 
>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
> 
> complete line:
> Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
> ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
> 'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
> [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in data 
> send/receive (code 30) at io.c(204) [sender=3.1.3]
> 
> 
> Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>> 
>> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
>> int.
>> 
>> I didn’t catch this as I was not specifying a port.  This should now be 
>> fixed in 1.3.1.  Would you please give it a try?
>> 
 On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
 
>>> 
 
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  Traceback (most recent call last):
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.compose_and_write_packet(pkt)
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 541, in 
 compose_and_write_packet
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.write_packet(selective_pkt)
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.rsync_data(pkt['dateTime'])
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  rsync_upload.run()
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  if self.port is not None and len(self.port.strip()) > 0:
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  AttributeError: 'int' object has no attribute 'strip'
 
 
>>> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
 
 @John: I have the following entry in the syslog, what is not suitable?
 
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> barometer_rate_secs: 10800
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_secs : 86400
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_points   : 16
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in 
> process_queue
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in 
> write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 

[weewx-user] Re: Wmr200: read_device() USB Error Reason:[Errno 110] Operation timed out

[Alessandro]

Hi Jason,
we are discussing this issue here: https://github.com/weewx/weewx/issues/578
and your experience can be important in order to fix this problem.
Thanks,
Alessandro

-- 
You received this message because you are subscribed 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/5075d3db-6d09-436f-a623-8cae24e341e9o%40googlegroups.com.

[weewx-user] Switching from Acu-Rite to Vantage Pro 2

[Kevin Davis]

I've been running on a Acu-Rite 5-in-1 for a couple years.  A few months
ago, I bought a Vantage Pro 2 and now I'm ready to switch my weewx install
over to pull data from it instead of the Acu-Rite.

Beyond backing up my config file and database, which happens every night
anyway, just looking for any gotchas to watch out for when transitioning
from one to other.

ie. Should I start with a fresh DB and combine the data later?

Thanks for any pointers!

-Kevin (KE7K)

-- 
You received this message because you are subscribed 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/CAHiQ_B2eeaZFbFMZX-%3DrQQC97M%2B9DC4VebAMNsOSjp0hvd--CA%40mail.gmail.com.

[weewx-user] Re: Interceptor setup

[Scott Grayban]

I corrected that typo. Sorry about the trouble.

On Tuesday, June 30, 2020 at 12:51:01 AM UTC-7, Zsolt Máté wrote:
>
> There was a typo in the wiki, edited it.
> Instead of domain_name_servers there was domain_name_server.
>
>
>
> On Tuesday, June 30, 2020 at 7:39:11 PM UTC+12, Zsolt Máté wrote:
>>
>> Did anything change with the latest raspberry pi images? I'm trying to do 
>> a clean install, downloaded the last image (based on Debian Buster), 
>> installed and configured hostapd as per wiki.
>> Now the DNS is not resolving any address. I can ping external IP 
>> addresses while I'm connected to the pi via LAN or WLAN.
>>
>

-- 
You received this message because you are subscribed 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/523ca5d1-bc3d-4c2d-acef-7aab2fe8faaco%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Zsolt Máté]

Solved by uninstalling python3 and installing 2.7.

On Wednesday, July 1, 2020 at 12:06:44 PM UTC+12, Zsolt Máté wrote:
>
> Did anyone find a fix for this?
> I'm in the same boat. Fresh raspberry pi image, clean install.
>
> sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=observer --mode=sniff 
> --iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
> mapped packet: {'barometer': 29.986, 'windchill': 45.5, 'dewpoint': 39.7, 
> 'pressure': 30.024, 'outHumidity': 77.0, 'UV': 1.0, 'radiation': 105.33, 
> 'rain': None, 'dateTime': 1593561263, 'windDir': 244.0, 'outTemp': 46.6, 
> 'windSpeed': 3.4, 'inHumidity': 44.0, 'inTemp': 69.6, 'windGust': 4.5, 
> 'usUnits': 1}
>
>
> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine: 
>>>   Observer.Parser(), handler=Observer.Handler, **stn_dict)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> iface, pcap_filter, promiscuous)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>>   File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> def open_live(self, *args): return _pcap.pcapObject_open_live(self, 
>>> *args)
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
>>> TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__: Unable to load 
>>> driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__:   
>>> Exiting...
>>
>>
>>

-- 
You received this message because you are subscribed 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/210d119f-7d07-4493-9c1e-4e98ca3e2fd3o%40googlegroups.com.

[weewx-user] Weewx 4.1 or later mqtt client

['ml' via weewx-user]

Hello, is it possible to publish the weather data via MQTT also with 
weewx4.x ?

Thanks

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

[weewx-user] Re: sftp upload not working

[Fam de Munck]

It seems you are confusing sftp and ftps.

Please have a look at:
https://github.com/weewx/weewx/wiki
http://www.weewx.com/docs/usersguide.htm#config_FTP


Op dinsdag 30 juni 2020 17:21:05 UTC+2 schreef Andre:
>
> I have problems to upload with sftp from my RPi to my new vServer.
>
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
> Jun 30 16:56:28 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
> secure connection to x.xx.xxx.xxx
> Jun 30 16:56:29 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:29 CEST (1593528989)
> Jun 30 16:56:31 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:31 CEST (1593528991)
> Jun 30 16:56:33 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:33 CEST (1593528993)
> Jun 30 16:56:35 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:35 CEST (1593528995)
> Jun 30 16:56:37 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:37 CEST (1593528997)
> Jun 30 16:56:39 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:39 CEST (1593528999)
> Jun 30 16:56:41 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:41 CEST (1593529001)
> Jun 30 16:56:43 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:43 CEST (1593529003)
> Jun 30 16:56:45 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:45 CEST (1593529005)
> Jun 30 16:56:47 weewx weewx[2174] INFO weewx.restx: MQTT: Published 
> record 2020-06-30 16:56:47 CEST (1593529007)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine: ftpgenerator: 
> (0): caught exception '': timed out
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:   
> Traceback (most recent call last):
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 330, in run
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  n = ftp_data.run()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  ftp_server.connect(self.server, self.port)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 155, in connect
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  self.welcome = self.getresp()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 236, in getresp
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  resp = self.getmultiline()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 226, in getmultiline
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  nextline = self.getline()
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/ftplib.py", line 204, in getline
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  line = self.file.readline(self.maxline + 1)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>File "/usr/lib/python3.7/socket.py", line 589, in readinto
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  return self._sock.recv_into(b)
> Jun 30 16:56:48 weewx weewx[2174] ERROR weewx.reportengine:  
>  socket.timeout: timed out
> Jun 30 16:56:48 weewx weewx[2174] DEBUG weeutil.ftpupload: Attempting 
> secure connection to x.xx.xxx.xxx
>
> [[FTP]]
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> skin = Ftp
> 
> # If you wish to use FTP, set "enable" to "true", then
> # fill out the next four lines.
> # Use quotes around passwords to guard against parsing errors.
> enable = true
> user = username
> password = "password"
> server = x.xx.xxx.xxx# The ftp server name, e.g, 
> www.myserver.org
> path = /var/www/html/www.doamainname.com/public_html# The 
> destination directory, e.g., /weather
> 
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
> secure_ftp = true
> 
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> HTML_ROOT = 

[weewx-user] Multi-year Graphs

[Richard G]

I would really like to have some charts of multiyear weather day so you can 
compare, for example, the rain this month compared to last year or the all 
time average. Looking through the posts here I notice a few people have 
asked similar questions but one from Alan Major from Birdham in the UK 
looked really promising using an external library and JS.

Visualisation of data using Highcharts charting library 


His site seems down at the moment but I was hoping Alan was still reading 
this group and may be able to share more of his solution and how well its 
worked in the longer term.

If anyone else has done anything similar then I would also be interested.

Many thanks


Richard

-- 
You received this message because you are subscribed 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/9c930896-4754-4401-a2b9-9c14c4c9549fn%40googlegroups.com.