meteohub.de

Making progress, but not yet free from error reports = too early to cry victory.
Datafile is
2.5,0.0,225.0,8.7,74.0,9.36,0.0,0.0,1015.0,0.2,0.3,19.8,42.0,8.3,79.0

See all these values nicely popping up under Live Data, with all fields also reported under Mapping.
However under Logging this ...

Now running the plugin a few days.
All seems well, besides today (= Feb11) following report in the Logging
logger (11.02.2024 20:40:40): station 3 (User-defined), unknown sensor type in plugin data "0.0,0.0,34.0,8.5,94.0,18.4,0.0,0.5,993.0,0.0,0.0,19.7,55.0,8.3,95.0"
logger (11.02.2024 20:40:40 ...

This weblink explains the actual formats expected by WOW_UK/MetOffice for various data-inputs through their API, with subsequent transfer of data to WOW_NL/KNMI, etc.

Because the nomenclature is not one-to-one, it triggers a question about Mapping in Meteobridge :
how can in Meteobridge's Mapping ...

Having Domoticz generate a datafile meeting the format of the CampbellSci-plugin is not a major effort.
Reading that datafile using the reading structure applied in the Luftdaten-plugin proved handier than application of nc.
In the sh-script below you see a mixture of both plugins mentioned above ...

In parallel trying to clone&tune the CampbellSci-plugin for transfer of a complete PWS-dataset.
Question popping up:
if the PWS-dataset is not complete, what is the correct code in the string to signal to Meteobridge the absence of a component?
Just leave the 'bin' empty which is designated to the ...

In Domoticz the simplest readout is making call to the desired Virtual Device.
For a T&H-sensor that results in a JSON-file like attached in zip-file Domoticz_RIDreadout.zip.
A related plugin for Meteobridge might rip out the data for T&H for that specific device:
is straightforward solution for 1 ...

@Mattk

Completely agreed that a home automation system is 'not the best PWS',
However, in my view Domoticz for Meteobridge potentially is a useful gateway/portal .
Because at least that home automation system for me has the technical & functional interfaces to read that 'misfit' PWS and a bunch of ...

Got a hint pointing to an example for direct external calling for a JSON-output, and 'translated/customized' that info into a template.
Not the whole bunch of data as available in Meteobridge, but still a grand selection.
The resulting experimental template-file in the attached ZIP-file has layout ...

Plenty of types of weatherstations have uploadfunctions readily integrated in Meteobridge.
Obviously still quite a few outside that catalogue.
Having such ‘misfit’ setup, but lucky to be able to read the subject weatherstation (and a series of DIY-sensors) with Domoticz.
Looking for a possibility to ...

At request Meteobridge can output an XML-file, as described under Add-On Services , or equivalent output of a TXT-file.
For data-extraction have a preference for JSON-format, because the JSON-tagging allows easy finding of 'borders' of the value-fields:
especially useful if the value-fields are of ...

GW1000-problem seems solved.
As result of reset GW1000 apparently shifted it's IP-address.
Had missed that shift: now (re)aligned.

Also found that via tab System > Administration you have access to a 'normal' Restart-button (at righthand-side bottom of webpage)

Learning curve .....

To renew & concentrate upload of my sensor data recently purchased a Meteobridge/Standard.
Main objective to get an alternative uploader for data from my TFA_Nexus.
Connection of TFA_Nexus, Tempest and GW1000 seemed easy enough,
but the Meteobridge is frequently loosing the sensor-mapping ...