Ecowitt GW1200BU messes up HP2560_C

[Ken22]

My Ecowitt HP2560_C was working fine with CumulusMX. The HP2560 is set to IP 192.168.0.243.
CumulusMX is set to "Ecowitt (and clones)", "HTTP Custom Sender".
Ecowitt Gateway devices IP address is set to 192.168.0.243.
All was well.

I then plugged in a GW1200BU, setting it at IP 192.168.0.244. Both stations work well in the Ecowitt app on my cell phone.

However, when the GW1200 is powered up, the Barometer reading in CumulusMX keeps jumping up and down.

It seems to me that things should be separate. Any ideas?

Ken
===

[mcrossley]

Have you configured the same custom server in the new GW1200?

[Ken22]

Have you configured the same custom server in the new GW1200?

When I first got the gw1200, I experimented with it connecting to Cumulus and trying different settings. I got it working using the TCP Local setting and enabled Auto Discovery. When I was done experimenting, I set Cumulus back to what it had been, connecting to the HP2560.

When I discovered that Cumulus was getting two different Barometer readings, my theory was that something in Cumulus remembered to GW1200 settings. I went back into settings and took out the IP address of the 1200 and turned off Auto Discovery. This did not help. I then searched through Cumulus.ini for the MAC or IP of the 1200 and found nothing. Then rebooted my computer. The problem still existed. I then powered off the HP2560. I expected Cumulus to still be getting signals from the 1200, but it got nothing.

My new theory is the the HP2560 is getting data from the GW1200 and passing them on to Cumulus. I'll work on this today.

Ken
===

[Ken22]

More results.
On the theory that the HP2560 was relaying data, I had both running and powered off the 2560. I expected all data flow to stop, but the 1200 kept sending data.

However, if I restarted Cumulus with the 2560 off and the 1200 on, no data came through.

To recap, if the 2560 starts first, Cumulus will also accept data from the 1200, but if the 2560 is off, Cumulus will initiate communications with the 1200, but will continue already established communications.

I don't know what else I can try to figure this out.

Ken
===

[mcrossley]

As you have MX configured to the HTTP Custom sender it does not "talk" to your stations at all. It just sits there passively waiting for data to be sent by the station.

Hence my question. Because of both stations are configured with a custom server to send to the MX IP address, then MX will flip-flop between the data it receives for each station.

[Ken22]

As you have MX configured to the HTTP Custom sender it does not "talk" to your stations at all. It just sits there passively waiting for data to be sent by the station.

Okay, I understand what you are saying.

My question now would be, is there any way for me to get MX to ignore messages from the 1200 while still accepting messages from the HP2560?

Ken
===

[mcrossley]

No, it has no idea where the messages are coming from, you need to configure the stations so only one of them sends the data. Or change the station type to use the TCP API and configure it to connect to the GW1200

[mcrossley]

I guess you could configure the firewall on the machine hosting Cumulus to block traffic from the GW1200. But it would be much easier to just disable the custom server on the GW1200 wouldn't it?

[Ken22]

But it would be much easier to just disable the custom server on the GW1200 wouldn't it?

I don't know how to disable the custom server on the GW1200.

Ken
===

[Ken22]

I think I found it. This is what I was looking for. Thanks much for your help.

Ken
===

[Gyvate]

It's not the GW1200 which messes/messed up the HP2560 (impossible) but your CMX readings, but you messed it all up by not properly understanding the data flow and not properly configuring your devices.
Take a look at https://meshka.eu/Ecowitt/dokuwiki/doku ... r_services
where it is all explained.

What you seemed to have done is sending data from each of your consoles (GW1200, HP2560) to the same CMX instance and were then astonished that they got messed up. CMX cannot tell who is sending. You can't make the letter box responsible for which letters are being thrown in.

For CMX there are two ways how to get data from an Ecowitt console
1. query via the Ecowitt local API from the consoles which have this API - the GW1200 does, the HP2560 not (details see WiKi https://mesha.eu/Ecowitt/dokuwiki)
2. reception via the so-called customized server - a console sends its data to a user defined IP address (in CMX that's the http(ecowitt) "station".

The GW1200 and the HP2560 have their own inbuilt pressure sensor, and if they are not calibrated the same way, they are likely to send different values. So no surprise. So, it is your job to "synchronize" the senders.

If you want to use the data of your consoles you have to make up your mind from which console the data are supposed to come. Then configure that console. If you want it from both, you have to install a second instance of CMX and connect it with the other console.
If a console like the GW1200 has two connection option, you decide which one you are going to use and configure this in the CMX settings. If you want to use the customized server posting, you will also have to configure the customized server in the respective console. For the Ecowitt local API the configuration in CMX alone is sufficient as CMX is the active part here.

[Ken22]

What you seemed to have done is sending data from each of your consoles (GW1200, HP2560) to the same CMX instance and were then astonished that they got messed up. CMX cannot tell who is sending. You can't make the letter box responsible for which letters are being thrown in.

The problem is solved. What I was trying to do was to access both units on my Android phone (one at a time), but only access the HP2560 from my Windows 10 machine.

My problem is that I thought that "HTTP Custom Sender" would only come from the HP2560 and the API would only come from the GW1200.

When mcrossley wrote: on Sat Nov 02, 2024 12:04 pm
"But it would be much easier to just disable the custom server on the GW1200 wouldn't it?"

I finally fully understood what was happening and was able to disable "Custom Server" on the GW1200, giving me exactly what I needed, with the HP2560 not using the API, and the GW1200 not using the "Custom Server".