FINE OFFSET WH2900 / Ambient Weather WS-2902

[44085w...@gmail.com]

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

[mwall]

On Saturday, April 1, 2017 at 10:37:01 AM UTC-4, 44085weather 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

as of april 2017, support for the wh2900 is via the weewx-interceptor driver.  weewx will capture the traffic from the wh2900 sent to weather underground.

do you have one of these wh2900 stations?

if you could do some network packet captures then we could figure out whether the wh2900 uses the same protocols as the wh2600 or hp1001 hardware.

m

[kan6526]

I have WH2950
------------------------------  apache syslog:   -------------------------------------------
192.168.2.224 - - [23/Apr/2017:22:21:29 +0800] "GET /weatherstation/updateweatherstation.php?ID=ICHANGHU4&PASSWORD=j64tgglf&indoortempf=79.3&tempf=70.9&dewptf=65.8&windchillf=70.9&indoorhumidity=62&humidity=84&windspeedmph=0.0&windgustmph=0.0&winddir=148&absbaromin=29.98&baromin=29.97&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=2.86&yearlyrainin=-9999&solarradiation=0.00&UV=0&dateutc=2017-4-23%2014:21:13&softwaretype=WeatherSmart%V1.7.0&action=updateraw&realtime=1&rtfreq=5 HTTP/1.0" 404 531 "-" "-"
192.168.2.224 - - [23/Apr/2017:22:21:33 +0800] "GET /v01/set?wid=253686183ff230b634fd&key=af324276cf5yb43e86a064e79f84544&tempin=263&temp=216&dew=188&chill=216&humin=62&hum=84&wspd=0&wdir=148&bar=10148&rain=0&solarrad=0&uvi=0&date=20170423&time=1421& HTTP/1.0" 404 494 "-" "-"

------------------------------------------------------------------------------------------------------------------------------------------
Apr 23 22:25:50 debian-weather weewx[954]: engine: Loading service weewx.restx.StdAWEKAS
Apr 23 22:25:50 debian-weather weewx[954]: restx: AWEKAS: Posting not enabled.
Apr 23 22:25:50 debian-weather weewx[954]: engine: Finished loading service weewx.restx.StdAWEKAS
Apr 23 22:25:50 debian-weather weewx[954]: engine: Loading service weewx.engine.StdPrint
Apr 23 22:25:50 debian-weather weewx[954]: engine: Finished loading service weewx.engine.StdPrint
Apr 23 22:25:50 debian-weather weewx[954]: engine: Loading service weewx.engine.StdReport
Apr 23 22:25:50 debian-weather weewx[954]: engine: Finished loading service weewx.engine.StdReport
Apr 23 22:25:50 debian-weather weewx[954]: engine: Starting up weewx version 3.7.1
Apr 23 22:25:50 debian-weather weewx[954]: engine: Station does not support reading the time
Apr 23 22:25:50 debian-weather weewx[954]: engine: Starting main packet loop.
Apr 23 22:26:00 debian-weather weewx[954]: interceptor: MainThread: empty queue

###################  etc/weewx/weewx.conf      ###################################

[Interceptor]
    driver = user.interceptor
    device_type = observer


weewx It can't work



mwall於 2017年4月1日星期六 UTC+8下午10時49分05秒寫道：

[mwall]

On Sunday, April 23, 2017 at 10:29:55 AM UTC-4, kan6526 wrote:

I have WH2950
------------------------------  apache syslog:   -------------------------------------------
192.168.2.224 - - [23/Apr/2017:22:21:29 +0800] "GET /weatherstation/updateweatherstation.php?ID=ICHANGHU4&PASSWORD=j64tgglf&indoortempf=79.3&tempf=70.9&dewptf=65.8&windchillf=70.9&indoorhumidity=62&humidity=84&windspeedmph=0.0&windgustmph=0.0&winddir=148&absbaromin=29.98&baromin=29.97&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=2.86&yearlyrainin=-9999&solarradiation=0.00&UV=0&dateutc=2017-4-23%2014:21:13&softwaretype=WeatherSmart%V1.7.0&action=updateraw&realtime=1&rtfreq=5 HTTP/1.0" 404 531 "-" "-"
192.168.2.224 - - [23/Apr/2017:22:21:33 +0800] "GET /v01/set?wid=253686183ff230b634fd&key=af324276cf5yb43e86a064e79f84544&tempin=263&temp=216&dew=188&chill=216&humin=62&hum=84&wspd=0&wdir=148&bar=10148&rain=0&solarrad=0&uvi=0&date=20170423&time=1421& HTTP/1.0" 404 494 "-" "-"

thank you for posting some wh29xx traffic!

from the tiny snippet you posted, we see two different protocols.  the first one is weather underground protocol (/weatherstation/updateweatherstation.php). the second is something new (/v01/set).  both of them misuse the http GET protocol, but that is the world we live in.

the interceptor driver will recognize the weather underground protocol.  you must do one of the following:

1) configure a cgi script on your web server to relay the updateweatherstation.php requests to the interceptor driver

2) shut down apache and let the interceptor driver listen directly for the updateweatherstation.php requests

3) configure the interceptor driver to sniff incoming traffic

all three of these are documented in the interceptor readme.

how did you get the hp29xx to send to your apache server?  can you send to the computer running weewx instead?  if so, then you might want option 2.

is weewx running on the same computer as apache?  do you need apache for other purposes?  if so, then you probably want to use option 3 or option 1.

m

ps

if you post more examples of the second protocol (/v01/set) then i could make the interceptor driver optionally use that instead of the weather underground protocol.  however, it looks like that protocol does not provide any information beyond what is in the weather underground uploads.

[kan6526]

WH2950 can update to WU  Weatherbug Weathercloud
########################### /etc/apache/syslog ######################################
 "GET /v01/set?wid=xxxxxxxxxxxxxd&key=rewrewrewrwerewrew&tempin=253&temp=233&dew=205&chill=233&humin=70&hum=84&wspd=0&wdir=116&bar=10160&rain=0&solarrad=1022&uvi=10&date=20170424&time=0254& HTTP/1.0" 404 494 "-" "-"
"GET /data/livedata.aspx?ID=xxxxxx&Key=wwerewrwer&num=324234234&dateutc=2017-4-24%202:54:51&tempf=73.9&tempf1=77.5&humidity=84&humidity1=70&baromin1=30.01&baromin=30.00&windspeedmph=0.0&windgustmph=0.0&winddir=108&rainin=0.00&dailyrainin=0.00&monthlyrainin=2.86&softwaretype=WeatherSmart%20V1.7.0 HTTP/1.0" 404 514 "-" "-"
"GET /weatherstation/updateweatherstation.php?ID=werewrI4&PASSWORD=werewr&indoortempf=77.5&tempf=73.9&dewptf=68.9&windchillf=73.9&indoorhumidity=70&humidity=84&windspeedmph=0.0&windgustmph=0.0&winddir=108&absbaromin=30.01&baromin=30.00&rainin=0.00&dailyrainin=0.00&weeklyrainin=0.00&monthlyrainin=2.86&yearlyrainin=-9999&solarradiation=101.86&UV=1&dateutc=2017-4-24%202:54:51&softwaretype=WeatherSmart%V1.7.0&action=updateraw&realtime=1&rtfreq=5 HTTP/1.0" 404 531 "-" "-"

[kan6526]

Hi

debian-weather server(192.168.1.100/gateway:192.168.1.1)
openwrt Router(192.168.1.1)  
wh2950(192.168.1.224/gateway:192.168.1.1)



-----------------------------192.168.1.100 debian-weather ----------------

engine: Using configuration file /etc/weewx/weewx.conf
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Loading station type Interceptor (user.interceptor)
Apr 25 15:06:31 debian-weather weewx[1373]: interceptor: MainThread: driver version is 0.30
Apr 25 15:06:31 debian-weather weewx[1373]: interceptor: MainThread: device type: observer
Apr 25 15:06:31 debian-weather weewx[1373]: interceptor: MainThread: sensor map: None
Apr 25 15:06:31 debian-weather weewx[1373]: interceptor: MainThread: mode is listen
Apr 25 15:06:31 debian-weather weewx[1373]: interceptor: MainThread: listen on :8080



---------------------------------192.168.1.100 ssh tcpdump 192.168.1.224(wH2950)------------------------------

root@debian-weather:~# ssh 192.168.1.1 "tcpdump -i br-lan src 192.168.1.224 and port 80"
ro...@192.168.1.1's password:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 65535 bytes
07:37:19.373565 IP WH2950.lan.8724 > ec2-107-23-220-109.compute-1.amazonaws.com.www: Flags [S], seq 120230359, win 5840, options [mss 1460], length 0
07:37:19.641187 IP WH2950.lan.8724 > ec2-107-23-220-109.compute-1.amazonaws.com.www: Flags [P.], seq 120230360:120230732, ack 2590929032, win 5840, length 372
07:37:20.023465 IP WH2950.lan.8724 > ec2-107-23-220-109.compute-1.amazonaws.com.www: Flags [R.], seq 372, ack 278, win 5840, length 0
07:37:20.023662 IP WH2950.lan.8724 > ec2-107-23-220-109.compute-1.amazonaws.com.www: Flags [.], ack 278, win 5563, length 0
07:37:22.868827 IP WH2950.lan.19206 > ec2-52-25-21-79.us-west-2.compute.amazonaws.com.www: Flags [S], seq 120325149, win 5840, options [mss 1460], length 0
07:37:23.105608 IP WH2950.lan.19206 > ec2-52-25-21-79.us-west-2.compute.amazonaws.com.www: Flags [P.], seq 120325150:120325673, ack 282921972, win 5840, length 523
07:37:23.216000 IP WH2950.lan.19206 > ec2-52-25-21-79.us-west-2.compute.amazonaws.com.www: Flags [F.], seq 523, ack 1, win 5840, length 0
07:37:23.299958 IP WH2950.lan.19206 > ec2-52-25-21-79.us-west-2.compute.amazonaws.com.www: Flags [R.], seq 523, ack 1, win 5840, length 0
07:37:23.445689 IP WH2950.lan.19206 > ec2-52-25-21-79.us-west-2.compute.amazonaws.com.www: Flags [R.], seq 524, ack 1, win 5840, length 0
07:37:27.339354 IP WH2950.lan.17679 > weathercloud.net.www: Flags [S], seq 120419973, win 5840, options [mss 1460], length 0
07:37:27.764565 IP WH2950.lan.17679 > weathercloud.net.www: Flags [P.], seq 120419974:120420250, ack 1492866511, win 5840, length 276
07:37:28.197903 IP WH2950.lan.17679 > weathercloud.net.www: Flags [F.], seq 276, ack 398, win 5443, length 0
07:37:28.204557 IP WH2950.lan.17679 > weathercloud.net.www: Flags [.], ack 399, win 5442, length 0

-----------------------------------/var/log/syslog -------------------------------------
Apr 25 15:06:31 debian-weather weewx[1373]: restx: AWEKAS: Posting not enabled.
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Finished loading service weewx.restx.StdAWEKAS
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Loading service weewx.engine.StdPrint
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Finished loading service weewx.engine.StdPrint
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Loading service weewx.engine.StdReport
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Finished loading service weewx.engine.StdReport
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Starting up weewx version 3.7.1
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Station does not support reading the time
Apr 25 15:06:31 debian-weather weewx[1373]: engine: Starting main packet loop.
Apr 25 15:06:41 debian-weather weewx[1373]: interceptor: MainThread: empty queue
Apr 25 15:06:51 debian-weather weewx[1373]: interceptor: MainThread: empty queue
Apr 25 15:07:01 debian-weather weewx[1373]: interceptor: MainThread: empty queue

It can not capture data

[mwall]

On Tuesday, April 25, 2017 at 4:42:11 AM UTC-4, kan6526 wrote:

debian-weather server(192.168.1.100/gateway:192.168.1.1)
openwrt Router(192.168.1.1)  
wh2950(192.168.1.224/gateway:192.168.1.1)

option 1: stop the apache web server that is running on 192.168.1.100, change the interceptor configuration on 192.168.1.100 to listen on port 80 (not port 8080), then restart weewx on 192.168.1.100.  do not run apache.

option 2: if you want to continue running a web server on 192.168.1.100, then you should make the apache server do a reverse proxy for GET requests to /weatherstation/updateweatherstation.php.  copy weewx-interceptor/util/apache2/conf.d/observer.conf to /etc/apache2/conf.d, change port 9999 to 8080 (in both places), then restart apache.  your existing interceptor (listening on port 8080) should start receiving data.

option 3: run a sniffer on 192.168.1.1 that sends a copy of any traffic from 192.168.1.224 to 192.168.1.100:8080

option 4: run weewx on openwrt on 192.168.1.1 in sniff mode

[kan6526]

option 3:

----------------------------------192.168.1.1 openWRT router --------------------------------------------
root@OpenWrt:~# /usr/sbin/tcpdump -i br-lan src 192.168.1.224 and port 80 | /usr/bin/nc  192.168.1.100 8080

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 65535 bytes

^C27 packets captured
28 packets received by filter
0 packets dropped by kernel
 
----------------------------------------------192.168.1.100 /etc/weewx/weewx.conf ---------------------

[Interceptor]
    driver = user.interceptor
    device_type = observer

    port = 8080
-----------------------------------------------192.168.1.100 /var/log/syslog -------------------------------------
Apr 26 22:06:26 debian-weather weewx[1663]: Reloading weewx weather system: weewx.
Apr 26 22:06:26 debian-weather weewx[1632]: engine: Received signal HUP. Restarting.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Using configuration file /etc/weewx/weewx.conf
Apr 26 22:06:27 debian-weather weewx[1632]: engine: debug is 1
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Initializing engine
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading station type Interceptor (user.interceptor)
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: MainThread: driver version is 0.30
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: MainThread: device type: observer
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: MainThread: sensor map: None
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: MainThread: mode is listen
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: MainThread: listen on :8080
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdTimeSynch
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdTimeSynch
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdConvert
Apr 26 22:06:27 debian-weather weewx[1632]: engine: StdConvert target unit is 0x1
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdConvert
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdCalibrate
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdCalibrate
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdQC
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdQC
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.wxservices.StdWXCalculate
Apr 26 22:06:27 debian-weather weewx[1632]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware
Apr 26 22:06:27 debian-weather weewx[1632]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdStationRegistry
Apr 26 22:06:27 debian-weather weewx[1632]: restx: StationRegistry: Registration not requested.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdStationRegistry
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdWunderground
Apr 26 22:06:27 debian-weather weewx[1632]: restx: Wunderground: Posting not enabled.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdWunderground
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdPWSweather
Apr 26 22:06:27 debian-weather weewx[1632]: restx: PWSweather: Posting not enabled.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdPWSweather
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdCWOP
Apr 26 22:06:27 debian-weather weewx[1632]: restx: CWOP: Posting not enabled.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdCWOP
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdWOW
Apr 26 22:06:27 debian-weather weewx[1632]: restx: WOW: Posting not enabled.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdWOW
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.restx.StdAWEKAS
Apr 26 22:06:27 debian-weather weewx[1632]: restx: AWEKAS: Posting not enabled.
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.restx.StdAWEKAS
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdPrint
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdPrint
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Loading service weewx.engine.StdReport
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Finished loading service weewx.engine.StdReport
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Starting up weewx version 3.7.1
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Station does not support reading the time
Apr 26 22:06:27 debian-weather weewx[1632]: engine: Starting main packet loop.
Apr 26 22:06:27 debian-weather weewx[1632]: interceptor: ServerThread: start tcp server
Apr 26 22:06:37 debian-weather weewx[1632]: interceptor: MainThread: empty queue
Apr 26 22:06:47 debian-weather weewx[1632]: interceptor: MainThread: empty queue

-------------------------------------192.168.1.100 iptraf-nc ---------------------------
                                                                                         ── Packets ─ Bytes ── Flag ─ Iface ─────
┌192.168.1.1:47201                                                             =       2               112      --A-    eth0            │
└192.168.1.100:8080                                                           =       1                60      S-A-    eth0      

After 15 seconds

                                                                                             ── Packets ─ Bytes ── Flag ─ Iface ─────
│┌192.168.1.1:47201                                                             =       3               164      CLOS    eth0            │
│└192.168.1.100:8080                                                           =       3               164      CLOS    eth0            │
│                                                                                                                                  

[mwall]

On Wednesday, April 26, 2017 at 10:19:47 AM UTC-4, kan6526 wrote:

option 3:

----------------------------------192.168.1.1 openWRT router --------------------------------------------
root@OpenWrt:~# /usr/sbin/tcpdump -i br-lan src 192.168.1.224 and port 80 | /usr/bin/nc  192.168.1.100 8080

it looks like the interceptor is still not receiving data.  so break it down one step at a time.

1) what is the output from tcpdump on 192.168.1.1?  is your tcpdump command actually capturing traffic?

2) what is the result of piping the output through nc?  if you run 'nc -l 8080' on 192.168.1.100, what do you see?


as a slightly different approach, what happens if you try to initiate the sniffing with a remote ssh command from 192.168.1.100 like this:

ssh 192.168.1.1 "tcpdump -U -w - -i br-lan src 192.168.1.224 and port 80" | nc localhost 8080

(i am assuming that br-lan is the correct ethernet interface on openwrt).  once again, first run the tcpdump part to verify the capture, then try adding the nc part to direct that output.

m

[kan6526]

Hi mwall

root@OpenWrt:~# tcpdump -U -w - -i br-lan src 192.168.1.224 and port 80
▒ò▒▒▒tcpdump: listening on br-lan, link-type EN10MB (Ethernet), capture size 65535 bytes
S▒Y▒::▒Q4_t\#▒E,L▒▒e▒▒k▒mP7▒▒`Ь▒▒S▒Y▒Q▒▒▒Q4_t\#▒E▒L▒▒c▒▒▒k▒mP7▒▒j}▒@P▒
'GET /data/livedata.aspx?ID=p24934&Key=Kan652266&num=360530&dateutc=2017-4-27%2011:43:14&tempf=61.0&tempf1=73.2&humidity=94&humidity1=65&baromin1=29.92&baromin=29.91&windspeedmph=15.4&windgustmph=17.4&winddir=32&rainin=0.00&dailyrainin=0.22&monthlyrainin=3.08&softwaretype=WeatherSmart%20V1.7.0 HTTP/1.0
Accept: */*
Host: data.backyard2.weatherbug.com
Connection: Close

S▒Y▒▒
     66▒Q4_t\#▒E(L▒▒e▒▒k▒mP7▒ mj}▒@P▒iYPuTTY^C3 packets captured
5 packets received by filter

0 packets dropped by kernel

mwall於 2017年4月27日星期四 UTC+8下午1時20分13秒寫道：

[kan6526]

weewx terceptor  success
http://192.168.1.100:8888/

Apr 28 12:18:54 debian-weather weewx[2604]: interceptor: ServerThread: GET:
Apr 28 12:18:54 debian-weather weewx[2604]: interceptor: MainThread: raw data:
Apr 28 12:18:54 debian-weather weewx[2604]: interceptor: MainThread: raw packet: {'usUnits': 16, 'dateTime': 1493353135}
Apr 28 12:18:54 debian-weather weewx[2604]: interceptor: MainThread: mapped packet: {'usUnits': 16, 'dateTime': 1493353135}
Apr 28 12:18:55 debian-weather weewx[2604]: interceptor: ServerThread: GET:
Apr 28 12:18:55 debian-weather weewx[2604]: interceptor: MainThread: raw data:
Apr 28 12:18:55 debian-weather weewx[2604]: interceptor: MainThread: raw packet: {'usUnits': 16, 'dateTime': 1493353135}
Apr 28 12:18:55 debian-weather weewx[2604]: interceptor: MainThread: mapped packet: {'usUnits': 16, 'dateTime': 1493353135}
Apr 28 12:19:05 debian-weather weewx[2604]: interceptor: MainThread: empty queue
Apr 28 12:19:15 debian-weather weewx[2604]: interceptor: MainThread: empty queue

-----------------------------------------------------------------------------------------------------------------------------------------------
 ssh 192.168.1.1  "tcpdump -U -w - -i br-lan src 192.168.1.224 and port 80" |nc 192.168.1.100 8888

tcpdump: listening on br-lan, link-type EN10MB (Ethernet), capture size 65535 bytes

<head>
<title>Error response</title>
</head>
<body>
<h1>Error response</h1>
<p>Error code 400.
<p>Message: Bad request syntax ('\xd4\xc3\xb2\xa1\x02\x00\x04\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\x00\x00\x01\x00\x00\x00\x8a\xc3\x02Y\xe2|\x02\x00:\x00\x00\x00:\x00\x00\x00\x04\xa1Q4_t\\\xcf\x7f#\xba*\x08\x00E\x00\x00,\x1c\xcf\x00\x00\xff\x06\x94\xef\xc0\xa8\x01\xe0k\x17\xdcm\xaa\xc2\x00P\x94\x0f+U\x00\x00\x00\x00`\x02\x16\xd0\x0c\xd2\x00\x00\x02\x04\x05\xb4\x8a\xc3\x02Y\xf9;\t\x00\xad\x01\x00\x00\xad\x01\x00\x00\x04\xa1Q4_t\\\xcf\x7f#\xba*\x08\x00E\x00\x01\x9f\x1c\xd0\x00\x00\xff\x06\x93{\xc0\xa8\x01\xe0k\x17\xdcm\xaa\xc2\x00P\x94\x0f+V\xe6m&gt;\x7fP\x18\x16\xd0\xbe\xd0\x00\x00GET /data/livedata.aspx?ID=p24934&amp;Key=&amp;num=&amp;dateutc=2017-4-28%204:22:33&amp;tempf=75.0&amp;tempf1=75.6&amp;humidity=55&amp;humidity1=50&amp;baromin1=29.93&amp;baromin=29.92&amp;windspeedmph=11.0&amp;windgustmph=15.0&amp;winddir=341&amp;rainin=0.00&amp;dailyrainin=0.00&amp;monthlyrainin=3.27&amp;softwaretype=WeatherSmart%20V1.7.0 HTTP/1.0').
<p>Error code explanation: 400 = Bad request syntax or unsupported method.
</body>

It does not work

[kan6526]

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

[gjr80]

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

[Thomas Keffer]

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

-tk

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[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

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

[Rome Weather]

I have yet to get it to work with weewx 

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/YWaFk_4S6UI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

[Andy Kerekes]

Ya have pretty much given up on weeds as nothing seems to work and no one really talking about how they got it working

To unsubscribe from this group and all its topics, send an email to weewx-user+unsubscribe@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+unsubscribe@googlegroups.com.

[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

[S R]

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

[galfert]

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

https://github.com/gjr80/weewx-gw1000

[S R]

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

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

--

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/853cc4c5-709d-491f-97b8-3fec2a1548d9n%40googlegroups.com.

[galfert]

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

[Interceptor]

driver = user.interceptor

device_type = wu-client  

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

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

Key:        xxxxxx

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

[galfert]

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

[S R]

almost there, but now

/usr/local/share/weewx # ./bin/wee_reports

Traceback (most recent call last):

  File "./bin/wee_reports", line 103, in <module>
    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)

[S R]

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.

[galfert]

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 sensors....etc. 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 server....BUT it is not WU protocol and it is not Ecowitt protocol....it 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 WH2900C....as it has a built in simple to configure "Customized" server upload feature.

[S R]

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.

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

--

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/ec3d9f49-dec2-4045-9832-9d4d6180e22an%40googlegroups.com.

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

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

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

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

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1d8cc1a8-f352-4c0e-9b9d-28a7a86ead51n%40googlegroups.com.

[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

[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" = "xxxxxxx"
    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.

[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

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/9fdffc01-22da-42d2-925c-b13bf3df4c18n%40googlegroups.com.

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

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/YWaFk_4S6UI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/fcc606b4-b356-c74a-2342-8a7c5c4a4d06%40gmail.com.