|
|
| Line 1: |
Line 1: |
| | __NOTOC__ | | __NOTOC__ |
| − | <languages /><translate> | + | <languages /><translate><!--T:1--> |
| − | <!--T:1--> | + | <br />This page allows to specify the station you have connected via USB to your meteobridge. Selection is very simple, just click on the radio button that matches your station type. |
| − | <br />Meteobridge provides a very flexible mechanism to smuggle sensor data of different kinds into strings to be used by Meteobrdge push services like Twitter, HTTP GET uploads or MSQL database insert requests. | + | |
| − | Simply type in the text you want to upload and represent the pieces of sensor data by so called variables. When data gets uploaded, these variables will be replaced by current sensor data and so a string filled with the data you intended will be uploaded.
| + | |
| | | | |
| | <!--T:2--> | | <!--T:2--> |
| − | Each variable starts with an opening square bracket "[" and is terminated by a closing square bracket "]". The structure of the variable name between these brackets is as follows: <pre>sensor-selector=converter.decimals:replacement</pre>
| + | [[File:page1.png]] |
| − | "converter", "decimals" and "replacement" can be omitted, "sensor" and "type" are mandatory.
| + | |
| − | While "sensor" tells what sensor and what piece of information of the sensor to use, "selector" decides data from what time period should be taken into account and "converter" does convert data into measurement units the user likes most. "Decimals" decides about precision the result should be shown in and "replacement" gives the string to be returned when there is no data for defined sensor available.
| + | |
| | | | |
| − | ==Sensors== <!--T:3--> | + | ==Automatic Station Identification== <!--T:3--> |
| − | These sensors are defined in Meteobridge.
| + | Meteobridge does not provide a complete automatic recognition of the station being connected, but it can do some checks, which might help you selecting the right station. |
| − | * '''th0temp''': outdoor temperature in degrees Celsius | + | * A '''green mark''' indicates that meteobridge's USB port has a device connected that identifies itself as being a weather station of that certain type. In case of Oregon stations WMR-88, WMR-100, and WMR200 meteobridge cannot decide which one is connected, but it can tell you if one of these is connected, so all of these are marked green when that type of station is connected. |
| − | * '''th0hum''': relative outdoor humidity as percentage
| + | * A '''red mark''' indicates that the corresponding station is not connected for sure. Nevertheless, you can select it, which might be usefull when you do the setup without the station connected. |
| − | * '''th0dew''': outdoor dew point in degrees Celsius | + | * '''No mark''' indicates that there is a RS232-USB converter connected, so one of the serial connected weather stations might be there, but meteobridge cannot say for sure if there is a station behind the converter and what type of station might be there. |
| − | * '''thb0temp''': indoor temperature in degrees Celsius
| + | |
| − | * '''thb0hum''': indoor humidity as percentage
| + | |
| − | * '''thb0dew''': indoor dewpoint in degrees Celsius
| + | |
| − | * '''thb0press''': station pressure in hPa
| + | |
| − | * '''thb0seapress''': normalized pressure (computed to sea level) in hPa
| + | |
| − | * '''wind0wind''': wind speed in m/s
| + | |
| − | * '''wind0avgwind''': average windspeed in m/s (time used for average depends on station)
| + | |
| − | * '''wind0dir''': wind direction in degress (0° is North) | + | |
| − | * '''wind0chill''': wind chill temperature in degrees Celsius
| + | |
| − | * '''rain0rate''': rain rate in mm/h
| + | |
| − | * '''rain0total''': rain fall in mm
| + | |
| − | * '''uv0index''': uv index
| + | |
| − | * '''sol0rad''': solar radiation in W/m^2
| + | |
| − | If a sensor is not there or data of sensor has passed the "tolerated data age" interval, Meteobridge will not provide data for it and will present the value defined as "replacement". If no replacement is given, variable will not be converted into data but will stay as is.
| + | |
| | | | |
| − | ==Selectors== <!--T:4--> | + | ====<font color="red">Limitation on USB 1.x Stations</font>==== <!--T:4--> |
| − | Sensors are followed by a selector (syntactically separated by a dash) that specifies what period in time should be used for evaluation. Valid selectors are:
| + | Please be aware that Meteobridge client hardware from TP-Link (TL-MR3020 and TL-WR703N) is not able to run old USB 1.x devices directly, but needs a small cheap, unpowered external USB 2.0 hub in between, which translates USB 1.x from your weather station to USB 2.0. Please check list of supported stations [http://www.meteobridge.com/wiki/index.php/Stations here], to learn in which situation you ned a USB 2.0 hub inbetween. As USB 2.0 hubs are available all around and do just cost a few dollars, this should be a no brainer. |
| − | * '''act''': most recent data
| + | |
| − | * '''hmin''': minimum value of this hour
| + | |
| − | * '''hmax''': maximum value of this hour
| + | |
| − | * '''dmin''': minimum value of today
| + | |
| − | * '''dmax''': maximum value of today
| + | |
| − | * '''ydmin''': minimum value of yesterday
| + | |
| − | * '''ydmax''': maximum value of yesterday
| + | |
| − | * '''mmin''': minimum value of this month
| + | |
| − | * '''mmax''': maximum value of this month
| + | |
| − | * '''ymin''': minimum value of this year
| + | |
| − | * '''ymax''': maximum value of this year
| + | |
| − | * '''amin''': minimum value of all time
| + | |
| − | * '''amax''': maximum value of all time
| + | |
| − | * '''daysum or sumday''', '''monthsum''', '''yearsum''', '''allsum''', '''ydaysum''': selects summerized delta values from today, this month, this year, all time or yesterday: "rain0total-sumday" is todays rain fall.
| + | |
| | | | |
| − | <!--T:13--> | + | ==Station selection== <!--T:5--> |
| − | When you are interested in timestamps of min/max values, you can make use of these selectors:
| + | Meteobridge supports the most popular weather stations in the market. Stations with a serial RS232 interface can be connected by a cheap RS232-USB converter. Converters with PL230x, CP210x and FTDI chipsets are supported by Meteobridge. |
| − | * '''hmintime''': timestamp of minimum value of this hour
| + | |
| − | * '''hmaxtime''': timestamp of maximum value of this hour
| + | |
| − | * '''dmintime''': timestamp of minimum value of today
| + | |
| − | * '''dmaxtime''': timestamp of maximum value of today
| + | |
| − | * '''ydmintime''': timestamp of minimum value of yesterday
| + | |
| − | * '''ydmaxtime''': timestamp of maximum value of yesterday
| + | |
| − | * '''mmintime''': timestamp of minimum value of this month
| + | |
| − | * '''mmaxtime''': timestamp of maximum value of this month
| + | |
| − | * '''ymintime''': timestamp of minimum value of this year
| + | |
| − | * '''ymaxtime''': timestamp of maximum value of this year
| + | |
| − | * '''amintime''': timestamp of minimum value of all time
| + | |
| − | * '''amaxtime''': timestamp of maximum value of all time
| + | |
| − | * '''starttime''': timestamp of first recorded value
| + | |
| − | Timestamps are strings of format "YYYYMMDDhhmmss". Year "YYYY" is reported in 4 digits, all other values (month "MM", day "DD", hour "hh", minute "mm", second "ss") come with 2 digits, leading zeros are not supressed.
| + | |
| | | | |
| − | <!--T:5--> | + | <!--T:6--> |
| − | Apart from selectors that use absolute, predefined time slots there are also selectors that look for a certain amount of time into the past.
| + | Davis Vantage Pro and Vue stations can be equipped with an IP-based Logger called WLIP. If you have one of these, you can enter IP and port (separated by a colon) in the "WLIP" input field (example: "192.168.1.222:10001"). This will tell Meteobridge to connect this station not via USB but via your LAN/WLAN (in the example on IP 192.168.1.222 at port 10001). |
| − | * '''val2''', '''val5''', '''val10''', '''val15''', '''val30''', '''val60''': selects the value the sensor has shown 2, 5, 10, 15, 30 or 60 minutes ago
| + | |
| − | * '''max2''', '''max5''', '''max10''', '''max15''', '''max30''', '''max60''': selects the maximum value from the last 2, 5, 10, 15, 30 or 60 minutes
| + | |
| − | * '''min2''', '''min5''', '''min10''', '''min15''', '''min30''', '''min60''': selects the minimum value from the last 2, 5, 10, 15, 30 or 60 minutes
| + | |
| − | * '''avg2''', '''avg5''', '''avg10''', '''avg15''', '''avg30''', '''avg60''': selects average value from the last 2, 5, 10, 15, 30 or 60 minutes
| + | |
| − | * '''sum2''', '''sum5''', '''sum10''', '''sum15''', '''sum30''', '''sum60''': selects summerized delta values from the last 2, 5, 10, 15, 30 or 60 minutes, which is useful to get amount of total rain in a certain time frame: "rain0total-sum60" is rainfall im mm of last 60 minutes.
| + | |
| | | | |
| − | ==Converters== <!--T:6--> | + | ==Station Altitude== <!--T:7--> |
| − | Sensor data is reported in ISO units (°C, hPa, mm, m/s) by default, but can be converted into non-ISO units (imperial) by adding a conversion token. Defined tokens are:
| + | It is important that you specify the station altitude. Meteobridge uses altitude information to compute sealevel pressure used by weather networks. You can specify altitude in meters or feet, please set down-down box for selection of "meters" or "feet" accordingly. |
| − | * '''F''' converts temperature from Celsius to Fahrenheit.
| + | |
| − | * '''psi''' converts pressure from hPa (equivalent to mbar) to psi.
| + | |
| − | * '''mmHg''' converts pressure from hPa to millimeters of mercury.
| + | |
| − | * '''inHg''' converts pressure from hPa to inches of mercury.
| + | |
| − | * '''kmh''' converts wind speed from meters per second to kilometers per hour.
| + | |
| − | * '''mph''' converts wind speed from meters per second to miles per hour.
| + | |
| − | * '''kn''' converts wind speed from meters per second to knots.
| + | |
| − | * '''bft''' converts wind speed from meters per second to Beaufort scale.
| + | |
| − | * '''in''' converts millimeters to inches.
| + | |
| − | * '''ft''' converts meters to feet.
| + | |
| − | If an unknown conversion string is used, no conversion will take place, no error message will appear.
| + | |
| | | | |
| − | <!--T:14--> | + | ==Tolerated Data Age== <!--T:8--> |
| − | When variable returns a timestamp, then this converter can be applied:
| + | Meteobridge needs to know how long a sensor value should be regarded valid. Standard is 10 minutes, it is not recommended to go below that value. If your weather station does have RF problems with certain sensors that only change slowly over time it might be a good move, to increase the value. When you don't know, stay with the default of 10 minutes. |
| − | * '''utc''' reports timestamp in UTC instead of localtime, which is default.
| + | |
| | | | |
| − | ==System Variables== <!--T:16--> | + | ==Confirm Changes== <!--T:9--> |
| − | Meteobridge provides some additional variables that tell details not directly related to weather conditions. Sensor name is "mbsystem", defined selectors are:
| + | When you press "Save" weather station selection is made permanent and data logger is restarted to adapt to the new settings. |
| − | * '''swversion''': Meteobridge version string (example: "1.1")
| + | |
| − | * '''buildnum''': build number as integer (example: 1673)
| + | |
| − | * '''platform''': string that specifies hw platform (example: "TL-MR3020")
| + | |
| − | * '''language''': language used on Meteobridge's web interface (example: "English")
| + | |
| − | * '''timezone''': defined timezone (example: "Europe/Berlin")
| + | |
| − | * '''latitude''': latitude as float (example: 53.875120)
| + | |
| − | * '''longitude''': longitude as float (example: 9.885357)
| + | |
| − | * '''lunarage''': days passes since new moon as integer (example: 28)
| + | |
| − | * '''lunarpercent''': lunarphase given as percentage from 0% (new moon) to 100% (full moon)
| + | |
| − | * '''lunarsegment''': lunarphase segment as integer (0 = new moon, 1-3 = growing moon: quarter, half, three quarters, 4 = full moon, 5-7 = shrinking moon: three quarter, half, quarter)
| + | |
| − | * '''daylength''': length of day (example: "11:28")
| + | |
| − | * '''civildaylength''': alternative method for daylength computation (example: "12:38")
| + | |
| − | * '''nauticaldaylength''': alternative method for daylength computation (example: "14:00")
| + | |
| − | * '''sunrise''': time of sunrise in local time. Can be converterd to UTC by applying "=utc" to the variable (example: "06:47", resp. "05:47")
| + | |
| − | * '''sunset'''. time of sunset in local time. Can be converterd to UTC by applying "=utc" to the variable (example: "18:15", resp. "17:15")
| + | |
| − | * '''civilsunrise''', '''civilsunset''', '''nauticalsunrise''', '''nauticalsunset''': alternative computations for sunset and sunrise.
| + | |
| − | * '''daynightflag''': returns "D" when there is daylight, otherwise "N".
| + | |
| − | * '''moonrise''': time of moonrise in local time. Can be converterd to UTC by applying "=utc" to the variable. Please notice that not every day has a moonrise time, therefore, variable can be non-existent on certain days (example: "05:46", resp. "04:46")
| + | |
| − | * '''moonset''': time of moonset in local time. Can be converterd to UTC by applying "=utc" to the variable. Please notice that not every day has a moonset time, therefore, variable can be non-existent on certain days (example: "17:00", resp. "16:00")
| + | |
| − | | + | |
| − | ==Time/Date Variables== <!--T:7-->
| + | |
| − | Variables representing current date/time don't come as "sensor-selector=converter" chains but have a distinct meaning by themselves.
| + | |
| − | | + | |
| − | <!--T:8-->
| + | |
| − | Date und time variables are defined as follows:
| + | |
| − | * '''YYYY''': year as four digit number
| + | |
| − | * '''YY''': year as two digit number
| + | |
| − | * '''MM''': month as two digit number, if only one digit neede a zero will be used as first digit
| + | |
| − | * '''M''': month as one or two digit number, no leading zeros
| + | |
| − | * '''DD''': day of month as two digit number, if only one digit neede a zero will be used as first digit
| + | |
| − | * '''D''': day of month as one or two digit number, no leading zeros
| + | |
| − | * '''hh''': hour as two digit number, if only one digit neede a zero will be used as first digit
| + | |
| − | * '''h''': hour as one or two digit number, no leading zeros
| + | |
| − | * '''mm''': minute as two digit number, if only one digit neede a zero will be used as first digit
| + | |
| − | * '''m''': minute as one or two digit number, no leading zeros
| + | |
| − | * '''ss''': seconds as two digit number, if only one digit neede a zero will be used as first digit
| + | |
| − | * '''s''': seconds as one or two digit number, no leading zeros
| + | |
| − | When a capital "U" preceeds a date/time variable name, UTC is used instead of local time ("[Uhh]:[Umm]:[Uss] UTC" is evaluated to a string like "16:03:33 UTC") | + | |
| − | | + | |
| − | ==Decimals== <!--T:9-->
| + | |
| − | Unless otherwise defined numbers are reported with one decimal. By specifying a value for "decimals" you can determine resolution of presented values.
| + | |
| − | | + | |
| − | <!--T:15-->
| + | |
| − | When variable returns a string instead of a number (in case of a timestamp for example), "decimal" specification does have a different format and meaning, which allows to select a substring. Specification of the substring consists of two lower-case letters. The first one specifies start point of the substring, second leter the position of last character of the string to be reported. For example, when string is timestamp "20130303121055" a specification of ".ad" selects a substring from first character (position code "a") until fourth character (position code "d"). When you want to grab the time for lowest outdoor temperature of today the template for that will be <font face="Courier"><span style="background-color:lightgrey;">[th0temp-dmintime.ij:--]:[th0temp-dmintime.kl:--]</span></font face>. "ij" selects the hour part at position 9-10 and "kl" selects minute part at position 11-12 of the timestamp.
| + | |
| − | | + | |
| − | ==Replacement== <!--T:10-->
| + | |
| − | When a variable is not defined or there is no data for a specified sensor, information specified as "replacement" string will be represented instead.
| + | |
| − | | + | |
| − | ==Examples== <!--T:11-->
| + | |
| − | Having a look at examples usually helps to understand how easy that is.
| + | |
| − | | + | |
| − | <!--T:12-->
| + | |
| − | # Template <font face="Courier"><span style="background-color:lightgrey;">Outdoor temperature is [th0temp-act=F.1:--]°F</span></font face> will be converted into <font face="Courier"><span style="background-color:lightgrey;">Outdoor temperature is 3.4°F</span></font face> when there is outdoor temp data and into <font face="Courier"><span style="background-color:lightgrey;">Outdoor temperature is --°F</span></font face> if outdoor temp sensor does not provide recent data.
| + | |
| − | # Template <font face="Courier"><span style="background-color:lightgrey;">Local time is [hh]:[mm]</span></font face> will be converted into <font face="Courier"><span style="background-color:lightgrey;">Local time is 09:27</span></font face>.
| + | |
| − | # Template <font face="Courier"><span style="background-color:lightgrey;">Max gust in last 10 minutes was: [wind0wind-max10.1:--]m/s, [wind0wind-max10=mph.1:--]mph, [wind0wind-max10=kn.0:--]kn</span></font face> will be converted into <font face="Courier"><span style="background-color:lightgrey;">Max gust in last 10 minutes was: 10.5m/s, 23.5mph, 20kn</span></font face>.
| + | |
| | </translate> | | </translate> |
This page allows to specify the station you have connected via USB to your meteobridge. Selection is very simple, just click on the radio button that matches your station type.
Meteobridge does not provide a complete automatic recognition of the station being connected, but it can do some checks, which might help you selecting the right station.
Please be aware that Meteobridge client hardware from TP-Link (TL-MR3020 and TL-WR703N) is not able to run old USB 1.x devices directly, but needs a small cheap, unpowered external USB 2.0 hub in between, which translates USB 1.x from your weather station to USB 2.0. Please check list of supported stations here, to learn in which situation you ned a USB 2.0 hub inbetween. As USB 2.0 hubs are available all around and do just cost a few dollars, this should be a no brainer.
Meteobridge supports the most popular weather stations in the market. Stations with a serial RS232 interface can be connected by a cheap RS232-USB converter. Converters with PL230x, CP210x and FTDI chipsets are supported by Meteobridge.
Davis Vantage Pro and Vue stations can be equipped with an IP-based Logger called WLIP. If you have one of these, you can enter IP and port (separated by a colon) in the "WLIP" input field (example: "192.168.1.222:10001"). This will tell Meteobridge to connect this station not via USB but via your LAN/WLAN (in the example on IP 192.168.1.222 at port 10001).
It is important that you specify the station altitude. Meteobridge uses altitude information to compute sealevel pressure used by weather networks. You can specify altitude in meters or feet, please set down-down box for selection of "meters" or "feet" accordingly.
Meteobridge needs to know how long a sensor value should be regarded valid. Standard is 10 minutes, it is not recommended to go below that value. If your weather station does have RF problems with certain sensors that only change slowly over time it might be a good move, to increase the value. When you don't know, stay with the default of 10 minutes.
When you press "Save" weather station selection is made permanent and data logger is restarted to adapt to the new settings.
