Cumulus Support

Posted: **Wed 19 Jul 2023 2:20 am**

[Edit: So, it turns out I mixed up model numbers. As was pointed out to me, I have the HP2560-C, which is NOT the WH2650. The former doesn't have local API access; the latter does.]

I have a new Ecowitt HP2650_C. I've been able to get CumulusMX set up to read the HTTP data coming from the 2650 using the HTTP (Ecowitt) station type with the custom server set on the console. Everything works great in that configuration. However, as I understand it, the local API access can pull in older data from the console rather than having to wait around for the console to push the latest ob (which I have set to happen every 1 min) and can pull data every ~16 s. I *think* the Ecowitt API is supposed to work with the 2650 -- see, e.g., https://osswww.ecowitt.net/uploads/2022 ... v1.6.4.pdf . In the command window / terminal, it says "Connected to station", which sounds good. However, the localhost:8998 site is showing all zeros from each sensor, and there are errors shown in the log file.

Here's a snippet of potentially relevant code from the day logfile:

Code: Select all

2023-07-18 21:00:00.972 Using IP address = 192.168.50.246 Port = 45000
2023-07-18 21:00:00.972 Ecowitt Gateway Connect attempt 1
2023-07-18 21:00:00.972 Ecowitt Gateway reconnected
2023-07-18 21:00:00.972 Connected OK
2023-07-18 21:00:00.972 Reading firmware version
2023-07-18 21:00:01.005 Checksum: Error - Bad checksum
2023-07-18 21:00:01.005 DoCommand(CMD_READ_FIRMWARE_VERSION): Invalid response
2023-07-18 21:00:01.005 Checksum: Error - Bad checksum
2023-07-18 21:00:01.005 command resp=80, checksum=BAD
2023-07-18 21:00:01.005 Received FF-FF-50-19-15-45-61-73-79-57-65-61-74-68-65-72-50-72-6F-5F-56-35-2E-31-2E
2023-07-18 21:00:01.005 Ecowitt firmware version: ???
2023-07-18 21:00:01.006 Reading Ecowitt system info
2023-07-18 21:00:01.427 This Cumulus MX instance is running the latest version
2023-07-18 21:00:03.518 DoCommand(CMD_READ_SSSS): Error - Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2023-07-18 21:00:03.518 Attempting to reopen the TCP port
2023-07-18 21:00:04.533 Ecowitt Gateway Connect attempt 1
2023-07-18 21:00:04.533 Ecowitt Gateway reconnected
2023-07-18 21:00:04.533 Nothing returned from System Info!
2023-07-18 21:00:04.539 Reading sensor ids
2023-07-18 21:00:07.044 DoCommand(CMD_READ_SENSOR_ID_NEW): Error - Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2023-07-18 21:00:07.044 Attempting to reopen the TCP port
2023-07-18 21:00:08.052 Ecowitt Gateway Connect attempt 1
2023-07-18 21:00:08.052 Ecowitt Gateway reconnected
2023-07-18 21:00:08.052 Loading last N hour data from data logs: 7/18/2023 8:49:00 PM
2023-07-18 21:00:08.052 LoadRecent: Attempting to load 7 days of entries to recent data list
2023-07-18 21:00:08.084 LoadRecent: Loaded 0 of 1 new entries to recent database
2023-07-18 21:00:08.101 LoadLast3Hour: Attempting to load 3 hour data list
2023-07-18 21:00:08.101 LoadLast3Hour: Loaded 79 entries to last 3 hour data list

I've attached the complete logfile to this email.

Any help you can provide would be greatly appreciated! Thank you!

Posted: **Wed 19 Jul 2023 7:43 am**

Looking at your log it would appear that you have picked up a GW1000 not a HP2650 using the Ecowitt protocol.

Yours states

Code: Select all

2023-07-18 21:00:00.812 Station type: 12 - GW1000

whereas my HP2551 using HTTP protocol states

Code: Select all

2023-07-15 19:06:28.082 Station type: 14 - HTTP Ecowitt

Are you allowing CumulusMX to pick up the station or have you directly pointed it at the IP address of the HP2650?

Posted: **Wed 19 Jul 2023 8:02 am**

According to the "bible" I use the 2650_C only supports the WUnderground and Ecowitt HTTP methods, there is no local API.

https://www.wxforum.net/index.php?topic ... #msg417956

Posted: **Wed 19 Jul 2023 8:41 am**

Mark according to the User manual on the Ecowitt.com you can set up a customised server.

Posted: **Wed 19 Jul 2023 10:08 am**

@water01 maybe you have misunderstood the terms?

Cusomized Server means that the console is actively sending data to the selected location.

Local API on the console means that an external client (eg CumulusMX) can send queries to the console to get the requested data.

Posted: **Wed 19 Jul 2023 10:12 am**

These are the same settings as my HP2551, so the Customised server can send out HTTP via Ecowitt (i.e. Same as Ecowitt) to an IP Host as demonstrated which can be picked up by CumulusMX as demonstrated by the manual settings page.

Posted: **Wed 19 Jul 2023 10:18 am**

SRHelicity wrote: ↑Wed 19 Jul 2023 2:20 am I have a new Ecowitt HP2650_C. I've been able to get CumulusMX set up to read the HTTP data coming from the 2650 using the HTTP (Ecowitt) station type with the custom server set on the console. Everything works great in that configuration. However, as I understand it, the local API access can pull in older data from the console rather than having to wait around for the console to push the latest ob (which I have set to happen every 1 min) and can pull data every ~16 s. I *think* the Ecowitt API is supposed to work with the 2650 -- see, e.g., https://osswww.ecowitt.net/uploads/2022 ... v1.6.4.pdf .

I think you have mixed the station models. HP2560-C (not 2650) is a graphical display console, and it does not have local api.

However WH2650 is a small black displayless gateway (functionally comparable to GW1000/1100) and it does have the local api.

Posted: **Wed 19 Jul 2023 10:19 am**

water01 wrote: ↑Wed 19 Jul 2023 10:12 am These are the same settings as my HP2551, so the Customised server can send out HTTP via Ecowitt (i.e. Same as Ecowitt) to an IP Host as demonstrated which can be picked up by CumulusMX as demonstrated by the manual settings page.

Yes, but the thread starter specifically was asking about getting the local api to work, not about the customized server.

Posted: **Wed 19 Jul 2023 3:51 pm**

SamiS wrote: ↑Wed 19 Jul 2023 10:18 am
SRHelicity wrote: ↑Wed 19 Jul 2023 2:20 am I have a new Ecowitt HP2650_C. I've been able to get CumulusMX set up to read the HTTP data coming from the 2650 using the HTTP (Ecowitt) station type with the custom server set on the console. Everything works great in that configuration. However, as I understand it, the local API access can pull in older data from the console rather than having to wait around for the console to push the latest ob (which I have set to happen every 1 min) and can pull data every ~16 s. I *think* the Ecowitt API is supposed to work with the 2650 -- see, e.g., https://osswww.ecowitt.net/uploads/2022 ... v1.6.4.pdf .
I think you have mixed the station models. HP2560-C (not 2650) is a graphical display console, and it does not have local api.

However WH2650 is a small black displayless gateway (functionally comparable to GW1000/1200) and it does have the local api.

That's exactly what I did, I think. I have the HP2560-C console, which as you note is NOT the WH2650 gateway. Ecowitt/FO and their naming conventions...

Sorry for wasting y'all's time! CumulusMX is a great tool that was surprisingly easy to configure on my Windows 11 machine -- thanks! Mods can delete this now-useless thread, unless there's a non-trivial chance that someone else will mix up model numbers like I did!

Cumulus Support

Local API access to HP2650 (EDIT: HP2560!)

Local API access to HP2650 (EDIT: HP2560!)

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650

Re: Local API access to HP2650