Cumulus Support

I am trying to improve the GW-1000 auto-discovery process. To that end I have created a small test utility that should discover the Ecowitt devices on your network.

So, if you have either...

1. A non-Ecowitt branded GW-1000 type device.
or
2. An Ecowitt/Ambient or other rebranded Ecowitt weather station that supports being read by the WS View app.

Then could you download the utility and run it for me please. It will just list the devices it finds on the network and exit. If you could copy the output and post it here that would great. I'm not bothered about the IP addresses, they are there to help you figure out which device is which, so you can blank that info if you wish.

The utility will run on Windows natively, or Linux using mono.

Cheers

https://weather.wilmslowastro.com/downl ... overy2.zip

I had to run it as admin on my Windows 10 version 20H2 name is the same as I see in WS View

I don't have a full Ecowitt station, just their PM2.5 and soil moisture. Also running it as admin on Windows10 it discovered the GW1000

Discovered Ecowitt device: IP=192.168.0.52, name=GW1000-WIFI1117

Press any key to continue . . .

Enjoy,
Paul

Mark,
This is a great improvement. The existing Cumulus MX discovery does not work well because it detects my other non-GW1000 hardware. I have a WS-2000, WS-2902A, and the GW1000. Therefore I have to turn off auto-discovery. The good news is that this new discovery is only resulting in the GW1000 and I ran it a few times to make sure it was not a random luck thing. Every time it resulted in just finding the GW1000.

My tests were done in Linux too:


UPDATE: Just tested again without sudo and it works that way too.

It is my understanding that if you do a UDP broadcast with hex command 0x12 that only a GW1000 or a WH2650 should respond....but I haven't tested this.
Is this the method used in this new discovery?...and do you have to filter the AP SSID name for GW1000 also?

Actually that is not what I was expecting, I thought it would list all your devices! Currently MX is just using the first device to respond, this was an attempt to capture them all, maybe it isn't waiting long enough. I'll create a new version that listens for longer and timestamps the responses, my gw1000 seems to respond multiple times.

Like MX it uses the broadcast mechanism, but all the eligible devices respond, I am looking for a way of detecting just GW-1000 devices. My doubt was that the rebranded versions may have a different name - ie not start with "GW1000". Hence I'd like to see responses from stations and non-Ecowitt gateways.

It seems the broadcast name is the same as that used in the WS View app, so if people could just take a look in there and report the names that should be sufficient.

OK, a new zip uploaded, this will run for 10 seconds. My GW1000 seems to broadcast its presence every 2-ish seconds.

https://weather.wilmslowastro.com/downl ... overy2.zip

Why do you need to find the other devices? You can only get data from the GW1000 and WH2650 via the GW1000 API, so who cares about the other consoles. Why do they need to be found?

If you only find the GW1000 (and WH2650) then that is a good method.

Some people though have more than one GW1000...and for those I suppose turning off the Auto-discover would be best. Unless you can come up with a method to find and then select form a list of options. But then you'd need a way to lock into that MAC. I'm turning off the Auto-discover now because you are finding my other consoles that will not work with the GW1000 API method of getting data.

I still think the best solution is for people to set a DHCP IP address reservation for the GW1000 / WH2650 / DP1500, and then enter the IP manually. But I understand trying to make it easier.

Its not that I'm "trying" to find the other devices, but as you have found they all respond to the discovery message I send. So I need a way of filtering them. Hence I need to know for sure what "names" these devices use.

Still only getting the GW1000. That is good. I don't know what method you were using before. But like I said if you are using the documented UDP broadcast hex command 0x12 then I think that it will only apply to GW1000 / WH2650 / DP1500 devices.

Here is my WS View devices discovery.

Thanks for that. This is using exactly the same method as MX always has, not sure why you are not seeing the other devices now?

OK folks, what I need now is confirmation that the Ambient/Froggit/whatever GW1000 equivalents also have names beginning with "GW1000"

I remember someone on wxforum.net sharing that the DP1500 does show up as GW1000 in WS View. I'm searching for that reference but I can't find it.
Shouldn't be too hard to get someone with a DP1500 to chime in.
But a WH2650 is rare....but Gyvate has one.

Some more testing shows that the GW1000 actually ignores the broadcast request.

From power on it broadcasts anyway, every 2 seconds, forever. The is no immediate response to the request I send.

So my current live code will be hit and miss as it only waits 1 second for a response - a lifetime if it actually responded, but it don't.

I'll change my code so that I wait longer.

Interesting...so you are saying that you don't need to send the broadcast request because it is advertising itself anyway every 2 seconds?