Difference between pages "File:Page2.png" and "Push Services"

From meteoplug
(Difference between pages)
Jump to: navigation, search
(Admin uploaded a new version of "File:Page2.png")
 
(Created page with "__NOTOC__ Meteobridge provides some additional "push services", which can distribute weather information to you via email, or to your twitter acoount. When you have email or t...")
 
Line 1: Line 1:
 +
__NOTOC__
 +
Meteobridge provides some additional "push services", which can distribute weather information to you via email, or to your twitter acoount. When you have email or twitter configured, Meteobridge can send alarms to you when a certain weather condition is met.
 +
When you have your ohen web server or MYSQL database server running, Meteobridge can also feed these with weather data.
  
 +
The following sections will explain how to setup push services in detail. These options are a bit more for the tech-savvy user, but they are not mandatory for Meteobridge's core task, to feed weather data to weather networks. So you can keep that all switched off, when you don't need it.
 +
 +
[[File:page6.png]]
 +
 +
 +
===Twitter Upload===
 +
Meteobridge allows you to send weather data snippets to your twitter account. As twitter requires a bit complicated authentication you will have to run through 6 steps.
 +
 +
<gallery perrow=1 widths=500 heigths=350>
 +
File:twitter0.png|1. Press "Request PIN" button.
 +
File:twitter2.png|2. An additional window will pop-up (please make sure your browser's pop-up blocker does not block it!) where twitter asks you to log-in to your twitter account.
 +
File:twitter2b.png|3. Please log-in and copy the pin that twitter does present to you.
 +
File:twitter4.png|4. Switch back to Meteobridge page and Insert pin into input field next to "Activate PIN" button and press this button.
 +
File:twitter3.png|5. Finally, insert message text that Meteobridge should tweet and set upload interval and retry count and press save to make these settings permanent. If Authentification with twitter does fail, you can start process with pressing "Request new PIN" from the start.
 +
File:twitter5.png|6. To fill message text with weather data and/or a timestamp, you can make use of Meteobridge variables as explained in [[Templates]] section. Example above is a result of this message text: <font face="Courier"><span style="background-color:lightgrey;">[hh]:[mm]h Outdoor temp: [th0temp-act=F.1:--]°F </span></font face>
 +
</gallery>
 +
 +
===Individual HTTP Upload===
 +
Data will be sent as HTTP GET requests with URL parmeters you can define to your liking. Parameters of a URL consist of name-value pairs seperated by '&'. You can define names yourself and can use a certain set of variables provided by Meteobridge to be used as values. Variable names will be automatically replaced by their current values, each time a HTTP request is sent. Please have a look at the example below.
 +
 +
 +
[[file:http-upload.png]]
 +
 +
 +
Upload schedule is defined to every 10 seconds. URL specifies server address, where to deliver data ("http://myserver.com/upload.php" in the example above). "Success Condition" allows to specify a matching string which is compared to to the return message from the server to decide if upload was successful or not.
 +
 +
Weather data is transported to the server by means of URL parameters. Meteobridge provides a large set of variables that can be used to feed URL parameters with current sensor data. Section [[Templates]] will explain how to use these variables to fill URL parameters with recent sensor data.
 +
 +
===Individual MYSQL Uploads===
 +
When you prefre to store your weather station's data in your own MYSQL database, Meteobridge can feed sensor data to it in a very easy way. Just state
 +
* '''Host''': server name or IP of server when DNS can' resolv the name
 +
* '''Port''': port number where to reach MYSQL database on your server
 +
* '''Database''': name of database to feed
 +
* '''User''': name of database user to use for data upload
 +
* '''Password''': passwrod for user name.
 +
* '''Query''': payload that should be sent to the database. Query usually contains a MSQL insert statement followed by a table name and a list of column names and values. The query ist subject to template replacement, so you can use Meteobridge variables to upload weather data to your database.
 +
 +
 +
[[File:mysql.png]]
 +
 +
 +
Query <font face="Courier"><span style="background-color:lightgrey;">insert upload (temp, wind) values ([th0temp-act.1:-9999], [wind0wind-act=kmh.1:-9999])</span></font face> in example above stores actual outdoor temperature to field "temp" of table "upload" of database "test". Field "wind" is filled with current non averaged wind speed in km/h. When temperature or wind data is not there a value of -9999 is stored.
 +
 +
Details of using variables in templates is explained in [[Templates]] section.

Revision as of 23:51, 2 February 2013

Meteobridge provides some additional "push services", which can distribute weather information to you via email, or to your twitter acoount. When you have email or twitter configured, Meteobridge can send alarms to you when a certain weather condition is met. When you have your ohen web server or MYSQL database server running, Meteobridge can also feed these with weather data.

The following sections will explain how to setup push services in detail. These options are a bit more for the tech-savvy user, but they are not mandatory for Meteobridge's core task, to feed weather data to weather networks. So you can keep that all switched off, when you don't need it.

Page6.png


Twitter Upload

Meteobridge allows you to send weather data snippets to your twitter account. As twitter requires a bit complicated authentication you will have to run through 6 steps.

Individual HTTP Upload

Data will be sent as HTTP GET requests with URL parmeters you can define to your liking. Parameters of a URL consist of name-value pairs seperated by '&'. You can define names yourself and can use a certain set of variables provided by Meteobridge to be used as values. Variable names will be automatically replaced by their current values, each time a HTTP request is sent. Please have a look at the example below.


Http-upload.png


Upload schedule is defined to every 10 seconds. URL specifies server address, where to deliver data ("http://myserver.com/upload.php" in the example above). "Success Condition" allows to specify a matching string which is compared to to the return message from the server to decide if upload was successful or not.

Weather data is transported to the server by means of URL parameters. Meteobridge provides a large set of variables that can be used to feed URL parameters with current sensor data. Section Templates will explain how to use these variables to fill URL parameters with recent sensor data.

Individual MYSQL Uploads

When you prefre to store your weather station's data in your own MYSQL database, Meteobridge can feed sensor data to it in a very easy way. Just state

  • Host: server name or IP of server when DNS can' resolv the name
  • Port: port number where to reach MYSQL database on your server
  • Database: name of database to feed
  • User: name of database user to use for data upload
  • Password: passwrod for user name.
  • Query: payload that should be sent to the database. Query usually contains a MSQL insert statement followed by a table name and a list of column names and values. The query ist subject to template replacement, so you can use Meteobridge variables to upload weather data to your database.


Mysql.png


Query insert upload (temp, wind) values ([th0temp-act.1:-9999], [wind0wind-act=kmh.1:-9999]) in example above stores actual outdoor temperature to field "temp" of table "upload" of database "test". Field "wind" is filled with current non averaged wind speed in km/h. When temperature or wind data is not there a value of -9999 is stored.

Details of using variables in templates is explained in Templates section.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current01:03, 17 February 2013Thumbnail for version as of 01:03, 17 February 2013687 × 228 (27 KB)Admin (Talk | contribs)
23:40, 2 February 2013Thumbnail for version as of 23:40, 2 February 2013687 × 205 (32 KB)Admin (Talk | contribs)
23:39, 2 February 2013Thumbnail for version as of 23:39, 2 February 2013687 × 205 (30 KB)Admin (Talk | contribs)
00:09, 24 January 2013Thumbnail for version as of 00:09, 24 January 2013688 × 230 (26 KB)Admin (Talk | contribs)
19:23, 17 January 2013Thumbnail for version as of 19:23, 17 January 2013691 × 216 (29 KB)Admin (Talk | contribs)
22:24, 21 December 2012Thumbnail for version as of 22:24, 21 December 2012691 × 216 (25 KB)Admin (Talk | contribs)
19:03, 21 December 2012Thumbnail for version as of 19:03, 21 December 2012690 × 203 (12 KB)Admin (Talk | contribs)
00:01, 17 December 2012Thumbnail for version as of 00:01, 17 December 2012546 × 198 (11 KB)Admin (Talk | contribs)
18:37, 16 December 2012Thumbnail for version as of 18:37, 16 December 2012596 × 222 (12 KB)Admin (Talk | contribs)
  • You cannot overwrite this file.

The following 2 pages link to this file: