Fine Offset WH2900 new FW ability to upload the data to custom server

985 views
Skip to first unread message

miso k

unread,
Oct 25, 2019, 3:52:24 AM10/25/19
to weewx-user
Hello,
I have this station from Fine Offset:

In last months, after fw update it gets the ability to upload data directly to custom server in:
- weatherunderground format
- ecowitt format

Is there a simple way how to process those data to ecowitt? I dont want to mess with Interceptor.

I have one unused RPi 3B, thinking how to use it. This could be a cool project :)


Thanks for answers!
Michal, Slovakia

Ingper

unread,
Oct 25, 2019, 4:06:34 AM10/25/19
to weewx-user
Exactly the same station I'm struggling with in combination with Weewx and a also R-pi 3B (see this thread). But I'm still trying with Interceptor (is there an alternative ?). As you can see in my thread data is received by the R-Pi and seems to be available on the ethernet interface for some sniffer SW's  - but Interceptor reads empty data.

If it was a simple way, I don't think Interceptor was developed at all. But I'll follow this thread with interest, and if I get answers in my thread that helps me make Interceptor work I will surely let you know.

// Ingemar, Sweden

miso k

unread,
Oct 25, 2019, 4:18:31 AM10/25/19
to weewx-user
Hello to Sweden, Ingemar!

i am using domoticz software for home automation, runned on RPi. There is a domoticz plugin, reading the data uploaded directly from my PWS to domoticz, called PWS (https://github.com/Xorfor/Domoticz-PWS-Plugin). 
Maybe someone smarter than me can use it as a base for weewx plugin?

M

Dňa piatok, 25. októbra 2019 10:06:34 UTC+2 Ingper napísal(-a):
domoticz.JPG

miso k

unread,
Nov 1, 2019, 1:44:50 AM11/1/19
to weewx-user
Nobody?

Ingper

unread,
Nov 1, 2019, 2:47:34 AM11/1/19
to weewx-user
As you may have seen in my thread (linked above) it's possible to get it work, quite easy with "Ecowitt" protocol (but not WU) by using Interceptor. I think that is the easiest way, even though you don't want to use Interceptor driver...

Den fredag 1 november 2019 kl. 06:44:50 UTC+1 skrev miso k:
Nobody?

miso k

unread,
Nov 7, 2019, 4:35:47 AM11/7/19
to weewx-user
thanks,
is it all about weewx on rpi, or do I need to make some changes on router/somewhere else too?


Dňa piatok, 1. novembra 2019 7:47:34 UTC+1 Ingper napísal(-a):

Ingper

unread,
Nov 7, 2019, 5:57:37 AM11/7/19
to weewx-user
No change on anything else besides WS and R-Pi - if they are on the same local network. But you need of course to set a static IP (disable DHCP) on your R-pi so the WS have a known destination IP when uploading data.

miso k

unread,
Nov 17, 2019, 9:18:33 AM11/17/19
to weewx-user
Cant install it.

during install I chose Simulator driver.

then continued here:

after entering the second command
sudo wee_extension --install weewx-interceptor-master.zip

i got this

 sudo wee_extension --install weewx-interceptor-master.zip
Request to install 'weewx-interceptor-master.zip'
Traceback (most recent call last):
  File "/usr/bin/wee_extension", line 82, in <module>
    main()
  File "/usr/bin/wee_extension", line 74, in main
    ext.install_extension(options.install)
  File "/usr/share/weewx/weecfg/extension.py", line 125, in install_extension
    raise InstallError("Extension '%s' not found." % extension_path)
weecfg.extension.InstallError: Extension 'weewx-interceptor-master.zip' not found.

:(


Dňa štvrtok, 7. novembra 2019 11:57:37 UTC+1 Ingper napísal(-a):

miso k

unread,
Nov 17, 2019, 9:31:50 AM11/17/19
to weewx-user
going further:

cant find /etc/dhcpd.config on my Pi

G Hammer

unread,
Nov 17, 2019, 10:16:58 AM11/17/19
to weewx-user
Look at a directory listing and see what the file name actually is. If you copy/paste from that page you will likely find weewx-interceptor.zip to be the name of the file.

G Hammer

unread,
Nov 17, 2019, 10:19:46 AM11/17/19
to weewx-user
If you are trying to use the custom server from a Fine Offset device you don't need anything except to assign as static IP to your WeeWx machine.
No AP, no DHCPD, just a static IP from your router.

miso k

unread,
Nov 17, 2019, 11:58:03 AM11/17/19
to weewx-user

G Hammer

unread,
Nov 17, 2019, 2:21:27 PM11/17/19
to weewx-user
Look at this thread:

Joerg Strobel

unread,
Apr 17, 2020, 8:53:38 AM4/17/20
to weewx-user
Hello from Germany,

i'm happy so see this thread. I also bought a Froggit WH3000SE. it's a Fine Offset WH2900 clone.
Since about one month i try to get the data from the Weather Station into my Raspberry Pi 4. I modified the RPI to an Accesspoint so that the Weather Station can connect over WLAN to the RPI. To catch the data from the weather station i use the weewx interceptor. But i wondered, why interceptor doesn't get any data from my weather station. With tcpdump i can't see any data from my weather station. I'm sure that the WS is connected to the RPI.Yesterday i connected my WS to the Ecowitt.net website. Every 60sec. the Ecowitt website gets the data from my WS. But what's wrong with tcpdump. 
The IP from my WS is 192.168.124.11.

with tcpdump i get this log.

pi@rpi-ap:~ $ sudo tcpdump -i wlan0 host 192.168.124.11

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on wlan0, link-type EN10MB (Ethernet), capture size 262144 bytes

14:45:15.788770 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:15.944508 IP rpi-ap.39178 > 192.168.124.11.hostmon: Flags [S], seq 3215304889, win 64240, options [mss 1460,sackOK,TS val 1504181529 ecr 0,nop,wscale 7,tfo  cookiereq,nop,nop], length 0

14:45:15.944811 IP rpi-ap.39180 > 192.168.124.11.hostmon: Flags [S], seq 3877188730, win 64240, options [mss 1460,sackOK,TS val 1504181529 ecr 0,nop,wscale 7,tfo  cookiereq,nop,nop], length 0

14:45:16.047568 IP 192.168.124.11.hostmon > rpi-ap.39178: Flags [R.], seq 0, ack 3215304890, win 5840, length 0

14:45:16.051489 IP 192.168.124.11.hostmon > rpi-ap.39180: Flags [R.], seq 0, ack 3877188731, win 5840, length 0

14:45:17.790363 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:19.791299 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:21.791665 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:23.795072 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:25.796424 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:27.795023 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:29.800054 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:31.799759 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:33.800491 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:35.798821 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:37.802714 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:39.802506 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:41.802255 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:43.805888 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:45.804335 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:47.805116 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:49.809307 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:51.811060 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:53.808178 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:55.808909 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:57.812490 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:45:59.813433 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:01.817349 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:03.812795 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:05.813742 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:07.814571 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:09.818768 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:11.816982 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:12.555902 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [S], seq 398209, win 5840, options [mss 1460], length 0

14:46:12.904968 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [S.], seq 4157333541, ack 398210, win 29200, options [mss 1444], length 0

14:46:12.991712 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [P.], seq 1:593, ack 1, win 5840, length 592: HTTP: POST /data/report/ HTTP/1.1

14:46:13.350249 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [.], ack 593, win 30192, length 0

14:46:13.364577 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [P.], seq 251:256, ack 593, win 30192, length 5: HTTP

14:46:13.364680 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [P.], seq 1:251, ack 593, win 30192, length 250: HTTP: HTTP/1.1 200 OK

14:46:13.364743 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [F.], seq 256, ack 593, win 30192, length 0

14:46:13.398901 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [.], ack 1, win 5840, length 0

14:46:13.402126 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [F.], seq 593, ack 257, win 5584, length 0

14:46:13.820562 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:14.705361 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [FP.], seq 1:256, ack 593, win 30192, length 255: HTTP: HTTP/1.1 200 OK

14:46:14.825807 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [R.], seq 593, ack 257, win 5840, length 0

14:46:15.819136 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:17.391656 IP 47.102.253.116.http > 192.168.124.11.44279: Flags [FP.], seq 1:256, ack 593, win 30192, length 255: HTTP: HTTP/1.1 200 OK

14:46:17.489029 IP 192.168.124.11.44279 > 47.102.253.116.http: Flags [R.], seq 593, ack 257, win 5840, length 0

14:46:17.820262 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:17.942710 ARP, Request who-has 192.168.124.11 tell rpi-ap, length 28

14:46:17.946136 ARP, Reply 192.168.124.11 is-at 2c:f4:32:4e:34:7c (oui Unknown), length 28

14:46:19.823604 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:21.824897 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:23.825912 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:25.827268 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:27.828712 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:29.826797 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:31.829809 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:33.831444 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:35.832886 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:37.831184 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:39.831137 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:41.834680 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:43.836079 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:45.834353 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:47.836037 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:49.838858 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:51.839997 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:53.841944 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:55.839077 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:57.840414 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:46:59.844133 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:01.845152 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:03.843317 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:05.844353 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:07.847777 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:09.849336 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:11.847257 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:13.848423 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:15.850068 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:16.553111 IP 192.168.124.11.4096 > rpi-ap.domain: 64569+ A? rtpdate.ecowitt.net. (37)

14:47:17.503269 IP 192.168.124.11.4096 > rpi-ap.domain: 357+ A? rtpdate.ecowitt.net. (37)

14:47:17.853221 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:18.528127 IP 192.168.124.11.4096 > rpi-ap.domain: 39196+ A? rtpdate.ecowitt.net. (37)

14:47:18.855228 IP 192.168.124.11.4096 > rpi-ap.domain: 5630+ A? www.amazon.com. (32)

14:47:19.553140 IP 192.168.124.11.4096 > rpi-ap.domain: 42153+ A? www.amazon.com. (32)

14:47:19.854768 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:20.579055 IP 192.168.124.11.4096 > rpi-ap.domain: 27538+ A? www.amazon.com. (32)

14:47:20.579913 IP 192.168.124.11.4096 > rpi-ap.domain: 9124+ A? rtpdate.ecowitt.net. (37)

14:47:21.855181 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:22.577836 IP 192.168.124.11.4096 > rpi-ap.domain: 6765+ A? www.amazon.com. (32)

14:47:23.856055 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:24.578103 IP 192.168.124.11.4096 > dns.google.domain: 43148+ A? rtpdate.ecowitt.net. (37)

14:47:24.855680 IP 192.168.124.11.4096 > rpi-ap.domain: 25532+ A? www.baidu.com. (31)

14:47:24.891779 IP dns.google.domain > 192.168.124.11.4096: 43148 1/0/0 A 47.102.253.116 (53)

14:47:24.897002 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:47:25.600429 IP 192.168.124.11.4096 > rpi-ap.domain: 32773+ A? www.baidu.com. (31)

14:47:25.600696 IP 192.168.124.11.4096 > dns.google.domain: 33952+ A? rtpdate.ecowitt.net. (37)

14:47:25.621534 IP dns.google.domain > 192.168.124.11.4096: 33952 1/0/0 A 47.102.253.116 (53)

14:47:25.628296 IP 192.168.124.11.30147 > 47.102.253.116.http: Flags [S], seq 401753, win 5840, options [mss 1460], length 0

14:47:25.857167 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:26.607767 IP 192.168.124.11.4096 > dns.google.domain: 51397+ A? www.amazon.com. (32)

14:47:26.608130 IP 192.168.124.11.4096 > rpi-ap.domain: 28796+ A? www.baidu.com. (31)

14:47:26.609174 IP 192.168.124.11.30147 > 47.102.253.116.http: Flags [S], seq 401753, win 5840, options [mss 1460], length 0

14:47:26.629435 IP dns.google.domain > 192.168.124.11.4096: 51397 4/0/0 CNAME tp.47cf2c8c9-frontier.amazon.com., CNAME www.amazon.com.edgekey.net., CNAME e15316.e22.akamaiedge.net., A 23.210.253.71 (160)

14:47:26.640937 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:47:26.967890 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [S.], seq 762804629, ack 401754, win 29200, options [mss 1444], length 0

14:47:27.128823 IP 192.168.124.11.30147 > 47.102.253.116.http: Flags [P.], seq 1:592, ack 1, win 5840, length 591: HTTP: POST /data/report/ HTTP/1.1

14:47:27.493284 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [.], ack 592, win 30141, length 0

14:47:27.503872 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [P.], seq 251:256, ack 592, win 30141, length 5: HTTP

14:47:27.504974 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [P.], seq 1:251, ack 592, win 30141, length 250: HTTP: HTTP/1.1 200 OK

14:47:27.505097 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [F.], seq 256, ack 592, win 30141, length 0

14:47:27.532097 IP 192.168.124.11.30147 > 47.102.253.116.http: Flags [.], ack 1, win 5840, length 0

14:47:27.539192 IP 192.168.124.11.30147 > 47.102.253.116.http: Flags [F.], seq 592, ack 257, win 5584, length 0

14:47:27.600096 IP 192.168.124.11.4096 > dns.google.domain: 38019+ A? www.amazon.com. (32)

14:47:27.619041 IP dns.google.domain > 192.168.124.11.4096: 38019 3/0/0 CNAME tp.47cf2c8c9-frontier.amazon.com., CNAME d3ag4hukkh62yn.cloudfront.net., A 52.222.159.131 (127)

14:47:27.625764 IP 192.168.124.11 > server-52-222-159-131.fra53.r.cloudfront.net: ICMP echo request, id 44975, seq 253, length 40

14:47:27.642012 IP server-52-222-159-131.fra53.r.cloudfront.net > 192.168.124.11: ICMP echo reply, id 44975, seq 253, length 40

14:47:27.858816 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:27.896288 IP 47.102.253.116.http > 192.168.124.11.30147: Flags [.], ack 593, win 30141, length 0

14:47:28.604575 IP 192.168.124.11.4096 > rpi-ap.domain: 1332+ A? www.baidu.com. (31)

14:47:29.855941 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:29.942712 ARP, Request who-has 192.168.124.11 tell rpi-ap, length 28

14:47:29.946355 ARP, Reply 192.168.124.11 is-at 2c:f4:32:4e:34:7c (oui Unknown), length 28

14:47:31.859586 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:32.605317 IP 192.168.124.11.4096 > dns.google.domain: 35375+ A? www.baidu.com. (31)

14:47:32.624314 IP dns.google.domain > 192.168.124.11.4096: 35375 4/0/0 CNAME www.a.shifen.com., CNAME www.wshifen.com., A 104.193.88.123, A 104.193.88.77 (116)

14:47:32.629100 IP 192.168.124.11 > 104.193.88.123: ICMP echo request, id 44975, seq 254, length 40

14:47:32.801364 IP 104.193.88.123 > 192.168.124.11: ICMP echo reply, id 44975, seq 254, length 40

14:47:33.861373 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:35.913759 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:37.863103 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:39.861085 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:41.864791 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:43.862880 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:45.867925 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:47.865709 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:49.866631 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:51.870157 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:53.870391 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:55.869363 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:57.869657 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:47:59.873225 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:01.874706 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:03.876001 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:05.874022 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:07.875795 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:09.876313 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:11.879906 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:13.878192 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:15.879267 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:17.882840 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:19.883743 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:21.882262 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:23.883467 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:25.886571 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:27.889276 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:29.890141 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:31.670883 IP 192.168.124.11.4096 > rpi-ap.domain: 44057+ A? cdnrtpdate.ecowitt.net. (40)

14:48:31.889554 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:32.126218 IP 192.168.124.11.4096 > rpi-ap.domain: 3869+ A? cdnrtpdate.ecowitt.net. (40)

14:48:33.151118 IP 192.168.124.11.4096 > rpi-ap.domain: 31924+ A? cdnrtpdate.ecowitt.net. (40)

14:48:33.890399 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:35.151089 IP 192.168.124.11.4096 > rpi-ap.domain: 42998+ A? cdnrtpdate.ecowitt.net. (40)

14:48:35.891338 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:37.892442 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:38.856167 IP 192.168.124.11.4096 > rpi-ap.domain: 60521+ A? www.amazon.com. (32)

14:48:39.151148 IP 192.168.124.11.4096 > dns.google.domain: 11040+ A? cdnrtpdate.ecowitt.net. (40)

14:48:39.153326 IP 192.168.124.11.4096 > rpi-ap.domain: 13613+ A? www.amazon.com. (32)

14:48:39.567636 IP dns.google.domain > 192.168.124.11.4096: 11040 2/0/0 CNAME cdnrtpdate.ecowitt.net.w.kunlunsl.com., A 47.246.43.207 (107)

14:48:39.572528 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:48:39.894377 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:40.150904 IP 192.168.124.11.4096 > dns.google.domain: 12693+ A? cdnrtpdate.ecowitt.net. (40)

14:48:40.152260 IP 192.168.124.11.4096 > rpi-ap.domain: 49507+ A? www.amazon.com. (32)

14:48:40.216560 IP dns.google.domain > 192.168.124.11.4096: 12693 2/0/0 CNAME cdnrtpdate.ecowitt.net.w.kunlunsl.com., A 47.246.43.207 (107)

14:48:40.223151 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:48:41.894458 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:42.197949 IP 192.168.124.11.4096 > dns.google.domain: 22712+ A? cdnrtpdate.ecowitt.net. (40)

14:48:42.198419 IP 192.168.124.11.4096 > rpi-ap.domain: 34253+ A? www.amazon.com. (32)

14:48:42.212379 IP dns.google.domain > 192.168.124.11.4096: 22712 2/0/0 CNAME cdnrtpdate.ecowitt.net.w.kunlunsl.com., A 47.246.43.207 (107)

14:48:42.215523 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:48:43.896177 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:44.582706 ARP, Request who-has 192.168.124.11 tell rpi-ap, length 28

14:48:44.741350 ARP, Reply 192.168.124.11 is-at 2c:f4:32:4e:34:7c (oui Unknown), length 28

14:48:44.852845 IP 192.168.124.11.4096 > rpi-ap.domain: 55556+ A? www.baidu.com. (31)

14:48:45.200447 IP 192.168.124.11.4096 > rpi-ap.domain: 26611+ A? www.baidu.com. (31)

14:48:45.896273 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:46.224930 IP 192.168.124.11.4096 > dns.google.domain: 42383+ A? www.amazon.com. (32)

14:48:46.225533 IP 192.168.124.11.4096 > rpi-ap.domain: 38729+ A? www.baidu.com. (31)

14:48:46.248768 IP dns.google.domain > 192.168.124.11.4096: 42383 4/0/0 CNAME tp.47cf2c8c9-frontier.amazon.com., CNAME www.amazon.com.edgekey.net., CNAME e15316.e22.akamaiedge.net., A 23.210.253.71 (160)

14:48:46.253574 IP 192.168.124.11 > dns.google: ICMP 192.168.124.11 udp port 4096 unreachable, length 36

14:48:47.224955 IP 192.168.124.11.4096 > dns.google.domain: 53064+ A? www.amazon.com. (32)

14:48:47.242728 IP dns.google.domain > 192.168.124.11.4096: 53064 4/0/0 CNAME tp.47cf2c8c9-frontier.amazon.com., CNAME www.amazon.com.edgekey.net., CNAME e15316.e22.akamaiedge.net., A 23.210.253.71 (160)

14:48:47.248390 IP 192.168.124.11 > a23-210-253-71.deploy.static.akamaitechnologies.com: ICMP echo request, id 44975, seq 255, length 40

14:48:47.265116 IP a23-210-253-71.deploy.static.akamaitechnologies.com > 192.168.124.11: ICMP echo reply, id 44975, seq 255, length 40

14:48:47.895752 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:48.248977 IP 192.168.124.11.4096 > rpi-ap.domain: 57509+ A? www.baidu.com. (31)

14:48:49.898830 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:51.900870 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:52.249397 IP 192.168.124.11.4096 > dns.google.domain: 56486+ A? www.baidu.com. (31)

14:48:52.263262 IP dns.google.domain > 192.168.124.11.4096: 56486 3/0/0 CNAME www.a.shifen.com., CNAME www.wshifen.com., A 103.235.46.39 (100)

14:48:52.268378 IP 192.168.124.11 > 103.235.46.39: ICMP echo request, id 44975, seq 256, length 40

14:48:52.524397 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [S], seq 405315, win 5840, options [mss 1460], length 0

14:48:52.531724 IP 103.235.46.39 > 192.168.124.11: ICMP echo reply, id 44975, seq 256, length 40

14:48:53.349094 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [S], seq 405315, win 5840, options [mss 1460], length 0

14:48:53.902241 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:54.362501 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [S], seq 405315, win 5840, options [mss 1460], length 0

14:48:54.730503 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [S.], seq 2440720010, ack 405316, win 29200, options [mss 1444], length 0

14:48:54.785575 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [P.], seq 1:592, ack 1, win 5840, length 591: HTTP: POST /data/report/ HTTP/1.1

14:48:55.155121 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [.], ack 592, win 30141, length 0

14:48:55.170050 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [F.], seq 256, ack 592, win 30141, length 0

14:48:55.170160 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [P.], seq 1:251, ack 592, win 30141, length 250: HTTP: HTTP/1.1 200 OK

14:48:55.170208 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [P.], seq 251:256, ack 592, win 30141, length 5: HTTP

14:48:55.192260 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [.], ack 1, win 5840, length 0

14:48:55.199275 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [F.], seq 592, ack 257, win 5584, length 0

14:48:55.902934 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:56.500169 IP 47.102.253.116.http > 192.168.124.11.20545: Flags [FP.], seq 1:256, ack 592, win 30141, length 255: HTTP: HTTP/1.1 200 OK

14:48:56.504724 IP 192.168.124.11.20545 > 47.102.253.116.http: Flags [R.], seq 592, ack 257, win 5840, length 0

14:48:57.903863 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:48:59.904924 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:01.906177 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:03.907349 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:05.905150 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:07.905992 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:09.910328 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:11.911895 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:13.908901 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:15.909930 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

14:49:17.916884 IP 192.168.124.11.2525 > 255.255.255.255.59387: UDP, length 39

^C

229 packets captured

229 packets received by filter

0 packets dropped by kernel


 

miso

unread,
Apr 17, 2020, 8:58:22 AM4/17/20
to weewx...@googlegroups.com
Hi Joerg. Forget the RPi accesspoint. It gets much easier by setting your weather station to send packets to custom server- would be RPi. Install latest Vs wire app on your Android phone and update the firmware. Last screen of the servers to upload is custom server.

I made it according to Czech webpage, works!

Dňa pi 17. 4. 2020, 14:53 'Joerg Strobel' via weewx-user <weewx...@googlegroups.com> napísal(a):
--
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/zEXfYCyTPb0/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/58c32518-0701-4a3b-b3c8-0cc8635e7aac%40googlegroups.com.

Mosconi

unread,
Apr 17, 2020, 3:43:16 PM4/17/20
to weewx-user
Thanks so far. I was looking for your app but i can't find it. Do you mean WS View? In this app, i can't find a field for a firmware version or an update.

Joerg
To unsubscribe from this group and all its topics, send an email to weewx...@googlegroups.com.

miso

unread,
Apr 17, 2020, 4:08:18 PM4/17/20
to weewx...@googlegroups.com
Yes, vs view. When i click on weather station, it offers update, when available. Latest is 1.4.9 I think

Dňa pi 17. 4. 2020, 21:43 Mosconi <joer...@gmail.com> napísal(a):
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/97265a98-1563-40e1-8af6-8684438e1874%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages