Cumulus Support

Hello,
I will Update from an WH1080 to a Froggit 1000SE. But i have Problems, the connection from CMX to the Station bring in the Mxdiag logfiles an checksum error. See below.

2022-12-28 12:24:50.609 Running Ecowitt Local API auto-discovery...
2022-12-28 12:24:50.609 Current IP address=192.168.178.66, current MAC=BC:FF:4D:0F:78:F6
2022-12-28 12:24:50.627 Using local IP address 192.168.178.61 to discover the Ecowitt device
2022-12-28 12:24:50.627 Discovery Run #1
2022-12-28 12:24:50.676 Discovered Ecowitt device: EasyWeatherPro-0F78F6 V5.1.0, IP=192.168.178.66, MAC=BC:FF:4D:0F:78:F6
2022-12-28 12:24:51.092 This Cumulus MX instance is running the latest version
2022-12-28 12:24:52.178 Discovery Run #2
2022-12-28 12:24:52.206 Discovered Ecowitt device: EasyWeatherPro-0F78F6 V5.1.0, IP=192.168.178.66, MAC=BC:FF:4D:0F:78:F6
2022-12-28 12:24:53.717 Discovered one Ecowitt device
2022-12-28 12:24:53.717 The discovered IP address for the GW1000 matches our current one
2022-12-28 12:24:53.719 Using IP address = 192.168.178.66 Port = 45000
2022-12-28 12:24:53.720 Ecowitt Gateway Connect attempt 1
2022-12-28 12:24:58.728 Ecowitt Gateway reconnected
2022-12-28 12:24:58.728 Connected OK
2022-12-28 12:24:58.729 Reading firmware version
2022-12-28 12:24:58.759 Checksum: Error - Bad checksum
2022-12-28 12:24:58.760 DoCommand(CMD_READ_FIRMWARE_VERSION): Invalid response
2022-12-28 12:24:58.760 Checksum: Error - Bad checksum
2022-12-28 12:24:58.760 command resp=80, checksum=BAD
2022-12-28 12:24:58.760 Ecowitt firmware version: ???
2022-12-28 12:24:59.092 Reading Ecowitt system info
2022-12-28 12:25:02.128 DoCommand(CMD_READ_SSSS): No response received
2022-12-28 12:25:02.128 Nothing returned from System Info!
2022-12-28 12:25:02.129 Reading sensor ids
2022-12-28 12:25:05.147 DoCommand(CMD_READ_SENSOR_ID_NEW): No response received

Is there a solution for this or can the 1000SE not work with CMX at all?


Greetings from near Leipzig

I *think* the Froggit 1000SE has to be configured as a "HTTP (Ecowitt)" station as it does not support the GW1000 API.

Thank you, this is the solution. Integrating the station as "Http Ecowitt" works. My mistake was that I entered the IP of the network gateway at "Ecowitt Gateway devices IP address:". But it has to be the IP address of the Froggit station.

Many thanks for the help.

otgatzen wrote: ↑Wed 28 Dec 2022 2:17 pm Thank you, this is the solution. Integrating the station as "Http Ecowitt" works. My mistake was that I entered the IP of the network gateway at "Ecowitt Gateway devices IP address:". But it has to be the IP address of the Froggit station.

Many thanks for the help.

I know it's an old thread, but for clarification and the sake of other readers I want to correct a misunderstanding....

Here is a misconception - when you use an Ecowitt console with the local Ecowitt Gateway API (GW1x00, GW2000, WH2650, WN19x0), you use the GW1000 option with the IP address of the console/gateway which CMX then queries.

If you use a console without the local Ecowitt Gateway API, a query from CMX will not provide console ("station") data - only firmware and weather service info. Here you have to use the customized server option (http(Ecowitt) in CMX) - however, you do not enter the IP address of the console but the IP address of the server where CMX runs on and where the console posts its data to.

Local Gateway API: CMX receives data on request
customized server option: console posts data without request from the CMX end