Cumulus Support

Just looking at this page & there's a lot of fields there.

10 for Temp, Humidity & Dew.
16 for Soil Temp & Moisture.
8 Air Qual.
4 for Leaf moisture etc
& 3 for Lightning.

Typically how are these fields populated, outside of the additional Davis stations that can be added (Up to 8 total from memory).

But how is Lightning treated?
Personally, I run a Blitzortung station (1928), can that be interfaced for starters?

Thanks in Advance.

Phil.

(Mulling over other ideas in this area, but don't have it quite clear in my head just yet).

Currently Davis stations (VP2 or WLL) can populate some of the extra fields.

The Ecowitt GW1000 can populate even more, the leak detection, air quality, and lightning fields are only used by those stations (currently). The GW1000 also supports more sensors attached concurrently than the Davis VP2.

What I've been mulling over goes back to Cumulus 1 & the way it read Easy Weather data.

Is a similar variation worth consideration for MX.

Not for the main data stream but as an additional data source for Extra sensors.

If whatever application a user was to choose could write a simple CSV file (or 5 for the above groups???),
then the option in MX could be set to read Extra data from that file.
Extras.csv or ExTemp, ExSoil, ExAir, etc.

The Extra files would only require a single line & some formatting rules and there would need to be provision station connected sensors as well as CSV supported sensors.

Then Arduino's, rPi etc could be responsible for writing the Extras csv & MX could be pointed to it.

Would be best to suit all FQDN's;
IE
C:\Whatever\Extra.csv
\\Server\Sharename\Extra.csv
http://domain.com/data/Extra.csv

Very simple in conceptual terms, but implementation would be an different thing.

Is the any demand for such a facility by other users? To make external data sort of universally available.

Cheers

Phil.

GW1000 works in this way: CumulusMX sends a request packet to the GW1000 and GW1000 answers with a binary packet.
This binary packet contains all data captured by the GW1000 from remote sensors.
These can be only one or can be a lot of sensors. More sensor mean bigger packet.
To add a sensor I simply turn on it (insert the batteries) and the GW1000 automatically registers it and starts to add data from it.
Then CumulusMX receives a packet that is a little bigger and has the new sensor data. I don't have to change any setting. New record inside packet can be long one, two or more bytes, you know how many bites only if you know the sensor ID.
If instead you have to set some setting, CumulusMX will be unable to decode the packet because when it will find the unknown ID it doesn't know how many bytes it has to discard.