from:"S R"

ok. thanks guys. i deleted the jail and started again per your 
instructions. everything installed without errors and I've loaded the 
startup scrip and the service starts. 
i can ping the weewx and ping from the weewx jail to the internet. 
if i try to reach via the browser i get Refused to Connect
On Friday, January 15, 2021 at 2:14:23 AM UTC+1 mscham...@gmail.com wrote:

> Using pip to install python packages under FreeBSD isn't a great idea. 
> Freshports can keep everything up to date for you. I've been running weewx 
> on my FreeBSD server for several years. 
>
> On Thursday, January 14, 2021 at 5:43:24 PM UTC-6 sjr4...@gmail.com wrote:
>
>> that didn't work in 2.
>> I managed to install python37 and pip
>> i then had to install with the commands below and follow the packages per 
>> debian10 instructions
>> pip install configobj 
>> pip install serial 
>> pip install usb 
>> pip install pip
>> pip install cheetah3
>> pip install ephem
>>
>> But i get an error with 
>> pip install pil  - "could not find a package that satisfies the 
>> requirement pil"
>> Do i need pil? 
>>
>> I have a WH2900 Fine Offset and in the forums it talks about using the 
>> interception driver, but this is not an option during install. 
>>
>>
>>
>> On Thursday, January 14, 2021 at 9:55:30 PM UTC+1 kilo...@gmail.com 
>> wrote:
>>
>>> I have used weewx on FreeNAS / TrueNAS for many years and it works well, 
>>> for hardware that sends loop data to an IP address.  Have not tried it with 
>>> usb hardware.  
>>>
>>> 1. Create and run weewx in it's own standard jail.  Given that you want 
>>> to play with FreeBSD I assume you are familiar with jails and you can 
>>> handle this.  All further instructions assume that you are working within 
>>> the active running jail.
>>> 2. Python packages are named a little different than  linux 
>>> distributions.  
>>>  a) Start by installing python3 using pkg command.  Available 
>>> package names are python36, python37, python38, python39.  Further 
>>> instruction will assume you installed python37
>>>  b) Install py37-cheetah3 using the pkg command
>>>  c) Install py37-configobj
>>>  d) Install py37-pillow
>>>  e) Install py37-sqlite3, assuming you are using sqlite database
>>> 3. Install weewx using the setup.py method
>>> 4. To run weewx directly con command line, cd to /home/weewx and use 
>>> the  ./bin/weewxd  command, run this as su.
>>> 5. To start weewx automatically from at startup,  copy the attached 
>>> script to */usr/local/etc/rc.d/*
>>> 6.  Add the following line *weewx_enable="YES"* to the */etc/rc.conf* 
>>> file.  Now weewx will start automatically and you can start and stop the 
>>> service with *service weewx start* or *service weewx stop* command
>>>
>>>
>>>
>>>
>>> On Thursday, January 14, 2021 at 10:04:06 a.m. UTC-8 sjr4...@gmail.com 
>>> wrote:
>>>

 I have a TrueNAS box and want to install in a FreeBSD jail. I'm a 
 complete knob, can anyone help with instructions for installing on 
 FreeBSD. 
 Sadly, such great document for Linux, but none for FreeBSD (although i see 
 there is a startup script, for those who know how to get that far)

>>>

-- 
You received this message because you are subscribed 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/2770c6fb-8308-4a73-9a19-b07c551e1af7n%40googlegroups.com.

[weewx-user] Re: FreeBSD / TrueNAS Jail Install Help

the process is definitely running. Do I have to add some user permissions 
for the public_html directory? 
i installed into path /usr/local/share/weewx

On Friday, January 15, 2021 at 12:29:52 PM UTC+1 S R wrote:

> ok. thanks guys. i deleted the jail and started again per your 
> instructions. everything installed without errors and I've loaded the 
> startup scrip and the service starts. 
> i can ping the weewx and ping from the weewx jail to the internet. 
> if i try to reach via the browser i get Refused to Connect
> On Friday, January 15, 2021 at 2:14:23 AM UTC+1 mscham...@gmail.com wrote:
>
>> Using pip to install python packages under FreeBSD isn't a great idea. 
>> Freshports can keep everything up to date for you. I've been running weewx 
>> on my FreeBSD server for several years. 
>>
>> On Thursday, January 14, 2021 at 5:43:24 PM UTC-6 sjr4...@gmail.com 
>> wrote:
>>
>>> that didn't work in 2.
>>> I managed to install python37 and pip
>>> i then had to install with the commands below and follow the packages 
>>> per debian10 instructions
>>> pip install configobj 
>>> pip install serial 
>>> pip install usb 
>>> pip install pip
>>> pip install cheetah3
>>> pip install ephem
>>>
>>> But i get an error with 
>>> pip install pil  - "could not find a package that satisfies the 
>>> requirement pil"
>>> Do i need pil? 
>>>
>>> I have a WH2900 Fine Offset and in the forums it talks about using the 
>>> interception driver, but this is not an option during install. 
>>>
>>>
>>>
>>> On Thursday, January 14, 2021 at 9:55:30 PM UTC+1 kilo...@gmail.com 
>>> wrote:
>>>
>>>> I have used weewx on FreeNAS / TrueNAS for many years and it works 
>>>> well, for hardware that sends loop data to an IP address.  Have not tried 
>>>> it with usb hardware.  
>>>>
>>>> 1. Create and run weewx in it's own standard jail.  Given that you want 
>>>> to play with FreeBSD I assume you are familiar with jails and you can 
>>>> handle this.  All further instructions assume that you are working within 
>>>> the active running jail.
>>>> 2. Python packages are named a little different than  linux 
>>>> distributions.  
>>>>  a) Start by installing python3 using pkg command.  Available 
>>>> package names are python36, python37, python38, python39.  Further 
>>>> instruction will assume you installed python37
>>>>  b) Install py37-cheetah3 using the pkg command
>>>>  c) Install py37-configobj
>>>>  d) Install py37-pillow
>>>>  e) Install py37-sqlite3, assuming you are using sqlite database
>>>> 3. Install weewx using the setup.py method
>>>> 4. To run weewx directly con command line, cd to /home/weewx and use 
>>>> the  ./bin/weewxd  command, run this as su.
>>>> 5. To start weewx automatically from at startup,  copy the attached 
>>>> script to */usr/local/etc/rc.d/*
>>>> 6.  Add the following line *weewx_enable="YES"* to the */etc/rc.conf* 
>>>> file.  Now weewx will start automatically and you can start and stop the 
>>>> service with *service weewx start* or *service weewx stop* command
>>>>
>>>>
>>>>
>>>>
>>>> On Thursday, January 14, 2021 at 10:04:06 a.m. UTC-8 sjr4...@gmail.com 
>>>> wrote:
>>>>
>>>>>
>>>>> I have a TrueNAS box and want to install in a FreeBSD jail. I'm a 
>>>>> complete knob, can anyone help with instructions for installing on 
>>>>> FreeBSD. 
>>>>> Sadly, such great document for Linux, but none for FreeBSD (although i 
>>>>> see 
>>>>> there is a startup script, for those who know how to get that far)
>>>>>
>>>>

-- 
You received this message because you are subscribed 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/52dc403b-5d4c-4e94-93fd-3dfa1255b47dn%40googlegroups.com.

[weewx-user] Re: FreeBSD / TrueNAS Jail Install Help

just tried to install on Kubuntu 20.10 via the debian packages. same thing. 
install completes, but "refuse to connect". 
Has any tested a fresh install recently. 

On Friday, January 15, 2021 at 2:20:08 PM UTC+1 S R wrote:

> the process is definitely running. Do I have to add some user permissions 
> for the public_html directory? 
> i installed into path /usr/local/share/weewx
>
> On Friday, January 15, 2021 at 12:29:52 PM UTC+1 S R wrote:
>
>> ok. thanks guys. i deleted the jail and started again per your 
>> instructions. everything installed without errors and I've loaded the 
>> startup scrip and the service starts. 
>> i can ping the weewx and ping from the weewx jail to the internet. 
>> if i try to reach via the browser i get Refused to Connect
>> On Friday, January 15, 2021 at 2:14:23 AM UTC+1 mscham...@gmail.com 
>> wrote:
>>
>>> Using pip to install python packages under FreeBSD isn't a great idea. 
>>> Freshports can keep everything up to date for you. I've been running weewx 
>>> on my FreeBSD server for several years. 
>>>
>>> On Thursday, January 14, 2021 at 5:43:24 PM UTC-6 sjr4...@gmail.com 
>>> wrote:
>>>
>>>> that didn't work in 2.
>>>> I managed to install python37 and pip
>>>> i then had to install with the commands below and follow the packages 
>>>> per debian10 instructions
>>>> pip install configobj 
>>>> pip install serial 
>>>> pip install usb 
>>>> pip install pip
>>>> pip install cheetah3
>>>> pip install ephem
>>>>
>>>> But i get an error with 
>>>> pip install pil  - "could not find a package that satisfies the 
>>>> requirement pil"
>>>> Do i need pil? 
>>>>
>>>> I have a WH2900 Fine Offset and in the forums it talks about using the 
>>>> interception driver, but this is not an option during install. 
>>>>
>>>>
>>>>
>>>> On Thursday, January 14, 2021 at 9:55:30 PM UTC+1 kilo...@gmail.com 
>>>> wrote:
>>>>
>>>>> I have used weewx on FreeNAS / TrueNAS for many years and it works 
>>>>> well, for hardware that sends loop data to an IP address.  Have not tried 
>>>>> it with usb hardware.  
>>>>>
>>>>> 1. Create and run weewx in it's own standard jail.  Given that you 
>>>>> want to play with FreeBSD I assume you are familiar with jails and you 
>>>>> can 
>>>>> handle this.  All further instructions assume that you are working within 
>>>>> the active running jail.
>>>>> 2. Python packages are named a little different than  linux 
>>>>> distributions.  
>>>>>  a) Start by installing python3 using pkg command.  Available 
>>>>> package names are python36, python37, python38, python39.  Further 
>>>>> instruction will assume you installed python37
>>>>>  b) Install py37-cheetah3 using the pkg command
>>>>>  c) Install py37-configobj
>>>>>  d) Install py37-pillow
>>>>>  e) Install py37-sqlite3, assuming you are using sqlite database
>>>>> 3. Install weewx using the setup.py method
>>>>> 4. To run weewx directly con command line, cd to /home/weewx and use 
>>>>> the  ./bin/weewxd  command, run this as su.
>>>>> 5. To start weewx automatically from at startup,  copy the attached 
>>>>> script to */usr/local/etc/rc.d/*
>>>>> 6.  Add the following line *weewx_enable="YES"* to the */etc/rc.conf* 
>>>>> file.  Now weewx will start automatically and you can start and stop the 
>>>>> service with *service weewx start* or *service weewx stop* command
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, January 14, 2021 at 10:04:06 a.m. UTC-8 sjr4...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> I have a TrueNAS box and want to install in a FreeBSD jail. I'm a 
>>>>>> complete knob, can anyone help with instructions for installing on 
>>>>>> FreeBSD. 
>>>>>> Sadly, such great document for Linux, but none for FreeBSD (although i 
>>>>>> see 
>>>>>> there is a startup script, for those who know how to get that far)
>>>>>>
>>>>>

-- 
You received this message because you are subscribed 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/7d4b1bec-5407-42ed-acba-daaa278e4af3n%40googlegroups.com.

[weewx-user] Re: FreeBSD / TrueNAS Jail Install Help

yeh, i figured that out in the end - thanks. 

I got the simulator running on both feebsd (nginx) and kubuntu (apache2) and
i have installed the interceptor on both with the instructions in her 
https://github.com/matthewwall/weewx-interceptor
i set to observer for the Fine Offset WH2900C but it is still showing me 
the Simulator on both firefox and chrome. 
I have tried clearing the cache and restarting, but even from a fresh 
machine it shows the simulator. 

On Friday, January 15, 2021 at 4:56:04 PM UTC+1 kilo...@gmail.com wrote:

> You need to run a web server on the local machine (jail) to be able to 
> view the files generated and placed in the  public_html directory.
>
> OR
>
> You need to upload the generated files to another machine that acts as a 
> web server.  This can be done with the ftp or rsync reports
>
> On Friday, January 15, 2021 at 5:20:08 a.m. UTC-8 sjr4...@gmail.com wrote:
>
>> the process is definitely running. Do I have to add some user permissions 
>> for the public_html directory? 
>> i installed into path /usr/local/share/weewx
>>
>> On Friday, January 15, 2021 at 12:29:52 PM UTC+1 S R wrote:
>>
>>> ok. thanks guys. i deleted the jail and started again per your 
>>> instructions. everything installed without errors and I've loaded the 
>>> startup scrip and the service starts. 
>>> i can ping the weewx and ping from the weewx jail to the internet. 
>>> if i try to reach via the browser i get Refused to Connect
>>> On Friday, January 15, 2021 at 2:14:23 AM UTC+1 mscham...@gmail.com 
>>> wrote:
>>>
>>>> Using pip to install python packages under FreeBSD isn't a great idea. 
>>>> Freshports can keep everything up to date for you. I've been running weewx 
>>>> on my FreeBSD server for several years. 
>>>>
>>>> On Thursday, January 14, 2021 at 5:43:24 PM UTC-6 sjr4...@gmail.com 
>>>> wrote:
>>>>
>>>>> that didn't work in 2.
>>>>> I managed to install python37 and pip
>>>>> i then had to install with the commands below and follow the packages 
>>>>> per debian10 instructions
>>>>> pip install configobj 
>>>>> pip install serial 
>>>>> pip install usb 
>>>>> pip install pip
>>>>> pip install cheetah3
>>>>> pip install ephem
>>>>>
>>>>> But i get an error with 
>>>>> pip install pil  - "could not find a package that satisfies the 
>>>>> requirement pil"
>>>>> Do i need pil? 
>>>>>
>>>>> I have a WH2900 Fine Offset and in the forums it talks about using the 
>>>>> interception driver, but this is not an option during install. 
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, January 14, 2021 at 9:55:30 PM UTC+1 kilo...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> I have used weewx on FreeNAS / TrueNAS for many years and it works 
>>>>>> well, for hardware that sends loop data to an IP address.  Have not 
>>>>>> tried 
>>>>>> it with usb hardware.  
>>>>>>
>>>>>> 1. Create and run weewx in it's own standard jail.  Given that you 
>>>>>> want to play with FreeBSD I assume you are familiar with jails and you 
>>>>>> can 
>>>>>> handle this.  All further instructions assume that you are working 
>>>>>> within 
>>>>>> the active running jail.
>>>>>> 2. Python packages are named a little different than  linux 
>>>>>> distributions.  
>>>>>>  a) Start by installing python3 using pkg command.  Available 
>>>>>> package names are python36, python37, python38, python39.  Further 
>>>>>> instruction will assume you installed python37
>>>>>>  b) Install py37-cheetah3 using the pkg command
>>>>>>  c) Install py37-configobj
>>>>>>  d) Install py37-pillow
>>>>>>  e) Install py37-sqlite3, assuming you are using sqlite database
>>>>>> 3. Install weewx using the setup.py method
>>>>>> 4. To run weewx directly con command line, cd to /home/weewx and use 
>>>>>> the  ./bin/weewxd  command, run this as su.
>>>>>> 5. To start weewx automatically from at startup,  copy the attached 
>>>>>> script to */usr/local/etc/rc.d/*
>>>>>> 6.  Add the following line *weewx_enable="YES"* to the */etc/rc.conf* 
>>>>>> file.  Now weewx will start automatically and you can start and stop the 
>>>>>> service with *service weewx start* or *service weewx stop* command
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thursday, January 14, 2021 at 10:04:06 a.m. UTC-8 
>>>>>> sjr4...@gmail.com wrote:
>>>>>>
>>>>>>>
>>>>>>> I have a TrueNAS box and want to install in a FreeBSD jail. I'm a 
>>>>>>> complete knob, can anyone help with instructions for installing on 
>>>>>>> FreeBSD. 
>>>>>>> Sadly, such great document for Linux, but none for FreeBSD (although i 
>>>>>>> see 
>>>>>>> there is a startup script, for those who know how to get that far)
>>>>>>>
>>>>>>

-- 
You received this message because you are subscribed 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/cf87cfa1-22cc-407f-b6af-cb1e8dc96765n%40googlegroups.com.

[weewx-user] Re: FreeBSD / TrueNAS Jail Install Help

I the linux box i had success. installation of the intercept driver does 
not disable the simulator. 

Now i have a healthy startup log, and the web page just says "success", 
there is not display like with the simulator. 

what do i have to do next pls

weewx[1369] INFO user.interceptor: driver version is 0.53
weewx[1369] INFO user.interceptor: device type: observer
weewx[1369] INFO user.interceptor: mode is listen
weewx[1369] INFO user.interceptor: listen on :80
weewx[1369] INFO user.interceptor: sensor map: {'pressure': 'pressure', 
'barometer': 'barometer', 'outHumidity': 'humidity_out', 'inHumidity': 
'humidity_in', 'outTemp': 'temperature_out', 'inTemp': 'temperature_in', 
'windSpeed': 'wind_speed', 'windGust': 'wind_gust', 'windDir': 'wind_dir', 
'windGustDir': 'wind_gust_dir', 'radiation': 'solar_radiation', 'dewpoint': 
'dewpoint', 'windchill': 'windchill', 'rain': 'rain', 'rainRate': 
'rain_rate', 'UV': 'uv', 'txBatteryStatus': 'battery', 'extraTemp1': 
'temperature_1', 'extraTemp2': 'temperature_2', 'extraTemp3': 
'temperature_3', 'extraHumid1': 'humidity_1', 'extraHumid2': 'humidity_2', 
'soilTemp1': 'soil_temperature_1', 'soilTemp2': 'soil_temperature_2', 
'soilMoist1': 'soil_moisture_1', 'soilMoist2': 'soil_moisture_2', 
'soilMoist3': 'soil_moisture_3', 'soilMoist4': 'soil_moisture_4', 
'leafWet1': 'leafwetness_1', 'leafWet2': 'leafwetness_2', 'pm2_5': 'pm2_5', 
'extraTemp4': 'temperature_4', 'extraTemp5': 'temperature_5', 'extraTemp6': 
'temperature_6', 'extraTemp7': 'temperature_7', 'extraTemp8': 
'temperature_8', 'extraHumid3': 'humidity_3', 'extraHumid4': 'humidity_4', 
'extraHumid5': 'humidity_5', 'extraHumid6': 'humidity_6', 'extraHumid7': 
'humidity_7', 'extraHumid8': 'humidity_8', 'soilTemp3': 
'soil_temperature_3', 'soilTemp4': 'soil_temperature_4'}
weewx[1369] INFO weewx.engine: StdConvert target unit is 0x1
weewx[1369] INFO weewx.engine: Archive will use data binding wx_binding
weewx[1369] INFO weewx.engine: Record generation will be attempted in 
'hardware'
eapema78g weewx[1369] INFO weewx.engine: Using archive interval of 300 
seconds (specified in weewx configuration)
weewx[1369] INFO weewx.restx: StationRegistry: Registration not requested.
weewx[1369] INFO weewx.restx: Wunderground: Posting not enabled.
weewx[1369] INFO weewx.restx: PWSweather: Posting not enabled.
weewx[1369] INFO weewx.restx: CWOP: Posting not enabled.
weewx[1369] INFO weewx.restx: WOW: Posting not enabled.
weewx[1369] INFO weewx.restx: AWEKAS: Posting not enabled.
weewx[1369] INFO __main__: Starting up weewx version 4.3.0
weewx[1369] INFO weewx.engine: Using binding 'wx_binding' to database 
'weewx.sdb'
weewx[1369] INFO weewx.manager: Starting backfill of daily summaries
weewx[1369] INFO weewx.engine: Starting main packet loop.

On Friday, January 15, 2021 at 8:43:05 PM UTC+1 kilo...@gmail.com wrote:

> Please post the startup log (the first bunch of lines of the weewx log 
> when it first starts up) so we can see which driver it is using
>
> On Friday, January 15, 2021 at 10:03:21 a.m. UTC-8 sjr4...@gmail.com 
> wrote:
>
>> yeh, i figured that out in the end - thanks. 
>>
>> I got the simulator running on both feebsd (nginx) and kubuntu (apache2) 
>> and
>> i have installed the interceptor on both with the instructions in her 
>> https://github.com/matthewwall/weewx-interceptor
>> i set to observer for the Fine Offset WH2900C but it is still showing me 
>> the Simulator on both firefox and chrome. 
>> I have tried clearing the cache and restarting, but even from a fresh 
>> machine it shows the simulator. 
>>
>> On Friday, January 15, 2021 at 4:56:04 PM UTC+1 kilo...@gmail.com wrote:
>>
>>> You need to run a web server on the local machine (jail) to be able to 
>>> view the files generated and placed in the  public_html directory.
>>>
>>> OR
>>>
>>> You need to upload the generated files to another machine that acts as a 
>>> web server.  This c

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

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/b6573046-cb8f-4016-bf68-823f462183ccn%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.

[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: FINE OFFSET WH2900 / Ambient Weather WS-2902

almost there, but now 

/usr/local/share/weewx # ./bin/wee_reports
Traceback (most recent call last):
  File "./bin/wee_reports", line 103, in 
main()
  File "./bin/wee_reports", line 51, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
read_config
default_encoding='utf-8')
  File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, in 
_load
content = self._handle_bom(content)

On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:

> 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/7f9d11e0-887a-4fba-916c-d4f401a8e318n%40googlegroups.com.

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

For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the Fine 
Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a connection 
to Ecowitt to set the Time/Date and automatically downloaded the 
EasyWeather 1.56 firmware update from Ecowitt. 

I haven't got the outdoor setup done yet, while i play with getting the 
unit up and running. but Ecowitt, shows my indoor temperature and pressure 
on the home page. I use pfsense so can run a packet capture if it helps. 
Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
this is related to me using European accented characters in my editors 
which are UTF-8. So that leaves me with two questions;
1) how to have it accept the UTF-8 characters
2) you mentioned not getting all the sensor data, unless using Ecowitt. In 
view, that i am. Can you tell me what additional parameters i need in the 
config file please.



On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:

> almost there, but now 
>
> /usr/local/share/weewx # ./bin/wee_reports
>
> Traceback (most recent call last):
>   File "./bin/wee_reports", line 103, in 
> main()
>   File "./bin/wee_reports", line 51, in main
> config_path, config_dict = weecfg.read_config(options.config_path, 
> args)
>   File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
> read_config
> default_encoding='utf-8')
>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, 
> in __init__
> self._load(infile, configspec)
>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, 
> in _load
> content = self._handle_bom(content)
>
> On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:
>
>> 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.

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

thanks for the clarification. i will switch the protocol to ecowitt, but 
the more immediate problem is the UTF-8 error which is now preventing weewx 
from starting.

On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:

> This thread started with the discussion being around the Ambient WS-2902 
> and that is totally different despite looking like the same unit. This is 
> because Ambient is the only Fine Offset clone reseller that changes the 
> firmware and they limit options. The Ambient version does not let you 
> upload to custom server address. The confusion here is that my response was 
> because I thought you had and Ambient branded unit. Since you don't have an 
> Ambient branded unit you do have the option to send to a custom server 
> using both WU and Ecowitt protocols. The WU protocol is limited and only 
> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
> sensorsetc. But still you'll have to configure the Interceptor driver 
> to match the protocol type that you set in you WH2900C for uploading to 
> your custom server. 
>
> The GW1000 though is still a more elegant and newer solution. 
>
> * The newest Ambient WS-2902 firmware finally after many years does gain 
> the ability to send to a custom serverBUT it is not WU protocol and it 
> is not Ecowitt protocolit is Ambientweather.net protocol and enough 
> significant differences that the Interceptor driver will not work. This 
> newest firmware is not yet officially supported by Ambient. They haven't 
> yet release the updated awnet mobile app to enable turning and configuring 
> this option. All of these complexities and changing nature of the situation 
> makes it difficult to explain the situation to cover all possible 
> scenarios...what model you have and whom it is from and what firmware 
> version you are running and all the different supporting protocols that are 
> possible. 
>
> Using pfsense to capture and forward packets is really unnecessary for 
> anyone with a non-Ambient WH2900Cas it has a built in simple to 
> configure "Customized" server upload feature.
>
>
>
> On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:
>
>> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the 
>> Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a 
>> connection to Ecowitt to set the Time/Date and automatically downloaded the 
>> EasyWeather 1.56 firmware update from Ecowitt. 
>>
>> I haven't got the outdoor setup done yet, while i play with getting the 
>> unit up and running. but Ecowitt, shows my indoor temperature and pressure 
>> on the home page. I use pfsense so can run a packet capture if it helps. 
>> Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
>> this is related to me using European accented characters in my editors 
>> which are UTF-8. So that leaves me with two questions;
>> 1) how to have it accept the UTF-8 characters
>> 2) you mentioned not getting all the sensor data, unless using Ecowitt. 
>> In view, that i am. Can you tell me what additional parameters i need in 
>> the config file please.
>>
>>
>>
>> On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:
>>
>>> almost there, but now 
>>>
>>> /usr/local/share/weewx # ./bin/wee_reports
>>>
>>> Traceback (most recent call last):
>>>   File "./bin/wee_reports", line 103, in 
>>> main()
>>>   File "./bin/wee_reports", line 51, in main
>>> config_path, config_dict = weecfg.read_config(options.config_path, 
>>> args)
>>>   File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
>>> read_config
>>> default_encoding='utf-8')
>>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, 
>>> in __init__
>>> self._load(infile, configspec)
>>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, 
>>> in _load
>>> content = self._handle_bom(content)
>>>
>>> On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:
>>>
>>>> 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

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

i figured out the utf-8 issue. weewx.conf has to be in utf, but i made the 
mistake of editing in the shell with edit. once i used geany and change the 
encoding back to utf-8 it came good. 

current status is; 
- console updates both ecowitt and wunderground online every minute. 
- config using ecowitt protocol with custom config pointing to local 
freenas jail / weewx server - path = index.php?
- using seasons default report 
- weewx is not upating and pfsense is showing me below with a packet 
capture, but no rules are blocking.
- i have tcp options enabled on both rules (WEEWX and WH2900C are on 
different VLANs)

222.968670WH2900CWEEWXTCP5820150 → 8080 [SYN] Seq=0 
Win=5840 Len=0 MSS=1460
232.969709WEEWXWH2900CTCP548080 → 20150 [RST, ACK] 
Seq=1 Ack=1 Win=0 Len=0


On Sunday, January 17, 2021 at 8:54:36 PM UTC+1 lang@googlemail.com 
wrote:

> As a workaround I would remove / replace your suspects - change "Umlaute", 
> if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit them and leave 
> the vowels without them.
> They will anyway only appear in temporary graphs. Then figure out your 
> UTF-8 issue and fix it, while your weewx could already run and archive data.
> On 17.01.2021 19:59, S R wrote:
>
> thanks for the clarification. i will switch the protocol to ecowitt, but 
> the more immediate problem is the UTF-8 error which is now preventing weewx 
> from starting.
>
> On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:
>
>> This thread started with the discussion being around the Ambient WS-2902 
>> and that is totally different despite looking like the same unit. This is 
>> because Ambient is the only Fine Offset clone reseller that changes the 
>> firmware and they limit options. The Ambient version does not let you 
>> upload to custom server address. The confusion here is that my response was 
>> because I thought you had and Ambient branded unit. Since you don't have an 
>> Ambient branded unit you do have the option to send to a custom server 
>> using both WU and Ecowitt protocols. The WU protocol is limited and only 
>> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
>> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
>> sensorsetc. But still you'll have to configure the Interceptor driver 
>> to match the protocol type that you set in you WH2900C for uploading to 
>> your custom server.  
>>
>> The GW1000 though is still a more elegant and newer solution. 
>>
>> * The newest Ambient WS-2902 firmware finally after many years does gain 
>> the ability to send to a custom serverBUT it is not WU protocol and it 
>> is not Ecowitt protocolit is Ambientweather.net protocol and enough 
>> significant differences that the Interceptor driver will not work. This 
>> newest firmware is not yet officially supported by Ambient. They haven't 
>> yet release the updated awnet mobile app to enable turning and configuring 
>> this option. All of these complexities and changing nature of the situation 
>> makes it difficult to explain the situation to cover all possible 
>> scenarios...what model you have and whom it is from and what firmware 
>> version you are running and all the different supporting protocols that are 
>> possible. 
>>
>> Using pfsense to capture and forward packets is really unnecessary for 
>> anyone with a non-Ambient WH2900Cas it has a built in simple to 
>> configure "Customized" server upload feature.
>>
>>
>>
>> On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:
>>
>>> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the 
>>> Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a 
>>> connection to Ecowitt to set the Time/Date and automatically downloaded the 
>>> EasyWeather 1.56 firmware update from Ecowitt. 
>>>
>>> I haven't got the outdoor setup done yet, while i play with getting the 
>>> unit up and running. but Ecowitt, shows my indoor temperature and pressure 
>>> on the home page. I use pfsense so can run a packet capture if it helps. 
>>> Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
>>> this is related to me using European accented characters in my editors 
>>> which are UTF-8. So that leaves me with two questions;
>>> 1) how to have it accept the UTF-8 characters
>>> 2) you mentioned not getting all the sensor data, unless using Ecowitt. 
>>> In view, that i am. Can you tell me what additional parameters i need in 
>>> th

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

2021-01-18 Thread S R

I see in interceptor.py the default interface is DEFAULT_IFACE = 'eth0'
if i do ifconfig in the shell to the jail, the interface is  'epair0b'

should i be changing the interface? 
still can't the debug to work. 

On Monday, January 18, 2021 at 8:55:28 AM UTC+1 S R wrote:

> i figured out the utf-8 issue. weewx.conf has to be in utf, but i made the 
> mistake of editing in the shell with edit. once i used geany and change the 
> encoding back to utf-8 it came good. 
>
> current status is; 
> - console updates both ecowitt and wunderground online every minute. 
> - config using ecowitt protocol with custom config pointing to local 
> freenas jail / weewx server - path = index.php?
> - using seasons default report 
> - weewx is not upating and pfsense is showing me below with a packet 
> capture, but no rules are blocking.
> - i have tcp options enabled on both rules (WEEWX and WH2900C are on 
> different VLANs)
>
> 222.968670WH2900CWEEWXTCP5820150 → 8080 [SYN] 
> Seq=0 Win=5840 Len=0 MSS=1460
> 232.969709WEEWXWH2900CTCP548080 → 20150 [RST, ACK] 
> Seq=1 Ack=1 Win=0 Len=0
>
>
> On Sunday, January 17, 2021 at 8:54:36 PM UTC+1 lang@googlemail.com 
> wrote:
>
>> As a workaround I would remove / replace your suspects - change 
>> "Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit them 
>> and leave the vowels without them.
>> They will anyway only appear in temporary graphs. Then figure out your 
>> UTF-8 issue and fix it, while your weewx could already run and archive data.
>> On 17.01.2021 19:59, S R wrote:
>>
>> thanks for the clarification. i will switch the protocol to ecowitt, but 
>> the more immediate problem is the UTF-8 error which is now preventing weewx 
>> from starting.
>>
>> On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:
>>
>>> This thread started with the discussion being around the Ambient WS-2902 
>>> and that is totally different despite looking like the same unit. This is 
>>> because Ambient is the only Fine Offset clone reseller that changes the 
>>> firmware and they limit options. The Ambient version does not let you 
>>> upload to custom server address. The confusion here is that my response was 
>>> because I thought you had and Ambient branded unit. Since you don't have an 
>>> Ambient branded unit you do have the option to send to a custom server 
>>> using both WU and Ecowitt protocols. The WU protocol is limited and only 
>>> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
>>> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
>>> sensorsetc. But still you'll have to configure the Interceptor driver 
>>> to match the protocol type that you set in you WH2900C for uploading to 
>>> your custom server.  
>>>
>>> The GW1000 though is still a more elegant and newer solution. 
>>>
>>> * The newest Ambient WS-2902 firmware finally after many years does gain 
>>> the ability to send to a custom serverBUT it is not WU protocol and it 
>>> is not Ecowitt protocolit is Ambientweather.net protocol and enough 
>>> significant differences that the Interceptor driver will not work. This 
>>> newest firmware is not yet officially supported by Ambient. They haven't 
>>> yet release the updated awnet mobile app to enable turning and configuring 
>>> this option. All of these complexities and changing nature of the situation 
>>> makes it difficult to explain the situation to cover all possible 
>>> scenarios...what model you have and whom it is from and what firmware 
>>> version you are running and all the different supporting protocols that are 
>>> possible. 
>>>
>>> Using pfsense to capture and forward packets is really unnecessary for 
>>> anyone with a non-Ambient WH2900Cas it has a built in simple to 
>>> configure "Customized" server upload feature.
>>>
>>>
>>>
>>> On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:
>>>
>>>> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the 
>>>> Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a 
>>>> connection to Ecowitt to set the Time/Date and automatically downloaded 
>>>> the 
>>>> EasyWeather 1.56 firmware update from Ecowitt. 
>>>>
>>>> I haven't got the outdoor setup done yet, while i play with getting the 
>>>>

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

2021-01-18 Thread S R

i put in the network network, but i can't get the interceptor.py debug to 
run. keeps falling over on the driver import line


On Monday, January 18, 2021 at 12:14:07 PM UTC+1 lang@googlemail.com 
wrote:

> I suggest that you first get weewx running with the interceptor driver in 
> a simple "normal" test environment.
> e.g. weewx host and console in the same subnet, no other fancy network and 
> virtualization constructions.
>
> Once that works, start changing step by step the test environment towards 
> your finally planned setup and 
> work out the issues on the path. Imho only such a systematic approach will 
> lead you to the goal.
>
> Many of your questions seem to come from your complex environment, and as 
> long as you don' find anyone
> who completely understands your architecture (who would probably need a 
> scheme, description, picture),
> the components used, their impact etc., you will most likely not get the 
> proper answers. 
>
> I suggest moving from simple to complex.
> epair0b is obviously a freenas speciality ...
>
> On 18.01.2021 12:00, S R wrote:
>
> I see in interceptor.py the default interface is DEFAULT_IFACE = 'eth0'
> if i do ifconfig in the shell to the jail, the interface is  'epair0b'
>
> should i be changing the interface? 
> still can't the debug to work. 
>
> On Monday, January 18, 2021 at 8:55:28 AM UTC+1 S R wrote:
>
>> i figured out the utf-8 issue. weewx.conf has to be in utf, but i made 
>> the mistake of editing in the shell with edit. once i used geany and change 
>> the encoding back to utf-8 it came good. 
>>
>> current status is; 
>> - console updates both ecowitt and wunderground online every minute. 
>> - config using ecowitt protocol with custom config pointing to local 
>> freenas jail / weewx server - path = index.php?
>> - using seasons default report 
>> - weewx is not upating and pfsense is showing me below with a packet 
>> capture, but no rules are blocking.
>> - i have tcp options enabled on both rules (WEEWX and WH2900C are on 
>> different VLANs)
>>
>> 222.968670WH2900CWEEWXTCP5820150 → 8080 [SYN] 
>> Seq=0 Win=5840 Len=0 MSS=1460
>> 232.969709WEEWXWH2900CTCP548080 → 20150 [RST, 
>> ACK] Seq=1 Ack=1 Win=0 Len=0
>>
>>
>> On Sunday, January 17, 2021 at 8:54:36 PM UTC+1 lang@googlemail.com 
>> wrote:
>>
>>> As a workaround I would remove / replace your suspects - change 
>>> "Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit them 
>>> and leave the vowels without them.
>>> They will anyway only appear in temporary graphs. Then figure out your 
>>> UTF-8 issue and fix it, while your weewx could already run and archive data.
>>> On 17.01.2021 19:59, S R wrote:
>>>
>>> thanks for the clarification. i will switch the protocol to ecowitt, but 
>>> the more immediate problem is the UTF-8 error which is now preventing weewx 
>>> from starting.
>>>
>>> On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:
>>>
>>>> This thread started with the discussion being around the Ambient 
>>>> WS-2902 and that is totally different despite looking like the same unit. 
>>>> This is because Ambient is the only Fine Offset clone reseller that 
>>>> changes 
>>>> the firmware and they limit options. The Ambient version does not let you 
>>>> upload to custom server address. The confusion here is that my response 
>>>> was 
>>>> because I thought you had and Ambient branded unit. Since you don't have 
>>>> an 
>>>> Ambient branded unit you do have the option to send to a custom server 
>>>> using both WU and Ecowitt protocols. The WU protocol is limited and only 
>>>> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
>>>> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
>>>> sensorsetc. But still you'll have to configure the Interceptor driver 
>>>> to match the protocol type that you set in you WH2900C for uploading to 
>>>> your custom server.  
>>>>
>>>> The GW1000 though is still a more elegant and newer solution. 
>>>>
>>>> * The newest Ambient WS-2902 firmware finally after many years does 
>>>> gain the ability to send to a custom serverBUT it is not WU protocol 
>>>> and it is not Ecowitt protocolit is Ambientweather.net protocol and 
>>>> enoug

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

2021-01-19 Thread S R

so, i connected the station on the same segment as the weewx server (using 
the linux desktop for proof of concept). 

I am successfully sending / receiving on Port 8000.
Example HTTP/1.1 that is sent. 

HTML Form URL Encoded: application/x-www-form-urlencoded
Form item: "PASSKEY" = "xxx"
Form item: "stationtype" = "EasyWeatherV1.5.6"
Form item: "dateutc" = "2021-01-19 14:07:31"
Form item: "tempinf" = "77.2"
Form item: "humidityin" = "41"
Form item: "baromrelin" = "29.537"
Form item: "baromabsin" = "29.315"
Form item: "freq" = "433M"
Form item: "model" = "WS2900C_V2.01.10"

But using the seasons skin, i am not seeing any updates in the data.




On Monday, January 18, 2021 at 4:02:31 PM UTC+1 S R wrote:

> i put in the network network, but i can't get the interceptor.py debug to 
> run. keeps falling over on the driver import line
>
>
> On Monday, January 18, 2021 at 12:14:07 PM UTC+1 lang@googlemail.com 
> wrote:
>
>> I suggest that you first get weewx running with the interceptor driver in 
>> a simple "normal" test environment.
>> e.g. weewx host and console in the same subnet, no other fancy network 
>> and virtualization constructions.
>>
>> Once that works, start changing step by step the test environment towards 
>> your finally planned setup and 
>> work out the issues on the path. Imho only such a systematic approach 
>> will lead you to the goal.
>>
>> Many of your questions seem to come from your complex environment, and as 
>> long as you don' find anyone
>> who completely understands your architecture (who would probably need a 
>> scheme, description, picture),
>> the components used, their impact etc., you will most likely not get the 
>> proper answers. 
>>
>> I suggest moving from simple to complex.
>> epair0b is obviously a freenas speciality ...
>>
>> On 18.01.2021 12:00, S R wrote:
>>
>> I see in interceptor.py the default interface is DEFAULT_IFACE = 'eth0'
>> if i do ifconfig in the shell to the jail, the interface is  'epair0b'
>>
>> should i be changing the interface? 
>> still can't the debug to work. 
>>
>> On Monday, January 18, 2021 at 8:55:28 AM UTC+1 S R wrote:
>>
>>> i figured out the utf-8 issue. weewx.conf has to be in utf, but i made 
>>> the mistake of editing in the shell with edit. once i used geany and change 
>>> the encoding back to utf-8 it came good. 
>>>
>>> current status is; 
>>> - console updates both ecowitt and wunderground online every minute. 
>>> - config using ecowitt protocol with custom config pointing to local 
>>> freenas jail / weewx server - path = index.php?
>>> - using seasons default report 
>>> - weewx is not upating and pfsense is showing me below with a packet 
>>> capture, but no rules are blocking.
>>> - i have tcp options enabled on both rules (WEEWX and WH2900C are on 
>>> different VLANs)
>>>
>>> 222.968670WH2900CWEEWXTCP5820150 → 8080 [SYN] 
>>> Seq=0 Win=5840 Len=0 MSS=1460
>>> 232.969709WEEWXWH2900CTCP548080 → 20150 [RST, 
>>> ACK] Seq=1 Ack=1 Win=0 Len=0
>>>
>>>
>>> On Sunday, January 17, 2021 at 8:54:36 PM UTC+1 lang@googlemail.com 
>>> wrote:
>>>
>>>> As a workaround I would remove / replace your suspects - change 
>>>> "Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit them 
>>>> and leave the vowels without them.
>>>> They will anyway only appear in temporary graphs. Then figure out your 
>>>> UTF-8 issue and fix it, while your weewx could already run and archive 
>>>> data.
>>>> On 17.01.2021 19:59, S R wrote:
>>>>
>>>> thanks for the clarification. i will switch the protocol to ecowitt, 
>>>> but the more immediate problem is the UTF-8 error which is now preventing 
>>>> weewx from starting.
>>>>
>>>> On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:
>>>>
>>>>> This thread started with the discussion being around the Ambient 
>>>>> WS-2902 and that is totally different despite looking like the same unit. 
>>>>> This is because Ambient is the only Fine Offset clone reseller that 
>>>>> changes 
>>>>> the firmware and

[weewx-user] wee_database sdb --create success but --check fails

2021-01-21 Thread S R

if i run wee_database -- check on the sdb that was installed during the
installed, it passes.
if i rename the original sdb and then run wee_database --create, the file
creates without error, but if i then immediately run the --check i get the
below error

sudo wee_database --check
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'weewx'
Checking daily summary tables version...
Daily summary tables are at version 3.0
Interval Weighting Fix is not required.
Daily summary tables version check completed in 0.01 seconds.
Preparing Null String Fix, this may take a while...
Traceback (most recent call last):
File "/usr/share/weewx/wee_database", line 1020, in
main()
File "/usr/share/weewx/wee_database", line 159, in main
check(config_dict, db_binding, options)
File "/usr/share/weewx/wee_database", line 582, in check
check_strings(config_dict, db_binding, options, fix=False)
File "/usr/share/weewx/wee_database", line 848, in check_strings
% (records, timestamp_to_string(record[0])), end=' ')
UnboundLocalError: local variable 'record' referenced before assignment

--
You received this message because you are subscribed 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/50265d72-27cc-4131-b4d7-d62bca674fe7n%40googlegroups.com.

Re: [weewx-user] wee_database sdb --create success but --check fails

2021-01-21 Thread S R

i also get 
./bin/wee_database --update
Using configuration file /usr/local/share/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_sqlite'
The update process does not affect archive data, but does alter the 
database.
Continue (y/n)? y
Preparing Interval Weighting Fix...
Daily summary tables are at version 3.0
Interval weighting fix is not required.
Preparing Maximum windSpeed Fix...
Traceback (most recent call last):
  File "./bin/wee_database", line 1020, in 
main()
  File "./bin/wee_database", line 162, in main
update(config_dict, db_binding, options)
  File "./bin/wee_database", line 639, in update
_fix_wind(config_dict, db_binding, options)
  File "./bin/wee_database", line 742, in _fix_wind
wind_obj.run()
  File "/usr/local/share/weewx/bin/weecfg/database.py"


On Thursday, January 21, 2021 at 11:15:52 PM UTC+1 tke...@gmail.com wrote:

> Not exactly a big problem, but fixed in commit 0f67337 
> <https://github.com/weewx/weewx/commit/0f67337e70d99c57893b1998ce5fcc7c05c636a6>
> .
>
>
> On Thu, Jan 21, 2021 at 12:53 PM John Kline  wrote:
>
>> Tom, the lines starting at line number 846 in wee_database need to be 
>> skipped if records == 0.  Not sure how you want to do that and whether you 
>> want a summary that says “no records in database”.  It will be easier for 
>> you to fix than to go back and forth with a PR.
>>
>> On Jan 21, 2021, at 12:42 PM, John Kline  wrote:
>>
>> 
>> I had a look.  This does not mean the database is bad.  The code needs a 
>> small fix as it’s using a variable that isn’t set if there are no records 
>> in the database.
>>
>> On Jan 21, 2021, at 12:37 PM, S R  wrote:
>>
>> 
>> if i run wee_database -- check on the sdb that was installed during the 
>> installed, it passes. 
>> if i rename the original sdb and then run wee_database --create, the file 
>> creates without error, but if i then immediately run the --check i get the 
>> below error 
>>
>> sudo wee_database --check 
>> Using configuration file /etc/weewx/weewx.conf 
>> Using database binding 'wx_binding', which is bound to database 'weewx' 
>> Checking daily summary tables version... 
>> Daily summary tables are at version 3.0 
>> Interval Weighting Fix is not required. 
>> Daily summary tables version check completed in 0.01 seconds. 
>> Preparing Null String Fix, this may take a while... 
>> Traceback (most recent call last): 
>>  File "/usr/share/weewx/wee_database", line 1020, in  
>>main() 
>>  File "/usr/share/weewx/wee_database", line 159, in main 
>>check(config_dict, db_binding, options) 
>>  File "/usr/share/weewx/wee_database", line 582, in check 
>>check_strings(config_dict, db_binding, options, fix=False) 
>>  File "/usr/share/weewx/wee_database", line 848, in check_strings 
>>% (records, timestamp_to_string(record[0])), end=' ') 
>> UnboundLocalError: local variable 'record' referenced before assignment
>>
>>
>> -- 
>> You received this message because you are subscribed 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/50265d72-27cc-4131-b4d7-d62bca674fe7n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/50265d72-27cc-4131-b4d7-d62bca674fe7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> -- 
>> You received this message because you are subscribed 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/07907469-7084-472A-9D1E-0F81685FD244%40johnkline.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/07907469-7084-472A-9D1E-0F81685FD244%40johnkline.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed 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/cc4b305b-3875-4e55-87ad-e48a496e98d5n%40googlegroups.com.

[weewx-user] Interceptor Bug: adding 'b' to POST: - user.interceptor: unrecognized parameter

2021-01-22 Thread S R

Packet capture shows below

POST  HTTP/1.1 
HOST: 192.168.x.x 
Connection: Close 
Content-Type: application/x-www-form-urlencoded 
Content-Length: 194 
 
PASSKEY=x&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:23:31&tempinf=75.2&humidityin=39&baromrelin=29.481&baromabsin=28.881&freq=433M&model=WS2900C_V2.01.10

however syslog shows 
22/1/21 9:20 AM   weewx.serviceweewx[125650] DEBUG user.interceptor: 
POST: *b*
'PASSKEY=&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:21:31&tempinf=75.2&humidityin=39&baromrelin=29.478&baromabsin=28.878&freq=433M&model=WS2900C_V2.01.10'
22/1/21 9:20 AM   weewx.serviceweewx[125650] DEBUG user.interceptor: 
raw data: *b*'PASSKEY= 
stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:21:31&tempinf=75.2&humidityin=39&baromrelin=29.478&baromabsin=28.878&freq=433M&model=WS2900C_V2.01.10'
22/1/21 9:20 AMweewx.serviceweewx[125650] INFO user.interceptor: 
unrecognized parameter *b*'PASSKEY=


-- 
You received this message because you are subscribed 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/0b21b543-8b16-4b78-afa9-a640ced85e0en%40googlegroups.com.

[weewx-user] Re: python3 with weewx4 and interceptor 0.54

2021-01-22 Thread S R

can you please clarify precisely what you setting you are referring to
"error where the /data/report/ path for the web-call on the station was 
changed - setting this back to the standard path"

aside from a couple of initial connections after weewx is restarted, my log 
then becomes full with this message and the db is not updated at all.

On Friday, May 1, 2020 at 4:20:27 PM UTC+2 gary@gmail.com wrote:

>
>
> On Friday, May 1, 2020 at 10:02:21 AM UTC-4, Max Gutberlet wrote:
>>
>> Reporting success(ish)
>>
>> Spend another 8 hours playing with this, got it to work but not without 
>> caveats:
>>
>> Did a squeaky clean install based on Matts new 4.0 deb package and using 
>> the 0.54b interceptor with  the latest GIT commit on the PASSKEY.
>>
>> - listen mode works using ecowitt-client - that was a RTFM error where 
>> the /data/report/ path for the web-call on the station was changed - setting
>>   this back to the standard path made this work - so happily logging data 
>> again. Btw, my system is running EasyWeather1.4.9 firmware.
>>
>>
> Glad to hear it works as ecowitt-client, I was stumped.
>
> As for the sniff, Ubuntu 20 has many functions supplied by a snap. Are you 
> installing via apt or via pip? May (or may not) make a difference.
> Take a look at how Tom installs to localenv;
> https://groups.google.com/d/msg/weewx-user/yG0aTuyosOc/Vo4bvUBNAAAJ
>

-- 
You received this message because you are subscribed 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/59c145a0-fcd8-420e-9406-a5376e1a0b19n%40googlegroups.com.

[weewx-user] Re: Interceptor Bug: adding 'b' to POST: - user.interceptor: unrecognized parameter

2021-01-22 Thread S R

Is the Interceptor driver not being actively maintained? 

https://github.com/matthewwall/weewx-interceptor/issues/80


On Friday, January 22, 2021 at 9:28:59 AM UTC+1 S R wrote:

> Packet capture shows below
>
> POST  HTTP/1.1 
> HOST: 192.168.x.x 
> Connection: Close 
> Content-Type: application/x-www-form-urlencoded 
> Content-Length: 194 
>  
>
> PASSKEY=x&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:23:31&tempinf=75.2&humidityin=39&baromrelin=29.481&baromabsin=28.881&freq=433M&model=WS2900C_V2.01.10
>
> however syslog shows 
> 22/1/21 9:20 AM   weewx.serviceweewx[125650] DEBUG user.interceptor: 
> POST: *b*
> 'PASSKEY=&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:21:31&tempinf=75.2&humidityin=39&baromrelin=29.478&baromabsin=28.878&freq=433M&model=WS2900C_V2.01.10'
> 22/1/21 9:20 AM   weewx.serviceweewx[125650] DEBUG user.interceptor: 
> raw data: *b*'PASSKEY= 
> stationtype=EasyWeatherV1.5.6&dateutc=2021-01-22+08:21:31&tempinf=75.2&humidityin=39&baromrelin=29.478&baromabsin=28.878&freq=433M&model=WS2900C_V2.01.10'
> 22/1/21 9:20 AMweewx.serviceweewx[125650] INFO user.interceptor: 
> unrecognized parameter *b*'PASSKEY=
>
>
>

-- 
You received this message because you are subscribed 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/a5b43e9e-cae5-4e56-89cd-231b44255769n%40googlegroups.com.

[weewx-user] simulator - generator critical crash

really can't get anything to work. 

simulator - simulator mode. weewx uptime =0
simulator - genarator mode - has below crash. 

python3[41323]: weewx[41323] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 272, in addRecord 
python3[41323]: weewx[41323] CRITICAL __main__:  
 self._updateHiLo(accumulator, cursor) 
python3[41323]: weewx[41323] CRITICAL __main__: File 
"/usr/share/weewx/weewx/manager.py", line 933, in _updateHiLo 
python3[41323]: weewx[41323] CRITICAL __main__:  
 _stats_dict.updateHiLo(accumulator) 
python3[41323]: weewx[41323] CRITICAL __main__: File 
"/usr/share/weewx/weewx/accum.py", line 444, in updateHiLo 
python3[41323]: weewx[41323] CRITICAL __main__:  
 self._check_units(accumulator.unit_system) 
python3[41323]: weewx[41323] CRITICAL __main__: File 
"/usr/share/weewx/weewx/accum.py", line 615, in _check_units 
python3[41323]: weewx[41323] CRITICAL __main__:   raise 
ValueError("Unit system mismatch %d v. %d" % (self.unit_system, 
python3[41323]: weewx[41323] CRITICAL __main__:   ValueError: Unit 
system mismatch 16 v. 1 
python3[41323]: weewx[41323] CRITICAL __main__:   Exiting.

are there any other alternatives to weewx? i'm ready to give up on it

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com.

Re: [weewx-user] simulator - generator critical crash

Hi Tom, 
I did a fresh install using the debian package method on Ubuntu 20.10.
I selected simulator during the prompted install and only added debug=1

The version of python3 is 3.8.6 from ubuntu

One thing of note, is: 

sudo apt install python3-sqlite 
Reading package lists... Done 
Building dependency tree
Reading state information... Done 
Package python3-sqlite is not available, but is referred to by another 
package. 
This may mean that the package is missing, has been obsoleted, or 
is only available from another source 
E: Package 'python3-sqlite' has no installation candidate

debug enclosed

thx


On Sunday, January 24, 2021 at 7:59:18 PM UTC+1 tke...@gmail.com wrote:

> Have you modified the simulator at all?
>
> It would be helpful if we saw the log from startup. Set debug=1 (in 
> weewx.conf), restart weewx, then post the log from startup to when it 
> crashed.
>
> If it makes you feel any better, this is the first time I've seen this.
>
> -tk
>
> On Sun, Jan 24, 2021 at 8:31 AM S R  wrote:
>
>> really can't get anything to work. 
>>
>> simulator - simulator mode. weewx uptime =0
>> simulator - genarator mode - has below crash. 
>>
>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 272, in addRecord 
>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>  self._updateHiLo(accumulator, cursor) 
>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/manager.py", line 933, in _updateHiLo 
>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>  _stats_dict.updateHiLo(accumulator) 
>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/accum.py", line 444, in updateHiLo 
>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>  self._check_units(accumulator.unit_system) 
>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>> "/usr/share/weewx/weewx/accum.py", line 615, in _check_units 
>> python3[41323]: weewx[41323] CRITICAL __main__:   raise 
>> ValueError("Unit system mismatch %d v. %d" % (self.unit_system, 
>> python3[41323]: weewx[41323] CRITICAL __main__:   ValueError: 
>> Unit system mismatch 16 v. 1 
>> python3[41323]: weewx[41323] CRITICAL __main__:   Exiting.
>>
>> are there any other alternatives to weewx? i'm ready to give up on it
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed 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/8ada322b-1a43-4074-b45e-a75f94efbdb5n%40googlegroups.com.

Re: [weewx-user] simulator - generator critical crash

now with the log

On Sunday, January 24, 2021 at 9:22:49 PM UTC+1 S R wrote:

> Hi Tom, 
> I did a fresh install using the debian package method on Ubuntu 20.10.
> I selected simulator during the prompted install and only added debug=1
>
> The version of python3 is 3.8.6 from ubuntu
>
> One thing of note, is: 
>
> sudo apt install python3-sqlite 
> Reading package lists... Done 
> Building dependency tree
> Reading state information... Done 
> Package python3-sqlite is not available, but is referred to by another 
> package. 
> This may mean that the package is missing, has been obsoleted, or 
> is only available from another source 
> E: Package 'python3-sqlite' has no installation candidate
>
> debug enclosed
>
> thx
>
>
> On Sunday, January 24, 2021 at 7:59:18 PM UTC+1 tke...@gmail.com wrote:
>
>> Have you modified the simulator at all?
>>
>> It would be helpful if we saw the log from startup. Set debug=1 (in 
>> weewx.conf), restart weewx, then post the log from startup to when it 
>> crashed.
>>
>> If it makes you feel any better, this is the first time I've seen this.
>>
>> -tk
>>
>> On Sun, Jan 24, 2021 at 8:31 AM S R  wrote:
>>
>>> really can't get anything to work. 
>>>
>>> simulator - simulator mode. weewx uptime =0
>>> simulator - genarator mode - has below crash. 
>>>
>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/manager.py", line 272, in addRecord 
>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>  self._updateHiLo(accumulator, cursor) 
>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/manager.py", line 933, in _updateHiLo 
>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>  _stats_dict.updateHiLo(accumulator) 
>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/accum.py", line 444, in updateHiLo 
>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>  self._check_units(accumulator.unit_system) 
>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>> "/usr/share/weewx/weewx/accum.py", line 615, in _check_units 
>>> python3[41323]: weewx[41323] CRITICAL __main__:   raise 
>>> ValueError("Unit system mismatch %d v. %d" % (self.unit_system, 
>>> python3[41323]: weewx[41323] CRITICAL __main__:   ValueError: 
>>> Unit system mismatch 16 v. 1 
>>> python3[41323]: weewx[41323] CRITICAL __main__:   Exiting.
>>>
>>> are there any other alternatives to weewx? i'm ready to give up on it
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed 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/a8965516-df09-4235-82ca-7924d74bb208n%40googlegroups.com.
24/1/21 8:32 PM	weewx.service	weewx[5160] INFO __main__: Starting up weewx version 4.3.0
24/1/21 8:32 PM	weewx.service	weewx[5160] INFO weewx.engine: Clock error is -0.29 seconds (positive is fast)
24/1/21 8:32 PM	weewx.service	weewx[5160] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
24/1/21 8:32 PM	weewx.service	weewx[5160] INFO weewx.manager: Starting backfill of daily summaries
24/1/21 8:32 PM	weewx.service	weewx[5160] INFO weewx.engine: Starting main packet loop.
24/1/21 8:33 PM	sudo	   stevo : TTY=pts/0 ; PWD=/etc/weewx ; USER=root ; COMMAND=/usr/bin/systemctl status weewx
24/1/21 8:35 PM	weewx.service	weewx[5160] INFO weewx.engine: Main loop exiting. Shutting engine down.
24/1/21 8:35 PM	weewx.service	weewx[5160] CRITICAL __main__: Caught unrecoverable exception:
24/1/21 8:35 PM	weewx.service	weewx[5160] CRITICAL __main

Re: [weewx-user] simulator - generator critical crash

Hi tom, as requested. 
@Vince, no doesn't mean anything to me. also, i should have been more 
specific. it is actually Kubuntu 20.10 that i am using. 

Bear in mind, i am trying to get this to work on Kubuntu, because i wasn't 
having any luck with a freebsd jail. 
so i thought i would prove the system on the more common linux. 

On Monday, January 25, 2021 at 3:01:01 AM UTC+1 tke...@gmail.com wrote:

> Please set debug=1 (in weewx.conf), restart weewx, then post the log *from 
> startup* to when it crashed.
>
> On Sun, Jan 24, 2021 at 12:23 PM S R  wrote:
>
>> now with the log
>>
>> On Sunday, January 24, 2021 at 9:22:49 PM UTC+1 S R wrote:
>>
>>> Hi Tom, 
>>> I did a fresh install using the debian package method on Ubuntu 20.10.
>>> I selected simulator during the prompted install and only added debug=1
>>>
>>> The version of python3 is 3.8.6 from ubuntu
>>>
>>> One thing of note, is: 
>>>
>>> sudo apt install python3-sqlite 
>>> Reading package lists... Done 
>>> Building dependency tree
>>> Reading state information... Done 
>>> Package python3-sqlite is not available, but is referred to by another 
>>> package. 
>>> This may mean that the package is missing, has been obsoleted, or 
>>> is only available from another source 
>>> E: Package 'python3-sqlite' has no installation candidate
>>>
>>> debug enclosed
>>>
>>> thx
>>>
>>>
>>> On Sunday, January 24, 2021 at 7:59:18 PM UTC+1 tke...@gmail.com wrote:
>>>
>>>> Have you modified the simulator at all?
>>>>
>>>> It would be helpful if we saw the log from startup. Set debug=1 (in 
>>>> weewx.conf), restart weewx, then post the log from startup to when it 
>>>> crashed.
>>>>
>>>> If it makes you feel any better, this is the first time I've seen this.
>>>>
>>>> -tk
>>>>
>>>> On Sun, Jan 24, 2021 at 8:31 AM S R  wrote:
>>>>
>>>>> really can't get anything to work. 
>>>>>
>>>>> simulator - simulator mode. weewx uptime =0
>>>>> simulator - genarator mode - has below crash. 
>>>>>
>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>> "/usr/share/weewx/weewx/manager.py", line 272, in addRecord 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>  self._updateHiLo(accumulator, cursor) 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>> "/usr/share/weewx/weewx/manager.py", line 933, in _updateHiLo 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>  _stats_dict.updateHiLo(accumulator) 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>> "/usr/share/weewx/weewx/accum.py", line 444, in updateHiLo 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>  self._check_units(accumulator.unit_system) 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>> "/usr/share/weewx/weewx/accum.py", line 615, in _check_units 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:   raise 
>>>>> ValueError("Unit system mismatch %d v. %d" % (self.unit_system, 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:   ValueError: 
>>>>> Unit system mismatch 16 v. 1 
>>>>> python3[41323]: weewx[41323] CRITICAL __main__:   Exiting.
>>>>>
>>>>> are there any other alternatives to weewx? i'm ready to give up on it
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to weewx-user+...@googlegroups.com.
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/weewx-user/76dc716b-8806-4100-aacb-448927d65ef0n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>> -- 
>> You received this me

Re: [weewx-user] simulator - generator critical crash

Hi Tom, yes. that sounds right. We use metric here, but I found the data 
being sent was in imperial, despite the device app setting being in metric. 
is the solution, delete the db and create a new one? 

What settings should i use; when the device sends imperial, and i want 
metric.

p.s. maybe an error handling routine in order?

Thanks

On Monday, January 25, 2021 at 2:03:54 PM UTC+1 tke...@gmail.com wrote:

> Thanks.
>
> What happened is that you started with a database that used METRIC units, 
> then later changed it to US. Unfortunately, you have to pick a unit system, 
> then stick with it.
>
> See the section [StdConvert] 
> <http://www.weewx.com/docs/usersguide.htm#StdConvert> in the User's Guide.
>
> -tk
>
> On Sun, Jan 24, 2021 at 10:10 PM S R  wrote:
>
>> Hi tom, as requested. 
>> @Vince, no doesn't mean anything to me. also, i should have been more 
>> specific. it is actually Kubuntu 20.10 that i am using. 
>>
>> Bear in mind, i am trying to get this to work on Kubuntu, because i 
>> wasn't having any luck with a freebsd jail. 
>> so i thought i would prove the system on the more common linux. 
>>
>> On Monday, January 25, 2021 at 3:01:01 AM UTC+1 tke...@gmail.com wrote:
>>
>>> Please set debug=1 (in weewx.conf), restart weewx, then post the log *from 
>>> startup* to when it crashed.
>>>
>>> On Sun, Jan 24, 2021 at 12:23 PM S R  wrote:
>>>
>>>> now with the log
>>>>
>>>> On Sunday, January 24, 2021 at 9:22:49 PM UTC+1 S R wrote:
>>>>
>>>>> Hi Tom, 
>>>>> I did a fresh install using the debian package method on Ubuntu 20.10.
>>>>> I selected simulator during the prompted install and only added debug=1
>>>>>
>>>>> The version of python3 is 3.8.6 from ubuntu
>>>>>
>>>>> One thing of note, is: 
>>>>>
>>>>> sudo apt install python3-sqlite 
>>>>> Reading package lists... Done 
>>>>> Building dependency tree
>>>>> Reading state information... Done 
>>>>> Package python3-sqlite is not available, but is referred to by another 
>>>>> package. 
>>>>> This may mean that the package is missing, has been obsoleted, or 
>>>>> is only available from another source 
>>>>> E: Package 'python3-sqlite' has no installation candidate
>>>>>
>>>>> debug enclosed
>>>>>
>>>>> thx
>>>>>
>>>>>
>>>>> On Sunday, January 24, 2021 at 7:59:18 PM UTC+1 tke...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Have you modified the simulator at all?
>>>>>>
>>>>>> It would be helpful if we saw the log from startup. Set debug=1 (in 
>>>>>> weewx.conf), restart weewx, then post the log from startup to when it 
>>>>>> crashed.
>>>>>>
>>>>>> If it makes you feel any better, this is the first time I've seen 
>>>>>> this.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>> On Sun, Jan 24, 2021 at 8:31 AM S R  wrote:
>>>>>>
>>>>>>> really can't get anything to work. 
>>>>>>>
>>>>>>> simulator - simulator mode. weewx uptime =0
>>>>>>> simulator - genarator mode - has below crash. 
>>>>>>>
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>>>> "/usr/share/weewx/weewx/manager.py", line 272, in addRecord 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>>>  self._updateHiLo(accumulator, cursor) 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>>>> "/usr/share/weewx/weewx/manager.py", line 933, in _updateHiLo 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>>>  _stats_dict.updateHiLo(accumulator) 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__: File 
>>>>>>> "/usr/share/weewx/weewx/accum.py", line 444, in updateHiLo 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__:  
>>>>>>>  self._check_units(accumulator.unit_system) 
>>>>>>> python3[41323]: weewx[41323] CRITICAL __main__:

Re: [weewx-user] simulator - generator critical crash

Hey tom, thanks. 
I re-created the db with US units and set metric in the reports. Simulator 
is working on ubuntu now. 
I will try to get this setup working in my freebsd jail before adding the 
interceptor to linux. 

dumb question. the climatogical report & summary - Name, is missing "ö" 
looks like it did not like UTF-8. 
is there a way to manually fix this?

On Monday, January 25, 2021 at 2:31:06 PM UTC+1 tke...@gmail.com wrote:

> 1. You will need to either delete the database and start all over, or set 
> the database unit system back to METRIC. 
>
> 2, Yes, the simulator emits packets in US, but if you use a METRIC 
> database, the packets will get converted. There is no need to try to match 
> device to database. The only requirement is to pick a database unit system, 
> then stick with it.
>
> 3. I do not know what you mean by "error handling routine."
>
> -tk
>
>
>
> On Mon, Jan 25, 2021 at 5:23 AM S R  wrote:
>
>> Hi Tom, yes. that sounds right. We use metric here, but I found the data 
>> being sent was in imperial, despite the device app setting being in metric. 
>> is the solution, delete the db and create a new one? 
>>
>> What settings should i use; when the device sends imperial, and i want 
>> metric.
>>
>> p.s. maybe an error handling routine in order?
>>
>> Thanks
>>
>> On Monday, January 25, 2021 at 2:03:54 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Thanks.
>>>
>>> What happened is that you started with a database that used METRIC 
>>> units, then later changed it to US. Unfortunately, you have to pick a unit 
>>> system, then stick with it.
>>>
>>> See the section [StdConvert] 
>>> <http://www.weewx.com/docs/usersguide.htm#StdConvert> in the User's 
>>> Guide.
>>>
>>> -tk
>>>
>>> On Sun, Jan 24, 2021 at 10:10 PM S R  wrote:
>>>
>>>> Hi tom, as requested. 
>>>> @Vince, no doesn't mean anything to me. also, i should have been more 
>>>> specific. it is actually Kubuntu 20.10 that i am using. 
>>>>
>>>> Bear in mind, i am trying to get this to work on Kubuntu, because i 
>>>> wasn't having any luck with a freebsd jail. 
>>>> so i thought i would prove the system on the more common linux. 
>>>>
>>>> On Monday, January 25, 2021 at 3:01:01 AM UTC+1 tke...@gmail.com wrote:
>>>>
>>>>> Please set debug=1 (in weewx.conf), restart weewx, then post the log 
>>>>> *from 
>>>>> startup* to when it crashed.
>>>>>
>>>>> On Sun, Jan 24, 2021 at 12:23 PM S R  wrote:
>>>>>
>>>>>> now with the log
>>>>>>
>>>>>> On Sunday, January 24, 2021 at 9:22:49 PM UTC+1 S R wrote:
>>>>>>
>>>>>>> Hi Tom, 
>>>>>>> I did a fresh install using the debian package method on Ubuntu 
>>>>>>> 20.10.
>>>>>>> I selected simulator during the prompted install and only added 
>>>>>>> debug=1
>>>>>>>
>>>>>>> The version of python3 is 3.8.6 from ubuntu
>>>>>>>
>>>>>>> One thing of note, is: 
>>>>>>>
>>>>>>> sudo apt install python3-sqlite 
>>>>>>> Reading package lists... Done 
>>>>>>> Building dependency tree
>>>>>>> Reading state information... Done 
>>>>>>> Package python3-sqlite is not available, but is referred to by 
>>>>>>> another package. 
>>>>>>> This may mean that the package is missing, has been obsoleted, or 
>>>>>>> is only available from another source 
>>>>>>> E: Package 'python3-sqlite' has no installation candidate
>>>>>>>
>>>>>>> debug enclosed
>>>>>>>
>>>>>>> thx
>>>>>>>
>>>>>>>
>>>>>>> On Sunday, January 24, 2021 at 7:59:18 PM UTC+1 tke...@gmail.com 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Have you modified the simulator at all?
>>>>>>>>
>>>>>>>> It would be helpful if we saw the log from startup. Set debug=1 (in 
>>>>>>>> weewx.conf), restart weewx, then post the log from startup to when it 
>>>>>>>> crashed.
>>>>>>>&g

Re: [weewx-user] How do I remove all the existing data and start again?

I've got the same problem. finished testing with the simulator, deleted the 
db and created again. 
cleared the browser cache on both chrome and firefox, but i goto the page 
and it shows 28.01 even though today is 25.01 and the data from when the 
simulator run


On Sunday, November 22, 2015 at 8:13:23 AM UTC+1 bjale...@gmail.com wrote:

> Haha magic indeed!
>
> I completely overlooked the internal logger in the station itself - thanks 
> very much for that.
>
>
> On Sunday, 22 November 2015 13:15:32 UTC+13, Tom Keffer wrote:
>>
>> Magic. :-)
>>
>> Your hardware must have an onboard logger. If you truly want a fresh 
>> start, you'll have to clear it. Specific instructions depends on the make 
>> of your hardware.
>>
>> -tk
>>
>> On Sat, Nov 21, 2015 at 3:52 PM, George Alexander  
>> wrote:
>>
>>>
>>>
>>> On Monday, 13 July 2015 09:28:49 UTC+12, mwall wrote:

 On Sunday, July 12, 2015 at 5:16:55 PM UTC-4, Dave Jeffries wrote:
>
> I used the setup.py method, just thought there may be a simple 
> command  to remove all the existing data.
> I guess the weewx.conf and skin.conf will be overwritten so will have 
> to take a copy first?
>

 if you do not care about any of the data in the database, then just 
 stop weewx, delete the database file (/home/weewx/archive/weewx.sdb), then 
 start weewx.

 if you want to surgically remove data from the database, do something 
 like this:


 *sqlite3 /home/weewx/archive/weewx.sdb*sqlite> *delete from archive 
 where dateTime < X;*

 where X is the timestamp (unix epoch) after which you started 
 collecting data from the real weather station.

 m 

>>>
>>> After trying the "Delete weewx.sdb" method for a refresh, when I 
>>> restarted weewx, the syslog showed it happily re-populating the database 
>>> with all my old data - where on earth did it get that from and how do I 
>>> stop it doing it again? 
>>>
>>> -- 
>>> You received this message because you are subscribed 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
You received this message because you are subscribed 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/5d1176ff-9e4a-43b8-96b4-55045ecb8a85n%40googlegroups.com.

Re: [weewx-user] How do I remove all the existing data and start again?

I just deleted the .sdb and then run wee_database --create. 

i don't see any cache data for nginx on either the ubuntu or freebsd 
versions i setup for testing, but they both show the same problem 


On Monday, January 25, 2021 at 10:10:47 PM UTC+1 gjr80 wrote:

> Did you delete any previously generated reports on both your WeeWX machine 
> and web server?
>
> Gary
>
> On Tuesday, 26 January 2021 at 06:40:48 UTC+10 sjr4...@gmail.com wrote:
>
>> I've got the same problem. finished testing with the simulator, deleted 
>> the db and created again. 
>> cleared the browser cache on both chrome and firefox, but i goto the page 
>> and it shows 28.01 even though today is 25.01 and the data from when the 
>> simulator run
>>
>>
>> On Sunday, November 22, 2015 at 8:13:23 AM UTC+1 bjale...@gmail.com 
>> wrote:
>>
>>> Haha magic indeed!
>>>
>>> I completely overlooked the internal logger in the station itself - 
>>> thanks very much for that.
>>>
>>>
>>> On Sunday, 22 November 2015 13:15:32 UTC+13, Tom Keffer wrote:

 Magic. :-)

 Your hardware must have an onboard logger. If you truly want a fresh 
 start, you'll have to clear it. Specific instructions depends on the make 
 of your hardware.

 -tk

 On Sat, Nov 21, 2015 at 3:52 PM, George Alexander  
 wrote:

>
>
> On Monday, 13 July 2015 09:28:49 UTC+12, mwall wrote:
>>
>> On Sunday, July 12, 2015 at 5:16:55 PM UTC-4, Dave Jeffries wrote:
>>>
>>> I used the setup.py method, just thought there may be a simple 
>>> command  to remove all the existing data.
>>> I guess the weewx.conf and skin.conf will be overwritten so will 
>>> have to take a copy first?
>>>
>>
>> if you do not care about any of the data in the database, then just 
>> stop weewx, delete the database file (/home/weewx/archive/weewx.sdb), 
>> then 
>> start weewx.
>>
>> if you want to surgically remove data from the database, do something 
>> like this:
>>
>>
>> *sqlite3 /home/weewx/archive/weewx.sdb*sqlite> *delete from archive 
>> where dateTime < X;*
>>
>> where X is the timestamp (unix epoch) after which you started 
>> collecting data from the real weather station.
>>
>> m 
>>
>
> After trying the "Delete weewx.sdb" method for a refresh, when I 
> restarted weewx, the syslog showed it happily re-populating the database 
> with all my old data - where on earth did it get that from and how do I 
> stop it doing it again? 
>
> -- 
> You received this message because you are subscribed 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
You received this message because you are subscribed 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/b467bb52-8601-4f17-b840-992cf2339888n%40googlegroups.com.

Re: [weewx-user] How do I remove all the existing data and start again?

deleted the entire html directory and run wee_reports and it is back with 
the simulator data... even though a db we deleted and created again

On Monday, January 25, 2021 at 11:20:26 PM UTC+1 peterq...@gmail.com wrote:

> There are .html pages on the web server public directory that your seeing
>
> On Mon, Jan 25, 2021, 1:16 PM S R  wrote:
>
>> I just deleted the .sdb and then run wee_database --create. 
>>
>> i don't see any cache data for nginx on either the ubuntu or freebsd 
>> versions i setup for testing, but they both show the same problem 
>>
>>
>> On Monday, January 25, 2021 at 10:10:47 PM UTC+1 gjr80 wrote:
>>
>>> Did you delete any previously generated reports on both your WeeWX 
>>> machine and web server?
>>>
>>> Gary
>>>
>>> On Tuesday, 26 January 2021 at 06:40:48 UTC+10 sjr4...@gmail.com wrote:
>>>
>>>> I've got the same problem. finished testing with the simulator, deleted 
>>>> the db and created again. 
>>>> cleared the browser cache on both chrome and firefox, but i goto the 
>>>> page and it shows 28.01 even though today is 25.01 and the data from when 
>>>> the simulator run
>>>>
>>>>
>>>> On Sunday, November 22, 2015 at 8:13:23 AM UTC+1 bjale...@gmail.com 
>>>> wrote:
>>>>
>>>>> Haha magic indeed!
>>>>>
>>>>> I completely overlooked the internal logger in the station itself - 
>>>>> thanks very much for that.
>>>>>
>>>>>
>>>>> On Sunday, 22 November 2015 13:15:32 UTC+13, Tom Keffer wrote:
>>>>>>
>>>>>> Magic. :-)
>>>>>>
>>>>>> Your hardware must have an onboard logger. If you truly want a fresh 
>>>>>> start, you'll have to clear it. Specific instructions depends on the 
>>>>>> make 
>>>>>> of your hardware.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>> On Sat, Nov 21, 2015 at 3:52 PM, George Alexander >>>>> > wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Monday, 13 July 2015 09:28:49 UTC+12, mwall wrote:
>>>>>>>>
>>>>>>>> On Sunday, July 12, 2015 at 5:16:55 PM UTC-4, Dave Jeffries wrote:
>>>>>>>>>
>>>>>>>>> I used the setup.py method, just thought there may be a simple 
>>>>>>>>> command  to remove all the existing data.
>>>>>>>>> I guess the weewx.conf and skin.conf will be overwritten so will 
>>>>>>>>> have to take a copy first?
>>>>>>>>>
>>>>>>>>
>>>>>>>> if you do not care about any of the data in the database, then just 
>>>>>>>> stop weewx, delete the database file (/home/weewx/archive/weewx.sdb), 
>>>>>>>> then 
>>>>>>>> start weewx.
>>>>>>>>
>>>>>>>> if you want to surgically remove data from the database, do 
>>>>>>>> something like this:
>>>>>>>>
>>>>>>>>
>>>>>>>> *sqlite3 /home/weewx/archive/weewx.sdb*sqlite> *delete from 
>>>>>>>> archive where dateTime < X;*
>>>>>>>>
>>>>>>>> where X is the timestamp (unix epoch) after which you started 
>>>>>>>> collecting data from the real weather station.
>>>>>>>>
>>>>>>>> m 
>>>>>>>>
>>>>>>>
>>>>>>> After trying the "Delete weewx.sdb" method for a refresh, when I 
>>>>>>> restarted weewx, the syslog showed it happily re-populating the 
>>>>>>> database 
>>>>>>> with all my old data - where on earth did it get that from and how do I 
>>>>>>> stop it doing it again? 
>>>>>>>
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed 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.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>
>>>>>> -- 
>> You received this message because you are subscribed 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/b467bb52-8601-4f17-b840-992cf2339888n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/b467bb52-8601-4f17-b840-992cf2339888n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed 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/8a737efe-6800-4492-b2a8-3847e4f3eb2en%40googlegroups.com.

Re: [weewx-user] simulator - generator critical crash

The staion name has a German umlaut in it. It shows correctly on the web 
pages, but in the NOAA files it misses the letter completely. 
e.g. name = "Köln", NOAA file has "Kln"

On Monday, January 25, 2021 at 11:52:49 PM UTC+1 tke...@gmail.com wrote:

> dumb question. the climatogical report & summary - Name, is missing "ö" 
>> looks like it did not like UTF-8. 
>> is there a way to manually fix this?
>>
>
> Not a dumb question at all, but I don't understand it either. What "ö"?
>

-- 
You received this message because you are subscribed 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/06ff3d83-d82d-4352-ac18-1db996d22059n%40googlegroups.com.

Re: [weewx-user] simulator - generator critical crash

wouldn't that make more sense to drop the umlaut and Düsseldorf = 
Dusseldorf - that is what other webservices do that can't deal with 
non-ascii characters. would be better than dropping the character completely

On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote:

> NOAA files use strict_ascii encoding 
>  so no 
> umlauts or other accented characters unfortunately. You can change the 
> encoding but as the NOAA format reports are tabulated reports it will mess 
> up the format of the report.
>
> Gary
>
> On Tuesday, 26 January 2021 at 15:53:23 UTC+10 sjr4...@gmail.com wrote:
>
>> The staion name has a German umlaut in it. It shows correctly on the web 
>> pages, but in the NOAA files it misses the letter completely. 
>> e.g. name = "Köln", NOAA file has "Kln"
>>
>> On Monday, January 25, 2021 at 11:52:49 PM UTC+1 tke...@gmail.com wrote:
>>
>>> dumb question. the climatogical report & summary - Name, is missing "ö" 
 looks like it did not like UTF-8. 
 is there a way to manually fix this?

>>>
>>> Not a dumb question at all, but I don't understand it either. What "ö"?
>>>
>>

-- 
You received this message because you are subscribed 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/2e7b2cd6-5504-472a-8e1f-f3d4a248224an%40googlegroups.com.

Re: [weewx-user] How do I remove all the existing data and start again?

done that mulitple times alreadyand more weirdness.

index web page is good - shows correct todays date (sessions template out 
of box)
day is good - shows todays date

week/month/year - shows date of 31.01 with simulator data.

On Tuesday, January 26, 2021 at 7:10:48 AM UTC+1 gjr80 wrote:

> Delete the html directory again (definitely on the WeeWX machine and also 
> delete the html/png files on your web server if applicable), delete the 
> database and restart WeeWX. Monitor the log, confirm a new database is 
> created (it will be logged) and which driver is being used. Confirm report 
> generation. If you still get old simulator data in a browser it’s a browser 
> cache issue or you have more than one WeeWX instance running or remnants 
> from another WeeWX instance. You can also take the browser out of the 
> equation and view the report output in an editor or cat it to your console.
>
> Gary
>
> On Tuesday, 26 January 2021 at 15:51:11 UTC+10 sjr4...@gmail.com wrote:
>
>> deleted the entire html directory and run wee_reports and it is back with 
>> the simulator data... even though a db we deleted and created again
>>
>> On Monday, January 25, 2021 at 11:20:26 PM UTC+1 peterq...@gmail.com 
>> wrote:
>>
>>> There are .html pages on the web server public directory that your seeing
>>>
>>> On Mon, Jan 25, 2021, 1:16 PM S R  wrote:
>>>
>>>> I just deleted the .sdb and then run wee_database --create. 
>>>>
>>>> i don't see any cache data for nginx on either the ubuntu or freebsd 
>>>> versions i setup for testing, but they both show the same problem 
>>>>
>>>>
>>>> On Monday, January 25, 2021 at 10:10:47 PM UTC+1 gjr80 wrote:
>>>>
>>>>> Did you delete any previously generated reports on both your WeeWX 
>>>>> machine and web server?
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 26 January 2021 at 06:40:48 UTC+10 sjr4...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> I've got the same problem. finished testing with the simulator, 
>>>>>> deleted the db and created again. 
>>>>>> cleared the browser cache on both chrome and firefox, but i goto the 
>>>>>> page and it shows 28.01 even though today is 25.01 and the data from 
>>>>>> when 
>>>>>> the simulator run
>>>>>>
>>>>>>
>>>>>> On Sunday, November 22, 2015 at 8:13:23 AM UTC+1 bjale...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> Haha magic indeed!
>>>>>>>
>>>>>>> I completely overlooked the internal logger in the station itself - 
>>>>>>> thanks very much for that.
>>>>>>>
>>>>>>>
>>>>>>> On Sunday, 22 November 2015 13:15:32 UTC+13, Tom Keffer wrote:
>>>>>>>>
>>>>>>>> Magic. :-)
>>>>>>>>
>>>>>>>> Your hardware must have an onboard logger. If you truly want a 
>>>>>>>> fresh start, you'll have to clear it. Specific instructions depends on 
>>>>>>>> the 
>>>>>>>> make of your hardware.
>>>>>>>>
>>>>>>>> -tk
>>>>>>>>
>>>>>>>> On Sat, Nov 21, 2015 at 3:52 PM, George Alexander <
>>>>>>>> bjale...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Monday, 13 July 2015 09:28:49 UTC+12, mwall wrote:
>>>>>>>>>>
>>>>>>>>>> On Sunday, July 12, 2015 at 5:16:55 PM UTC-4, Dave Jeffries wrote:
>>>>>>>>>>>
>>>>>>>>>>> I used the setup.py method, just thought there may be a simple 
>>>>>>>>>>> command  to remove all the existing data.
>>>>>>>>>>> I guess the weewx.conf and skin.conf will be overwritten so will 
>>>>>>>>>>> have to take a copy first?
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> if you do not care about any of the data in the database, then 
>>>>>>>>>> just stop weewx, delete the database file 
>>>>>>>>>> (/home/weewx/archive/weewx.s

Re: [weewx-user] How do I remove all the existing data and start again

yes. i did fresh install (Standard Seasons skin) with the simulator to make 
get it working. Then i added the interceptor driver. 
Simulator in generator mode created data up to 31.01.21. I have the ecowitt 
unit inside, so only inside temperature, humidity and pressure is being 
sent at the moment. 
index.html page time/date is showing correct. inside temp/hum is correct 
and all other values are NA/0 
day graphs are showing correctly for the collection time the system has 
been up. as in today 26.01
week/month/year graphs are still showing plots for 26 -> 31.01.21 






On Tuesday, January 26, 2021 at 9:39:48 AM UTC+1 gjr80 wrote:

> What skin are we talking about Seasons? Standard or something else. ‘Index 
> page has correct date’ what about observations? Plots? ‘week/month/year - 
> shows date of 31.01 with simulator data’ so date is wrong but is data 
> correct. What do the plots show? What is the timestamp under the x axis of 
> the plots? Seeing a startup log after deleting everything would help. What 
> about time stamps on generated files? Is there a link to your site?
>
> You are looking at your pages we are not, so you need to give us a 
> detailed picture.
>
> Gary
> On Tuesday, 26 January 2021 at 18:24:56 UTC+10 sjr4...@gmail.com wrote:
>
>> done that mulitple times alreadyand more weirdness.
>>
>> index web page is good - shows correct todays date (sessions template out 
>> of box)
>> day is good - shows todays date
>>
>> week/month/year - shows date of 31.01 with simulator data.
>>
>> On Tuesday, January 26, 2021 at 7:10:48 AM UTC+1 gjr80 wrote:
>>
>>> Delete the html directory again (definitely on the WeeWX machine and 
>>> also delete the html/png files on your web server if applicable), delete 
>>> the database and restart WeeWX. Monitor the log, confirm a new database is 
>>> created (it will be logged) and which driver is being used. Confirm report 
>>> generation. If you still get old simulator data in a browser it’s a browser 
>>> cache issue or you have more than one WeeWX instance running or remnants 
>>> from another WeeWX instance. You can also take the browser out of the 
>>> equation and view the report output in an editor or cat it to your console.
>>>
>>> Gary
>>>
>>> On Tuesday, 26 January 2021 at 15:51:11 UTC+10 sjr4...@gmail.com wrote:
>>>
>>>> deleted the entire html directory and run wee_reports and it is back 
>>>> with the simulator data... even though a db we deleted and created again
>>>>
>>>> On Monday, January 25, 2021 at 11:20:26 PM UTC+1 peterq...@gmail.com 
>>>> wrote:
>>>>
>>>>> There are .html pages on the web server public directory that your 
>>>>> seeing
>>>>>
>>>>> On Mon, Jan 25, 2021, 1:16 PM S R  wrote:
>>>>>
>>>>>> I just deleted the .sdb and then run wee_database --create. 
>>>>>>
>>>>>> i don't see any cache data for nginx on either the ubuntu or freebsd 
>>>>>> versions i setup for testing, but they both show the same problem 
>>>>>>
>>>>>>
>>>>>> On Monday, January 25, 2021 at 10:10:47 PM UTC+1 gjr80 wrote:
>>>>>>
>>>>>>> Did you delete any previously generated reports on both your WeeWX 
>>>>>>> machine and web server?
>>>>>>>
>>>>>>> Gary
>>>>>>>
>>>>>>> On Tuesday, 26 January 2021 at 06:40:48 UTC+10 sjr4...@gmail.com 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I've got the same problem. finished testing with the simulator, 
>>>>>>>> deleted the db and created again. 
>>>>>>>> cleared the browser cache on both chrome and firefox, but i goto 
>>>>>>>> the page and it shows 28.01 even though today is 25.01 and the data 
>>>>>>>> from 
>>>>>>>> when the simulator run
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sunday, November 22, 2015 at 8:13:23 AM UTC+1 bjale...@gmail.com 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Haha magic indeed!
>>>>>>>>>
>>>>>>>>> I completely overlooked the internal logger in the station itself 
>>>>>>>>> - thanks very much for that.
>>>>>>>>>
>>>>>&

Re: [weewx-user] How do I remove all the existing data and start again

all is good now only there is no pressure. i think this is because the 
skin is using barometer, but the ecowitt is directing baromabsin to pressure

On Tuesday, January 26, 2021 at 10:31:10 AM UTC+1 gjr80 wrote:

> Sounds like all is fine except for week/month/year plots? By default week 
> plots are generated once per hour, month every three hours and year every 
> 24 hours. Did you delete all of the generated plot image files (xxx.png)? 
> This forces WeeWX to regenerate them all on the next report cycle.
>
> Gary
>
> On Tuesday, 26 January 2021 at 19:26:36 UTC+10 sjr4...@gmail.com wrote:
>
>> yes. i did fresh install (Standard Seasons skin) with the simulator to 
>> make get it working. Then i added the interceptor driver. 
>> Simulator in generator mode created data up to 31.01.21. I have the 
>> ecowitt unit inside, so only inside temperature, humidity and pressure is 
>> being sent at the moment. 
>> index.html page time/date is showing correct. inside temp/hum is correct 
>> and all other values are NA/0 
>> day graphs are showing correctly for the collection time the system has 
>> been up. as in today 26.01
>> week/month/year graphs are still showing plots for 26 -> 31.01.21 
>>
>>
>>
>>
>>
>>
>> On Tuesday, January 26, 2021 at 9:39:48 AM UTC+1 gjr80 wrote:
>>
>>> What skin are we talking about Seasons? Standard or something else. 
>>> ‘Index page has correct date’ what about observations? Plots? 
>>> ‘week/month/year - shows date of 31.01 with simulator data’ so date is 
>>> wrong but is data correct. What do the plots show? What is the timestamp 
>>> under the x axis of the plots? Seeing a startup log after deleting 
>>> everything would help. What about time stamps on generated files? Is there 
>>> a link to your site?
>>>
>>> You are looking at your pages we are not, so you need to give us a 
>>> detailed picture.
>>>
>>> Gary
>>> On Tuesday, 26 January 2021 at 18:24:56 UTC+10 sjr4...@gmail.com wrote:
>>>
>>>> done that mulitple times alreadyand more weirdness.
>>>>
>>>> index web page is good - shows correct todays date (sessions template 
>>>> out of box)
>>>> day is good - shows todays date
>>>>
>>>> week/month/year - shows date of 31.01 with simulator data.
>>>>
>>>> On Tuesday, January 26, 2021 at 7:10:48 AM UTC+1 gjr80 wrote:
>>>>
>>>>> Delete the html directory again (definitely on the WeeWX machine and 
>>>>> also delete the html/png files on your web server if applicable), delete 
>>>>> the database and restart WeeWX. Monitor the log, confirm a new database 
>>>>> is 
>>>>> created (it will be logged) and which driver is being used. Confirm 
>>>>> report 
>>>>> generation. If you still get old simulator data in a browser it’s a 
>>>>> browser 
>>>>> cache issue or you have more than one WeeWX instance running or remnants 
>>>>> from another WeeWX instance. You can also take the browser out of the 
>>>>> equation and view the report output in an editor or cat it to your 
>>>>> console.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 26 January 2021 at 15:51:11 UTC+10 sjr4...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> deleted the entire html directory and run wee_reports and it is back 
>>>>>> with the simulator data... even though a db we deleted and created again
>>>>>>
>>>>>> On Monday, January 25, 2021 at 11:20:26 PM UTC+1 peterq...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> There are .html pages on the web server public directory that your 
>>>>>>> seeing
>>>>>>>
>>>>>>> On Mon, Jan 25, 2021, 1:16 PM S R  wrote:
>>>>>>>
>>>>>>>> I just deleted the .sdb and then run wee_database --create. 
>>>>>>>>
>>>>>>>> i don't see any cache data for nginx on either the ubuntu or 
>>>>>>>> freebsd versions i setup for testing, but they both show the same 
>>>>>>>> problem 
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, January 25, 2021 at 10:10:47 PM UTC+1 gjr80 wrote:
>>>>>>>>
>>>>>>>>> Did you delete any previ

Re: [weewx-user] simulator - generator critical crash

worked like a charmthank you. 

With the Seasons skin, i am not getting any barometer info because the 
template seems to use baromabsin but i see the ecowitt-client in 
interceptor is writing to the pressure field. 
Is it possible to tell the skin via the conf file which is the correct 
field to pull the pressure from? 
also, the ecowitt client also supports baromrelin - relative pressure, can 
we get the db extended to support that field too pls?

On Tuesday, January 26, 2021 at 3:18:19 PM UTC+1 tke...@gmail.com wrote:

> Easy fix to allow characters with an umlaut. In the skin.conf file that 
> you are using, change this
>
> [[SummaryByMonth]]
> # Reports that summarize "by month"
> [[[NOAA_month]]]
> encoding = strict_ascii
> template = NOAA/NOAA-%Y-%m.txt.tmpl
>
> [[SummaryByYear]]
> # Reports that summarize "by year"
> [[[NOAA_year]]]
> encoding = strict_ascii
> template = NOAA/NOAA-%Y.txt.tmpl
>
> to this
>
> [[SummaryByMonth]]
> # Reports that summarize "by month"
> [[[NOAA_month]]]
> encoding = utf8
> template = NOAA/NOAA-%Y-%m.txt.tmpl
>
> [[SummaryByYear]]
> # Reports that summarize "by year"
> [[[NOAA_year]]]
> encoding = utf8
> template = NOAA/NOAA-%Y.txt.tmpl
>
>
>
> On Tue, Jan 26, 2021 at 12:42 AM gjr80  wrote:
>
>> Yes it would but the current code base is limited to what we can do with 
>> the python string encode() function. However, I have an idea for something 
>> we could do to hopefully improve things, let me discuss with Tom.
>>
>> Gary
>>
>> On Tuesday, 26 January 2021 at 17:55:23 UTC+10 sjr4...@gmail.com wrote:
>>
>>> wouldn't that make more sense to drop the umlaut and Düsseldorf = 
>>> Dusseldorf - that is what other webservices do that can't deal with 
>>> non-ascii characters. would be better than dropping the character completely
>>>
>>> On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote:
>>>
 NOAA files use strict_ascii encoding 
  so 
 no umlauts or other accented characters unfortunately. You can change the 
 encoding but as the NOAA format reports are tabulated reports it will mess 
 up the format of the report.

 Gary

 On Tuesday, 26 January 2021 at 15:53:23 UTC+10 sjr4...@gmail.com wrote:

> The staion name has a German umlaut in it. It shows correctly on the 
> web pages, but in the NOAA files it misses the letter completely. 
> e.g. name = "Köln", NOAA file has "Kln"
>
> On Monday, January 25, 2021 at 11:52:49 PM UTC+1 tke...@gmail.com 
> wrote:
>
>> dumb question. the climatogical report & summary - Name, is missing "ö" 
>>> looks like it did not like UTF-8. 
>>> is there a way to manually fix this?
>>>
>>
>> Not a dumb question at all, but I don't understand it either. What 
>> "ö"?
>>
> -- 
>>
> You received this message because you are subscribed 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/614395f3-d991-45f9-ad80-dba7fe59168en%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/c7414cf9-7067-4d24-8d8d-1ebeb4bb3892n%40googlegroups.com.

Re: [weewx-user] simulator - generator critical crash

if you look into the interceptor.py code, you will find under IGNORED 
LABELS - 'baromrelin'.

my unit is sending
POST: 
PASSKEY=&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-26+12:16:31&tempinf=73.9&humidityin=39&
baromrelin=30.115&baromabsin=29.599&freq=433M&model=WS2900C_V2.01.10

The other issue i have, the seasons skin is not showing anything for 
pressure, but interceptor.py is mapping baromabsin to "pressure" - which is 
not what is used in the template

On Tuesday, January 26, 2021 at 3:42:42 PM UTC+1 tke...@gmail.com wrote:

> I have not been following the Ecowitt barometer discussion. 
>
> As for the database, it already supports three kinds of barometric 
> pressure: fields 'pressure', 'altimeter', and 'barometer'. See the wiki 
> article *Barometer, pressure, altimeter 
> <https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter>* for 
> the differences between them.
>
> What does relative pressure offer that these fields don't already do? In 
> any case, it's easy enough for you to add a new field in your own database. 
> See the section *Adding a new type to the database 
> <http://www.weewx.com/docs/customizing.htm#add_archive_type>* in the 
> Customizing Guide.
>
>
>
> On Tue, Jan 26, 2021 at 6:34 AM S R  wrote:
>
>> worked like a charmthank you. 
>>
>> With the Seasons skin, i am not getting any barometer info because the 
>> template seems to use baromabsin but i see the ecowitt-client in 
>> interceptor is writing to the pressure field. 
>> Is it possible to tell the skin via the conf file which is the correct 
>> field to pull the pressure from? 
>> also, the ecowitt client also supports baromrelin - relative pressure, 
>> can we get the db extended to support that field too pls?
>>
>> On Tuesday, January 26, 2021 at 3:18:19 PM UTC+1 tke...@gmail.com wrote:
>>
>>> Easy fix to allow characters with an umlaut. In the skin.conf file that 
>>> you are using, change this
>>>
>>> [[SummaryByMonth]]
>>> # Reports that summarize "by month"
>>> [[[NOAA_month]]]
>>> encoding = strict_ascii
>>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>
>>> [[SummaryByYear]]
>>> # Reports that summarize "by year"
>>> [[[NOAA_year]]]
>>> encoding = strict_ascii
>>> template = NOAA/NOAA-%Y.txt.tmpl
>>>
>>> to this
>>>
>>> [[SummaryByMonth]]
>>> # Reports that summarize "by month"
>>> [[[NOAA_month]]]
>>> encoding = utf8
>>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>
>>> [[SummaryByYear]]
>>> # Reports that summarize "by year"
>>> [[[NOAA_year]]]
>>> encoding = utf8
>>> template = NOAA/NOAA-%Y.txt.tmpl
>>>
>>>
>>>
>>> On Tue, Jan 26, 2021 at 12:42 AM gjr80  wrote:
>>>
>>>> Yes it would but the current code base is limited to what we can do 
>>>> with the python string encode() function. However, I have an idea for 
>>>> something we could do to hopefully improve things, let me discuss with Tom.
>>>>
>>>> Gary
>>>>
>>>> On Tuesday, 26 January 2021 at 17:55:23 UTC+10 sjr4...@gmail.com wrote:
>>>>
>>>>> wouldn't that make more sense to drop the umlaut and Düsseldorf = 
>>>>> Dusseldorf - that is what other webservices do that can't deal with 
>>>>> non-ascii characters. would be better than dropping the character 
>>>>> completely
>>>>>
>>>>> On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote:
>>>>>
>>>>>> NOAA files use strict_ascii encoding 
>>>>>> <http://weewx.com/docs/customizing.htm#Specifying_template_files> so 
>>>>>> no umlauts or other accented characters unfortunately. You can change 
>>>>>> the 
>>>>>> encoding but as the NOAA format reports are tabulated reports it will 
>>>>>> mess 
>>>>>> up the format of the report.
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>> On Tuesday, 26 January 2021 at 15:53:23 UTC+10 sjr4...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> The staion name has a German umlaut in i

Re: [weewx-user] simulator - generator critical crash

A quick search around and baromrelin = altimeter. don't know why it is an 
ignored field in interceptor.py. 
I modified interceptor.py and the database is updating both pressure 
measures. 

But i am still not displaying any pressure values in the Seasons skin


On Tuesday, January 26, 2021 at 3:55:41 PM UTC+1 S R wrote:

> if you look into the interceptor.py code, you will find under IGNORED 
> LABELS - 'baromrelin'.
>
> my unit is sending
> POST: 
> PASSKEY=&stationtype=EasyWeatherV1.5.6&dateutc=2021-01-26+12:16:31&tempinf=73.9&humidityin=39&
> baromrelin=30.115&baromabsin=29.599&freq=433M&model=WS2900C_V2.01.10
>
> The other issue i have, the seasons skin is not showing anything for 
> pressure, but interceptor.py is mapping baromabsin to "pressure" - which is 
> not what is used in the template
>
> On Tuesday, January 26, 2021 at 3:42:42 PM UTC+1 tke...@gmail.com wrote:
>
>> I have not been following the Ecowitt barometer discussion. 
>>
>> As for the database, it already supports three kinds of barometric 
>> pressure: fields 'pressure', 'altimeter', and 'barometer'. See the wiki 
>> article *Barometer, pressure, altimeter 
>> <https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter>* 
>> for 
>> the differences between them.
>>
>> What does relative pressure offer that these fields don't already do? In 
>> any case, it's easy enough for you to add a new field in your own database. 
>> See the section *Adding a new type to the database 
>> <http://www.weewx.com/docs/customizing.htm#add_archive_type>* in the 
>> Customizing Guide.
>>
>>
>>
>> On Tue, Jan 26, 2021 at 6:34 AM S R  wrote:
>>
>>> worked like a charmthank you. 
>>>
>>> With the Seasons skin, i am not getting any barometer info because the 
>>> template seems to use baromabsin but i see the ecowitt-client in 
>>> interceptor is writing to the pressure field. 
>>> Is it possible to tell the skin via the conf file which is the correct 
>>> field to pull the pressure from? 
>>> also, the ecowitt client also supports baromrelin - relative pressure, 
>>> can we get the db extended to support that field too pls?
>>>
>>> On Tuesday, January 26, 2021 at 3:18:19 PM UTC+1 tke...@gmail.com wrote:
>>>
>>>> Easy fix to allow characters with an umlaut. In the skin.conf file that 
>>>> you are using, change this
>>>>
>>>> [[SummaryByMonth]]
>>>> # Reports that summarize "by month"
>>>> [[[NOAA_month]]]
>>>> encoding = strict_ascii
>>>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>>
>>>> [[SummaryByYear]]
>>>> # Reports that summarize "by year"
>>>> [[[NOAA_year]]]
>>>> encoding = strict_ascii
>>>> template = NOAA/NOAA-%Y.txt.tmpl
>>>>
>>>> to this
>>>>
>>>> [[SummaryByMonth]]
>>>> # Reports that summarize "by month"
>>>> [[[NOAA_month]]]
>>>> encoding = utf8
>>>> template = NOAA/NOAA-%Y-%m.txt.tmpl
>>>>
>>>> [[SummaryByYear]]
>>>> # Reports that summarize "by year"
>>>> [[[NOAA_year]]]
>>>> encoding = utf8
>>>> template = NOAA/NOAA-%Y.txt.tmpl
>>>>
>>>>
>>>>
>>>> On Tue, Jan 26, 2021 at 12:42 AM gjr80  wrote:
>>>>
>>>>> Yes it would but the current code base is limited to what we can do 
>>>>> with the python string encode() function. However, I have an idea for 
>>>>> something we could do to hopefully improve things, let me discuss with 
>>>>> Tom.
>>>>>
>>>>> Gary
>>>>>
>>>>> On Tuesday, 26 January 2021 at 17:55:23 UTC+10 sjr4...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> wouldn't that make more sense to drop the umlaut and Düsseldorf = 
>>>>>> Dusseldorf - that is what other webservices do that can't deal with 
>>>>>> non-ascii characters. would be better than dropping the character 
>>>>>> completely
>>>>>>
>>>>>> On Tuesday, January 26, 2021 at 7:02:00 AM UTC+1 gjr80 wrote:
>

[weewx-user] interceptor + WH2900C (ecowitt comptible)

I finally got interceptor working with the Seasons template on both Ubuntu
python 3.8 and FreeBSD (freenas jail) python 3.7
Enclosed is the interceptor.py consolidating the fixes posted in;
- #82 do_GET(self): change
- #80 def do_POST(self)

plus a change from myself to map the baromrelin' : 'altimeter' fields

--
You received this message because you are subscribed 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/040f846e-6fc0-4d0e-aee8-de8cbe31cae0n%40googlegroups.com.
#!/usr/bin/env python
# Copyright 2016-2020 Matthew Wall
# Distributed under the terms of the GNU Public License (GPLv3)

"""
This driver runs a simple web server or sniffs network traffic in order to
capture data directly from an internet weather reporting device including:

- Acurite Internet Bridge (also known as the SmartHub) (acurite protocol)
- Acurite Access (wu protocol)
- Oregon Scientific LW301/302 (OS protocol)
- Fine Offset HP1000/WH2600
- Fine Offset GW1000 (ecowitt protocol or wu protocol)
- Fine Offset wifi consoles (including Ambient)
- LaCrosse GW1000U (LaCrosse protocol)

When this driver was first written (early 2016), there were many different
firmware versions using different variations of the weather underground
protocol. The WU protocol has stabilized, and other protocols similar to it
have been developed (e.g., ambient, ecowitt) to provide functionality not
available in the WU protocol.

See the readme file for configuration examples. The sections below include
details about and quirks of various supported hardware models.

Thanks to rich of modern toil and george nincehelser for acurite parsing
http://moderntoil.com/?p=794
http://nincehelser.com/ipwx/

Thanks to Pat at obrienlabs.net for the fine offset parsing
http://obrienlabs.net/redirecting-weather-station-data-from-observerip/

Thanks to sergei and waebi for the LW301/LW302 samples
http://www.silent-gardens.com/blog/shark-hunt-lw301/

Thanks to Sam Roza for packet captures from the LW301

Thanks to skydvrz, keckec, mycal, kennkong for publishing their lacrosse work
http://www.wxforum.net/index.php?topic=14299.0
https://github.com/lowerpower/LaCrosse
https://github.com/kennkong/Weather-ERF-Gateway-1000U

Thanks to Jerome Helbert for the pypcap option.

===
SniffServer vs TCPServer

The driver can obtain packets by sniffing network traffic using pcap, or by
listening for TCP/IP requests. The pcap approach requires the python pypcap
module, which in turn requires libpcap. This means a separate installation
on most platforms.

https://github.com/pynetwork/pypcap

To run a listener, specify an address and port. This is the default mode.
For example:

[Interceptor]
mode = listen
address = localhost
port =

To run a sniffer, specify an interface and filter. For example:

[Interceptor]
mode = sniff
iface = eth0
pcap_filter = src host 192.168.1.5 && dst port 80

The following sections provide some details about each type of hardware.

===
WUClient

This is not a specific type of hardware, but rather *any* hardware that
communicates data using the weather underground protocol. The protocol is
defined here:

https://feedback.weather.com/customer/en/portal/articles/2924682-pws-upload-protocol?b_id=17298

Since that protocol has changed over the years, a PDF version of the protocol
as of 03jun2019 is incuded in this distribution in the doc directory.

===
Acurite Bridge

The Acurite bridge communicates with Acurite 5-in-1, 3-in-1, temperature, and
temperature/humidity sensors. It receives signals from any number of sensors,
even though Acurite's web interface is limited to 3 devices (or 10 as of the
July 2016 firmware update).

By default, the bridge transmits data to www.acu-link.com. Acurite requires
registration of the bridge's MAC address in order to use acu-link.com.
However, the bridge will function even if it is not registered, as long as it
receives the proper response.

The bridge sends data as soon as it receives an observation from the sensors.

Chaney did a firmware update to the bridge in July 2016. This update made the
bridge emit data using the weather underground protocol instead of the
Chaney protocol.

The old firmware (acurite bridge) sends to aculink.com in a proprietary 'chaney
format'. The new firmware (smarthub) sends to hubapi.acurite.com as well as to
rtupdate.wunderground.com. The format for hubapi is similar to the rtupdate
format used at weather underground. The user interface of the aculink service
has been shut down, and it has been replaced

[weewx-user] belchertown skin - errors with not out door sensors