Ecowitt cloud vs. http.

[grwkak]

Updated to V4 with no apparent issues and have been running for about a week now.

I have an Ecowitt GW1000 that I use as a station for several extra sensors. In MX4 (and 3 prior), I configured access by selecting http Ecowitt.

One issue I have is that when I have to restart Cumulus, in the restart period I see zeros on all the extra sensor data. Would selecting the cloud fix this issue?

Guy

[Dador]

Exactly.
Fill in the data for the API and the station, after starting, will download data from the Ecowitt cloud.
I also have GW1000 and with this configuration I never have any data loss (unless there is no electricity at home).

[SamiS]

Updated to V4 with no apparent issues and have been running for about a week now.

I have an Ecowitt GW1000 that I use as a station for several extra sensors. In MX4 (and 3 prior), I configured access by selecting http Ecowitt.

One issue I have is that when I have to restart Cumulus, in the restart period I see zeros on all the extra sensor data. Would selecting the cloud fix this issue?

Do not set Ecowitt cloud as your station type. It is meant only for stations that do not have any local connectivity (eg. a station connected straight to 4g mobile network on remote location).

Edit. Cloud as station type is a different thing than the cloud api settings needed for startup catch-up that Dador is referring above.

If you are seeing zeroes only on extra sensors data, but main sensors are ok, then we probably would need a log file of the startup, and at least data logging enabled, maybe debug log would not hurt either.

Edit2. If you have GW1000, you could and probably should use Ecowitt Local API as your station type.

Edit3. Or do you have a different station as your main station?

[mcrossley]

All the Ecowitt stations use a common bit of code to perform the historic catch-up.

This is interesting (along with the requested log file)...

If you are seeing zeroes only on extra sensors data, but main sensors are ok, then we probably would need a log file of the startup, and at least data logging enabled, maybe debug log would not hurt either.

[SamiS]

All the Ecowitt stations use a common bit of code to perform the historic catch-up.

This is interesting (along with the requested log file)...

If you are seeing zeroes only on extra sensors data, but main sensors are ok, then we probably would need a log file of the startup, and at least data logging enabled, maybe debug log would not hurt either.

The user profile suggests that he could be using Davis as main station and Ecowitt http as secondary station for extra sensors. Does this option give you any clues or will it be just guessing without the logs?

[mcrossley]

Ah, if that is the case there is no catch-up for Extra Sensors from a different station type at the moment.

[grwkak]

I have a Tempest as the primary/main station, Ecowitt as additional for the extra sensors (configured in Extra Sensors menu). Both that and my Ecowitt are local to my CMX PC and on the same wireless network.

Guy