Cumulus Support

Just found this post and wanted to ask exactly how the 2.5 second updated weather data is accessed. I just purchased a 6263 system in December and of course it has the 6313 console. I also would like to have access to 2.5 sec data. I don’t see any serial output from the 6100 WTT so assume it would only be available on the LAN since it has a network cable port. Has anyone actually set this up? What format is the data presented and how is it accessed?
I apologize is I am beating a dead horse here but don’t want to purchase a 6100WLL only to fine It doesn’t do what I think it does.
I am concerned that it is encrypted in some fashion.
I have had a Peet Brothers system for over 20 years and have enjoyed live data (1 sec). So disappointed in Davis Weather’s decision to lock our weather data.
Thanks in advance for any help.

Hi,

Just found this post and wanted to ask exactly how the 2.5 second updated weather data is accessed. I just purchased a 6263 system in December and of course it has the 6313 console. I also would like to have access to 2.5 sec data. I don’t see any serial output from the 6100 WTT so assume it would only be available on the LAN since it has a network cable port. Has anyone actually set this up? What format is the data presented and how is it accessed?

I don't know the technical side, but CumulusMX is able to access the live data from the Weatherlink Live device through its local IP address that is then set in the CumulusMX network settings for the station.

Mark will know all the particulars for CumulusMX to access the data.

Enjoy,
Paul

The WLL multicasts the 2.5 second data packets on the local network (when requested).

mcrossley wrote: ↑Tue 21 Jan 2025 10:32 am The WLL multicasts the 2.5 second data packets on the local network (when requested).

So what data can Cumulus MX intercept and at these intervals, and which data is only available as downloaded from the Davis weatherlink cloud at whatever intervals you pay for? What is the end result of the larger intervals on Cumulus MX data so far as historical records and graphing created by Cumulus MX go?

SUBYDAZZ wrote: ↑Wed 19 Feb 2025 6:55 am

mcrossley wrote: ↑Tue 21 Jan 2025 10:32 am The WLL multicasts the 2.5 second data packets on the local network (when requested).

So what data can Cumulus MX intercept and at these intervals, and which data is only available as downloaded from the Davis weatherlink cloud at whatever intervals you pay for? What is the end result of the larger intervals on Cumulus MX data so far as historical records and graphing created by Cumulus MX go?

From the WLL Cumulus gets Wind and Rain data every 2.5 seconds, all other data at 1-minute intervals.

The only data that comes from the cloud is historic data for "catch-up" for periods that Cumulus is not running.

Hi all,

I've got the weather link live console, but when trying to use the Cumulus MX, the diag log, states that the machine refused the connection to the API witht the correct WLL console ip.

Any help would be apreciated.

Hi,

I've got the weather link live console,

The title of this thread says 6313 which is the new Weatherlink Console (colour console). The Davis Weatheslink Live device is 6100.
If you are asking about the 6100 Weatherlink Live then make sure you have the 'Weatherlink Live' selected in Station type settings, then under Davis Weatherlink Live > Network Settings > tick Auto Discovery or enter your local IP address for your WLL device
Then fill in your Weatherlink.com API Detail

If you have done that and still not connecting please zip and attach the MXdiags log file and we can have a look.

Enjoy,
Paul

rjacome wrote: ↑Wed 19 Feb 2025 8:41 pm Hi all,

I've got the weather link live console, but when trying to use the Cumulus MX, the diag log, states that the machine refused the connection to the API witht the correct WLL console ip.

Any help would be apreciated.

Double-check that the IP address for the console is correctly set in Cumulus MX. Also, make sure you have an internet connection and there are no firewalls blocking the connection. Try restarting both the console and Cumulus MX, and see if that helps