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

[stevo]

Hi 

Getting the same error trying to run interceptor.py in debug mode on
ubuntu, as i got on freefsd.

python3 /usr/share/weewx/user/interceptor.py --device=ecowitt-client --
mode=listen --port=8000 --debug
Traceback (most recent call last):
 File "/usr/share/weewx/user/interceptor.py", line 302, in 
   import weewx.drivers
ModuleNotFoundError: No module named 'weewx'

python is in the search path, so it seems not to recognise the weewx
config/run path

do you have any ideas on how to run the config please?

locations are;
/etc/weewx - config
/usr/share/weewx  - app root
/usr/share/weewx/user - interceptor
/var/lib/weewx - db
/var/www/html/weewx - html

doesn't look like the sensor details below match to the sensor data
sent over IP
    Form item: "tempinf" = "77.2"
    Form item: "humidityin" = "41"
    Form item: "baromrelin" = "29.537"
    Form item: "baromabsin" = "29.315"

interceptor.py sensor from log
{
'pressure': 'pressure', 
'barometer': 'barometer', 
'outHumidity': 'humidity_4', 
'inHumidity': 'humidity_1', 
'outTemp': 'temperature_4', 
'inTemp': 'temperature_1', 
'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'
}


On Mon, 2021-01-18 at 12:13 +0100, Rainer Lang 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)
> > > 
> > > 
> > > 22    2.968670    WH2900C    WEEWX    TCP    58    20150 → 8080
> > > [SYN] Seq=0 Win=5840 Len=0 MSS=1460
> > > 23    2.969709    WEEWX    WH2900C    TCP    54    8080 → 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.
> > > > 
> 

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

[Rainer Lang]

1. can you send us the system log from the time on that weewx started

otherwise difficult to say what's going on in your system

2. also add your weewx.conf

3. Have you created a temporary file system for the pictures and html 
files ?
If not (yet - that's to protect your SD card but not necessary right 
now), could you also include the content of

/var/www/html/weewx ?

that could give us some ideas wrong you are still missing


On 19.01.2021 15:14, S R wrote:

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)

22    2.968670    WH2900C    WEEWX    TCP    58 20150 →
8080 [SYN] Seq=0 Win=5840 Len=0 MSS=1460
23    2.969709    WEEWX WH2900C    TCP    54    8080 →
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 

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

[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 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 
> 

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

[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 
 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 

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

[Rainer Lang]

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)

22    2.968670    WH2900C    WEEWX    TCP    58    20150 → 8080
[SYN] Seq=0 Win=5840 Len=0 MSS=1460
23    2.969709    WEEWX    WH2900C TCP    54    8080 → 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 

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

[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 
 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, 

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

[S R]

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 
>>> 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 

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

[Rainer Lang]

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 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 

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

[Rainer Lang]

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


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


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

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

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


On 16.01.2021 20:54, S R wrote:


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

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

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



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

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

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

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

--
You received this message because you are subscribed to the Google 
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to weewx-user+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/853cc4c5-709d-491f-97b8-3fec2a1548d9n%40googlegroups.com 
.


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

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

[kan6526]

debian9 + weewx3.8.2 + interceptor0.41 
WH2950  it work very 
wall to upload pwsweather , 
 Windguru 
 ,  AWEKAS 


thanks mwall
107.11.21 
*Babuza.Hemei.TW *

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

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

[Andy Kerekes]

Hello Thomas!!!

I see you are using an Ambient 2902 as I. I can not for the life of me get 
my 2902 to work with weewx. Is there a tread where I can find detailed info 
on getting this ws-2902 to work off the console or any method?

I get the same on my -tail -f /var/log/syslog as kan6526 above.

Andy

On Thursday, May 25, 2017 at 10:20:07 PM UTC-5, Thomas Keffer wrote:
>
> In addition to Gary's suggestions, I would add one more: your disk may be 
> failing.
>
> -tk
>
> On Thu, May 25, 2017 at 4:20 PM, gjr80  
> wrote:
>
>> Hi,
>>
>> This is likely why you are seeing the error message:
>>
>> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 14 
>>> files for report StandardReport in 1038.33 seconds
>>>
>>
>> 1038 seconds is roughly 17 minutes. I don't know what your archive 
>> interval is but if it is anything less than 20 minutes this would cause 
>> problems. The report cycle is triggered at the end of an archive period and 
>> each report cycle is run in its own thread. If a new report thread is 
>> created before the old one is complete then you will run into the sort of 
>> errors you see above - ie files the old thread is expecting to use no 
>> longer exist because the new report thread has taken over. If this is a 
>> one-off situation things will come good after an archive period or 2, but 
>> if it is an ongoing problem your report threads will not generate (some or 
>> all) reports and what you will see are your pages not being updated.
>>
>> A few things to look at:
>> 1. What is your archive period? You should see it mentioned explicitly in 
>> the log when weeWX starts. If its less than 5 minutes then it is possible 
>> you are asking weeWX to do too much (ie generate too many or too complex 
>> reports).
>> 2. What skins are you running? Just the Standard skin or some others? If 
>> your PC cannot generate all of the reports in each skin within an archive 
>> period you will experience the problem you describe.
>> 3. Is the error you posted above happening regularly, ie every archive 
>> period, or just now and then. If now and then it may be a case of something 
>> else loading your PC causing weeWX to be unable to complete reports in a 
>> timely manner. If it's occurring regularly then you may be 'overloading' 
>> weeWX.
>>
>> Gary
>>
>> On Friday, 26 May 2017 01:45:26 UTC+10, kan6526 wrote:
>>>
>>>
>>> WeeWX generates HTML pages, but it does not update them
>>>
>>>
>>> ---stop weewx 
>>>  
>>> msg
>>>  weewx[7366]: interceptor: MainThread: unrecognized parameter 
>>> absbaromin=29.78
>>>
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   os.rename(tmpname, 
>>> _fullname)
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   OSError: [Errno 2] 沒有此一檔案或目錄
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 14 
>>> files for report StandardReport in 1038.33 seconds
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   Traceback (most recent call 
>>> last):
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   os.rename(tmpname, 
>>> _fullname)
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   OSError: [Errno 2] 沒有此一檔案或目錄
>>> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 7 
>>> files for report StandardReport in 270.15 seconds
>>> May 25 23:37:03 GA-8IEXRR weewx[7366]: imagegenerator: Generated 12 
>>> images for StandardReport in 1.29 seconds
>>> May 25 23:37:03 GA-8IEXRR weewx[7366]: copygenerator: copied 0 files to 
>>> /var/www/weewx
>>> May 25 23:37:03 GA-8IEXRR weewx[7366]: imagegenerator: Generated 12 
>>> images for StandardReport in 1.30 seconds
>>> May 25 23:37:03 GA-8IEXRR weewx[7366]: copygenerator: copied 9 files to 
>>> /var/www/weewx
>>>
>>>  --weewx start msg --
>>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Initializing weewx 
>>> version 3.7.1
>>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Using Python 2.6.6 
>>> (r266:84292, Dec 27 2010, 00:02:40) #012[GCC 4.4.5]
>>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Platform 
>>> Linux-2.6.32-5-686-i686-with-debian-6.0.10
>>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Locale is 'zh_TW.UTF-8'
>>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: pid file is 
>>> /var/run/weewx.pid
>>> May 25 23:43:35 GA-8IEXRR weewx[7643]: engine: Using configuration file 
>>> /etc/weewx/weewx.conf
>>> May 25 23:43:35 GA-8IEXRR weewx[7643]: engine: Loading station type 
>>> Interceptor (user.interceptor)
>>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: driver 
>>> version is 0.30
>>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: device 

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

[Thomas Keffer]

In addition to Gary's suggestions, I would add one more: your disk may be
failing.

-tk

On Thu, May 25, 2017 at 4:20 PM, gjr80  wrote:

> Hi,
>
> This is likely why you are seeing the error message:
>
> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 14
>> files for report StandardReport in 1038.33 seconds
>>
>
> 1038 seconds is roughly 17 minutes. I don't know what your archive
> interval is but if it is anything less than 20 minutes this would cause
> problems. The report cycle is triggered at the end of an archive period and
> each report cycle is run in its own thread. If a new report thread is
> created before the old one is complete then you will run into the sort of
> errors you see above - ie files the old thread is expecting to use no
> longer exist because the new report thread has taken over. If this is a
> one-off situation things will come good after an archive period or 2, but
> if it is an ongoing problem your report threads will not generate (some or
> all) reports and what you will see are your pages not being updated.
>
> A few things to look at:
> 1. What is your archive period? You should see it mentioned explicitly in
> the log when weeWX starts. If its less than 5 minutes then it is possible
> you are asking weeWX to do too much (ie generate too many or too complex
> reports).
> 2. What skins are you running? Just the Standard skin or some others? If
> your PC cannot generate all of the reports in each skin within an archive
> period you will experience the problem you describe.
> 3. Is the error you posted above happening regularly, ie every archive
> period, or just now and then. If now and then it may be a case of something
> else loading your PC causing weeWX to be unable to complete reports in a
> timely manner. If it's occurring regularly then you may be 'overloading'
> weeWX.
>
> Gary
>
> On Friday, 26 May 2017 01:45:26 UTC+10, kan6526 wrote:
>>
>>
>> WeeWX generates HTML pages, but it does not update them
>>
>>
>> ---stop weewx  msg--
>> --
>>  weewx[7366]: interceptor: MainThread: unrecognized parameter
>> absbaromin=29.78
>>
>> May 25 23:37:01 GA-8IEXRR weewx[7366]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   os.rename(tmpname,
>> _fullname)
>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   OSError: [Errno 2] 沒有此一檔案或目錄
>> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 14
>> files for report StandardReport in 1038.33 seconds
>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   Traceback (most recent call
>> last):
>> May 25 23:37:01 GA-8IEXRR weewx[7366]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   os.rename(tmpname,
>> _fullname)
>> May 25 23:37:01 GA-8IEXRR weewx[7366]:   OSError: [Errno 2] 沒有此一檔案或目錄
>> May 25 23:37:01 GA-8IEXRR weewx[7366]: cheetahgenerator: Generated 7
>> files for report StandardReport in 270.15 seconds
>> May 25 23:37:03 GA-8IEXRR weewx[7366]: imagegenerator: Generated 12
>> images for StandardReport in 1.29 seconds
>> May 25 23:37:03 GA-8IEXRR weewx[7366]: copygenerator: copied 0 files to
>> /var/www/weewx
>> May 25 23:37:03 GA-8IEXRR weewx[7366]: imagegenerator: Generated 12
>> images for StandardReport in 1.30 seconds
>> May 25 23:37:03 GA-8IEXRR weewx[7366]: copygenerator: copied 9 files to
>> /var/www/weewx
>>
>>  --weewx start msg --
>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Initializing weewx version
>> 3.7.1
>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Using Python 2.6.6
>> (r266:84292, Dec 27 2010, 00:02:40) #012[GCC 4.4.5]
>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Platform
>> Linux-2.6.32-5-686-i686-with-debian-6.0.10
>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: Locale is 'zh_TW.UTF-8'
>> May 25 23:43:35 GA-8IEXRR weewx[7638]: engine: pid file is
>> /var/run/weewx.pid
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: engine: Using configuration file
>> /etc/weewx/weewx.conf
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: engine: Loading station type
>> Interceptor (user.interceptor)
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: driver
>> version is 0.30
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: device
>> type: observer
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: sensor
>> map: None
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: mode is
>> sniff
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: sniff
>> iface=eth1 promiscuous=0
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: interceptor: MainThread: sniff
>> filter 'src 192.168.2.224 and dst port 80'
>> May 25 23:43:35 GA-8IEXRR weewx[7643]: engine: StdConvert target unit is
>> 0x1
>>
>>
>>> --
> You received