Extra Sensors, particularly WN31

[mcrossley]

The extra sensor data is logged in the "ExtraLogYYYYMM.txt" files. See the header file in \MXutils\fileheaders folder for details of which field is which.

If an extra sensor is mapped to a primary sensor, it will still be logged in the ExtraLog files as well as being logged in the primary data files.

[chsims1]

Thanks for that Mark.

Is there a relatively simple way to get this daily data analysed by CMX to produce historical summaries ..... max, min, average, weekly etc. etc. like is available for main sensor data, or would it be a case of starting from scratch with python scripts, or whatever to generate such records?

Regards,

Ian

[mcrossley]

MX doesn't do anything much with extra sensor data, you're pretty much on your own.

I find pushing the data to a MySQL database then querying that the most flexible way of accessing stats that MX does not provide. Much of my web site is driven from my database.

[Gyvate]

Thanks for that Mark.

Is there a relatively simple way to get this daily data analysed by CMX to produce historical summaries ..... max, min, average, weekly etc. etc. like is available for main sensor data, or would it be a case of starting from scratch with python scripts, or whatever to generate such records?

Regards,

Ian

you have several options - even without CMX - beyond using a mySQL database
e.g use HomeAssistant (there is an Ecowitt integration or an MQTT import via FOSHKplugin)
use InfluxDB also via FOSHplugin or via CMX
it all works using the Customized Server postings each Ecowitt console can do - if you need more than one target, because you are using Customized Server option already,, FOSHplugin (see Ecowitt WiKi) is the tool (a smart information broker with target multiplication (up to 100), data conversion and addition etc specially developed for the FineOffset/Ecowitt universe).
see the respective chapters in the Ecowitt WiKi (my signature) for Home Assistant, FOSHKplugin ...

[mcrossley]

Don't forget MX also offers forwarding of the custom server data to additional receivers. That feature is not limited to FOSHplugin.

You can also get data into the likes of HA via MQTT topics, or (what I do), get HA to directly poll MX using the local API.

[Gyvate]

Don't forget MX also offers forwarding of the custom server data to additional receivers. That feature is not limited to FOSHplugin.

You can also get data into the likes of HA via MQTT topics, or (what I do), get HA to directly poll MX using the local API.

I don't want to establish a competition here, but FOSHKplugin is simply a different type of program and in this capacity much more powerful - more of an information broker - in addition it can provide a complete ready-made set of entities via MQTT which otherwise would have to be configured manually in the respective YAML file. As is it specially made for Ecowitt consoles, it also provides a few more options with the extra sensors which in CMX are just stored, providing extra data and values CMX doesn't have - and also beyond the more customized server data. Never mind.

That said, how do you get HA to poll data directly from CMX ?
That might be an interesting option and/or alternative to be documented in my WiKi for Ecowitt CMX and HA users.
Some with the CS forward mentioned by you ...

And where is the custom server forward option ?
I didn't find a simple 1:1 option to forward the CS string as is...
Or do you have to create a template file used for custom 3rd party http(s) forward ?
or create a 3rd party http post with webtags mimiking/reproducing the custom server post ?

[mcrossley]

Sure FOSHplugin is very capable and can do things that MX cannot. But I was just pointing out that for people already running MX there is no need for another piece of software just to get the forwarding or MQTT capabilities to HA (or anywhere else).

For polling for data from MX you use the http interface. There are two options:

Simple HTTP GET

Code: Select all

http//<ip_address>:8998/api/tags/process.json?webtag1&webtag2...

Where webtag1 is the name of the data webtag you want. Eg. <#temp>, just use "temp" in the URL
The data is returned as JSON in the form:

Code: Select all

{
    "webtag1"="value1",
    "webtag2"="value2"
}

You can use a global parameter "rc" as the first URL parameter to force all decimal values to use dot decimals in comma decimal locales.

Code: Select all

http//<ip_address>:8998/api/tags/process.json?rc&webtag1&webtag2...

HTTP POST
When you want more control, use the POST API

Code: Select all

http//<ip_address>:8998/api/tags/process.txt

Send the text as the POST body, and embed webtags in the same way as you would in a file.
The API will return the body text with the tags processed like they would be in a file.
You must use the full webtag format <#tagname [param=val]>.
This allows you to have data formats other than JSON (eg plain CSV), its free format, and full access to all the usual web tag parameters.

HTTP Forwarders
This option appears in station settings for the HTTP Custom Sender (Ecowitt), and when using the HTTP Station (Ecowitt) for extra sensors.

You just specify the forwarding URLs, and the data received from your stations Custom Server option is forwarded as-is to the list of URLs.