jut doesn't work....
.....
when I update the api.php with your examples I do not get sensible values in, I only see in the apisetup.php someting like air2!0pm-lastval:2,air2!1pm-lastval:2, air2!2pm-lastval:2]
.....
air2!0pm-lastval:2 you won't see from my API string - maybe air0!0pm-lastval: (that's the air quality sensor #1 [counting starts with zero !] of the primary station (station #0) or air0!1pm (air sensor#2 of primary) or air0!2pm (air sensor #3 of primary) ... -
you need to understand the syntax !!! of the sensor names and of the sensor-selection expressions: sensor-selector.decimal:replacement quote from the WiKi (reading recommended - e.g. setup --> primary station --> mapping (
https://meteobridge.com/wiki/index.php/Select_Station)
Physical
sensor names are composed of
the sensor category (t, th, thb, wind, rain, uv, sol, air, ...)
station number (0 = primary station)
exclamation mark "!" as delimiter
sensor number (0 = primary sensor of the specific station)
sensor type (temp, hum, dew, ...)
Therefore, "th1!0temp" is the primary temp outdoor sensor of station #1.
take your time - in my country we say - "no master just fell down from the sky" - or, in English: "no one is born a master"
I assume (I haven't seen your system though) that your second airlink is air0!2pm (
selection expression: [air0!2pm-lastval.1:] ), provided it comes from the primary station. In your raw sensor data it may just show as Air#1.
maybe you attach a screencopy of your raw sensor data and your min/max history
and - maybe just start with a very simple export - see attachment (you have to rename the file from .txt to .exp - the forum software doesn't allow attachments with the ending .exp)
use the export instructions from Reply #11 - nothing to edit yet - you've got already a ready-made little export template
the export template:
- # as a first character means that the line is a commentary and is ignored by the MB processor
- what stands behind $# is just a text line creating the headers of the selector values created in the following line (for better reading)
- now comes the export instruction line:
[YYYY]-[MM]-[DD] [hh]:[mm],[air0!0pm],[air0!3pm],[air0!3pm],[air0!3pm]
the first five selectors with the characters in between will create an entry: year-month-day hour:minute (e.g. 2022-05-16 00:00),
the entry [air0!0pm] inside the export file is an instruction for Meteobridge to read from its database the values of the chosen resolution (here minutes [Reply #11] inside the chosen time frame (here current day) and write them into a file named template-name-date.txt (e.g. air-sensors-20220516.txt) and place it into the \\METEOBRIDGE\data\export directory.
If after the first selector a second one comes, separated by a comma, it means to the processor: write that comma and place the value of the 2nd selector behind it etc. until the end of the line
the complete export lines should look like (if you do the export today) - values just ficticious
date-time, Air Quality [ug/m3], Air Quality 2 [ug/m3], Air Quality 3 [ug/m3], Air Quality 4 [ug/m3]
2022-05-16 00:00, 4, 6, 4, 2
2022-05-16 00:01, 4, 6, 4, 3
......
run it - see what it produces (in \\METEOBRIDGE\data\export) and understand what it does
once your export provides the wanted results, transfer the expressions (what's inside the [ ] including the [ ]
) to the API string