No connection with GW1000 wifi gateway

[galfert]

I attached the log files. I disabled auto-discovery.

I have only one GW-1000 wi-fi gateway. My firmware version: GW1000A_V1.5.8.

Can you ping the IP address of the GW1000?

Yes. Generated response:

Code: Select all

Pinging 192.xxx.x.15 with 32 bytes of data:
Reply from 192.xxx.x.15: bytes=32 time=128ms TTL=255
Reply from 192.xxx.x.15: bytes=32 time=143ms TTL=255
Reply from 192.xxx.x.15: bytes=32 time=59ms TTL=255
Reply from 192.xxx.x.15: bytes=32 time=291ms TTL=255

Ping statistics for 192.xxx.x.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 59ms, Maximum = 291ms, Average = 155ms

Still something blocks the connection.

Something is not right with your network. Those ping response times are way too high for a local network. Also there is no need to obfuscate your internal IP addresses as internal IP addresses are not able to be reached from the Internet.

Did you ping test to the GW1000 from the Cumulus MX computer?

Please provide more details about your network.
Brand router
Is the WiFi access point also the main router?
How many other network devices exist on the network?
How many WiFi access points? ... Any WiFi extenders or mesh nodes?
What is the router's LAN side IP address and subnet mask?
What is the Cumulus MX computer's IP address and subnet mask?
Is the Cumulus MX computer on both WiFi and Ethernet at the same time?
Is your modem in bridge mode? Or is the modem also the WiFi access point?

[Mark14]

Did you ping test to the GW1000 from the Cumulus MX computer?

Yes, I did. Today the times are shorter.

Code: Select all

Pinging 192.168.1.15 with 32 bytes of data:
Reply from 192.168.1.15: bytes=32 time=131ms TTL=255
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255

Ping statistics for 192.168.1.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 131ms, Average = 35ms

I am connected to the same wifi network as GW-1000 but I have wifi extender. When I switch it off I have better ping response:

Code: Select all

Pinging 192.168.1.15 with 32 bytes of data:
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255
Reply from 192.168.1.15: bytes=32 time=3ms TTL=255
Reply from 192.168.1.15: bytes=32 time=9ms TTL=255

Ping statistics for 192.168.1.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 9ms, Average = 4ms

Brand router: Orange FunBox 3.0. I don't know if that tells you anything, it's a standard router by SAGEMCOM with fiber optic connection.

Is the WiFi access point also the main router?

Yes, and all Ecowitt devices connect to main router.

How many other network devices exist on the network?

2 display consoles by Ecowitt and GW1000 connect to the wifi network. Besides, my laptop, smart TV and set-top box.

How many WiFi access points? ... Any WiFi extenders or mesh nodes?

Yes, one but I use main WiFi access point from the router.

What is the router's LAN side IP address and subnet mask?

192.168.1.1 and subnet mask: 255.255.255.0

Is the Cumulus MX computer on both WiFi and Ethernet at the same time?

No, my laptop is only connected by WiFi (I don't have any Ethernet input).

Is your modem in bridge mode? Or is the modem also the WiFi access point?

I guess it is not possible to set the bridge mode. Yes, it is the WiFi access point.

[mcrossley]

2 display consoles by Ecowitt and GW1000 connect to the wifi network.

Ah, that may be relevant, do either of the consoles show up in WSview?

Anyway, try version 3.6.0 I have just released - the disabling discovery should work properly now.

[galfert]

I recommend powering down the GW1000. Then ping 192.168.1.15 and see if there is a response. Looking for IP address conflict.
If you get no response then it almost rules out IP conflict...but the other device could be blocking ICMP pings.

Your new ping times do look normal now.

Test new Cumulus MX version like Mark suggested and let us know.

All display consoles show up on WS View. But they don't support the GW1000 local API for data. The display consoles show up on WS View for the purpose of configuring their upload to Ecowitt.net/Ambientweather.net and WU, WeatherCloud...etc. And they also show up on WS View for purpose of firmware updates.

[galfert]

Delete ...double post mistake.

[mcrossley]

If you have more than one device then I suspect that you will have to disable auto-discovery in CMX as currently it just uses the first device to respond to the device query.

@Mark14's problem though is that no device appears to be responding, or at least the response getting back to CMX

[galfert]

I am connected to the same wifi network as GW-1000 but I have wifi extender. When I switch it off I have better ping response:

So you have a WiFi extender and this can be a problem. I recommend testing without the WiFi extender. Move the Cumulus MX computer and the GW1000 so that they are both near the main WiFi router. Then test. Make sure that the WiFi extender is powered down during this test too.

Let use know the results.

There are various ways to do WiFi extender setup. If the WiFi extender is not a true access point it could be acting as a second network and not allow traffic to pass both ways back and forth between network devices. Meaning that there is a route one way but that there is no route back.

[Mark14]

2 display consoles by Ecowitt and GW1000 connect to the wifi network.

Ah, that may be relevant, do either of the consoles show up in WSview?

Anyway, try version 3.6.0 I have just released - the disabling discovery should work properly now.

Yes, both consoles are also detected by WSView.

Thanks guys for all the assistance. The new update 3.6.0 has solved the issue and Cumulus receives readings from GW1000. I only disabled Auto-Discovery.