[weewx-user] Weewx interceptor not working with Ecowitt GW1000 in WU mode ?

2019-12-01 Thread Tim Tuck

Hi all,

I've been having issues with trying to get my Ecowitt GW1000 and its 
collection of sensors to work with Weewx.


First up, let me say that it works just fine posting data to both WU and 
Ecowitt servers.


I've tried getting the script mentioned here...

https://www.wxforum.net/index.php?topic=37471.0

to work for Ecowitt mode, but that has not been successful.

Running that script in debug mode did not produce any data at all for 
the Ecowitt mode.


If I change the GW1000 custom server setting to WU mode I do see some 
data in debug mode thus...


# PYTHONPATH=. python user/interceptor.py --device=wu-client 
--mode=listen --port=8000 --debug

identifiers: {}
raw data:
raw packet: {'usUnits': 1, 'dateTime': 1575261732}
mapped packet: {'usUnits': 1, 'dateTime': 1575261732}
identifiers: {}
raw data:
raw packet: {'usUnits': 1, 'dateTime': 1575261793}
mapped packet: {'usUnits': 1, 'dateTime': 1575261793}
identifiers: {}
raw data:
raw packet: {'usUnits': 1, 'dateTime': 1575261854}
mapped packet: {'usUnits': 1, 'dateTime': 1575261854}
identifiers: {}
raw data:

I get the same output REGARDLESS of which interceptor.py I use.

Both the modified script and Mathew's original produce identical output.

Thinking it might be my ratty old server I built a shiny new one and got 
exactly the same result!


I know all the data is reaching the servers since I can run tcpdump in a 
different terminal and see the data.


Versions of all as follows...

Weewx is 3.9.2 on both servers.

GW1000 is the latest firmware 1.5.4

Server 1 is Debian 9 Linux 4.9.0-11-686-pae on i686, python 2.7.13

Server 2 is Centos Linux 7.7.1908, Python 2.7.5

I have pcap files if someone wants to look at the actual raw packets.

Any help appreciated.

thanks

Tim



--
You received this message because you are subscribed 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/2e449776-2ad6-e3a2-1580-45382800e527%40skybase.net.


[weewx-user] Re: bootstrap history page

2019-12-01 Thread Andrew Milner
i only copied the files a week or so ago.  The only problem I am having is 
with the noaa table which is giving me an error - i have got the summary 
columns for the min, max, rain tables working as expected.



On Sunday, 1 December 2019 23:43:50 UTC+2, Mikael Fredriksson wrote:
>
> Ok, thanks Andrew!
>
> I did also try to update and use the new files but nothing changed so I 
> guess this has been removed in the latest update.
>
> Mikael
>
>

-- 
You received this message because you are subscribed 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/c4491f79-5f50-49a5-9a75-3398c42be6e1%40googlegroups.com.


[weewx-user] Re: Weewx "off line"

2019-12-01 Thread Teva MERVIN
*syslog :*

Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Using pc time 
adjusting archive record time by -251 sec 2019-12-02 10:15:00 +11 
(1575242100) => 2019-12-02 10:10:49 +11 (1575241849) 
Dec  2 10:11:50 Nas weewx[1784]: manager: Added record 2019-12-02 10:10:49 
+11 (1575241849) to database 'weewx.sdb' 
Dec  2 10:11:50 Nas weewx[1784]: engine: Main loop exiting. Shutting engine 
down. 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-8: I USB polling device 
thread exiting 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I USB polling thread 
expired 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-7: I Watchdog received 
shutdown 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: Thread-7: I Watchdog thread 
exiting 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Watchdog thread 
expired 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Received packet 
count live:2951 archive:20 control:188 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Received bytes:592 
sent bytes:40 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Packet archive queue 
len:0 live queue len:8 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: W Exiting with packets 
still in live queue cnt:8 
Dec  2 10:11:50 Nas weewx[1784]: wmr200: MainThread: I Driver gracefully 
exiting 
Dec  2 10:11:50 Nas weewx[1784]: engine: Caught unrecoverable exception in 
engine: 
Dec  2 10:11:50 Nas weewx[1784]:   Non-positive value for record 
field 'interval': 0 
Dec  2 10:11:50 Nas weewx[1784]:   Traceback (most recent call 
last): 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 894, in main 
Dec  2 10:11:50 Nas weewx[1784]:   engine.run() 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 160, in run 
Dec  2 10:11:50 Nas weewx[1784]:  
 self.dispatchEvent(weewx.Event(weewx.STARTUP)) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent 
Dec  2 10:11:50 Nas weewx[1784]:   callback(event) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 520, in startup 
Dec  2 10:11:50 Nas weewx[1784]:  
 self._catchup(self.engine.console.genStartupRecords) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 635, in _catchup 
Dec  2 10:11:50 Nas weewx[1784]:   origin='hardware')) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent 
Dec  2 10:11:50 Nas weewx[1784]:   callback(event) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record 
Dec  2 10:11:50 Nas weewx[1784]:  
 dbmanager.addRecord(event.record, accumulator=self.old_accumulator) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/manager.py", line 246, in addRecord 
Dec  2 10:11:50 Nas weewx[1784]:  
 self._addSingleRecord(record, cursor, log_level) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord 
Dec  2 10:11:50 Nas weewx[1784]:   _weight = 
self._calc_weight(record) 
Dec  2 10:11:50 Nas weewx[1784]: File 
"/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight 
Dec  2 10:11:50 Nas weewx[1784]:   raise 
ValueError("Non-positive value for record field 'interval': %s" % 
(record['interval'], )) 
Dec  2 10:11:50 Nas weewx[1784]:   ValueError: Non-positive value 
for record field 'interval': 0 
Dec  2 10:11:50 Nas weewx[1784]:   Exiting.





Le mardi 19 novembre 2019 16:36:37 UTC+11, Teva MERVIN a écrit :
>
> Hello.
> I have a problem that I can not identify.
> It happens at least once a day, and I have to restart weewx.
> Do you have ideas?
>
> root@Nas:~# service weewx status
> ● weewx.service - LSB: weewx weather system 
>   Loaded: loaded (/etc/init.d/weewx; generated) 
>   Active: active (exited) since Sun 2019-11-17 19:09:21 +11; 1 day 21h 
> ago 
> Docs: man:systemd-sysv-generator(8) 
>  Process: 2094 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS) 
>
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record 
> nov. 19 13:34:26 Nas weewx[2110]:  
>  dbmanager.addRecord(event.record, accumulator=self.old_accumulator) 
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/manager.py", line 246, in addRecord 
> nov. 19 13:34:26 Nas weewx[2110]:  
>  self._addSingleRecord(record, cursor, log_level) 
> nov. 19 13:34:26 Nas weewx[2110]: File 
> "/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord 
> nov. 19 13:34:26 Nas weewx[2110]:   _weight = 
> 

[weewx-user] Re: wee_import PWS station not found.

2019-12-01 Thread transmorph
Hey Gary,

Did you end up getting this one finished? I'd be vey happy to give it a 
whirl on my 3.9.2 installation.

Thanks.

On Tuesday, November 12, 2019 at 8:18:54 PM UTC+11, gjr80 wrote:
>
> I have made the necessary changes to the 4.0 release wee_import to fix 
> this issue; however, I still have a few more checks to do before it can be 
> used. Unfortunately other things have limited the time I have had available 
> for wee_import development lately. I will let Tom speak for when 4.0 
> might be released, though I do have a means by which the 4.0 wee_import 
> utility can be used under an existing 3.x install without interfering with 
> the existing 3.x install. So the release of 4.0 is not the limiting factor 
> here, rather it is me finishing up with wee_import. Should be this week 
> but I can't promise that.
>
> I am not a Weatherlink user so I can't comment on any other means of 
> importing Weatherlink data,
>
> Gary 
>
> On Tuesday, 12 November 2019 02:18:38 UTC+10, George Anestopoulos wrote:
>>
>> Hi all, 
>>
>> I'm new to weewx, I have moved from weatherlink to weewx, but I cannot 
>> import my historical data because of the same error. 
>>
>> Is any Estimate when 4.0 version will come out? 
>>
>> Is any other way to import my data from weatherlink?
>>
>> Thanks.
>>
>> On Friday, August 30, 2019 at 4:20:13 PM UTC+1, Clint Parrish wrote:
>>>
>>> I’m having a problem importing records from WU.  I have over 11 years of 
>>> records that I want to combine into my weewx.sdb. 
>>>
>>> I have entered my nine digit PWS ID into my config file and get the 
>>> following when I run wee_import: 
>>>
>>> wee_import --config=/etc/weewx/weewx.conf 
>>> --import-config=/var/tmp/wu.conf --from=2019-08-29 --to=2019-08-30 
>>> --dry-run 
>>> Starting wee_import... 
>>> Observation history for Weather Underground station 'KILSULLI1' will be 
>>> imported. 
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'weewx.sdb' 
>>> Destination table 'archive' unit system is '0x01' (US). 
>>> Missing derived observations will be calculated. 
>>> Observations timestamped after 2019-08-29 00:00:00 CDT (1567054800) and 
>>> up to and 
>>> including 2019-08-31 00:00:00 CDT (1567227600) will be imported. 
>>> This is a dry run, imported data will not be saved to archive. 
>>> Unable to open Weather Underground station KILSULLI1 
>>>  
>>>  Unable to load config file. 
>>>   
>>>  Nothing done, exiting. 
>>>
>>> Could somebody please help?  Thanks! 
>>>
>>> Clint
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/73edaccb-e03a-4ace-b1c3-7de90dbba712%40googlegroups.com.


[weewx-user] Re: bootstrap history page

2019-12-01 Thread Mikael Fredriksson
Ok, thanks Andrew!

I did also try to update and use the new files but nothing changed so I guess 
this has been removed in the latest update.

Mikael

-- 
You received this message because you are subscribed 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/7b139144-bbbf-49f8-9e97-cf7f4e26ec8f%40googlegroups.com.


Re: [weewx-user] Memory usage of the imaging library when the imaging library's default is used

2019-12-01 Thread Rich Bell
Not sure what happened to the plots... Hopefully this works.
-rich


On Sun, Dec 1, 2019 at 3:43 PM Rich Bell  wrote:

> This is not new information, but I thought it might help others seeing a
> steady increase in memory consumption.
> TL;DR
> I am seeing a memory leak when the imaging library default font is used.
> Ensuring that a font is specified for each label (top_label_font_path,
> unit_label_font_path, bottom_label_font_path, axis_label_font_path,
> rose_label_font_path) seems to have fixed it.
>
> Backgound:
> Running with:
> OS: Linux-4.19.49v6v7-aufs-armv7l-with-debian-9.6
> Python: 3.5.3 (default, Sep 27 2018, 17:25:39)
> [GCC 6.3.0 20170516]
> PIL/Pillow: 4.0.0
>
> I was seeing the following:
>


> The following is a graph of memory size over the same time period.  It
> graphs the same weewx instance as above - no fonts specified for the images
> (base), an instance with the skin disabled (disabled), and one with the
> fonts specified (fontsall).
>


> Here is a plot of the RSS over the same time.
>


> Here are a few more data points that may or may not be of interest.
> "noimage" does not call plot.render() while render does, but does not save
> the image (image.save).
> Here is the memory size plot.
>


> And the RSS.
>


>
> - rich
>
> --
> You received this message because you are subscribed 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/fe7997e1-15d9-4f83-b338-44075df42ef1%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/CAG4CQqwU-8UmejSTF-ViKasnw1%3Df8P5GLH5Jef1Qx6D%3DYuajuw%40mail.gmail.com.


[weewx-user] Memory usage of the imaging library when the imaging library's default is used

2019-12-01 Thread Rich Bell
This is not new information, but I thought it might help others seeing a 
steady increase in memory consumption.
TL;DR
I am seeing a memory leak when the imaging library default font is used.  
Ensuring that a font is specified for each label (top_label_font_path, 
unit_label_font_path, bottom_label_font_path, axis_label_font_path, 
rose_label_font_path) seems to have fixed it.

Backgound:
Running with:
OS: Linux-4.19.49v6v7-aufs-armv7l-with-debian-9.6
Python: 3.5.3 (default, Sep 27 2018, 17:25:39) 
[GCC 6.3.0 20170516]
PIL/Pillow: 4.0.0

I was seeing the following:
[image: week]

The following is a graph of memory size over the same time period.  It 
graphs the same weewx instance as above - no fonts specified for the images 
(base), an instance with the skin disabled (disabled), and one with the 
fonts specified (fontsall).
[image: week3]

Here is a plot of the RSS over the same time.
[image: week3]

Here are a few more data points that may or may not be of interest.  
"noimage" does not call plot.render() while render does, but does not save 
the image (image.save).  
Here is the memory size plot.
[image: week4]

And the RSS.
[image: week4]

- rich

-- 
You received this message because you are subscribed 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/fe7997e1-15d9-4f83-b338-44075df42ef1%40googlegroups.com.


[weewx-user] Re: weewx-sdr can't parse Oregon Scientific UVR128

2019-12-01 Thread mwall
added to weewx-sdr at commit 27eadb9

-- 
You received this message because you are subscribed 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/4338dcb0-00a5-4e39-837f-6a3054a84f81%40googlegroups.com.


[weewx-user] Re: sensor data wind and rain hideki (tfa Sinus-bresser ...)

2019-12-01 Thread mwall
thank you andy.  had to do a units conversion, but the fix is in at commit 
c37ba53 

-- 
You received this message because you are subscribed 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/549f9818-5131-4de1-9df6-b27775a6bc2d%40googlegroups.com.


[weewx-user] Help needed

2019-12-01 Thread rimas petronis
I have a controler that scans a lot of sensors, I want to scan data with a 
weewx server
The controller response is passed in json format
Requesting request: '\ x1B \ n0? 9 \ x1B \ r'
Answer:{"D":"2019-12-01 
09:57:41","T01":-2.8,"T02":1.1,"T03":54.1,"T04":41.8,"T05":58.7,"T06":22.6,"T07":41.5,"T08":37.5,"T09":31.6,"T10":30.3,"T11":21.3,"T12":22.1,"T13":50.2,"T14":20.3,"T15":48.1,"T16":20.9,"T17":20.8,"T18":20.2,"T19":20.9,"T20":21.0,"T21":21.3,"T22":20.1,"T23":42.2,"T24":48.6,"T25":39.0,"T26":37.3,"T27":54.9,"T28":48.0,"T29":35.0,"T30":23.5,"T31":21.7,"T32":9.8,"T33":76.0,"T34":28.5,"T35":29.3,"T36":20.4,"T38":21.0,"T39":14.3,"T40":20.2,"T41":-99.9,"T42":-99.9,"T43":-99.9,"T44":-99.9,"T45":-99.9,"T46":-99.9,"T47":-99.9,"T48":-99.9,"T49":-99.9,"T50":-99.9,"O01":0,"O02":3,"O03":3,"O04":0,"O05":0,"O06":0,"O07":0,"O08":0,"O09":0,"O10":8,"O11":0,"O12":0,"O13":3,"O14":0,"O15":3,"O16":3,"O17":3,"O18":3,"O19":0,"O20":0,"O21":0,"O22":3,"O23":0,"O24":0,"O25":0,"O26":3,"O27":3,"O28":0,"O29":3,"O30":3,"O31":0,"O32":8,"D1":0,"D2":0,"D3":0,"D4":0,"D5":0,"D6":0,"D7":0,"D8":1,"D9":0,"D10":0,"PID1":{"St":0,"Tp":41.1,"To":-1.1,"Ti":
 
0.0,"Fk":0.0,"Tu":40.0,"Pv":36},"PID2":{"St":0,"Tp":31.4,"To":-1.4,"Ti": 
0.0,"Fk":0.0,"Tu":30.0,"Pv":22},"Fl1":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":22.2},"Fl2":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl3":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":19.8},"Fl4":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":20.3},"Fl5":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl6":{"On":1,"To":-2.5,"Ti":1.2,"GK":6,"Fz":21.0},"Fl7":{"On":0,"To":0.0,"Ti":0.0,"GK":7,"Fz":0.0},"Fl8":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl9":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl10":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":20.0},"Fl11":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl12":{"On":1,"To":0.0,"Ti":-2.4,"GK":6,"Fz":21.0},"Fl13":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":20.2},"Fl14":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":22.6},"Fl15":{"On":1,"To":0.0,"Ti":0.0,"GK":6,"Fz":21.0},"Fl16":{"On":0,"To":0.0,"Ti":0.0,"GK":6,"Fz":61.5},"Spp":0,"KwB":0,"Cpm":0.00,"Hup":1,"Acu":0,"PkW":0,"BoPr":0,"AcOn":0,"Tl":-2.8,"Coo":0,"Gl":0,"Cgl":8,"Stp":49,"Sk1":745012,"Sk2":220282,"Sk3":208918,"Sk4":0,"Sk5":0,"DAC1":6.3,"DAC2":7.7,"DAC3":0.0,"DAC4":0.0,"DAC5":0.0,"DAC6":0.0,"DAC7":0.0,"DAC8":0.0}
I want to create WeeWX extensions
Maybe someone could help

-- 
You received this message because you are subscribed 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/adecb289-daea-48b3-ad34-c5ba1c63552c%40googlegroups.com.