Cumulus Support

dazza1223 wrote: ↑Thu 07 Oct 2021 3:14 pm

freddie wrote: ↑Thu 07 Oct 2021 2:55 pm Good job @stefanbagnato got there in the end. For once it wasn't DNS
@dazza1223 probably need an incoming rule on your Windows firewall for port 8998.

and i haven't got windows im ruining GW-1000 on the big boys toy Linux i was pinging in on windows as it was on the same network

Okay, I don't think GW1000 runs an HTTP server so not surprised that wget failed to work.
You need to try pinging from the box that is hosting your MX installation rather than from another host. Perhaps you have an IPTables rule preventing incoming traffic on port 8998?

freddie wrote: ↑Thu 07 Oct 2021 3:49 pm

dazza1223 wrote: ↑Thu 07 Oct 2021 3:14 pm

freddie wrote: ↑Thu 07 Oct 2021 2:55 pm Good job @stefanbagnato got there in the end. For once it wasn't DNS
@dazza1223 probably need an incoming rule on your Windows firewall for port 8998.

and i haven't got windows im ruining GW-1000 on the big boys toy Linux i was pinging in on windows as it was on the same network

Okay, I don't think GW1000 runs an HTTP server so not surprised that wget failed to work.
You need to try pinging from the box that is hosting your MX installation rather than from another host. Perhaps you have an IPTables rule preventing incoming traffic on port 8998?

maybe if i ping my GW1000 that looking good

PING 10.0.0.15 (10.0.0.15) 56(84) bytes of data.
64 bytes from 10.0.0.15: icmp_seq=1 ttl=255 time=3.30 ms
64 bytes from 10.0.0.15: icmp_seq=2 ttl=255 time=8.20 ms
64 bytes from 10.0.0.15: icmp_seq=3 ttl=255 time=2.86 ms
64 bytes from 10.0.0.15: icmp_seq=4 ttl=255 time=2.85 ms
64 bytes from 10.0.0.15: icmp_seq=5 ttl=255 time=2.96 ms
64 bytes from 10.0.0.15: icmp_seq=6 ttl=255 time=3.28 ms
64 bytes from 10.0.0.15: icmp_seq=7 ttl=255 time=5.19 ms
64 bytes from 10.0.0.15: icmp_seq=8 ttl=255 time=2.81 ms
64 bytes from 10.0.0.15: icmp_seq=9 ttl=255 time=2.63 ms
64 bytes from 10.0.0.15: icmp_seq=10 ttl=255 time=5.10 ms
64 bytes from 10.0.0.15: icmp_seq=11 ttl=255 time=10.7 ms
64 bytes from 10.0.0.15: icmp_seq=12 ttl=255 time=2.63 ms

that from where Cumulus is from and i ping that ip and that good two?

PING 10.0.0.35 (10.0.0.35) 56(84) bytes of data.
64 bytes from 10.0.0.35: icmp_seq=1 ttl=64 time=0.092 ms
64 bytes from 10.0.0.35: icmp_seq=2 ttl=64 time=0.094 ms
64 bytes from 10.0.0.35: icmp_seq=3 ttl=64 time=0.073 ms
64 bytes from 10.0.0.35: icmp_seq=4 ttl=64 time=0.092 ms
64 bytes from 10.0.0.35: icmp_seq=5 ttl=64 time=0.066 ms
64 bytes from 10.0.0.35: icmp_seq=6 ttl=64 time=0.106 ms
64 bytes from 10.0.0.35: icmp_seq=7 ttl=64 time=0.119 ms

Okay so it's visible on the network. You need to check your Linux host firewall that it is allowing incoming traffic on port 8998 from your GW.

freddie wrote: ↑Thu 07 Oct 2021 4:16 pm Okay so it's visible on the network. You need to check your Linux host firewall that it is allowing incoming traffic on port 8998 from your GW.

lol now ur talking do you know there command line for that i hanvt gone that deep in to Linux


is it something like this
https://averagelinuxuser.com/linux-firewall/

Yep that's a start. What Linux distribution are you using?

thank god im on the right track.... im running raspberry pi 4 buster

Okay so SSH into your pi and type the following:
and send the result in a pm

ok will do

hi i just got this for my girlfriend

https://www.amazon.co.uk/gp/product/B09 ... UTF8&psc=1

im setting up Cumulus MX on a laptop on her network

Station model
HTTP (Ecowitt)

Configure your Ecowitt station, or GW-1000 device to send data to Cumulus using the Ecowitt protocol

In WS View configure the Custom Server to use:-
Protocol: Ecowitt
Server: CMX IP Address
Path: /station/ecowitt
Port: 8998


i put all this in the setting but still getting no data?

am i missing somthing as i can see the weather st is on the network?

Can you connect to CMX on port 8998 from a browser on computer other than where CMX is installed - to eliminate the local firewall.

yep firewall mark all sorted now!!!! is there anyway to change Interval: 20sec to like 3 sec on Cumulus MX setting?

In WS View configure the Custom Server to use:-
Protocol: Ecowitt
Server: CMX IP Address
Path: /station/ecowitt
Port: 8998
Interval: 20

Nope that is the minimum.

dazza1223 wrote: ↑Wed 17 Nov 2021 1:25 pm yep firewall mark all sorted now!!!! is there anyway to change Interval: 20sec to like 3 sec on Cumulus MX setting?

In WS View configure the Custom Server to use:-
Protocol: Ecowitt
Server: CMX IP Address
Path: /station/ecowitt
Port: 8998
Interval: 20

not in CMX - but in WS View it can be set to 16 seconds (and by the help of a tool like FOSHKplugin even down to 5 seconds)
If this has an effect on how fast, often CMX processes the received messages, I don't know - probably only Mark can tell.
Or you can test ...
In my MXdiags log file I can see that my (console's) posts are processed every 16 seconds - and 16 seconds I have set in WSView for my HP2551 console to post to CMX.
From there I would consider the 20 seconds as a recommendation, not as a hard threshold.

Going below 16 seconds only makes sense if you use a WS80 6-in-1 sensor array whose ultrasonic anemometer transmits every 4.7 seconds.
For all other Ecowitt sensors the lowest transmission interval is 16 seconds.