Meteoplug Wiki - User contributions [en]

Meteoplug Wiki:Privacy policy

2024-12-04T18:10:31Z

Admin: Created page with "__NOTOC__ <h4>Privacy Policy</h4> <p>We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the smartbedded GmbH. The use of the Internet pages of the smartbedded GmbH is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of persona..."

__NOTOC__
<h4>Privacy Policy</h4>

<p>We are very delighted that you have shown interest in our enterprise. Data protection is of a particularly high priority for the management of the smartbedded GmbH. The use of the Internet pages of the smartbedded GmbH is possible without any indication of personal data; however, if a data subject wants to use special enterprise services via our website, processing of personal data could become necessary. If the processing of personal data is necessary and there is no statutory basis for such processing, we generally obtain consent from the data subject.</p>

<p>The processing of personal data, such as the name, address, e-mail address, or telephone number of a data subject shall always be in line with the General Data Protection Regulation (GDPR), and in accordance with the country-specific data protection regulations applicable to the smartbedded GmbH. By means of this data protection declaration, our enterprise would like to inform the general public of the nature, scope, and purpose of the personal data we collect, use and process. Furthermore, data subjects are informed, by means of this data protection declaration, of the rights to which they are entitled.</p>

<p>As the controller, the smartbedded GmbH has implemented numerous technical and organizational measures to ensure the most complete protection of personal data processed through this website. However, Internet-based data transmissions may in principle have security gaps, so absolute protection may not be guaranteed. For this reason, every data subject is free to transfer personal data to us via alternative means, e.g. by telephone. </p>

<h4>1. Definitions</h4>
<p>The data protection declaration of the smartbedded GmbH is based on the terms used by the European legislator for the adoption of the General Data Protection Regulation (GDPR). Our data protection declaration should be legible and understandable for the general public, as well as our customers and business partners. To ensure this, we would like to first explain the terminology used.</p>

<p>In this data protection declaration, we use, inter alia, the following terms:</p>

<ul style="list-style: none">
<li><h4>a) Personal data</h4>
<p>Personal data means any information relating to an identified or identifiable natural person (“data subject”). An identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person.</p>
</li>
<li><h4>b) Data subject</h4>
<p>Data subject is any identified or identifiable natural person, whose personal data is processed by the controller responsible for the processing.</p>
</li>
<li><h4>c) Processing</h4>
<p>Processing is any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction. </p>
</li>
<li><h4>d) Restriction of processing</h4>
<p>Restriction of processing is the marking of stored personal data with the aim of limiting their processing in the future. </p>
</li>
<li><h4>e) Profiling</h4>
<p>Profiling means any form of automated processing of personal data consisting of the use of personal data to evaluate certain personal aspects relating to a natural person, in particular to analyse or predict aspects concerning that natural person's performance at work, economic situation, health, personal preferences, interests, reliability, behaviour, location or movements. </p>
</li>
<li><h4>f) Pseudonymisation</h4>
<p>Pseudonymisation is the processing of personal data in such a manner that the personal data can no longer be attributed to a specific data subject without the use of additional information, provided that such additional information is kept separately and is subject to technical and organisational measures to ensure that the personal data are not attributed to an identified or identifiable natural person. </p>
</li>
<li><h4>g) Controller or controller responsible for the processing</h4>
<p>Controller or controller responsible for the processing is the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law. </p>
</li>
<li><h4>h) Processor</h4>
<p>Processor is a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller. </p>
</li>
<li><h4>i) Recipient</h4>
<p>Recipient is a natural or legal person, public authority, agency or another body, to which the personal data are disclosed, whether a third party or not. However, public authorities which may receive personal data in the framework of a particular inquiry in accordance with Union or Member State law shall not be regarded as recipients; the processing of those data by those public authorities shall be in compliance with the applicable data protection rules according to the purposes of the processing. </p>
</li>
<li><h4>j) Third party</h4>
<p>Third party is a natural or legal person, public authority, agency or body other than the data subject, controller, processor and persons who, under the direct authority of the controller or processor, are authorised to process personal data.</p>
</li>
<li><h4>k) Consent</h4>
<p>Consent of the data subject is any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her. </p>
</li>
</ul>

<h4>2. Name and Address of the controller</h4>
<p>Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:

</p>

<p>smartbedded GMBH</p>
<p>Querweg 35</p>
<p>24632 Lentföhrden</p>
<p>Deutschland</p>
<p>Phone: 04192-8192250</p>
<p>Email: info@smartbedded.com</p>
<p>Website: www.smartbedded.com</p>

<h4>3. Name and Address of the Data Protection Officer</h4>
<p>The Data Protection Officer of the controller is:</p>

Inhaber Boris Pasternak
<p>smartbedded GmbH</p>
<p>Querweg 35</p>
<p>24632 Lentföhrden</p>
<p>Deutschland</p>
<p>Phone: 04192-8192250</p>
<p>Email: info@smartbedded.com</p>
<p>Website: www.smartbedded.com</p>

<p>Any data subject may, at any time, contact our Data Protection Officer directly with all questions and suggestions concerning data protection.</p>

<h4>4. Cookies</h4>
<p>The Internet pages of the smartbedded GmbH use cookies. Cookies are text files that are stored in a computer system via an Internet browser.</p>

<p>Many Internet sites and servers use cookies. Many cookies contain a so-called cookie ID. A cookie ID is a unique identifier of the cookie. It consists of a character string through which Internet pages and servers can be assigned to the specific Internet browser in which the cookie was stored. This allows visited Internet sites and servers to differentiate the individual browser of the data subject from other Internet browsers that contain other cookies. A specific Internet browser can be recognized and identified using the unique cookie ID.</p>

<p>Through the use of cookies, the smartbedded GmbH can provide the users of this website with more user-friendly services that would not be possible without the cookie setting.</p>

<p>By means of a cookie, the information and offers on our website can be optimized with the user in mind. Cookies allow us, as previously mentioned, to recognize our website users. The purpose of this recognition is to make it easier for users to utilize our website. The website user that uses cookies, e.g. does not have to enter access data each time the website is accessed, because this is taken over by the website, and the cookie is thus stored on the user's computer system. Another example is the cookie of a shopping cart in an online shop. The online store remembers the articles that a customer has placed in the virtual shopping cart via a cookie.</p>

<p>The data subject may, at any time, prevent the setting of cookies through our website by means of a corresponding setting of the Internet browser used, and may thus permanently deny the setting of cookies. Furthermore, already set cookies may be deleted at any time via an Internet browser or other software programs. This is possible in all popular Internet browsers. If the data subject deactivates the setting of cookies in the Internet browser used, not all functions of our website may be entirely usable.</p>

<h4>5. Collection of general data and information</h4>
<p>The website of the smartbedded GmbH collects a series of general data and information when a data subject or automated system calls up the website. This general data and information are stored in the server log files. Collected may be (1) the browser types and versions used, (2) the operating system used by the accessing system, (3) the website from which an accessing system reaches our website (so-called referrers), (4) the sub-websites, (5) the date and time of access to the Internet site, (6) an Internet protocol address (IP address), (7) the Internet service provider of the accessing system, and (8) any other similar data and information that may be used in the event of attacks on our information technology systems.</p>

<p>When using these general data and information, the smartbedded GmbH does not draw any conclusions about the data subject. Rather, this information is needed to (1) deliver the content of our website correctly, (2) optimize the content of our website as well as its advertisement, (3) ensure the long-term viability of our information technology systems and website technology, and (4) provide law enforcement authorities with the information necessary for criminal prosecution in case of a cyber-attack. Therefore, the smartbedded GmbH analyzes anonymously collected data and information statistically, with the aim of increasing the data protection and data security of our enterprise, and to ensure an optimal level of protection for the personal data we process. The anonymous data of the server log files are stored separately from all personal data provided by a data subject.</p>

<h4>6. Registration on our website</h4>
<p>The data subject has the possibility to register on the website of the controller with the indication of personal data. Which personal data are transmitted to the controller is determined by the respective input mask used for the registration. The personal data entered by the data subject are collected and stored exclusively for internal use by the controller, and for his own purposes. The controller may request transfer to one or more processors (e.g. a parcel service) that also uses personal data for an internal purpose which is attributable to the controller.</p>

<p>By registering on the website of the controller, the IP address—assigned by the Internet service provider (ISP) and used by the data subject—date, and time of the registration are also stored. The storage of this data takes place against the background that this is the only way to prevent the misuse of our services, and, if necessary, to make it possible to investigate committed offenses. Insofar, the storage of this data is necessary to secure the controller. This data is not passed on to third parties unless there is a statutory obligation to pass on the data, or if the transfer serves the aim of criminal prosecution.

</p>

<p>The registration of the data subject, with the voluntary indication of personal data, is intended to enable the controller to offer the data subject contents or services that may only be offered to registered users due to the nature of the matter in question. Registered persons are free to change the personal data specified during the registration at any time, or to have them completely deleted from the data stock of the controller.</p>

<p>The data controller shall, at any time, provide information upon request to each data subject as to what personal data are stored about the data subject. In addition, the data controller shall correct or erase personal data at the request or indication of the data subject, insofar as there are no statutory storage obligations. A Data Protection Officer particularly designated in this data protection declaration, as well as the entirety of the controller’s employees are available to the data subject in this respect as contact persons.</p>

<h4>7. Routine erasure and blocking of personal data</h4>
<p>The data controller shall process and store the personal data of the data subject only for the period necessary to achieve the purpose of storage, or as far as this is granted by the European legislator or other legislators in laws or regulations to which the controller is subject to.</p>

<p>If the storage purpose is not applicable, or if a storage period prescribed by the European legislator or another competent legislator expires, the personal data are routinely blocked or erased in accordance with legal requirements.</p>

<h4>8. Rights of the data subject</h4>
<ul style="list-style: none;">
<li><h4>a) Right of confirmation</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the confirmation as to whether or not personal data concerning him or her are being processed. If a data subject wishes to avail himself of this right of confirmation, he or she may, at any time, contact our Data Protection Officer or another employee of the controller.</p>
</li>
<li><h4>b) Right of access</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller free information about his or her personal data stored at any time and a copy of this information. Furthermore, the European directives and regulations grant the data subject access to the following information:</p>

<ul style="list-style: none;">
<li>the purposes of the processing;</li>
<li>the categories of personal data concerned;</li>
<li>the recipients or categories of recipients to whom the personal data have been or will be disclosed, in particular recipients in third countries or international organisations;</li>
<li>where possible, the envisaged period for which the personal data will be stored, or, if not possible, the criteria used to determine that period;</li>
<li>the existence of the right to request from the controller rectification or erasure of personal data, or restriction of processing of personal data concerning the data subject, or to object to such processing;</li>
<li>the existence of the right to lodge a complaint with a supervisory authority;</li>
<li>where the personal data are not collected from the data subject, any available information as to their source;</li>
<li>the existence of automated decision-making, including profiling, referred to in Article 22(1) and (4) of the GDPR and, at least in those cases, meaningful information about the logic involved, as well as the significance and envisaged consequences of such processing for the data subject.</li>

</ul>
<p>Furthermore, the data subject shall have a right to obtain information as to whether personal data are transferred to a third country or to an international organisation. Where this is the case, the data subject shall have the right to be informed of the appropriate safeguards relating to the transfer.</p>

<p>If a data subject wishes to avail himself of this right of access, he or she may at any time contact our Data Protection Officer or another employee of the controller.</p>
</li>
<li><h4>c) Right to rectification </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller without undue delay the rectification of inaccurate personal data concerning him or her. Taking into account the purposes of the processing, the data subject shall have the right to have incomplete personal data completed, including by means of providing a supplementary statement.</p>

<p>If a data subject wishes to exercise this right to rectification, he or she may, at any time, contact our Data Protection Officer or another employee of the controller.</p></li>
<li>
<h4>d) Right to erasure (Right to be forgotten) </h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller the erasure of personal data concerning him or her without undue delay, and the controller shall have the obligation to erase personal data without undue delay where one of the following grounds applies, as long as the processing is not necessary: </p>

<ul style="list-style: none;">
<li>The personal data are no longer necessary in relation to the purposes for which they were collected or otherwise processed.</li>
<li>The data subject withdraws consent to which the processing is based according to point (a) of Article 6(1) of the GDPR, or point (a) of Article 9(2) of the GDPR, and where there is no other legal ground for the processing.</li>
<li>The data subject objects to the processing pursuant to Article 21(1) of the GDPR and there are no overriding legitimate grounds for the processing, or the data subject objects to the processing pursuant to Article 21(2) of the GDPR. </li>
<li>The personal data have been unlawfully processed.</li>
<li>The personal data must be erased for compliance with a legal obligation in Union or Member State law to which the controller is subject.</li>
<li>The personal data have been collected in relation to the offer of information society services referred to in Article 8(1) of the GDPR.</li>

</ul>
<p>If one of the aforementioned reasons applies, and a data subject wishes to request the erasure of personal data stored by the smartbedded GmbH, he or she may at any time contact our Data Protection Officer or another employee of the controller. The Data Protection Officer of the smartbedded GmbH or another employee shall promptly ensure that the erasure request is complied with immediately.</p>

<p>Where the controller has made personal data public and is obliged pursuant to Article 17(1) to erase the personal data, the controller, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform other controllers processing the personal data that the data subject has requested erasure by such controllers of any links to, or copy or replication of, those personal data, as far as processing is not required. The Data Protection Officer of the smartbedded GmbH or another employee will arrange the necessary measures in individual cases.</p>
</li>
<li><h4>e) Right of restriction of processing</h4>
<p>Each data subject shall have the right granted by the European legislator to obtain from the controller restriction of processing where one of the following applies:</p>

<ul style="list-style: none;">
<li>The accuracy of the personal data is contested by the data subject, for a period enabling the controller to verify the accuracy of the personal data. </li>
<li>The processing is unlawful and the data subject opposes the erasure of the personal data and requests instead the restriction of their use instead.</li>
<li>The controller no longer needs the personal data for the purposes of the processing, but they are required by the data subject for the establishment, exercise or defence of legal claims.</li>
<li>The data subject has objected to processing pursuant to Article 21(1) of the GDPR pending the verification whether the legitimate grounds of the controller override those of the data subject.</li>

</ul>
<p>If one of the aforementioned conditions is met, and a data subject wishes to request the restriction of the processing of personal data stored by the smartbedded GmbH, he or she may at any time contact our Data Protection Officer or another employee of the controller. The Data Protection Officer of the smartbedded GmbH or another employee will arrange the restriction of the processing. </p>
</li>
<li><h4>f) Right to data portability</h4>
<p>Each data subject shall have the right granted by the European legislator, to receive the personal data concerning him or her, which was provided to a controller, in a structured, commonly used and machine-readable format. He or she shall have the right to transmit those data to another controller without hindrance from the controller to which the personal data have been provided, as long as the processing is based on consent pursuant to point (a) of Article 6(1) of the GDPR or point (a) of Article 9(2) of the GDPR, or on a contract pursuant to point (b) of Article 6(1) of the GDPR, and the processing is carried out by automated means, as long as the processing is not necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the controller.</p>

<p>Furthermore, in exercising his or her right to data portability pursuant to Article 20(1) of the GDPR, the data subject shall have the right to have personal data transmitted directly from one controller to another, where technically feasible and when doing so does not adversely affect the rights and freedoms of others.</p>

<p>In order to assert the right to data portability, the data subject may at any time contact the Data Protection Officer designated by the smartbedded GmbH or another employee.</p>

</li>
<li>
<h4>g) Right to object</h4>
<p>Each data subject shall have the right granted by the European legislator to object, on grounds relating to his or her particular situation, at any time, to processing of personal data concerning him or her, which is based on point (e) or (f) of Article 6(1) of the GDPR. This also applies to profiling based on these provisions.</p>

<p>The smartbedded GmbH shall no longer process the personal data in the event of the objection, unless we can demonstrate compelling legitimate grounds for the processing which override the interests, rights and freedoms of the data subject, or for the establishment, exercise or defence of legal claims.</p>

<p>If the smartbedded GmbH processes personal data for direct marketing purposes, the data subject shall have the right to object at any time to processing of personal data concerning him or her for such marketing. This applies to profiling to the extent that it is related to such direct marketing. If the data subject objects to the smartbedded GmbH to the processing for direct marketing purposes, the smartbedded GmbH will no longer process the personal data for these purposes.</p>

<p>In addition, the data subject has the right, on grounds relating to his or her particular situation, to object to processing of personal data concerning him or her by the smartbedded GmbH for scientific or historical research purposes, or for statistical purposes pursuant to Article 89(1) of the GDPR, unless the processing is necessary for the performance of a task carried out for reasons of public interest.</p>

<p>In order to exercise the right to object, the data subject may directly contact the Data Protection Officer of the smartbedded GmbH or another employee. In addition, the data subject is free in the context of the use of information society services, and notwithstanding Directive 2002/58/EC, to use his or her right to object by automated means using technical specifications.</p>
</li>
<li><h4>h) Automated individual decision-making, including profiling</h4>
<p>Each data subject shall have the right granted by the European legislator not to be subject to a decision based solely on automated processing, including profiling, which produces legal effects concerning him or her, or similarly significantly affects him or her, as long as the decision (1) is not is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) is not authorised by Union or Member State law to which the controller is subject and which also lays down suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, or (3) is not based on the data subject's explicit consent.</p>

<p>If the decision (1) is necessary for entering into, or the performance of, a contract between the data subject and a data controller, or (2) it is based on the data subject's explicit consent, the smartbedded GmbH shall implement suitable measures to safeguard the data subject's rights and freedoms and legitimate interests, at least the right to obtain human intervention on the part of the controller, to express his or her point of view and contest the decision.</p>

<p>If the data subject wishes to exercise the rights concerning automated individual decision-making, he or she may at any time directly contact our Data Protection Officer of the smartbedded GmbH or another employee of the controller.</p>

</li>
<li><h4>i) Right to withdraw data protection consent </h4>
<p>Each data subject shall have the right granted by the European legislator to withdraw his or her consent to processing of his or her personal data at any time. </p>

<p>f the data subject wishes to exercise the right to withdraw the consent, he or she may at any time directly contact our Data Protection Officer of the smartbedded GmbH or another employee of the controller.</p>

</li>
</ul>
<h4>9. Data protection provisions about the application and use of YouTube</h4>
<p>On this website, the controller has integrated components of YouTube. YouTube is an Internet video portal that enables video publishers to set video clips and other users free of charge, which also provides free viewing, review and commenting on them. YouTube allows you to publish all kinds of videos, so you can access both full movies and TV broadcasts, as well as music videos, trailers, and videos made by users via the Internet portal.
</p>

<p>The operating company of YouTube is YouTube, LLC, 901 Cherry Ave., San Bruno, CA 94066, UNITED STATES. The YouTube, LLC is a subsidiary of Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, UNITED STATES.</p>

<p>With each call-up to one of the individual pages of this Internet site, which is operated by the controller and on which a YouTube component (YouTube video) was integrated, the Internet browser on the information technology system of the data subject is automatically prompted to download a display of the corresponding YouTube component. Further information about YouTube may be obtained under https://www.youtube.com/yt/about/en/. During the course of this technical procedure, YouTube and Google gain knowledge of what specific sub-page of our website was visited by the data subject.</p>

<p>If the data subject is logged in on YouTube, YouTube recognizes with each call-up to a sub-page that contains a YouTube video, which specific sub-page of our Internet site was visited by the data subject. This information is collected by YouTube and Google and assigned to the respective YouTube account of the data subject.</p>

<p>YouTube and Google will receive information through the YouTube component that the data subject has visited our website, if the data subject at the time of the call to our website is logged in on YouTube; this occurs regardless of whether the person clicks on a YouTube video or not. If such a transmission of this information to YouTube and Google is not desirable for the data subject, the delivery may be prevented if the data subject logs off from their own YouTube account before a call-up to our website is made.</p>

<p>YouTube's data protection provisions, available at https://www.google.com/intl/en/policies/privacy/, provide information about the collection, processing and use of personal data by YouTube and Google.</p>

<h4>10. Payment Method: Data protection provisions about the use of PayPal as a payment processor</h4>
<p>On this website, the controller has integrated components of PayPal. PayPal is an online payment service provider. Payments are processed via so-called PayPal accounts, which represent virtual private or business accounts. PayPal is also able to process virtual payments through credit cards when a user does not have a PayPal account. A PayPal account is managed via an e-mail address, which is why there are no classic account numbers. PayPal makes it possible to trigger online payments to third parties or to receive payments. PayPal also accepts trustee functions and offers buyer protection services.</p>

<p>The European operating company of PayPal is PayPal (Europe) S.à.r.l. & Cie. S.C.A., 22-24 Boulevard Royal, 2449 Luxembourg, Luxembourg.</p>

<p>If the data subject chooses "PayPal" as the payment option in the online shop during the ordering process, we automatically transmit the data of the data subject to PayPal. By selecting this payment option, the data subject agrees to the transfer of personal data required for payment processing.</p>

<p>The personal data transmitted to PayPal is usually first name, last name, address, email address, IP address, telephone number, mobile phone number, or other data necessary for payment processing. The processing of the purchase contract also requires such personal data, which are in connection with the respective order.</p>

<p>The transmission of the data is aimed at payment processing and fraud prevention. The controller will transfer personal data to PayPal, in particular, if a legitimate interest in the transmission is given. The personal data exchanged between PayPal and the controller for the processing of the data will be transmitted by PayPal to economic credit agencies. This transmission is intended for identity and creditworthiness checks.</p>

<p>PayPal will, if necessary, pass on personal data to affiliates and service providers or subcontractors to the extent that this is necessary to fulfill contractual obligations or for data to be processed in the order.</p>

<p>The data subject has the possibility to revoke consent for the handling of personal data at any time from PayPal. A revocation shall not have any effect on personal data which must be processed, used or transmitted in accordance with (contractual) payment processing.</p>

<p>The applicable data protection provisions of PayPal may be retrieved under https://www.paypal.com/us/webapps/mpp/ua/privacy-full.</p>

<h4>11. Legal basis for the processing </h4>
<p>Art. 6(1) lit. a GDPR serves as the legal basis for processing operations for which we obtain consent for a specific processing purpose. If the processing of personal data is necessary for the performance of a contract to which the data subject is party, as is the case, for example, when processing operations are necessary for the supply of goods or to provide any other service, the processing is based on Article 6(1) lit. b GDPR. The same applies to such processing operations which are necessary for carrying out pre-contractual measures, for example in the case of inquiries concerning our products or services. Is our company subject to a legal obligation by which processing of personal data is required, such as for the fulfillment of tax obligations, the processing is based on Art. 6(1) lit. c GDPR.
In rare cases, the processing of personal data may be necessary to protect the vital interests of the data subject or of another natural person. This would be the case, for example, if a visitor were injured in our company and his name, age, health insurance data or other vital information would have to be passed on to a doctor, hospital or other third party. Then the processing would be based on Art. 6(1) lit. d GDPR.
Finally, processing operations could be based on Article 6(1) lit. f GDPR. This legal basis is used for processing operations which are not covered by any of the abovementioned legal grounds, if processing is necessary for the purposes of the legitimate interests pursued by our company or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data. Such processing operations are particularly permissible because they have been specifically mentioned by the European legislator. He considered that a legitimate interest could be assumed if the data subject is a client of the controller (Recital 47 Sentence 2 GDPR).
</p>

<h4>12. The legitimate interests pursued by the controller or by a third party</h4>
<p>Where the processing of personal data is based on Article 6(1) lit. f GDPR our legitimate interest is to carry out our business in favor of the well-being of all our employees and the shareholders.</p>

<h4>13. Period for which the personal data will be stored</h4>
<p>The criteria used to determine the period of storage of personal data is the respective statutory retention period. After expiration of that period, the corresponding data is routinely deleted, as long as it is no longer necessary for the fulfillment of the contract or the initiation of a contract.</p>

<h4>14. Provision of personal data as statutory or contractual requirement; Requirement necessary to enter into a contract; Obligation of the data subject to provide the personal data; possible consequences of failure to provide such data </h4>
<p>We clarify that the provision of personal data is partly required by law (e.g. tax regulations) or can also result from contractual provisions (e.g. information on the contractual partner).

Sometimes it may be necessary to conclude a contract that the data subject provides us with personal data, which must subsequently be processed by us. The data subject is, for example, obliged to provide us with personal data when our company signs a contract with him or her. The non-provision of the personal data would have the consequence that the contract with the data subject could not be concluded.

Before personal data is provided by the data subject, the data subject must contact our Data Protection Officer. Our Data Protection Officer clarifies to the data subject whether the provision of the personal data is required by law or contract or is necessary for the conclusion of the contract, whether there is an obligation to provide the personal data and the consequences of non-provision of the personal data.
</p>

<h4>15. Existence of automated decision-making</h4>
<p>As a responsible company, we do not use automatic decision-making or profiling.</p>

<p>This Privacy Policy has been generated by the Privacy Policy Generator of the <a href="https://dg-datenschutz.de/services/external-data-protection-officer/?lang=en">DGD - Your External DPO</a> that was developed in cooperation with RC GmbH, which sells <a href="http://remarketing.company/">used computers</a> and the <a href="https://www.wbs-law.de/eng/">German Lawyers</a> from WBS-LAW.
</p>

---------------------------

<h4>Datenschutzerklärung</h4>

<p>Wir freuen uns sehr über Ihr Interesse an unserem Unternehmen. Datenschutz hat einen besonders hohen Stellenwert für die Geschäftsleitung der smartbedded GmbH. Eine Nutzung der Internetseiten der smartbedded GmbH ist grundsätzlich ohne jede Angabe personenbezogener Daten möglich. Sofern eine betroffene Person besondere Services unseres Unternehmens über unsere Internetseite in Anspruch nehmen möchte, könnte jedoch eine Verarbeitung personenbezogener Daten erforderlich werden. Ist die Verarbeitung personenbezogener Daten erforderlich und besteht für eine solche Verarbeitung keine gesetzliche Grundlage, holen wir generell eine Einwilligung der betroffenen Person ein.</p>

<p>Die Verarbeitung personenbezogener Daten, beispielsweise des Namens, der Anschrift, E-Mail-Adresse oder Telefonnummer einer betroffenen Person, erfolgt stets im Einklang mit der Datenschutz-Grundverordnung und in Übereinstimmung mit den für die smartbedded GmbH geltenden landesspezifischen Datenschutzbestimmungen. Mittels dieser Datenschutzerklärung möchte unser Unternehmen die Öffentlichkeit über Art, Umfang und Zweck der von uns erhobenen, genutzten und verarbeiteten personenbezogenen Daten informieren. Ferner werden betroffene Personen mittels dieser Datenschutzerklärung über die ihnen zustehenden Rechte aufgeklärt.</p>

<p>Die smartbedded GmbH hat als für die Verarbeitung Verantwortlicher zahlreiche technische und organisatorische Maßnahmen umgesetzt, um einen möglichst lückenlosen Schutz der über diese Internetseite verarbeiteten personenbezogenen Daten sicherzustellen. Dennoch können Internetbasierte Datenübertragungen grundsätzlich Sicherheitslücken aufweisen, sodass ein absoluter Schutz nicht gewährleistet werden kann. Aus diesem Grund steht es jeder betroffenen Person frei, personenbezogene Daten auch auf alternativen Wegen, beispielsweise telefonisch, an uns zu übermitteln.</p>

<h4>1. Begriffsbestimmungen</h4>
<p>Die Datenschutzerklärung der smartbedded GmbH beruht auf den Begrifflichkeiten, die durch den Europäischen Richtlinien- und Verordnungsgeber beim Erlass der Datenschutz-Grundverordnung (DS-GVO) verwendet wurden. Unsere Datenschutzerklärung soll sowohl für die Öffentlichkeit als auch für unsere Kunden und Geschäftspartner einfach lesbar und verständlich sein. Um dies zu gewährleisten, möchten wir vorab die verwendeten Begrifflichkeiten erläutern.</p>

<p>Wir verwenden in dieser Datenschutzerklärung unter anderem die folgenden Begriffe:</p>

<ul style="list-style: none">
<li><h4>a) personenbezogene Daten</h4>
<p>Personenbezogene Daten sind alle Informationen, die sich auf eine identifizierte oder identifizierbare natürliche Person (im Folgenden „betroffene Person“) beziehen. Als identifizierbar wird eine natürliche Person angesehen, die direkt oder indirekt, insbesondere mittels Zuordnung zu einer Kennung wie einem Namen, zu einer Kennnummer, zu Standortdaten, zu einer Online-Kennung oder zu einem oder mehreren besonderen Merkmalen, die Ausdruck der physischen, physiologischen, genetischen, psychischen, wirtschaftlichen, kulturellen oder sozialen Identität dieser natürlichen Person sind, identifiziert werden kann.</p>
</li>
<li><h4>b) betroffene Person</h4>
<p>Betroffene Person ist jede identifizierte oder identifizierbare natürliche Person, deren personenbezogene Daten von dem für die Verarbeitung Verantwortlichen verarbeitet werden.</p>
</li>
<li><h4>c) Verarbeitung</h4>
<p>Verarbeitung ist jeder mit oder ohne Hilfe automatisierter Verfahren ausgeführte Vorgang oder jede solche Vorgangsreihe im Zusammenhang mit personenbezogenen Daten wie das Erheben, das Erfassen, die Organisation, das Ordnen, die Speicherung, die Anpassung oder Veränderung, das Auslesen, das Abfragen, die Verwendung, die Offenlegung durch Übermittlung, Verbreitung oder eine andere Form der Bereitstellung, den Abgleich oder die Verknüpfung, die Einschränkung, das Löschen oder die Vernichtung.</p>
</li>
<li><h4>d) Einschränkung der Verarbeitung</h4>
<p>Einschränkung der Verarbeitung ist die Markierung gespeicherter personenbezogener Daten mit dem Ziel, ihre künftige Verarbeitung einzuschränken.</p>
</li>
<li><h4>e) Profiling</h4>
<p>Profiling ist jede Art der automatisierten Verarbeitung personenbezogener Daten, die darin besteht, dass diese personenbezogenen Daten verwendet werden, um bestimmte persönliche Aspekte, die sich auf eine natürliche Person beziehen, zu bewerten, insbesondere, um Aspekte bezüglich Arbeitsleistung, wirtschaftlicher Lage, Gesundheit, persönlicher Vorlieben, Interessen, Zuverlässigkeit, Verhalten, Aufenthaltsort oder Ortswechsel dieser natürlichen Person zu analysieren oder vorherzusagen.</p>
</li>
<li><h4>f) Pseudonymisierung</h4>
<p>Pseudonymisierung ist die Verarbeitung personenbezogener Daten in einer Weise, auf welche die personenbezogenen Daten ohne Hinzuziehung zusätzlicher Informationen nicht mehr einer spezifischen betroffenen Person zugeordnet werden können, sofern diese zusätzlichen Informationen gesondert aufbewahrt werden und technischen und organisatorischen Maßnahmen unterliegen, die gewährleisten, dass die personenbezogenen Daten nicht einer identifizierten oder identifizierbaren natürlichen Person zugewiesen werden.</p>
</li>
<li><h4>g) Verantwortlicher oder für die Verarbeitung Verantwortlicher</h4>
<p>Verantwortlicher oder für die Verarbeitung Verantwortlicher ist die natürliche oder juristische Person, Behörde, Einrichtung oder andere Stelle, die allein oder gemeinsam mit anderen über die Zwecke und Mittel der Verarbeitung von personenbezogenen Daten entscheidet. Sind die Zwecke und Mittel dieser Verarbeitung durch das Unionsrecht oder das Recht der Mitgliedstaaten vorgegeben, so kann der Verantwortliche beziehungsweise können die bestimmten Kriterien seiner Benennung nach dem Unionsrecht oder dem Recht der Mitgliedstaaten vorgesehen werden.</p>
</li>
<li><h4>h) Auftragsverarbeiter</h4>
<p>Auftragsverarbeiter ist eine natürliche oder juristische Person, Behörde, Einrichtung oder andere Stelle, die personenbezogene Daten im Auftrag des Verantwortlichen verarbeitet.</p>
</li>
<li><h4>i) Empfänger</h4>
<p>Empfänger ist eine natürliche oder juristische Person, Behörde, Einrichtung oder andere Stelle, der personenbezogene Daten offengelegt werden, unabhängig davon, ob es sich bei ihr um einen Dritten handelt oder nicht. Behörden, die im Rahmen eines bestimmten Untersuchungsauftrags nach dem Unionsrecht oder dem Recht der Mitgliedstaaten möglicherweise personenbezogene Daten erhalten, gelten jedoch nicht als Empfänger.</p>
</li>
<li><h4>j) Dritter</h4>
<p>Dritter ist eine natürliche oder juristische Person, Behörde, Einrichtung oder andere Stelle außer der betroffenen Person, dem Verantwortlichen, dem Auftragsverarbeiter und den Personen, die unter der unmittelbaren Verantwortung des Verantwortlichen oder des Auftragsverarbeiters befugt sind, die personenbezogenen Daten zu verarbeiten.</p>
</li>
<li><h4>k) Einwilligung</h4>
<p>Einwilligung ist jede von der betroffenen Person freiwillig für den bestimmten Fall in informierter Weise und unmissverständlich abgegebene Willensbekundung in Form einer Erklärung oder einer sonstigen eindeutigen bestätigenden Handlung, mit der die betroffene Person zu verstehen gibt, dass sie mit der Verarbeitung der sie betreffenden personenbezogenen Daten einverstanden ist.</p>
</li>
</ul>

<h4>2. Name und Anschrift des für die Verarbeitung Verantwortlichen</h4>
<p>Verantwortlicher im Sinne der Datenschutz-Grundverordnung, sonstiger in den Mitgliedstaaten der Europäischen Union geltenden Datenschutzgesetze und anderer Bestimmungen mit datenschutzrechtlichem Charakter ist die:</p>

<p>smartbedded GmbH</p>
<p>Querweg 35</p>
<p>24632 Lentföhrden</p>
<p>Deutschland</p>
<p>Tel.: 04192-8192250</p>
<p>E-Mail: info@smartbedded.com</p>
<p>Website: www.smartbedded.com</p>

<h4>3. Name und Anschrift des Datenschutzbeauftragten</h4>
<p>Der Datenschutzbeauftragte des für die Verarbeitung Verantwortlichen ist:</p>

Inhaber Boris Pasternak
<p>smartbedded GmbH</p>
<p>Querweg 35</p>
<p>24632 Lentföhrden</p>
<p>Deutschland</p>
<p>Tel.: 04192-8192250</p>
<p>E-Mail: info@smartbedded.com</p>
<p>Website: www.smartbedded.com</p>

<p>Jede betroffene Person kann sich jederzeit bei allen Fragen und Anregungen zum Datenschutz direkt an unseren Datenschutzbeauftragten wenden.</p>

<h4>4. Cookies</h4>
<p>Die Internetseiten der smartbedded GmbH verwenden Cookies. Cookies sind Textdateien, welche über einen Internetbrowser auf einem Computersystem abgelegt und gespeichert werden.</p>

<p>Zahlreiche Internetseiten und Server verwenden Cookies. Viele Cookies enthalten eine sogenannte Cookie-ID. Eine Cookie-ID ist eine eindeutige Kennung des Cookies. Sie besteht aus einer Zeichenfolge, durch welche Internetseiten und Server dem konkreten Internetbrowser zugeordnet werden können, in dem das Cookie gespeichert wurde. Dies ermöglicht es den besuchten Internetseiten und Servern, den individuellen Browser der betroffenen Person von anderen Internetbrowsern, die andere Cookies enthalten, zu unterscheiden. Ein bestimmter Internetbrowser kann über die eindeutige Cookie-ID wiedererkannt und identifiziert werden.</p>

<p>Durch den Einsatz von Cookies kann die smartbedded GmbH den Nutzern dieser Internetseite nutzerfreundlichere Services bereitstellen, die ohne die Cookie-Setzung nicht möglich wären.</p>

<p>Mittels eines Cookies können die Informationen und Angebote auf unserer Internetseite im Sinne des Benutzers optimiert werden. Cookies ermöglichen uns, wie bereits erwähnt, die Benutzer unserer Internetseite wiederzuerkennen. Zweck dieser Wiedererkennung ist es, den Nutzern die Verwendung unserer Internetseite zu erleichtern. Der Benutzer einer Internetseite, die Cookies verwendet, muss beispielsweise nicht bei jedem Besuch der Internetseite erneut seine Zugangsdaten eingeben, weil dies von der Internetseite und dem auf dem Computersystem des Benutzers abgelegten Cookie übernommen wird. Ein weiteres Beispiel ist das Cookie eines Warenkorbes im Online-Shop. Der Online-Shop merkt sich die Artikel, die ein Kunde in den virtuellen Warenkorb gelegt hat, über ein Cookie.</p>

<p>Die betroffene Person kann die Setzung von Cookies durch unsere Internetseite jederzeit mittels einer entsprechenden Einstellung des genutzten Internetbrowsers verhindern und damit der Setzung von Cookies dauerhaft widersprechen. Ferner können bereits gesetzte Cookies jederzeit über einen Internetbrowser oder andere Softwareprogramme gelöscht werden. Dies ist in allen gängigen Internetbrowsern möglich. Deaktiviert die betroffene Person die Setzung von Cookies in dem genutzten Internetbrowser, sind unter Umständen nicht alle Funktionen unserer Internetseite vollumfänglich nutzbar.</p>

<h4>5. Erfassung von allgemeinen Daten und Informationen</h4>
<p>Die Internetseite der smartbedded GmbH erfasst mit jedem Aufruf der Internetseite durch eine betroffene Person oder ein automatisiertes System eine Reihe von allgemeinen Daten und Informationen. Diese allgemeinen Daten und Informationen werden in den Logfiles des Servers gespeichert. Erfasst werden können die (1) verwendeten Browsertypen und Versionen, (2) das vom zugreifenden System verwendete Betriebssystem, (3) die Internetseite, von welcher ein zugreifendes System auf unsere Internetseite gelangt (sogenannte Referrer), (4) die Unterwebseiten, welche über ein zugreifendes System auf unserer Internetseite angesteuert werden, (5) das Datum und die Uhrzeit eines Zugriffs auf die Internetseite, (6) eine Internet-Protokoll-Adresse (IP-Adresse), (7) der Internet-Service-Provider des zugreifenden Systems und (8) sonstige ähnliche Daten und Informationen, die der Gefahrenabwehr im Falle von Angriffen auf unsere informationstechnologischen Systeme dienen.</p>

<p>Bei der Nutzung dieser allgemeinen Daten und Informationen zieht die smartbedded GmbH keine Rückschlüsse auf die betroffene Person. Diese Informationen werden vielmehr benötigt, um (1) die Inhalte unserer Internetseite korrekt auszuliefern, (2) die Inhalte unserer Internetseite sowie die Werbung für diese zu optimieren, (3) die dauerhafte Funktionsfähigkeit unserer informationstechnologischen Systeme und der Technik unserer Internetseite zu gewährleisten sowie (4) um Strafverfolgungsbehörden im Falle eines Cyberangriffes die zur Strafverfolgung notwendigen Informationen bereitzustellen. Diese anonym erhobenen Daten und Informationen werden durch die smartbedded GmbH daher einerseits statistisch und ferner mit dem Ziel ausgewertet, den Datenschutz und die Datensicherheit in unserem Unternehmen zu erhöhen, um letztlich ein optimales Schutzniveau für die von uns verarbeiteten personenbezogenen Daten sicherzustellen. Die anonymen Daten der Server-Logfiles werden getrennt von allen durch eine betroffene Person angegebenen personenbezogenen Daten gespeichert.</p>

<h4>6. Registrierung auf unserer Internetseite</h4>
<p>Die betroffene Person hat die Möglichkeit, sich auf der Internetseite des für die Verarbeitung Verantwortlichen unter Angabe von personenbezogenen Daten zu registrieren. Welche personenbezogenen Daten dabei an den für die Verarbeitung Verantwortlichen übermittelt werden, ergibt sich aus der jeweiligen Eingabemaske, die für die Registrierung verwendet wird. Die von der betroffenen Person eingegebenen personenbezogenen Daten werden ausschließlich für die interne Verwendung bei dem für die Verarbeitung Verantwortlichen und für eigene Zwecke erhoben und gespeichert. Der für die Verarbeitung Verantwortliche kann die Weitergabe an einen oder mehrere Auftragsverarbeiter, beispielsweise einen Paketdienstleister, veranlassen, der die personenbezogenen Daten ebenfalls ausschließlich für eine interne Verwendung, die dem für die Verarbeitung Verantwortlichen zuzurechnen ist, nutzt.</p>

<p>Durch eine Registrierung auf der Internetseite des für die Verarbeitung Verantwortlichen wird ferner die vom Internet-Service-Provider (ISP) der betroffenen Person vergebene IP-Adresse, das Datum sowie die Uhrzeit der Registrierung gespeichert. Die Speicherung dieser Daten erfolgt vor dem Hintergrund, dass nur so der Missbrauch unserer Dienste verhindert werden kann, und diese Daten im Bedarfsfall ermöglichen, begangene Straftaten aufzuklären. Insofern ist die Speicherung dieser Daten zur Absicherung des für die Verarbeitung Verantwortlichen erforderlich. Eine Weitergabe dieser Daten an Dritte erfolgt grundsätzlich nicht, sofern keine gesetzliche Pflicht zur Weitergabe besteht oder die Weitergabe der Strafverfolgung dient.</p>

<p>Die Registrierung der betroffenen Person unter freiwilliger Angabe personenbezogener Daten dient dem für die Verarbeitung Verantwortlichen dazu, der betroffenen Person Inhalte oder Leistungen anzubieten, die aufgrund der Natur der Sache nur registrierten Benutzern angeboten werden können. Registrierten Personen steht die Möglichkeit frei, die bei der Registrierung angegebenen personenbezogenen Daten jederzeit abzuändern oder vollständig aus dem Datenbestand des für die Verarbeitung Verantwortlichen löschen zu lassen.</p>

<p>Der für die Verarbeitung Verantwortliche erteilt jeder betroffenen Person jederzeit auf Anfrage Auskunft darüber, welche personenbezogenen Daten über die betroffene Person gespeichert sind. Ferner berichtigt oder löscht der für die Verarbeitung Verantwortliche personenbezogene Daten auf Wunsch oder Hinweis der betroffenen Person, soweit dem keine gesetzlichen Aufbewahrungspflichten entgegenstehen. Ein in dieser Datenschutzerklärung namentlich benannter Datenschutzbeauftragter und die Gesamtheit der Mitarbeiter des für die Verarbeitung Verantwortlichen stehen der betroffenen Person in diesem Zusammenhang als Ansprechpartner zur Verfügung.</p>

<h4>7. Routinemäßige Löschung und Sperrung von personenbezogenen Daten</h4>
<p>Der für die Verarbeitung Verantwortliche verarbeitet und speichert personenbezogene Daten der betroffenen Person nur für den Zeitraum, der zur Erreichung des Speicherungszwecks erforderlich ist oder sofern dies durch den Europäischen Richtlinien- und Verordnungsgeber oder einen anderen Gesetzgeber in Gesetzen oder Vorschriften, welchen der für die Verarbeitung Verantwortliche unterliegt, vorgesehen wurde.</p>

<p>Entfällt der Speicherungszweck oder läuft eine vom Europäischen Richtlinien- und Verordnungsgeber oder einem anderen zuständigen Gesetzgeber vorgeschriebene Speicherfrist ab, werden die personenbezogenen Daten routinemäßig und entsprechend den gesetzlichen Vorschriften gesperrt oder gelöscht.</p>

<h4>8. Rechte der betroffenen Person</h4>
<ul style="list-style: none;">
<li><h4>a) Recht auf Bestätigung</h4>
<p>Jede betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber eingeräumte Recht, von dem für die Verarbeitung Verantwortlichen eine Bestätigung darüber zu verlangen, ob sie betreffende personenbezogene Daten verarbeitet werden. Möchte eine betroffene Person dieses Bestätigungsrecht in Anspruch nehmen, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden.</p>
</li>
<li><h4>b) Recht auf Auskunft</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, jederzeit von dem für die Verarbeitung Verantwortlichen unentgeltliche Auskunft über die zu seiner Person gespeicherten personenbezogenen Daten und eine Kopie dieser Auskunft zu erhalten. Ferner hat der Europäische Richtlinien- und Verordnungsgeber der betroffenen Person Auskunft über folgende Informationen zugestanden:</p>

<ul style="list-style: none;">
<li>die Verarbeitungszwecke</li>
<li>die Kategorien personenbezogener Daten, die verarbeitet werden</li>
<li>die Empfänger oder Kategorien von Empfängern, gegenüber denen die personenbezogenen Daten offengelegt worden sind oder noch offengelegt werden, insbesondere bei Empfängern in Drittländern oder bei internationalen Organisationen</li>
<li>falls möglich die geplante Dauer, für die die personenbezogenen Daten gespeichert werden, oder, falls dies nicht möglich ist, die Kriterien für die Festlegung dieser Dauer</li>
<li>das Bestehen eines Rechts auf Berichtigung oder Löschung der sie betreffenden personenbezogenen Daten oder auf Einschränkung der Verarbeitung durch den Verantwortlichen oder eines Widerspruchsrechts gegen diese Verarbeitung</li>
<li>das Bestehen eines Beschwerderechts bei einer Aufsichtsbehörde</li>
<li>wenn die personenbezogenen Daten nicht bei der betroffenen Person erhoben werden: Alle verfügbaren Informationen über die Herkunft der Daten</li>
<li>das Bestehen einer automatisierten Entscheidungsfindung einschließlich Profiling gemäß Artikel 22 Abs.1 und 4 DS-GVO und — zumindest in diesen Fällen — aussagekräftige Informationen über die involvierte Logik sowie die Tragweite und die angestrebten Auswirkungen einer derartigen Verarbeitung für die betroffene Person</li>

</ul>
<p>Ferner steht der betroffenen Person ein Auskunftsrecht darüber zu, ob personenbezogene Daten an ein Drittland oder an eine internationale Organisation übermittelt wurden. Sofern dies der Fall ist, so steht der betroffenen Person im Übrigen das Recht zu, Auskunft über die geeigneten Garantien im Zusammenhang mit der Übermittlung zu erhalten.</p>

<p>Möchte eine betroffene Person dieses Auskunftsrecht in Anspruch nehmen, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden.</p>
</li>
<li><h4>c) Recht auf Berichtigung</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, die unverzügliche Berichtigung sie betreffender unrichtiger personenbezogener Daten zu verlangen. Ferner steht der betroffenen Person das Recht zu, unter Berücksichtigung der Zwecke der Verarbeitung, die Vervollständigung unvollständiger personenbezogener Daten — auch mittels einer ergänzenden Erklärung — zu verlangen.</p>

<p>Möchte eine betroffene Person dieses Berichtigungsrecht in Anspruch nehmen, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden.</p></li>
<li>
<h4>d) Recht auf Löschung (Recht auf Vergessen werden)</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, von dem Verantwortlichen zu verlangen, dass die sie betreffenden personenbezogenen Daten unverzüglich gelöscht werden, sofern einer der folgenden Gründe zutrifft und soweit die Verarbeitung nicht erforderlich ist:</p>

<ul style="list-style: none;">
<li>Die personenbezogenen Daten wurden für solche Zwecke erhoben oder auf sonstige Weise verarbeitet, für welche sie nicht mehr notwendig sind.</li>
<li>Die betroffene Person widerruft ihre Einwilligung, auf die sich die Verarbeitung gemäß Art. 6 Abs. 1 Buchstabe a DS-GVO oder Art. 9 Abs. 2 Buchstabe a DS-GVO stützte, und es fehlt an einer anderweitigen Rechtsgrundlage für die Verarbeitung.</li>
<li>Die betroffene Person legt gemäß Art. 21 Abs. 1 DS-GVO Widerspruch gegen die Verarbeitung ein, und es liegen keine vorrangigen berechtigten Gründe für die Verarbeitung vor, oder die betroffene Person legt gemäß Art. 21 Abs. 2 DS-GVO Widerspruch gegen die Verarbeitung ein.</li>
<li>Die personenbezogenen Daten wurden unrechtmäßig verarbeitet.</li>
<li>Die Löschung der personenbezogenen Daten ist zur Erfüllung einer rechtlichen Verpflichtung nach dem Unionsrecht oder dem Recht der Mitgliedstaaten erforderlich, dem der Verantwortliche unterliegt.</li>
<li>Die personenbezogenen Daten wurden in Bezug auf angebotene Dienste der Informationsgesellschaft gemäß Art. 8 Abs. 1 DS-GVO erhoben.</li>

</ul>
<p>Sofern einer der oben genannten Gründe zutrifft und eine betroffene Person die Löschung von personenbezogenen Daten, die bei der smartbedded GmbH gespeichert sind, veranlassen möchte, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden. Der Datenschutzbeauftragte der smartbedded GmbH oder ein anderer Mitarbeiter wird veranlassen, dass dem Löschverlangen unverzüglich nachgekommen wird.</p>

<p>Wurden die personenbezogenen Daten von der smartbedded GmbH öffentlich gemacht und ist unser Unternehmen als Verantwortlicher gemäß Art. 17 Abs. 1 DS-GVO zur Löschung der personenbezogenen Daten verpflichtet, so trifft die smartbedded GmbH unter Berücksichtigung der verfügbaren Technologie und der Implementierungskosten angemessene Maßnahmen, auch technischer Art, um andere für die Datenverarbeitung Verantwortliche, welche die veröffentlichten personenbezogenen Daten verarbeiten, darüber in Kenntnis zu setzen, dass die betroffene Person von diesen anderen für die Datenverarbeitung Verantwortlichen die Löschung sämtlicher Links zu diesen personenbezogenen Daten oder von Kopien oder Replikationen dieser personenbezogenen Daten verlangt hat, soweit die Verarbeitung nicht erforderlich ist. Der Datenschutzbeauftragte der smartbedded GmbH oder ein anderer Mitarbeiter wird im Einzelfall das Notwendige veranlassen.</p>
</li>
<li><h4>e) Recht auf Einschränkung der Verarbeitung</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, von dem Verantwortlichen die Einschränkung der Verarbeitung zu verlangen, wenn eine der folgenden Voraussetzungen gegeben ist:</p>

<ul style="list-style: none;">
<li>Die Richtigkeit der personenbezogenen Daten wird von der betroffenen Person bestritten, und zwar für eine Dauer, die es dem Verantwortlichen ermöglicht, die Richtigkeit der personenbezogenen Daten zu überprüfen.</li>
<li>Die Verarbeitung ist unrechtmäßig, die betroffene Person lehnt die Löschung der personenbezogenen Daten ab und verlangt stattdessen die Einschränkung der Nutzung der personenbezogenen Daten.</li>
<li>Der Verantwortliche benötigt die personenbezogenen Daten für die Zwecke der Verarbeitung nicht länger, die betroffene Person benötigt sie jedoch zur Geltendmachung, Ausübung oder Verteidigung von Rechtsansprüchen.</li>
<li>Die betroffene Person hat Widerspruch gegen die Verarbeitung gem. Art. 21 Abs. 1 DS-GVO eingelegt und es steht noch nicht fest, ob die berechtigten Gründe des Verantwortlichen gegenüber denen der betroffenen Person überwiegen.</li>

</ul>
<p>Sofern eine der oben genannten Voraussetzungen gegeben ist und eine betroffene Person die Einschränkung von personenbezogenen Daten, die bei der smartbedded GmbH gespeichert sind, verlangen möchte, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden. Der Datenschutzbeauftragte der smartbedded GmbH oder ein anderer Mitarbeiter wird die Einschränkung der Verarbeitung veranlassen.</p>
</li>
<li><h4>f) Recht auf Datenübertragbarkeit</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, die sie betreffenden personenbezogenen Daten, welche durch die betroffene Person einem Verantwortlichen bereitgestellt wurden, in einem strukturierten, gängigen und maschinenlesbaren Format zu erhalten. Sie hat außerdem das Recht, diese Daten einem anderen Verantwortlichen ohne Behinderung durch den Verantwortlichen, dem die personenbezogenen Daten bereitgestellt wurden, zu übermitteln, sofern die Verarbeitung auf der Einwilligung gemäß Art. 6 Abs. 1 Buchstabe a DS-GVO oder Art. 9 Abs. 2 Buchstabe a DS-GVO oder auf einem Vertrag gemäß Art. 6 Abs. 1 Buchstabe b DS-GVO beruht und die Verarbeitung mithilfe automatisierter Verfahren erfolgt, sofern die Verarbeitung nicht für die Wahrnehmung einer Aufgabe erforderlich ist, die im öffentlichen Interesse liegt oder in Ausübung öffentlicher Gewalt erfolgt, welche dem Verantwortlichen übertragen wurde.</p>

<p>Ferner hat die betroffene Person bei der Ausübung ihres Rechts auf Datenübertragbarkeit gemäß Art. 20 Abs. 1 DS-GVO das Recht, zu erwirken, dass die personenbezogenen Daten direkt von einem Verantwortlichen an einen anderen Verantwortlichen übermittelt werden, soweit dies technisch machbar ist und sofern hiervon nicht die Rechte und Freiheiten anderer Personen beeinträchtigt werden.</p>

<p>Zur Geltendmachung des Rechts auf Datenübertragbarkeit kann sich die betroffene Person jederzeit an den von der smartbedded GmbH bestellten Datenschutzbeauftragten oder einen anderen Mitarbeiter wenden.</p>

</li>
<li>
<h4>g) Recht auf Widerspruch</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, aus Gründen, die sich aus ihrer besonderen Situation ergeben, jederzeit gegen die Verarbeitung sie betreffender personenbezogener Daten, die aufgrund von Art. 6 Abs. 1 Buchstaben e oder f DS-GVO erfolgt, Widerspruch einzulegen. Dies gilt auch für ein auf diese Bestimmungen gestütztes Profiling.</p>

<p>Die smartbedded GmbH verarbeitet die personenbezogenen Daten im Falle des Widerspruchs nicht mehr, es sei denn, wir können zwingende schutzwürdige Gründe für die Verarbeitung nachweisen, die den Interessen, Rechten und Freiheiten der betroffenen Person überwiegen, oder die Verarbeitung dient der Geltendmachung, Ausübung oder Verteidigung von Rechtsansprüchen.</p>

<p>Verarbeitet die smartbedded GmbH personenbezogene Daten, um Direktwerbung zu betreiben, so hat die betroffene Person das Recht, jederzeit Widerspruch gegen die Verarbeitung der personenbezogenen Daten zum Zwecke derartiger Werbung einzulegen. Dies gilt auch für das Profiling, soweit es mit solcher Direktwerbung in Verbindung steht. Widerspricht die betroffene Person gegenüber der smartbedded GmbH der Verarbeitung für Zwecke der Direktwerbung, so wird die smartbedded GmbH die personenbezogenen Daten nicht mehr für diese Zwecke verarbeiten.</p>

<p>Zudem hat die betroffene Person das Recht, aus Gründen, die sich aus ihrer besonderen Situation ergeben, gegen die sie betreffende Verarbeitung personenbezogener Daten, die bei der smartbedded GmbH zu wissenschaftlichen oder historischen Forschungszwecken oder zu statistischen Zwecken gemäß Art. 89 Abs. 1 DS-GVO erfolgen, Widerspruch einzulegen, es sei denn, eine solche Verarbeitung ist zur Erfüllung einer im öffentlichen Interesse liegenden Aufgabe erforderlich.</p>

<p>Zur Ausübung des Rechts auf Widerspruch kann sich die betroffene Person direkt an den Datenschutzbeauftragten der smartbedded GmbH oder einen anderen Mitarbeiter wenden. Der betroffenen Person steht es ferner frei, im Zusammenhang mit der Nutzung von Diensten der Informationsgesellschaft, ungeachtet der Richtlinie 2002/58/EG, ihr Widerspruchsrecht mittels automatisierter Verfahren auszuüben, bei denen technische Spezifikationen verwendet werden.</p>
</li>
<li><h4>h) Automatisierte Entscheidungen im Einzelfall einschließlich Profiling</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, nicht einer ausschließlich auf einer automatisierten Verarbeitung — einschließlich Profiling — beruhenden Entscheidung unterworfen zu werden, die ihr gegenüber rechtliche Wirkung entfaltet oder sie in ähnlicher Weise erheblich beeinträchtigt, sofern die Entscheidung (1) nicht für den Abschluss oder die Erfüllung eines Vertrags zwischen der betroffenen Person und dem Verantwortlichen erforderlich ist, oder (2) aufgrund von Rechtsvorschriften der Union oder der Mitgliedstaaten, denen der Verantwortliche unterliegt, zulässig ist und diese Rechtsvorschriften angemessene Maßnahmen zur Wahrung der Rechte und Freiheiten sowie der berechtigten Interessen der betroffenen Person enthalten oder (3) mit ausdrücklicher Einwilligung der betroffenen Person erfolgt.</p>

<p>Ist die Entscheidung (1) für den Abschluss oder die Erfüllung eines Vertrags zwischen der betroffenen Person und dem Verantwortlichen erforderlich oder (2) erfolgt sie mit ausdrücklicher Einwilligung der betroffenen Person, trifft die smartbedded GmbH angemessene Maßnahmen, um die Rechte und Freiheiten sowie die berechtigten Interessen der betroffenen Person zu wahren, wozu mindestens das Recht auf Erwirkung des Eingreifens einer Person seitens des Verantwortlichen, auf Darlegung des eigenen Standpunkts und auf Anfechtung der Entscheidung gehört.</p>

<p>Möchte die betroffene Person Rechte mit Bezug auf automatisierte Entscheidungen geltend machen, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden.</p>

</li>
<li><h4>i) Recht auf Widerruf einer datenschutzrechtlichen Einwilligung</h4>
<p>Jede von der Verarbeitung personenbezogener Daten betroffene Person hat das vom Europäischen Richtlinien- und Verordnungsgeber gewährte Recht, eine Einwilligung zur Verarbeitung personenbezogener Daten jederzeit zu widerrufen.</p>

<p>Möchte die betroffene Person ihr Recht auf Widerruf einer Einwilligung geltend machen, kann sie sich hierzu jederzeit an unseren Datenschutzbeauftragten oder einen anderen Mitarbeiter des für die Verarbeitung Verantwortlichen wenden.</p>

</li>
</ul>
<h4>9. Datenschutzbestimmungen zu Einsatz und Verwendung von YouTube</h4>
<p>Der für die Verarbeitung Verantwortliche hat auf dieser Internetseite Komponenten von YouTube integriert. YouTube ist ein Internet-Videoportal, dass Video-Publishern das kostenlose Einstellen von Videoclips und anderen Nutzern die ebenfalls kostenfreie Betrachtung, Bewertung und Kommentierung dieser ermöglicht. YouTube gestattet die Publikation aller Arten von Videos, weshalb sowohl komplette Film- und Fernsehsendungen, aber auch Musikvideos, Trailer oder von Nutzern selbst angefertigte Videos über das Internetportal abrufbar sind.</p>

<p>Betreibergesellschaft von YouTube ist die YouTube, LLC, 901 Cherry Ave., San Bruno, CA 94066, USA. Die YouTube, LLC ist einer Tochtergesellschaft der Google Inc., 1600 Amphitheatre Pkwy, Mountain View, CA 94043-1351, USA.</p>

<p>Durch jeden Aufruf einer der Einzelseiten dieser Internetseite, die durch den für die Verarbeitung Verantwortlichen betrieben wird und auf welcher eine YouTube-Komponente (YouTube-Video) integriert wurde, wird der Internetbrowser auf dem informationstechnologischen System der betroffenen Person automatisch durch die jeweilige YouTube-Komponente veranlasst, eine Darstellung der entsprechenden YouTube-Komponente von YouTube herunterzuladen. Weitere Informationen zu YouTube können unter https://www.youtube.com/yt/about/de/ abgerufen werden. Im Rahmen dieses technischen Verfahrens erhalten YouTube und Google Kenntnis darüber, welche konkrete Unterseite unserer Internetseite durch die betroffene Person besucht wird.</p>

<p>Sofern die betroffene Person gleichzeitig bei YouTube eingeloggt ist, erkennt YouTube mit dem Aufruf einer Unterseite, die ein YouTube-Video enthält, welche konkrete Unterseite unserer Internetseite die betroffene Person besucht. Diese Informationen werden durch YouTube und Google gesammelt und dem jeweiligen YouTube-Account der betroffenen Person zugeordnet.</p>

<p>YouTube und Google erhalten über die YouTube-Komponente immer dann eine Information darüber, dass die betroffene Person unsere Internetseite besucht hat, wenn die betroffene Person zum Zeitpunkt des Aufrufs unserer Internetseite gleichzeitig bei YouTube eingeloggt ist; dies findet unabhängig davon statt, ob die betroffene Person ein YouTube-Video anklickt oder nicht. Ist eine derartige Übermittlung dieser Informationen an YouTube und Google von der betroffenen Person nicht gewollt, kann diese die Übermittlung dadurch verhindern, dass sie sich vor einem Aufruf unserer Internetseite aus ihrem YouTube-Account ausloggt.</p>

<p>Die von YouTube veröffentlichten Datenschutzbestimmungen, die unter https://www.google.de/intl/de/policies/privacy/ abrufbar sind, geben Aufschluss über die Erhebung, Verarbeitung und Nutzung personenbezogener Daten durch YouTube und Google.</p>

<h4>10. Zahlungsart: Datenschutzbestimmungen zu PayPal als Zahlungsart</h4>
<p>Der für die Verarbeitung Verantwortliche hat auf dieser Internetseite Komponenten von PayPal integriert. PayPal ist ein Online-Zahlungsdienstleister. Zahlungen werden über sogenannte PayPal-Konten abgewickelt, die virtuelle Privat- oder Geschäftskonten darstellen. Zudem besteht bei PayPal die Möglichkeit, virtuelle Zahlungen über Kreditkarten abzuwickeln, wenn ein Nutzer kein PayPal-Konto unterhält. Ein PayPal-Konto wird über eine E-Mail-Adresse geführt, weshalb es keine klassische Kontonummer gibt. PayPal ermöglicht es, Online-Zahlungen an Dritte auszulösen oder auch Zahlungen zu empfangen. PayPal übernimmt ferner Treuhänderfunktionen und bietet Käuferschutzdienste an.</p>

<p>Die Europäische Betreibergesellschaft von PayPal ist die PayPal (Europe) S.à.r.l. & Cie. S.C.A., 22-24 Boulevard Royal, 2449 Luxembourg, Luxemburg.</p>

<p>Wählt die betroffene Person während des Bestellvorgangs in unserem Online-Shop als Zahlungsmöglichkeit „PayPal“ aus, werden automatisiert Daten der betroffenen Person an PayPal übermittelt. Mit der Auswahl dieser Zahlungsoption willigt die betroffene Person in die zur Zahlungsabwicklung erforderliche Übermittlung personenbezogener Daten ein.</p>

<p>Bei den an PayPal übermittelten personenbezogenen Daten handelt es sich in der Regel um Vorname, Nachname, Adresse, Email-Adresse, IP-Adresse, Telefonnummer, Mobiltelefonnummer oder andere Daten, die zur Zahlungsabwicklung notwendig sind. Zur Abwicklung des Kaufvertrages notwendig sind auch solche personenbezogenen Daten, die im Zusammenhang mit der jeweiligen Bestellung stehen.</p>

<p>Die Übermittlung der Daten bezweckt die Zahlungsabwicklung und die Betrugsprävention. Der für die Verarbeitung Verantwortliche wird PayPal personenbezogene Daten insbesondere dann übermitteln, wenn ein berechtigtes Interesse für die Übermittlung gegeben ist. Die zwischen PayPal und dem für die Verarbeitung Verantwortlichen ausgetauschten personenbezogenen Daten werden von PayPal unter Umständen an Wirtschaftsauskunfteien übermittelt. Diese Übermittlung bezweckt die Identitäts- und Bonitätsprüfung.</p>

<p>PayPal gibt die personenbezogenen Daten gegebenenfalls an verbundene Unternehmen und Leistungserbringer oder Subunternehmer weiter, soweit dies zur Erfüllung der vertraglichen Verpflichtungen erforderlich ist oder die Daten im Auftrag verarbeitet werden sollen.</p>

<p>Die betroffene Person hat die Möglichkeit, die Einwilligung zum Umgang mit personenbezogenen Daten jederzeit gegenüber PayPal zu widerrufen. Ein Widerruf wirkt sich nicht auf personenbezogene Daten aus, die zwingend zur (vertragsgemäßen) Zahlungsabwicklung verarbeitet, genutzt oder übermittelt werden müssen. </p>

<p>Die geltenden Datenschutzbestimmungen von PayPal können unter https://www.paypal.com/de/webapps/mpp/ua/privacy-full abgerufen werden.</p>

<h4>11. Rechtsgrundlage der Verarbeitung</h4>
<p>Art. 6 I lit. a DS-GVO dient unserem Unternehmen als Rechtsgrundlage für Verarbeitungsvorgänge, bei denen wir eine Einwilligung für einen bestimmten Verarbeitungszweck einholen. Ist die Verarbeitung personenbezogener Daten zur Erfüllung eines Vertrags, dessen Vertragspartei die betroffene Person ist, erforderlich, wie dies beispielsweise bei Verarbeitungsvorgängen der Fall ist, die für eine Lieferung von Waren oder die Erbringung einer sonstigen Leistung oder Gegenleistung notwendig sind, so beruht die Verarbeitung auf Art. 6 I lit. b DS-GVO. Gleiches gilt für solche Verarbeitungsvorgänge die zur Durchführung vorvertraglicher Maßnahmen erforderlich sind, etwa in Fällen von Anfragen zur unseren Produkten oder Leistungen. Unterliegt unser Unternehmen einer rechtlichen Verpflichtung durch welche eine Verarbeitung von personenbezogenen Daten erforderlich wird, wie beispielsweise zur Erfüllung steuerlicher Pflichten, so basiert die Verarbeitung auf Art. 6 I lit. c DS-GVO. In seltenen Fällen könnte die Verarbeitung von personenbezogenen Daten erforderlich werden, um lebenswichtige Interessen der betroffenen Person oder einer anderen natürlichen Person zu schützen. Dies wäre beispielsweise der Fall, wenn ein Besucher in unserem Betrieb verletzt werden würde und daraufhin sein Name, sein Alter, seine Krankenkassendaten oder sonstige lebenswichtige Informationen an einen Arzt, ein Krankenhaus oder sonstige Dritte weitergegeben werden müssten. Dann würde die Verarbeitung auf Art. 6 I lit. d DS-GVO beruhen.
Letztlich könnten Verarbeitungsvorgänge auf Art. 6 I lit. f DS-GVO beruhen. Auf dieser Rechtsgrundlage basieren Verarbeitungsvorgänge, die von keiner der vorgenannten Rechtsgrundlagen erfasst werden, wenn die Verarbeitung zur Wahrung eines berechtigten Interesses unseres Unternehmens oder eines Dritten erforderlich ist, sofern die Interessen, Grundrechte und Grundfreiheiten des Betroffenen nicht überwiegen. Solche Verarbeitungsvorgänge sind uns insbesondere deshalb gestattet, weil sie durch den Europäischen Gesetzgeber besonders erwähnt wurden. Er vertrat insoweit die Auffassung, dass ein berechtigtes Interesse anzunehmen sein könnte, wenn die betroffene Person ein Kunde des Verantwortlichen ist (Erwägungsgrund 47 Satz 2 DS-GVO).
</p>

<h4>12. Berechtigte Interessen an der Verarbeitung, die von dem Verantwortlichen oder einem Dritten verfolgt werden</h4>
<p>Basiert die Verarbeitung personenbezogener Daten auf Artikel 6 I lit. f DS-GVO ist unser berechtigtes Interesse die Durchführung unserer Geschäftstätigkeit zugunsten des Wohlergehens all unserer Mitarbeiter und unserer Anteilseigner.</p>

<h4>13. Dauer, für die die personenbezogenen Daten gespeichert werden</h4>
<p>Das Kriterium für die Dauer der Speicherung von personenbezogenen Daten ist die jeweilige gesetzliche Aufbewahrungsfrist. Nach Ablauf der Frist werden die entsprechenden Daten routinemäßig gelöscht, sofern sie nicht mehr zur Vertragserfüllung oder Vertragsanbahnung erforderlich sind.</p>

<h4>14. Gesetzliche oder vertragliche Vorschriften zur Bereitstellung der personenbezogenen Daten; Erforderlichkeit für den Vertragsabschluss; Verpflichtung der betroffenen Person, die personenbezogenen Daten bereitzustellen; mögliche Folgen der Nichtbereitstellung</h4>
<p>Wir klären Sie darüber auf, dass die Bereitstellung personenbezogener Daten zum Teil gesetzlich vorgeschrieben ist (z.B. Steuervorschriften) oder sich auch aus vertraglichen Regelungen (z.B. Angaben zum Vertragspartner) ergeben kann.
Mitunter kann es zu einem Vertragsschluss erforderlich sein, dass eine betroffene Person uns personenbezogene Daten zur Verfügung stellt, die in der Folge durch uns verarbeitet werden müssen. Die betroffene Person ist beispielsweise verpflichtet uns personenbezogene Daten bereitzustellen, wenn unser Unternehmen mit ihr einen Vertrag abschließt. Eine Nichtbereitstellung der personenbezogenen Daten hätte zur Folge, dass der Vertrag mit dem Betroffenen nicht geschlossen werden könnte.
Vor einer Bereitstellung personenbezogener Daten durch den Betroffenen muss sich der Betroffene an unseren Datenschutzbeauftragten wenden. Unser Datenschutzbeauftragter klärt den Betroffenen einzelfallbezogen darüber auf, ob die Bereitstellung der personenbezogenen Daten gesetzlich oder vertraglich vorgeschrieben oder für den Vertragsabschluss erforderlich ist, ob eine Verpflichtung besteht, die personenbezogenen Daten bereitzustellen, und welche Folgen die Nichtbereitstellung der personenbezogenen Daten hätte.
</p>

<h4>15. Bestehen einer automatisierten Entscheidungsfindung</h4>
<p>Als verantwortungsbewusstes Unternehmen verzichten wir auf eine automatische Entscheidungsfindung oder ein Profiling.</p>

<p>Diese Datenschutzerklärung wurde durch den Datenschutzerklärungs-Generator von den <a href="https://dg-datenschutz.de/">Datenschutzbeauftragten</a> in Kooperation mit der RC GmbH, die <a href="http://remarketing.company/">gebrauchte Notebooks</a> wiederverwertet und den <a href="https://www.wbs-law.de/abmahnung-filesharing/">Filesharing Rechtsanwälten</a> von WBS-LAW erstellt.
</p>

MediaWiki:Sidebar

2024-12-04T18:10:05Z

Admin:

MediaWiki:Sidebar

2024-12-04T18:09:26Z

Admin:

Instruments

2024-12-04T18:08:02Z

Admin: Created page with "__NOTOC__ Meteoplug provides an easy way to display a dashboard with weather instruments. To keep it simple, configuration of instruments is very limited but allows you to have a quick view on your most important sensor data in a convenient way. Instruments are visualized by "Weather Display Live (WDL)" applet of Julian Best. If you are interested in details about WDL, you might visit [http://www.weather-display.com/wdlive.php these] pages. <center>File:mp-wdlive.png..."

__NOTOC__
Meteoplug provides an easy way to display a dashboard with weather instruments. To keep it simple, configuration of instruments is very limited but allows you to have a quick view on your most important sensor data in a convenient way. Instruments are visualized by "Weather Display Live (WDL)" applet of Julian Best. If you are interested in details about WDL, you might visit [http://www.weather-display.com/wdlive.php these] pages.

<center>[[File:mp-wdlive.png]]</center>

==Instruments Configuration==
To make use of Meteoplug instruments you have to enter
* '''Station Name''' which might describe location of weather station.
* '''Language''' used with instruments. You just can choose between English, Finnish, Danish, Dutch, French, Swedish, German, Catalan, Spanish, Norwegian, Italian, Portuguese, Estonian, Faroese, Frisian, Greek, Czech, Hungarian, and Bulgarian.
* '''Sensors''' to be used for
** Outdoor Temperature and Humidity
** Presure
** Wind
** Rain
** Solar (if a solar sensor available)
** UV (if an UV sensor available)
** Indoor Temperature and Humidity
* '''Units''' to be used for display. Meteoplug provides a set of units for these categories:
** Temperature: °C, °F
** Wind Speed: km/h, mps, kts, m/s
** Rain Fall: mm, in
** Pressure: mb, hPa, kPa, inHg
** Height: m, yds, ft

==Emdebbing Instruments==
Link "Call instruments directly calls a HTML page that displays instruments without administration interface. The URL does not need any login, it just displays your actual weather data as instruments as you have configured these with the steps mentioned above. URL parameters are encrypted in a way that does not allow anyone to guess your user name, station's MAC or any other information you might not want to share with the public.

You can very easily embed these instruments into your homepage by placing the provided link into an IFRAME onto your homepage's HTML code. IFRAME tag on your Homepage might look like this:

<pre>
<iframe src="https://www.meteoplug.com/cgi-bin/meteochart.cgi?draw=1c1d190602145f504218...."
allign="top"
scrolling="no"
frameborder="0"
width="550"
height="400">
Browser does not support IFRAMEs
</iframe>
</pre>

Show Chart

2024-12-04T18:07:46Z

Admin: Created page with "__NOTOC__ ==Show Chart== Meteoplug allows to display result of applying your chart definition to your weather data. Simply select chart you want to display from drop-down menu. The chart will immediately generated. If something goes wrong an error message will appear instead of chart. <center>File:mp-showchart-temphum1day.png</center> The link at the bottom allows to access the chart as a stand alone HTML page. When you want to include the chart into your homepage..."

__NOTOC__
==Show Chart==
Meteoplug allows to display result of applying your chart definition to your weather data. Simply select chart you want to display from drop-down menu. The chart will immediately generated. If something goes wrong an error message will appear instead of chart.

<center>[[File:mp-showchart-temphum1day.png]]</center>

The link at the bottom allows to access the chart as a stand alone HTML page. When you want to include the chart into your homepage, just put this link into an IFRAME section like this:

<pre>
<iframe src="http://www.meteoplug.com/cgi-bin/meteochart.cgi?draw=6f686c6a6d791900065249..."
allign="top"
scrolling="no"
frameborder="0"
width="580"
height="430">
Browser does not support IFRAMEs
</iframe>
</pre>

Using this IFRAME wrapper, the chart will be included into your home page like you can see below. Inclusion by IFRAMES is a very simply but powerful technique to bring Meteoplug content onto your web pages.

<center><iframe key="meteoplug" path="examples/example-4.html" height="440" width="590" /></center>

The URL that "Show Chart" page of Meteoplug does give to you for external reference of the chart is valid as long as
* your Meteoplug account is active and has a valid license (or is in demo mode)
* graph definition exists and still has the same name as during generation of the link

==Additional URL parameters==
There are a couple of additional URL parameters you can use to change some settings of your chart definition when calling the chart for generation. These parameters have to follow the "draw" token in the URL.

You can make use of these additional URL parameters:
* <b>timeframe</b>: While the chart definition also defines time frame to be used for display, you can overwrite time frame defined in the chart by adding URL parameter "&timeframe=20100101000000-20100131235959" to it. In the given example this will display data for January of 2010.
* <b>resolution</b>: Changes the resolution gives with "res" name-value pair in the chart definition. Example: "&resolution=min10"
* <b>client</b>: This parameter is valid for clients attached to a Meteoplug group account. You can apply the chart definition to a client with a given name. Example: "&client=beach1"

==Alternative URL==
Meteoplug can generate pure graphic files (like png) when used in gnuplot or picture mode. Some data polling devices need the URL to address a ".png" or ".jpg" file. Therefore, URLs like "http://www.meteoplug.com/cgi-bin/meteochart.cgi?draw=696368686d7930264f0b100b090b5449130f0414792a343a3337" won't do, because this does not match the expected URL naming schema. For situations like this you can change the URL to "http://www.meteoplug.com/draw/696368686d7930264f0b100b090b5449130f0414792a343a3337/temp-1month.png" where the draw toke is used as a path identifier and a filename of your choice in that path. This technique was designed to generate overlay png file to be used by Mobotix webcams but might be usefull in other situations as well.

Additional URL parameters cannot be handled by this type of URL resolution.

Define Chart

2024-12-04T18:07:27Z

Admin: Created page with "Generating graphs and displays in Meteoplug is probably one of the most exciting things as it gives you a lot of freedom to present your weather data. Meteoplug makes use of [http://amcharts.com amcharts] for interactive graphing and [http://www.fusioncharts.com/widgets/Gallery.asp fusionwidgets] for live displays with meters and gauges. Both are based on recent Flash technology. In addition to that a classical graphing based on [http://gnuplot.info gnuplot] can also be..."

Generating graphs and displays in Meteoplug is probably one of the most exciting things as it gives you a lot of freedom to present your weather data. Meteoplug makes use of [http://amcharts.com amcharts] for interactive graphing and [http://www.fusioncharts.com/widgets/Gallery.asp fusionwidgets] for live displays with meters and gauges. Both are based on recent Flash technology. In addition to that a classical graphing based on [http://gnuplot.info gnuplot] can also be used for line graphs. This section explains what kind of charts you can make use of an how to configure these. We differentate between graphs, which show the development of weather condition over a choosen period of time, and displays, which show near real-time weather conditions. As these two types do have different requirements, they are handled in separate sections.

==Definition of a Graph or Display==
When you enter Meteoplug's "Define Chart" page you see an empty page you can put your graphing or display commands into.

<center>[[File:mp-define-chart.png]]</center>

When you want to edit an existing chart or display, you can select one from the drop-down menu at the top. There are a couple of predefined charts. These are listed beginning with an underscore "_".

When you want to store a chart definition you have to enter a name for your chart next to "Save as" button. When you press "Save as" chart definition will be stored. If a chart definition with this name already exists it will be overwritten without warning. Saved charts will be added to the ones in the drop-down list. This allows you to build your personal library of definitions over time. Chart names should not include spaces or special characters and they cannot start with an underscore "_", because chart names starting with underscores are reserved for predefined charts. Predefined charts cannot be deleted or altered.

When you want to test a loaded chart definition, simply press "Display" button. A separate Window will pop-up and will show your chart. If the chart definition is wrong, an error message will appear instead. Please make sure that your browser doesn't block pop-ups from "www.meteoplug.com". JavaScript and FLASH also need to be enabled in your browser.

To delete a saved chart definition select the cart in the drop-down list and press "Delete". A warning will appear asking you if you really want to delete. Press "OK" to make the delete happen. When you abort, nothing will be deleted.

==Graphing Language==
Graphing language used in Meteoplug is derived from a subset of amcharts options. It can be easily used and provides quite some capabilities to adapt graphs to your needs. Chart commands are represented as name-value pairs separated by "=". No spaces are allowed between name, "=" and value. Name-value pairs are separated by white space characters (blanks and/or new lines). As a result you can place each name value pair into a new line or you can define multiple name-value pairs in one line separated by white spaces.

When value should include a space character (might be useful for sensor names), you have to use underscore "_" instead of space. Underscores will be converted back to spaces when being displayed. When you need a underscore "_" not to be converted into space, type two underscores "__", which will be converted to one underscore "_". If you need a line feed character in the string, use vertical bar character "|" instead.

You can add comments to the chart definition. When Meteoplug hits a "#" when it expects a new name value pair, then rest of current line will be skipped and not evaluated. This allows you to type any text you like after comment character "#". As you can see, example below makes heavy use of commenting.

When you specify numbers the decimal separator is "." regardless what language you might have selected.

===Graphing Example===
Before graphing language is explained in detail, you might have a look at chart definition below as an example. This chart defines a graph that displays monthly rainfall and number of days with rain per month for the last 3 years (including actual year). Rainfall is displayed as blue bars, number of days with rain is displayed as a smoothed red line.

<center>[[File:mp-chartxxx-rain1year.png]]</center>

Applied to my rain data the result looks like displayed above. It is a snapshot where the interactive cursor points to November 2009. To give a idea how graphing in Meteoplug does work, I will try to explain this graph definition, line by line.

Chart commands:
* <code>timeframe=3Y</code> tells Meteoplug that time frame to use is last threes years (including actual year)
* <code>zoom=1Y</code> sets display mode when initially showing the graph to 1 year. By pressing another zoom button or moving the scroller this can be changed interactively when graph is displayed.
* <code>res=month1</code> sets resolution of data to one month. Meteoplug provides data at various time resolutions you can choose from.

Graph commands:
* <code>gtitle=Rain</code> sets the title "Rain" to the top left of the graph.
* <code>gheight=400</code> defines height of graph to be 400 pixel.
* <code>gwidth=550</code> defines width of graph to be 550 pixel.
* <code>glunit=mm</code> defines unit for left y-axis to be "mm".
* <code>grunit=days</code> defines unit of right y-axis to be "days".
* <code>gtype=step</code> defines standard display type of graph to be a stepped line.
* <code>gtrim=1</code> defines that left and right end of time frame to be adapted to existing data. As data for 2010 is just covering January and February, graph does strip empty months of 2010 from graph.

Sensor commands:
* <code>sid0=rain0 scolor0=AADDFF sfill0=50 sline0=100 sname0=rain_fall ssel0=total</code> selects sensor "rain0" for display. Data field to be displayed is "total", which represents total rain fall. color of graph is "AADDFF" (light blue), line has 100% color coverage, fill area has just 50% color coverage, name of sensor is "rain fall".
* <code>sid1=rain0 ssmooth1=1 stype1=line syaxis1=r sname1=days_with_rain ssel1=days</code> selects sensor "rain0" for display. Data field to be displayed is "days", which represents number of days with rain fall, graph type is "line" with attribute "smoothed", sensor is measured on right y-axis, name of sensor is "days with rain".

===Chart Settings===
A chart definition should start with settings that are valid for all graphs in the chart and all sensors in the chart's graphs. Meteoplug provides these name-value pairs to define chart settings

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory [Applicable]''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| timeframe|| yes [LJRTCGED] || see section "time ranges"|| none || defines start and end time to be considered. This parameter can be overwritten by an URL parameter in same notation to allow change of time frame when displaying the graph. || timeframe=1Y (actual year)<br>timeframe=-1D (yesterday)<br>timeframe=20091201000000<br>-20091231235959 (December 2009)
|-
| res|| no [LJRTCGED]|| see section "time resolution"|| depends on timeframe|| defines resolution of data to be taken for graphing. This can be overwritten by an URL parameter called "resolution". || res=month1 (monthly data)<br>res=min5 (data from 5 minute buckets)<br>res=hour1 (hourly data)
|-
| zoom|| no [LJM]|| see section "chart zoom" or "maps" || depends on timeframe|| defines initial subset of data (or map) to be displayed. || zoom=1D (current day)<br>zoom=YTD (data since beginning of year until now)<br>zoom=MAX (all data of selected time range)<br>zoom=4 (show about one continent on map)
|-
| monlist, monlistlong|| no [LJ]|| list of 12 month names separated by ",". monlistlong can provide full month names instead of abbreviations (JS only) || jan,feb,mar, apr,may,jun, jul,aug,sep, oct,nov,dec || defines strings to be taken for display of months || monlist=jan,feb,mar,api,jun, jul,aug,sep,okt,nov,dez
|-
| daylist, daylistlong|| no [LJ]|| list of 7 day names separated by ",". daylistlong can provide full day names instead of abbreviations (JS only) || sun,mon,tue, wed,thu,fri,sat || defines strings to be taken for display of day names || daylist=so,mo,di,mi,do,fr,sa
|-
| dirlist|| no [TRX]|| list of 16 compass direction names separated by "," || N,NNE,NE,ENE, E,ESE,SE,SSE, S,SSW,SW,WSW, W,WNW,W,NNW || defines strings to be taken for display of compass directions || dirlist=N,NNO,NO,ONO,<BR>O,OSO,SO,SSW,S,SSW,<BR>SW,WSW,W,WNW,W,NNW
|-
| phasetextlist|| no [TX]|| list names of 8 lunar phases separated by "," || New_Moon, Waxing_Crescent, First_Quarter, Waxing_Gibbous, Full_Moon, Waning_Gibbous, Last_Quarter, Waning_Cresent || defines strings to be taken for display of lunar phases || phasetextlist=1/8,2/8,3/8,4/8,<BR>5/8,6/8,7/8,8/8
|-
| phaseiconlist|| no [TX]|| list URLs for display of lunar phases separated by "," || mp0.png, mp1.txt, ... || defines URLs to be taken for display of lunar phase icons || phaseiconlist=<BR><nowiki>http://www.meteoplug.com/mp0.png</nowiki>,...
|-
| fctextlist|| no [TX]|| list names of 9 forecast situations, separated by "," || Rainy, Cloudy, Half Cloudy, Sunny, Snowy, Half-Cloudy Night, Clear Night, Light Rainy, Light Snowy || defines strings to be taken for display of forecast values || fctextlist=Regen, Bewölkung, leichte_Bewölkung, Sonne,Schnee, leicht_bewölkte_Nacht, klare_Nacht,l eichter_Regen, leichter_Schneefall
|-
| fciconlist|| no [TX]|| list URLs for display of 9 forecast situations, separated by "," || fc0.png, fc1.txt, ... || defines URLs to be taken for display of forecast icons || fciconlist=<BR><nowiki>http://www.meteoplug.com/fc0.png</nowiki>,...
|-
| periodm, periodh, periodD, periodM, periodY || no [LJ]|| date format string for x-axis depending on time scale || see examples || provides a format template for time scales: minutes (m), hours (h), days (D), months (M), years (Y) as outlined [http://amcharts.com/docs/v.1/stock/settings/settings_reference#date_formats here] (flash) and [http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/formatters/DateFormatter.html here] (JS) || periodm=J:NN\nEEE_DD.MM. (standard for JS), periodm=hh:mm\nWW_DD.MM. (standard for flash)
|-
| legendm, legendh, legendD, legendW, legendM, legendY || no [L]|| date format string for legend depending on time scale || see examples || provides a format template for time scales: minutes (m), hours (h), days (D), weeks (W), months (M), years (Y) as outlined [http://amcharts.com/docs/v.1/stock/settings/settings_reference#date_formats here] (flash) and [http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/formatters/DateFormatter.html here] (JS) || legendh=YYYY-MM-DD_hh:mm (standard for flash)
|-
| legendpos|| no [LJ]|| top, left, right || top || defines position of legend relative to graphs || legendpos=left (legend is positioned at left side of graph and organized vertically)
|-
| legendwidth|| no [LJ]|| positive number of pixels || unknown|| defines width of legend in pixels. Needed when legendpos is left or right. Specifies size of value display in legend when used with JS|| legendwidth=100
|-
| decimalsep|| no [LJ]|| character used for separating decimals || "." (point) || Defines character to be used to separate decimals || decimalsep=, (comma)
|-
| thousandsep|| no [LJ]|| character used for separating thousands || " " (blank) || Defines character to be used to separate thousands || thousandsep=_ (blank)
|-
| xymode|| no [D]|| specifies distribution chart || 0 (no distribution chart) || Sets chart mode to type "distribution" where x-axis is not time axis but shows distribution of weather data. Number specifies how many buckets should be used. || xymode=20 (sets distribution chart, 20 buckets to use)
|-
| xstart || no [D]|| specifies first value to start with || 0.0 || Sets starting point for value iteration of distribution chart. || xstart=0.0 (sets lower bound of first buckets to 0.0, xfactor and xoffset are not applied here)
|-
| xinc || no [D]|| specifies increment value to separate buckets || 1.0 || Increment value used for computation of lower bound of next bucket. Upper bound is lower bound of next bucket. || xinc=1.0 (sets bucket size and increment between buckets to 1.0, xoffset and xfactor are not applied here)
|-
| xoffset || no [D]|| specifies offset to be applied to bucket value. || 0.0 || Offset value used when displaying bucket ranges. This can be used to make a distribution graph that lists temperature durations segmented by °F instead of °C. || xoffset=0.0 (sets bucket value offset to zero)
|-
| xfactor || no [D]|| specifies factor to be applied to bucket value. || 1.0 || Factor used when displaying bucket ranges. This can be used to make a Weibull wind speed distribution graph that lists wind speed durations segmented by mp/h instead of m/s. || xfactor=3.6 (Converts bucket values on x-axis from m/s to km/h)
|-
| restrictip || no [LJRTCGEXD] || WAN IP of requesting computer || none || restricts access to the chart to a certain requesting IP. When requesting IP does not match an error is displayed. || restrictip=81.123.23.77 (restricts access to given IP)
|-
| periodselector|| no [LJM] || defines if period selector below scroll bar should be displayed || 1 (yes) || This allows to make interactive chart a less bit high, by stripping off the period selector at the bottom. || periodselector=0 (don't use period selector)
|-
| scrollerselector|| no [LJM] || defines if scroller below graphs should be displayed || 1 (yes) || This allows to make interactive chart a less bit high, by stripping off the acroller at the bottom. In JavaScript charts this also controls if chart can be panned (scrollerselector=0) or zoomed (scrollerselector=1) with the cursor. || scrollerselector=0 (don't use scroller)
|-
| textcolor || no<br>[LJRCD] || string || black || Specifies text color in RGB style || textcolor=#0000FF (blue)
|-
| gridcolor || no<br>[LJRCD] || string || black || Defines color of grid lines in a chart's graph in RGB style || ggridcolor=#FF0000 (red)
|-
| gridalpha || no<br>[LJRCD] || 0-100 || 15 (dark gray) || Defines intensity of grid lines in a chart's graphs || ggridalpha=100 (no transparency)
|-
| bgcolor || no<br>[LJRCD] || string || white || Specifies background color in RGB style || bgcolor=#0000FF (blue)
|-
| bgalpha || no<br>[LJRCD] || 0-100 || 100 || Specifies intensity (alpha) of background color in percent || bgalpha=50 (50% intensity)
|-
| title || no<br>[LJTRCD] || string (blank chars replaced with "_") || "Meteoplug_Chart" || Defines HTML title of the chart || title=temp_of_today
|-
| engine|| no<br>[LJGT] || "flash", "javascript", "gnuplot" || "flash" || Selects which charting engine to be used. Default is flash, but you can also use javascript and gnuplot || engine=javascript
|}
<font size=1>Letter in brackets indicate applicability: [L] = flash line or bar graphs; [J] = JavaSrcipt line or bar graphs; [T] = HTML tables; [R] = radar charts; [C] = color maps; [G] = GPline/step/bar/needle/point; [E] = csv export; [X] = template replacement; [D] = distribution chart; [M] = map</font>

====Time Ranges====
Meteoplug supports absolute and relative time ranges. Notations are as follows:
* "'''YYYYMMDDhhmmss-YYYYMMDDhhmmss'''" defines a absolute range in time defined by a starting point and a end point, which are in a notation where year is given by 4 digits (YYYY), followed by a 2-digit month (MM), a 2-digit day (DD), a 2-digit hour (hh), a 2-digit minute (mm) and a 2-digit second (ss). Timestamps that exactly match a starting or end point are part of the time range.
* An integer number followed by a alpha character defines a relative range in time. Examples assume that current time is 20100130175213 (2010-01-30 17:52:13).
** "x'''s'''" sets starting point x seconds in the past and end point to actual time (example: "60s" is mapped to 20100130175113-20100130175213).
** "x'''m'''" sets starting point x minutes in the past. End point is set to actual time (example: "5m" is mapped to 20100130174713-20100130175213).
** "x'''h'''" sets starting point x hours in the past. End point is set to actual time (example: "3h" is mapped to 20100130145213-20100130175213).
** "x'''H'''" sets starting point to the beginning of the hour, x-1 hours ago. End point is set to end of current hour (example: "3H" is mapped to 20100130150000-20100130175959).
** "x'''d'''" sets starting point x days in the past. End point is set to actual time (example: "3d" is mapped to 20100127175213-20100130175213).
** "x'''D'''" sets starting point to the beginning of the day, x-1 days ago. End point is set to end of current day (example: "3D" is mapped to 20100128000000-20100130235959).
** "x'''W'''y" sets starting point to the beginning of the week, x-1 weeks ago. y controls what days is first day of week (0=Sun, 1=Mon, 2=Tue, 3=Wed, 4=Thu, 5=Fri, 6=Sat). End point is set to end of current week (example: "3W1" is mapped to 20100111000000-20100131235959).
** "x'''M'''" sets starting point to the beginning of the month, x-1 months ago. End point is set to end of current month (example: "3M" is mapped to 20091101000000-20100131235959).
** "x'''Y'''" sets starting point to the beginning of the year, x-1 years ago. End point is set to end of current year (example: "1Y" is mapped to 20100101000000-20101231235959).
* When relative time ranges are preceded by a minus sign ("'''-'''"), end point for capital letter operations (H, D, M, Y) is set to end of previous hour, day, month or year (depending on choosen operation).

====Time Resolution====
Meteoplug supports good details for graphing. If no resolution is specified Meteoplug will compute a suitable resolution for given time frame without grabbing too much data which will overcrowd graphs and will explode loading times. While Meteoplug's computation of resolution is probably fine for many graphing purposes, there are situations where you want control level of detail. When you are planing to make a graph that displays rain fall per day, time resolution should be a day, as you are looking for exactly that data. In situations like this, a explicit resolution definition will be necessary. Meteoplug will not allow to select a resolution that forces a too big amount of data and will automatically switch to be lower resolution for sake of load time.

Defined resolutions are:
* '''min5''' (data assigned to 5 minute buckets)
* '''min10''' (data assigned to 10 minute buckets)
* '''min30''' (data assigned to 30 minute buckets)
* '''hour1''' (data assigned to hourly buckets)
* '''hour6''' (data assigned to 6 hour buckets)
* '''day1''' (data assigned to days)
* '''month1''' (data assigned to months)
* '''year1''' (data assigned to years)
* '''alltime''' (all data assigned to just one bucket, useful to select all time min/max/average values)

====Chart Zoom====
When chart is displayed it starts with an initial zoom setting you can control. Available zoom settings are:
* '''1D''' (last day of selected time range)
* '''10D''' (last 10 days of selected time range)
* '''1M''' (last month of selected time range)
* '''3M''' (last 3 months of selected time range)
* '''1Y''' (last 12 months of selected time range)
* '''YTD''' (last year of selected time range)
* '''MAX''' (complete time range)

===Graph Settings===
A Meteoplug chart can be made out of several graphs. At the moment Meteoplug just supports one graph per chart. Graph settings are always starting with a "g". These settings are valid for graphs:

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory [Applicable]''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| gtitle|| yes<br>[LJTRCGEM] || string (blank chars replaced with "_") || none || Defines title to be displayed in graph's legend. || gtitle=Todays_Outdoor_Temperature
|-
| gtype|| yes<br>[LJTRCGEDM]|| see section "graph types"|| none || Defines overall type of graph. Setting can be overwritten by a sensor definition. Once a charting engine is selected (by graph type name or engine tag) only graph types of that charting engine can be used. || gtype=line (line chart)<br>gtype=bar (chart with bars)
|-
| gfont || no<br>[LJRCG] || string || arial (gnuplot), Tahoma (flash), Verdana (javascript) || Defines font to use for display of numbers and text || gfont=cour (select Courier as font, valid for gpline)
|-
| gfontsize || no<br>[LJRCG] || number || 9 (gpline), 11 (other) || Defines font size to use for display of numbers and text || gfontsize=12 (selects 12pt font)
|-
| ggridcolor || no<br>[LJRCD] || string || black || Defines color of grid lines in graph in RGB style, overrides gridcolor defined on chart level || ggridcolor=#FF0000 (red)
|-
| ggridalpha || no<br>[LJRCD] || 0-100 || 15 (dark gray) || Defines intensity of grid lines in graph, overrides gridalpha defined on chart level || ggridalpha=100 (no transparency)
|-
| glunit || no<br>[LJTRCGED] || string || empty string || Defines what physical unit should be added to the right of numbers of left y-axis. When set to "none", left y-axis is not displayed. Has special meaning as header of first column in table mode and as delimiter string in export mode. Is added to values when displayed as balloon in color map mode. || glunit=°C (unit is defined as degrees Celsius)
|-
| glmin || no<br>[LJRCGD] || number|| none|| Defines minimum value to be displayed on left y-axis. Specifies minimum value to be expected in chart and maps this value (and values below) to color defined in "grmin" when used in color map mode. || glmin=-0.5
|-
| glmax || no<br>[LJRCGD] || number|| none|| Defines maximum value to be displayed on left y-axis. Specifies maximum value to be expected in chart and maps this value (and values above) to color defined in "grmax" when used in color map mode. || glmax=40
|-
| grunit || no<br>[LJTCGED] || string || empty string || Defines what physical unit should be added to the right of numbers of right y-axis. When set to "none", righty-axis is not displayed. Has special meaning (format string for time stamps) in table and export mode. In color map mode it specifies a color (in 6-digit hex RGB) used for map positions where no data is present. Defines format string for x-value in distribution charts. || grunit=hPa (unit is defined as hecto pascal)<br>grunit=#EEEEEE (defines a light grey for missing data in color map mode)
|-
| grmin || no<br>[LJCG] || number|| none|| Defines minimum value to be displayed on right y-axis. Defines color for minimum value (as defined in "glmin") in 6-digit hex RGB. || grmin=-0.5<br>gr=#0022FF (defines a strong blue as color for minimum values in color map mode)
|-
| grmax || no<br>[LJCGD] || number|| none|| Defines maximum value to be displayed on right y-axis. Defines color for minimum value (as defined in "glmin") in 6-digit hex RGB. || grmax=40<br>gr=#FF0000 (defines red as color for maximum values in color map mode)
|-
| gtrim || no<br>[LJTRCGE] || number|| 1 || Specifies if time range should be trimmed to available data in the time range. In distribution mode setting trim will purge all buckets with zero count. || gtrim=1 (trimming is on)
|-
| gbgcolor || no<br>[LJRCD] || string || white || Specifies background color in RGB style, overrides background color defined on chart level || gbgcolor=#0000FF (blue)
|-
| gbgalpha || no<br>[LJRCD] || 0-100 || 100 || Specifies intensity (alpha) of background color in percent, overrides background color intensity defined on chart level || gbgalpha=50 (50% intensity)
|-
| gnightcolor || no<br>[J] || string || values defined for "gbgcolor" || Specifies background color of chart between sunset and sunrise in RGB style. || gnightcolor=#000077 (dark blue)
|-
| gnightalpha || no<br>[J] || 0-100 || 100 (when gnightcolor defined, else 0 || Specifies intensity (alpha) of nightcolor overlay in percent. || gnightalpha=10 (10% intensity)
|-
| gscroller || no<br>[LJ] || number|| 0 || Specifies sensor to be used for display as timeline scroller. || gscroller=1 (takes data from sensor 1 for display of scroller)
|-
| gcolwidth || no<br>[LD] || number 0-100|| depends on graph type || Specifies width of bars and needles in percent. || gcolwidth=50 (bars and spaces between bars are of equal size)
|-
| gheight|| no<br>[LJTRCGDM] || number|| 400 || Specifies height of graph. || gheight=450 (graph is 450 pixel high)
|-
| gwidth|| no<br>[LJTRCGDM] || number|| 600 || Specifies width of graph. In color map mode width will be adapted to graph size. || gwidth=550 (graph is 550 pixel wide)
|-
| gtablestyle|| no<br>[TD] || string|| empty string || Specifies style information for HTML tables. || gtablestyle=style="background-color:#fafafa;" (sets table background color to a light grey)
|-
| gtrheadstyle|| no<br>[TD] || string|| empty string || Specifies style information for HTML table head rows. || gtrheadstyle=style="font-family:Verdana;font-weight:bold;" (sets font for table head line row as Verdana bold)
|-
| gtdheadstyle|| no<br>[TD] || string|| empty string || Specifies style information for HTML table heads cells. || gtdheadstyle=style="font-size:12px;" (sets font size for table head line cells to 12px)
|-
| gtrstyle|| n<br>[TD]o || string|| empty string || Specifies style information for HTML table rows. || gtrstyle=style="font-family:Verdana;font-weight:bold;" (sets font for table rows as Verdana bold)
|-
| gtdstyle|| no<br>[TD] || string|| empty string || Specifies style information for HTML table cells. || gtdstyle=style="font-size:12px;" (sets font size for table cells to 12px)
|-
| ggpformat || no<br>[G] || string|| empty string || Specifies additional format information for "gpline" graphs. Linefeed is represented as "|", "_" stands for blank character and "__" is converted to a single "_". || ggpformat=set_locale_"de__DE" (sets date format to German)
|-
|}
<font size=1>Use with: [L] = line/step/bar graphs; [J] = javascript graphs; [T] = HTML tables; [R] = radar charts; [C] = color maps; [G] = GPline/GPstep/GPbar/GPneedle/GPpoint; [E] = cvs export; [D] = distribution chart; [M] = map</font>

====Graph Types====
Meteoplug supports different types of graphs. Letters in brackets do indicate which charting engine does support this type of graph: [F] = flash, [J] = javascript, [G] = gnuplot

=====Interactive Graphs=====
* '''Line''' [FJG]: Interactive line graph where all data point are connected by a straight line. Gaps in data ore omitted, no lines are drawn to fill gaps.
* '''Minmax''' [FJ]: Interactive bar graph where top and bottom of bar represent a minimum and maximum value.
* '''Step''' [FJG]: Interactive line graph were connection of data points is done by vertical steps. Gaps in data are omitted, no lines are drawn to fill gaps.
* '''Bar''' [FJG]: Interactive bar graph
* '''Needle''' [FJG]: Interactive needle graph, width of needles is controlled by "swidth" setting.
* '''Radar''' [F]: Interactive radar chart
* '''Radar%''' [F]: Interactive radar chart that shows percentual distribution of values
* '''Colormap''' [FJ]: Interactive two dimensional representation, where columns represent days, rows represent hour of day and color represents values of sensor. In color map mode these settings have a special meaning:
** ''glmin'' defines lower boundary of values expected. Values less or equal "glmin" will be displayed with color defined by "grmin".
** ''glmax'' defines upper boundary of values expected. Values greater or equal "glmax" will be displayed with color defined by "grmax".
** ''glmin'' defines lower boundary color as 6-digit hex RGB value.
** ''glmax'' defines upper boundary color as 6-digit hex RGB value. Depending on distance of a value to "glim" and "glmax" a color will be picked from line in HSV color space between colors "glmin" and "glmax".
** grunit defines 6-digit hex RGB value for points in time where no data available.
** ''res'' can be any valid specifier between "min5" and "day1". In most cases "hour1" will be suitable as it decomposes values of a day into a column with 24 stacked colors, each color representing value for that particular hour of the day. According to selected time frame, a number of additional columns is added to the right for following days.
** ''balloon'' must be set to 1 when using JavaScript to make mouse-over balloons appear.

When choosing distribution mode for charts with "xymode" setting, only these charts can be used: Line, Bar, Needle. All other interactive graphs cannot be used in distribution mode.

=====Non-Interactive Graphs=====
* '''GPline''' [G]: Non-interactive line graph which is generated by Gnuplot and delivered as ".png" image.
* '''GPstep''' [G]: Non-interactive line step graph which is generated by Gnuplot and delivered as ".png" image.
* '''GPbar''' [G]: Non-interactive bar graph which is generated by Gnuplot and delivered as ".png" image.
* '''GPneedle''' [G]: Non-interactive needle graph which is generated by Gnuplot and delivered as ".png" image.
* '''GPpoint''' [G]: Non-interactive point graph which is generated by Gnuplot and delivered as ".png" image.

Following fonts can be selected for GP graph types listed above. These fonts are provided by Meteoplug server to render a graph as ".png" picture:
* andalemo
* arial, arialbd, arialbi, ariali, ariblk
* comic, comicbd
* cour, courbd, courbi, couri,
* georgia, georgiab, georgiai, georgiaz,
* impact
* luximb, luximbi, luximr, luximri, luxirb, luxirbi, luxirr, luxirri, luxisb, luxisbi, luxisr, luxisri
* times, timesbd, timesbi, timesi
* trebuc, trebucbd, trebucbi, trebucit
* verdana, verdanab, verdanai, verdanaz
* webdings

Non-interactive graphs cannot be used in distribution mode (xymode setting).

=====HTML Tables=====
* '''Table''': HTML table, where each sensor is represented as a column and time stamped data sets are represented as rows. There are a couple of special settings for tables:
** ''gtablestyle'' defines table style.
** ''gtrheadstyle'' defines style of head line row.
** ''gtdheadstyle'' defines style of head line cells.
** ''gtrstyle'' defines style of rows.
** ''gtdstyle'' defines style of cells.
** ''glunit'' defines text to be displayed on time stamp column.
** ''grunit'' defines time stamp format in a notation used with gnu c function "strftime" ([http://www.kernel.org/doc/man-pages/online/pages/man3/strftime.3.html see manual]). Is used as format string for "x-value" in distribution mode charts.

HTML-Tables can be used in distribution mode (xymode set to a non-null value). As distribution charts are not showing data in respect to a time line, ''grunit'' has a slightly different meaning. ''grunit'' is used as a format string (linke in printf statements in language c). Format string can contain information how to format the floating point number that defines the buckets which show distribution of values in the chart. Example: "%.1fm/s" will show wind speeds for buckets as a floating point number with one decimal digit followed by "m/s". Having set "xstart" to 0.0 and "xinc" to 0.5 the buckets/rows will be named in the first column of the table like "0.0m/s", "0.5m/s", "1.0m/s" and so on.

=====CSV Exports=====
* '''Export''': CSV export, where each sensor is represented as a column and time stamped data sets are represented as rows. There are a couple of special settings for exports:
** ''glunit'' defines text to be used as separator between columns.
** ''grunit'' defines time stamp format in a notation used with gnu c function "strftime" ([http://www.kernel.org/doc/man-pages/online/pages/man3/strftime.3.html see manual]). Is used as format string for "x-value" in distribution chart mode.
** ''sname'' defines value to be taken for export if no value found for that specific sensor in database.
** ''sunit'' define additional characters to follow current value. This can be used to fill in some static text columns following actual sensor value. It is a useful feature to give columns default values where no data can be delivered from Meteoplug.

CSV exports can be used in distribution mode (xymode set to a non-null value). As distribution charts are not showing data in respect to a time line, ''grunit'' has a slightly different meaning. ''grunit'' is used as a format string (linke in printf statements in language c). Format string can contain information how to format the floating point number that defines the buckets which show distribution of values in the chart. Example: "%.1fm/s" will show wind speeds for buckets as a floating point number with one decimal digit followed by "m/s". Having set "xstart" to 0.0 and "xinc" to 0.5 the buckets/rows will be named in the first column of the csv export like "0.0m/s", "0.5m/s", "1.0m/s" and so on.

=====Maps=====
* '''Map''': defines a Google map with weather stations of your group as markers. On the right is an info window that displays weather data of weather station touched by the cursor on the map. Registered stations do also provide an interactive weather graph when clicked.
** ''zoom'' defines zoom factor of the map. default for start is "4".
** ''ssel'' specifies a sensor value in form of a variable enclosed in square brackets. See [[#Numeric Variables]] and [[#Text Variables]] for details.

===Sensor Settings===
A Meteoplug graph can display data for a couple of sensors. As most sensors do present more than one type of data you have to define the sensor and what type of data to use from a sensor. All sensor definitions as preceded with a "s". To identify which settings are valid for which sensor, sensors are enumerated. Enumeration of sensors must start at 0 and must not have a gap in enumeration. Each sensor setting ends with an number that defines for which sensor these settings should apply. This number is represented by a "#" in the list of valid for sensor settings below:

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory<br>[applicable]''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| sid# || yes<br>[LJTRCGEDM] || see section "sensor IDs" || none || Defines the sensor to take data from. || sid0=wind0 (wind sensor)<br>sid1=th* (primary outdoor temp/hum sensor)
|-
| ssel# || yes, if not a "minmax" graph or "daycount" graph<br>[LJTRCGEDM] || see section "sensor IDs" || none || Defines the sensor's value to be used for graphing. Has special meaning when doing maps, when this holds a text variable.|| ssel0=gustmax (maximum gust speed of wind sensor)<br>ssel0=[actual_min5_th0_temp] (actual temp for display on map)
|-
| sclient# || no<br>[LJTRCGEDM] || name of the client that provides data || none || When using Meteoplug groups, you can use data from various clients of that group in one chart. Client parameter specifies what client to take the data from. || sclient0=citygroup-hamburg
|-
| sselmin# || yes, in case of a minmax graph<br>[LJG] || see section "sensor IDs" || none || Defines the sensor's value to be used for graphing as minimum value.|| sselmin0=tempmin (minimum temperature of a temp sensor)
|-
| sselmax# || yes, if a minmax graph<br>[LJG] || see section "sensor IDs" || none || Defines the sensor's value to be used for graphing as maximum value. || sselmax0=tempmax (maximum temperature of a temp sensor)
|-
| sdaycount# || yes, if a "daycount" graph<br>[LJ] || SQL conditional clauses mapped to predefined variable "day", see section "sensor IDs" for possible qualifiers || none || Defines the sensor's value to be used for graphing as daycount. This setting is defined for time resolution "month1" only. || sdaycount0=day.tempmax>=0.0&&day.tempmax<5.0 (counts number of days that meet condition: tempmax >= 0.0 and tempmax <5.0)
|-
| sname# || yes<br>[LJTRCGEDM] || string || none || Defines the name of the sensor as displayed in the graph. Has special meaning in export mode as definition of value that should be written when no value available in database. || sname0=Outdoor_Temperature
|-
| stype# || no<br>[LJGD] || see section "graph types"|| as defined by "gtype"|| Defines type of graph for this particular sensor. || stype0=line
|-
| swidth# || no<br>[LJRGD] || number|| 0|| Defines line thickness for graph types: line, step, needle || swidth0=4 (line is 4 pixels wide)
|-
| syaxis# || no<br>[LJRG] || left, right|| left|| Defines which y-axis to by used for current sensor. || syaxis0=r (right y-axis to be used)
|-
| scolor# || no<br>[LJRGD] || hex number|| taken from internal table|| Defines color of sensor in the graph. || scolor0=AADDFF (sensor is displayed in a light blue)
|-
| scursorcolor# || no<br>[LJR] || hex number|| same color as used for display of sensor data || Defines color of interactive cursor in the graph. || scursorcolor0=000000 (cursor is displayed in black)
|-
| sunit# || no<br>[TEDM] || string || empty string || Defines unit text to be displayed as unit for sensor data in table columns. Defines Text to be added to current column in export mode. This allows to add static output on columns where Meteoplug can't deliver useful data. || sunit0=°C (numbers are displayed as temperatures)
|-
| slabel# || no<br>[J] || string || no label used || Defines label to be displayed on top of each data item in the chart. Label can contain "[[value]]" for current data value or in min/max charts "[[low]]" and "[[high]]" for min resp. max values. || slabel0=°C (each data item of this sensor has the value added with "°C" on its top)
|-
| ssmooth# || no<br>[LJG] || number || 0 || Defines if lines should be smoothed. || ssmooth0=1 (smoothing enabled)<br>ssmooth0=2 (defines bezier smoothing, available with graph type "gpline" only)
|-
| sstack# || no<br>[LJ] || number || none || Defines a sensor this sensor's data should be stacked on when displayed. Just works for "line" graphs without "smooth" option. || sstack1=0 (data for sensor 1 is stacked on data for sensor 0)
|-
| sline# || no<br>[LJRGD] || number 0-100 || 100 || Defines color intensity of line to be drawn. || sline0=100 (color of line for data of sensor 0 has full intensity)
|-
| sfill# || no<br>[LJRGD] || number 0-100 || 100 || Defines color intensity of area below line. || sfill0=50 (color of area for data of sensor 0 has 50% intensity)
|-
| sconnect# || no<br>[LJRGD] || number 0,1 || 0 || If set, missing data does not result in holes in the graph. Neighbouring points are always connected. || sconnect0=1 (graph for sensor 0 shows a perfectly connected line, even when some data is missing)
|-
| scursoralpha# || no<br>[LJR] || number 0-100 || 100 || Defines color intensity of cursor. || scursoralpha0=0 (cursor is invisible)
|-
| slowbound# || no<br>[LJG] || number || undefined || Defines a lower bound. Values below that are mapped to 0.0, values above or equal become 1.0. Offset and factor are applied after this operation. || slowbound0=100.0 (maps values below 100.0 to 0.0 and values of 100.0 and above to 1.0)
|-
| supbound# || no<br>[LJG] || number || undefined || Defines an upper bound. Values below that are mapped to 1.0, values above or equal become 0.0. Offset and factor are applied after this operation. || supbound0=200.0 (maps values below 200.0 to 1.0 and values of 200.0 and above to 0.0)
|-
| slegend# || no<br>[LJG] || number 0,1 || 1 || Defines if a sensor's values do appear in the legend: 0=no, 1=yes || slegend0=0 (no data in legend for sensor 0)
|-
| soffset# || no<br>[LJTRCGED] || number || 0.0 || Defines offset to be applied to sensor data. || soffset0=32 (adds 32 to data)
|-
| sfactor# || no<br>[LJTRCGED] || number || 1.0 || Defines factor to be applied to sensor data. || sfactor0=1.8 (multiplies with 1.8)
|-
| scumul# || no<br>[LJTRCGED] || 0 or 1 || 0 || Defines if data should be used as is or being added up to display cumulative development. This can be used to generate stairway charts for rainfall over a time period. || scumul0=1 (use cumulative display for sensor 0)
|-
| sprec# || no<br>[LJTRCGED] || number || depends on type of data || Defines number of decimals that should be used when printing values in graphs. When applied to timestamps it defines number of characters (from left when positive number, from right when negative number) to be displayed. || sprec0=1 (display data with 1 decimal)
|-
| sprec# || no<br>[LJTRCGED] || number || depends on type of data || Defines number of decimals that should be used when printing values in graphs. When applied to timestamps it defines number of characters (from left when positive number, from right when negative number) to be displayed. || sprec0=1 (display data with 1 decimal)
|-
| sminmarker# || no<br>[J] || string || none || Determines if lowest sensor value of selected time range should be marked with a star in the graph. Specified text is used as prefix for the value displayed inside the balloon connected to the star || sminmarker0=MIN (inserts a star on minimum value in the graph and sets balloon text to "MIN: 12.5°C", when lowest value was "12.5°C")
|-
| smaxmarker# || no<br>[J] || string || none || Determines if highest sensor value of selected time range should be marked with a star in the graph. Specified text is used as prefix for the value displayed inside the balloon connected to the star || smaxmarker0=MAX (inserts a star on maximum value in the graph and sets balloon text to "MAX: 32.5°C", when highest value was "32.5°C")
|-
| smarker# || no<br>[J] || string || star || Determines marker type to be used for this sensor. Defined types are "square", "circle". "diamond" and "star" || smarker0=circle (marks min/max vaules with a ircle in the chart)
|-
| smarkeralpha# || no<br>[J] || number 0-100 || 100 || Determines intensity used for display of marker symbol (in oercent) || smarkeralpha0=50 (marker displayed with 50% intensity)
|}
<font size=1>Use with: [L] = line/step/bar graphs; [J] = javascript line/step/bar graphs; [T] = HTML tables; [R] = radar charts; [C] = color maps; [G] = GPline/GPstep/GPbar/GPneedle/GPpoint; [E] = csv export; [D] = distribution chart</font>

====Sensor IDs and Values====
Meteoplug supports different types of sensors. When you configure sensors on "Sensors" page you define IDs for these sensors. The same IDs are used as "sid" in graphing. Each of the sensor types present a different set of properties as listed below. Data for sensors of type "text" and "number" are not taken from the database but computed on request. While "number" sensors might be useful for graphing, "text" are limited to be used for HTML-tables, csv exports and template replacements.
When you use a fixed number like "th0" exactly that sensor is used. When you make use of wild-card notation "th*" the "th" sensor that has been specified on weather network page as your outdoor temp sensor will be used. This allows to write chart definitions that make use of your primary sensors, regardless which number you have given them on your "sensors" page. If no definition can be found on "weather network" page, the sensor with ID zero will be used as a default.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Sensor Type''' !! '''Sensor IDs''' !! '''Properties''' !! '''Comment'''
|-
| Temp|| t0, t1,<br> ...,<br> t39 || temp, tempmin, tempmax, tempmintime, tempmaxtime || sensor reports temperature (°C) only
|-
| Temp/Hygro|| th*, th0, th1,<br> ...,<br>th39 || temp, tempmin, tempmax, hum, hummin, hummax, dew, dewmin, dewmax, humi, humimin, humimax, heat, heatmin, heatmax, tempmintime, tempmaxtime, hummintime, hummaxtine, dewmintime, dewmaxtime || sensor reports temperature (°C)and humidity (%)
|-
| Temp/Hygro/Baro|| thb*, thb0, thb1,<br> ...,<br>thb39 || temp, tempmin, tempmax, hum, hummin, hummax, dew, dewmin, dewmax, humi, humimin, humimax, heat, heatmin, heatmax, press, pressmin, pressmax, seapress, seapressmin, seapressmax, tempmintime, tempmaxtime, hummintime, hummaxtine, dewmintime, dewmaxtime, pressmintime, pressmaxtime, forecast, forecasttext, forecasticon || sensor reports temperature (°C), humidity (%) and air pressure (hPa), forecast information
|-
| Wind|| wind*, wind0, wind1,<br> ...,<br>wind9|| gust, gustmin, gustmax, wind, windmax, windmin, chill, chillmin, chillmax, maindir, highdir, gustmaxtime, windmaxtime, chillmintime, chillmaxtime<BR>maindirtext, highdirtext (for chart types "table" and "template" only) || sensor reports wind (m/s) and windchill data (°C)
|-
| Rain|| rain*, rain0, rain1,<br> ...,<br>rain9|| rate, ratemin, ratemax, total, days, ratemaxtime || sensor reports rain (mm)
|-
| UV|| uv*, uv0, uv1,<br> ...,<br>uv9|| uvi, uvimin, uvimax, uvimaxtime || sensor reports UV data (uvi)
|-
| Solar|| sol*, sol0, sol1,<br> ...,<br>sol9|| rad, radmin, radmax, radmaxtime || sensor reports solar data (W/qm)
|-
| Data|| data0, data1,<br> ...,<br>data39 || val, valmin, valmax, sum, summin, suminc, rise, fall, valmintime, valmaxtime || sensor reports numerical data, ''sum'' is sum of data, ''suminc'' is sum of increments, ''summin'' is sum of increments per minute, ''rise'' is number of events where data changes from falling to rise, ''fall'' is number of events where data changes from rising to fall.
|-
| text || misc || longitude, latitude || report longitude or latitude as a decimal number. Does ignore given time stamps and time resolutions.
|-
| text || misc || localtime, utctime || report recent time in format "YYYY-MM-DD hh:mm:ss". Does ignore given time stamps and time resolutions.
|-
| text || misc || uploadlocaltime, uploadutctime|| report time of last data upload in format "YYYY-MM-DD hh:mm:ss". Does ignore given time stamps and time resolutions.
|-
| text || misc || timestamp || reports time stamp used for request in format "YYYY-MM-DD hh:mm". This can be used to find out an absolute point in time that corrsponds to a given relative time description.
|-
| number || misc || lunarphasepercentage || reports of visibility of moon as percentage (100% = full moon, 0% = new moon).
|-
| number || misc || lunarphasesegment || reports a number of 0 to 7 which represents lunar phase (0 = new moon, 4 = full moon).
|-
| number || misc || lunaragedays || reports a number of days since last new moon.
|-
| text || misc || lunarphasetext || reports a test string that represents a lunarpahase. 8 Lunar phases are defined. Strings can be adapted to specific needs by "phasetextlist" definition.
|-
| text || misc || lunarphaseicon || reports a HTML image tag that links to an image to be used for representation of lunarpahases. URLs can be adapted to specific needs by "phaseiconlist" definition.
|-
| number || misc || daylengthstandardhours, daylengthcivilhours, daylengthnauticalhours || reports number of hours a day has. hours come with decimals. Computation is available in standard, civil or nautical mode.
|-
| text || misc || daylengthstandardtime, daylengthciviltime, daylengthnauticaltime || reports number of hours and minutes a day has in "hh:mm" notation. Computation is available in standard, civil or nautical mode.
|-
| text || misc || sunrisestandardutctime, sunsetstandardutctime, sunrisestandardlocaltime, sunsetstandardlocaltime, sunriseciviltwilightutctime, sunsetciviltwilightutctime, sunriseciviltwilightlocaltime, sunsetciviltwilightlocaltime, sunrisenauticaltwilightutctime, sunsetnauticaltwilightutctime, sunrisenauticaltwilightlocaltime, sunsetnauticaltwilightlocaltime || reports time of sunrise and sunset in "hh:mm" notation. Computation is available in standard, civil or nautical mode and in UTC and local time.
|-
| text || misc || moonriseutctime, moonsetutctime, moonriselocaltime, moonsetlocaltime || reports time of moon rise and moon set in "hh:mm" notation. Computation is available in UTC and local time.
|-
| text || misc || mac || reports MAC of the sending client.
|-
|}

===Template Settings===
Beside generation of graphs and tables it might also be useful to allow for handling of templates. Template mechanism works like this:
* Meteoplug loads a textfile somewhere located on the Internet (will mostly be HTML content) or inside the chart definition following the "template=inline" statement
* Meteoplug scans the file or data for existence of specific Meteoplug weather variables.
* Meteoplug replaces these variables by corresponding weather data
* Meteoplug returns the file or data (filled with data) to the requester

Template handling is realized in Meteoplug by a chart definition that makes use of the following name-value pairs.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| template || yes || URL in complete syntax including "http://" or "inline" || none || URL of template to be used or "inline" tag, which indicates that template data follows after template statement || template=<nowiki>http://www.meteoplug.com/xyz.html</nowiki>
|-
| content || no || http content type description || text/html || defines what type of content is delivered || content=text/plain (content=raw will supress content header information to be sent out)
|-
| picture || no || type of picture || no picture template, html template is default || defines if URL given as template is a picture definition to be handled by ImageMagick's convert program and defines type of picture || picture=png
|-
| dirlist<BR>phasetextlist<BR>phaseiconlist || no || lists as defined in [[#Chart Settings]] || see [[#Chart Settings]] || define text values or URLs to be taken instead of default settings || dirlist=N,NNO,NO,ONO,O,OSO,SO,SSW, S,SSW,SW,WSW,W,WNW,W,NNW
|-
| debug || no || 0 = normal operation<BR>1 = show replacement of variables and corresponding errors || 0 || allows for debugging of variable replacement || debug=1 (enables debug mode)
|-
|}

Variables that Meteoplug replaces in templates are starting with "[" and end with "]". There are two types of variables, text and numbers which are handled slightly different. Any "[...]" enclosed strings that do not syntactically match a Meteoplug variable definition will not be touched.

====Special Variables====
Beside the regular weather data values of numerical or textual type there are a couple of special variables returning usefull information:
* '''drawtoken_<chartname>''' returns the encoded draw token for the current user and the chart defined as <chartname>.
* '''engine''' returns the display engine currently used by the chart (can be "flash", "javascript" or "gnuplot").

====Numeric Variables====
Numeric variables are composed of the following fields, separated by an underscore "_":
* '''time stamp''': This can be any point in time given in "YYYYMMDDhhmmss" notation. When the last recorded data is meant, the string "actual" has to be used instead of a time stamp. Instead of absolute time stamps you can also use relative timestamps as explained in paragraph [[#Time Ranges]]. Please notice, that in this context relative timestamps are not interpreted as ranges up to the current date/time, but as a range where the relative timestamp gives the starting point. Endpoint is determined by start point plus the resolution specification. Assume your time is 13:17, then relative time stamp "3H_hour1_..." will select timeframe "11:00 - 11:59" as "3H" points to 3 hours in the past ("3H" is taking actual hour as an already started hour additional into consideration, "-3H" will select "10:00 - 10:59" omitting the actual hour). Following that rule, "3H_min10_..." will select "11:00 - 11:09" as time frame and "-1D_day1_.." will select yesterday's data. As a side effect not all relative timeframe definitions make sense here. Lower letter definitions can't be used and a given resolution has to be smaller or equal than the startpoint definition, i.e. "3D_month1_..." is not making sense, as the "month1" resolution is not alligned to the beginning of a day, selected by "3D". Using inappropriate timeframe defintions will lead to empty results.
* '''resolution''': Meteoplug uses raw logged data to generate a hierarchy of various time buckets. Below you find time buckets available in Meteoplug. These are the same resolution settings as can be used for graphing. "Time stamp" and "resolution" strongly interact. As not all combination do make sense, it is important to understand how it works together. Assume that you are looking for some daily data (like daily max temperature or rainfall) for x-mas 2009, then "time stamp" will be "20091225000000" and "resolution" will be "day1". To get data about actual month "time stamp" will be "actual" and resolution will be "month1".
** min5 (5 minutes time frame)
** min10 (10 minutes time frame)
** min15 (15 minutes time frame)
** min30 (30 minutes time frame)
** hour1 (hourly time frame)
** hour6 (6 hour time frame)
** day1 (daily time frame)
** month1 (monthly time frame)
** year1 (yearly time frame)
** alltime (time frame covering all ever logged data)
* '''sensor id''': This determines the sensor to take data from. It is in the usual format as used in graphing specification, like "th0", "wind0", etc. You can also make use of default primary sensor names like "th*", "wind*", etc. When your station is part of a Meteoplug group, you can reference data from any client in the group by a "@<clientname>" suffix. Example: [actual_min5_th0@citygroup-hamburg_temp_1]
* '''selector''': Which selectors are available depends on selected type of sensor. List of defined selectors per sensor is lined out in [[#Sensor IDs and Values]]. If you are selecting a text variable or a numeric variable is determined by the selector you are using. When the selector is named "time" or "text" at the end it is a time stamp or other string and therefore a text variable. All other variables are of numeric type. There is one additional selector named "ts" (means time stamp) that reports time stamp of data, which also is regarded as a text variable.
* '''precision''': This defines how many decimal digits should be displayed. Decimals are just cut off, no rounding rules are applied. Default is one digit.
* '''factor''': Defines a factor to be applied to the value. Default factor is 1.0.
* '''offset''': Defines an offset to be applied to values. Default offset is 0.0.

An example for a numeric variable constructed according rules above is [actual_day1_th0_tempmax_1_1.8_32], which will be replaced by max temperature of current day in degree Fahrenheit (Celsius value * 1.8 + 32) with one decimal digit precision.

====Text Variables====
Fields used for definition of text variable are mainly the same as with numerical variables. Fields "time stamp", "resolution", "sensor id", "selector" are exactly the same. "selector" just needs to be "ts" or something ending with "time" to select a text variable. Fields "precision", "factor" and "offset" are not defined with text variables, but new fields "index" and "length" are added instead.
* '''index''': Index defines a position in the text where to start with reading. Default is 0 which is equivalent to start of text.
* '''length''': This defines how many character to take from the text. Default is to take the complete string.

An example for a text variable is [actual_day1_th0_tempmaxtime_11_5] which cuts off the "hh:mm" portion of the time stamp of highest temperature reading of recent day. Time stamps do have format "YYYY-MM-DD hh:mm:ss" when reading them from Meteoplug's database.

====Additional Features====
A ":" followed by a string can be added at the end of every variable. The string is used as a default replacement, when no value can be derived from Meteoplug's database for a given variable.

Example: [20100101000000_day1_th0_tempmax_1_1.8_32:no data] does result in "no data" when there is no maximum temperature available for new year's day 2010 in Meteoplug's database. Default setting for missing variable data is "--".

A "#" followed by a number indicates the maximum age of sensor data allowed to regard this sensor data as still being valid. This is very usefull in combination with "actual" timeframes.

Example: [actual_min5_uv*_uvi_1:outdated#3600] reports the average uv index of last 5 minute bucket available, as long as it is not older than 3600 seconds, otherwise "outdated" is returned.

===Maps===
When using Meteoplug's map feature some additional parameters can be used.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| outdate || no|| seconds since last data from stations || 15 days (15*86400 seconds) || This defines maximum age a connect from the Meteoplug client is allowed to have in order to be still displayed on the map || outdate=2592000 (defines a clip level of 30 days)
|-
| latitude || no || decimal latitude || your stations latitude || defines the center of the map || latitude=59.234
|-
| longitude || no || decimal longitude || your stations longitude || defines the center of the map || longitude=10.456
|-
| mapchart || no || name of a defined map (should be defined for all users of the group) || "_mapaio" || you can direct the weather data graph when clicking onto a marker in the map to an alternative chart definition. Might only be useful in dedicated groups, where your own chart definitions are valid for the whole group per default. || mapchart=mychart (defines mychart to be used on maps)
|}

===URL Parameters===
To allow a more flexible use of defined charts, some of the chart parameters can be provided when calling a chart definition. Usually you receive a chart you defined by calling "<nowiki>http://www.meteoplug.com/cgi-gin/meteochart.cgi?drawtoken=...</nowiki>". Meteoplug derives user and name of the requested chart from the encrypted draw token and returns the chart. You can also a these additional URL parameters behind the drawtoken.
{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Applicable''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| timeframe || [INCH] || timefame definition as described [[#Time Ranges]] || as given in the chart definition || selects th time frame the cahrt definition gets applied to. || timeframe=1M (current month)
|-
| resolution || [INCH] || time resolution as defineded [[#Time Resolution]] || as given in the chart definition || defines granularity of data used for the chart. Only distinct values are allow. || resolution=10min (chart shows data in 10 minute buckets)
|-
| engine|| [IND] || one of "javascript", "flash, "gnuplot" || flash || meteoplug provides flash and javascript engines for drawing interactive charts and live data. As long as the cart definition use generic types (like line, bar, needle, step, ...) the engine setting does determine which engine to use. If engine specific types (like gpline, ...) are used, calling the chart with a different engime definition will trhow an error. || engine=javascript (use javascript variants of interactive charts)
|-
| latitude || [M] || decimal latitude || your stations latitude || defines the center of the map || latitude=59.234
|-
| longitude || [M] || decimal longitude || your stations longitude || defines the center of the map || longitude=10.456
|-
| all || [M] || 0 or 1 || 0 || defines if map of a group does include public stations (all=1) or does show group only stations (all=0) || all=1
|-
| latitudemin || [M] || decimal latitude || minimal latitude of stations to be shown on map || can be used to restrict geografical range of stations to be shown || latitudemin=58.0
|-
| latitudemax || [M] || decimal latitude || maximal latitude of stations to be shown on map || can be used to restrict geografical range of stations to be shown || latitudemin=60.0
|-
| longitudemin || [M] || decimal longitude || minimal longitude of stations to be shown on map || can be used to restrict geografical range of stations to be shown || longitudemin=8.0
|-
| longitudemax || [M] || decimal longitude || maximal longitude of stations to be shown on map || can be used to restrict geografical range of stations to be shown || longitudemax=10.0
|-
| client || [INCHMD] || a meteoplug client name || client as specified in draw token || allows selecting a different client of the same meteoplug group. This is only applicable for clients of the same group || client=beach1
|-
| zoom || [IM] || number between 1 and 15 on maps or fraction of time frame to be initially displayed on interactive charts || 4 (maps), MAX (interactive charts) || defines how close to zoom in on maps and what fraction of the time frame to display on interactive charts || zoom=1D (start displaying actual day on interactive chart)
|}
<font size=1>Use with: [I] = any interactive chart; [N] = non-interactive chart; [C] = CSV exports; [H] = HTML tables; [M] = Maps; [D] = Live display</font>

Values for "latitude", "longitude" (in degrees with decimals) and "zoom" (as integer from 1 to 15) can also be given as URL parameters when calling the chart generator.

==Display Language==
Display language used in Meteoplug is derived from a subset of fusionwidget options. It can be used very similar as if you would define widgets directly in funsionwidgets. This is especially true for the options that control the look and feel of the meters and gauges. Secification of values to be selected for display is similar to how Meteoplug does handle graphs. So it might be a good idea, to get familar with Meteoplug graphing first, before stepping into details with displays.

Display commands are represented as name-value pairs separated by "=". No spaces are allowed between name, "=" and value. Name-value pairs are separated by white space characters (blanks and/or new lines). As a result you can place each name value pair into a new line or you can define multiple name-value pairs in one line separated by white spaces.

When value should include a space character (might be useful for sensor names), you have to use underscore "_" instead of space. Underscores will be converted back to spaces when being displayed. When you need a underscore "_" not to be converted into space, type two underscores "__", which will be converted to one underscore "_". If you need a line feed character in the string, use vertical bar character "|" instead.

You can add comments to a display definition. When Meteoplug hits a "#" when it expects a new name value pair, then rest of current line will be skipped and not evaluated. This allows you to type any text you like after comment character "#". As you can see, the coming up examples make heavy use of commenting.

When you specify numbers the decimal separator is "." regardless what language you might have selected.

There is one important difference compared to graph definitions. When you define a widget, you specify the type of widget (i.e. Thermometer) in the usual name-value pair mimic. The lines following that special name-vaue pair are not handled as name-value pairs anymore but the entire followon text is taken as is and interpreted as XML data for description of the widget options. This XML is directly handed over to the corresponding fusionwidget flash widget. Meteoplug does no further processing on that. The end of XML data in the display definition is marked by an empty line. After that Meteoplug is in name-values piar mode again and operation continues in normal parsing mode until next widget name-value pair. Breaking the name-value pair logic by that might be seen as not very elegant, but it allows easy adaption of examples from fusionwidgets repository, which might be regarded as a major advantage. What options the choose for in context of each of the widgets is defined [http://www.fusioncharts.com/widgets/docs/ here].

As with graph definitions, the definition of displays is done on three levels
* on '''display settings''' are valid for all widgets in the display.
* on '''widget settings''' define characteristics of a single widget.
* on '''sensor settings''' give paramters for use of sensors for a specific widget.

===Display Settings===
A display definition should start with settings that are valid for all widgets in the display and all sensors used in the widgets. Meteoplug provides these name-value pairs to define display settings

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory [Applicable]''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| restrictip || no [TCAHS] || WAN IP of requesting computer || none || restricts access to the chart to a certain requesting IP. When requesting IP does not match an error is displayed. || restrictip=81.123.23.77 (restricts access to given IP)
|-
| bgcolor || no<br>[TCAHS] || string || white || Specifies background color in RGB style || bgcolor=#0000FF (blue)
|-
| title || no<br>[TCAHS] || string (blank chars replaced with "_") || "Meteoplug_Chart" || Defines HTML title of the chart || title=temp_of_today
|-
| height || no<br>[TCAHS] || number || 400 || Defines height of display in pixels || height=200
|-
| width || no<br>[TCAHS] || number || 600 || Defines width of display in pixels || width=400
|}
<font size=1>Letter in brackets indicate applicability: [T] = thermometer; [C] = cylinder; [A] = angular gauge; [H] = horizontal gauge; [S] = status pad</font>

===Widget Settings===
Widget settings have a meaning to an overall display comparable to graph settings for a chart. That means, each single display element (thermometer, gauge, etc.) is defined by a stack of widget definitions. These definitions can be used with widgets, each of them needs the widget number as a suffix. A missing widget number suffix is interpreted as suffix "0". As a lot of the definitions are borrowed from graph definitions, we kept the prefix "g" for all widget commands.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory [Applicable]''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| gtitle || no<br>[TCAHS] || string (blank chars replaced with "_") || none || reserved for future use || gtitle=Outdoor_Temp
|-
| gheight || no<br>[TCAHS] || number || 400 || specifies height of widget || gheight=450 (widget is 450 pixel high)
|-
| gwidth || no<br>[TCAHS] || number || 600 || specifies width of widget || gwidth=550 (widget is 550 pixel wide)
|-
| gtimeout || no<br>[TCAHS] || number || 1800 || specifies update age in seconds to determine a widget being outdated and not showing data anymore || gtimeout=900 (timeout after 15 mins)
|-
| gcss || no<br>[TCAHS] || string (blank chars replaced with "_") || none || gives css information used for widget placement and style || gcss=position:absolute;_top:0;_left:0 (position widget in upper left corner)
|-
| gwidget || yes<br>[TCAHS] || Thermometer, Cylinder, AngularGauge, HLinearGauge, Status || none || defines which widget to use, followon lines define widget options in XML style as described by [http://www.fusioncharts.com/widgets/docs/ fusionwidget documentation] || gwidget=AngularGauge (select angular gauge type from fusionwidgets selection)
|}
<font size=1>Letter in brackets indicate applicability: [T] = thermometer; [C] = cylinder; [A] = angular gauge; [H] = horizontal gauge; [S] = status pad</font>

The example below illustrates how the different kinds of widgets can be used to setup a live data dashboard.

[[file:live-board.png]]

====Thermometer Widget====
This widget can handle just one value to display. Example above uses this widget for display of temperature, chill and dew point. Description of options to control look of the widget can be directly taken from corresponding fusionwidget documentation named "Thermometer Gauge" ([http://www.fusioncharts.com/widgets/docs/ link])

====Cylinder Widget====
Like the thermometer widget this widget also can handle just one value but brings a different look and can be displayed in a pseudo 3D style from various angles of view. Example above does use this widget type for display of daily rainfall. Description of options to control look of the widget can be directly taken from corresponding fusionwidget documentation named "Cylinder Gauge" ([http://www.fusioncharts.com/widgets/docs/ link])

====Angular Gauge====
This widget is usefull to display values in a tachometer like style. Example above makes use of this widget for wind direction and barometric pressure. The widget supports multiple dials and various design and annotation options. Description of options to control look of the widget can be directly taken from corresponding fusionwidget documentation named "Angular Gauge" ([http://www.fusioncharts.com/widgets/docs/ link])

====Linear Gauge====
This widget is similar to the angular gauge - but without curves. Example above uses this for wind speed, humidity, solar radiation and UV index. It also supports display of multiple values and various design and annotation options. Description of options to control look of the widget can be directly taken from corresponding fusionwidget documentation named "Linear Gauge" ([http://www.fusioncharts.com/widgets/docs/ link])

====Status Pad====
This is not something from fusionwidgets, but a very simple widget that can bring additional text on the display. It is particular useful to show some info like date and time of last display update. Example above does use this widget in the upper left corner. These patterns can be used as text variables:
* '''%Y''' represents the year, in 4 digit representation.
* '''%M''' represents the month (01-12).
* '''%D''' represents day of month (01-31).
* '''%h''' represents hours (00-23).
* '''%m''' represents minutes (00-59).
* '''%s''' represents seconds (00-59).
* '''%I''' represents the computed update interval. This can be less frequent than the regular 10 second interval when multiple Users are polling data for a specific station. Update rate adapts to intensity of usage to keep overall server performance in line. Example above specifies output message with string "last update %h:%m:%s (%I secs)".

===Sensor Settings===
Depending on the choosen widget, a Meteoplug widget can display data for a couple of sensors. As most sensors do present more than one type of data you have to define the sensor and what type of data to use from a sensor. All sensor definitions as preceded with a "s". To identify which settings are valid for which sensor, sensors are enumerated. Enumeration of sensors must start at 0 and must not have a gap in enumeration. Each sensor setting ends with an number that defines for which sensor these settings should apply. This number is represented by a "#" in the list of valid for sensor settings below:

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Name''' !! '''Mandatory''' !! '''Value''' !! '''Default''' !! '''Explanation''' !! '''Example'''
|-
| sid# || yes<br>[TCAH] || see section "sensor IDs" || none || defines the sensor to take data from || sid0=wind0 (wind sensor)<br>sid1=th* (primary outdoor temp/hum sensor)
|-
| ssel# || yes<br>[TCAH] || see section "sensor IDs" || none || defines the sensor's value to be used for widget display || ssel0=gust (gust speed of wind sensor)
|-
| sclient# || no<br>[TCAH] || name of the client that provides data || none || When using Meteoplug groups, you can use data from various clients of that group in one widget. Client parameter specifies what client to take the data from. || sclient0=citygroup-hamburg
|-
| soffset# || no<br>[TCAH] || number || 0.0 || Defines offset to be applied to sensor data. || soffset0=32 (adds 32 to data)
|-
| sfactor# || no<br>[TCAH] || number || 1.0 || Defines factor to be applied to sensor data. || sfactor0=1.8 (multiplies with 1.8)
|-
| sprec# || no<br>[TCAH] || number || depends on type of data || Defines number of decimals that should be used when printing values in widgets. || sprec0=1 (display data with 1 decimal)
|}
<font size=1>Letter in brackets indicate applicability: [T] = thermometer; [C] = cylinder; [A] = angular gauge; [H] = horizontal gauge; [S] = status pad</font>

====Sensor IDs and Values====
Meteoplug supports different types of sensors. When you configure sensors on "Sensors" page you define IDs for these sensors. The same IDs are used as "sid" for display in widgets. Each of the sensor types present a different set of properties as listed below.
When you use a fixed number like "th0" exactly that sensor is used. When you make use of wild-card notation "th*" the "th" sensor that has been specified on weather network page as your outdoor temp sensor will be used. This allows to write chart definitions that make use of your primary sensors, regardless which number you have given them on your "sensors" page. If no definition can be found on "weather network" page, the sensor with ID zero will be used as a default.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Sensor Type''' !! '''Sensor IDs''' !! '''Properties''' !! '''Comment'''
|-
| Temp|| t0, t1,<br> ...,<br> t39 || temp, tempmin, tempmax || sensor reports temperature (°C) and daily min/max values only
|-
| Temp/Hygro|| th*, th0, th1,<br> ...,<br>th39 || temp, tempmin, tempmax, hum, hummin, hummax, dew, dewmin, dewmax || sensor reports temperature (°C) and humidity (%) and dewpoint (°C) and daily min/max values for these
|-
| Temp/Hygro/Baro|| thb*, thb0, thb1,<br> ...,<br>thb39 || temp, tempmin, tempmax, hum, hummin, hummax, dew, dewmin, dewmax, seapress, seapressmin, seapressmax || sensor reports temperature, dew point (°C), humidity (%) and air pressure (in hPa) with daily min and max)
|-
| Wind|| wind*, wind0, wind1,<br> ...,<br>wind9|| dir, wind, gust, gust10min, gustday, chill, chillmin, chillmax || sensor reports wind dir, average wind sped (wind), current wind (gust), highest gust last 10 minutes (gust10min), highest gust of day (gustday) and wind chill (°C) inclusing min/max, all speeds in m/s
|-
| Rain|| rain*, rain0, rain1,<br> ...,<br>rain9|| rate, total, day, month, year || sensor reports rain rate (mm/h), total counter value (total), sum of day, month, year in mm.
|-
| UV|| uv*, uv0, uv1,<br> ...,<br>uv9|| uvi, uvimax || sensor reports current UV data (uvi) and maximum of day (uvimax)
|-
| Solar|| sol*, sol0, sol1,<br> ...,<br>sol9|| rad, radmax || sensor reports current solar data (rad) in W/qm and maximum of day (radmax)
|-
| Data|| data0, data1,<br> ...,<br>data39 || val, valmin, valmax || sensor reports numerical data inclunding min/max of day
|}

==Examples==
You will find examples for all graph and display types in the [[gallery]] of this wiki. You can see the graphs and you can inspect definition that created the graph or display. Definitions are commented, which should allow to get a better understanding how graphing works.

Weather Networks

2024-12-04T18:07:12Z

Admin: Created page with "__NOTOC__ Meteoplug allows to feed weather data to a broad range of Internet weather networks. As Meteoplug server gets data from clients at a shortest interval of 10 minutes, sending data more often than every 10 minutes to weather networks does not make sense and is not supported. While most weather networks are not expecting to get data more often then every 10 minutes, there is one exception. Weather Underground offers a so called "rapid fire" mode, where data gets u..."

__NOTOC__
Meteoplug allows to feed weather data to a broad range of Internet weather networks. As Meteoplug server gets data from clients at a shortest interval of 10 minutes, sending data more often than every 10 minutes to weather networks does not make sense and is not supported. While most weather networks are not expecting to get data more often then every 10 minutes, there is one exception. Weather Underground offers a so called "rapid fire" mode, where data gets updated every few seconds. Meteoplug support regular Weather Underground mode but does not support "rapid fire" mode.

<center>[[File:mp-weather-networks.png]]</center>

==Supported Weather Networks==

Table below lists supported weather networks and provides a link to these, where you can further information what the weather network can do for you. To have Meteoplug feeding the network you simply have to select it by setting the check mark near the weather network's name. In most cases you also have to provide also an ID an password which will be given to you when registering at a certain weather network. Depending on weather network data is provided by one of three modes:
* '''Pull''': Data is provided at a certain location at "http://www.meteoplug.com/wnet/xxx/yyy" (where "xxx" is your Meteoplug user name and "yyy" is the file name of generated weather data). Weather networks looks at this location from time to time to read actual weather data of your station. Usually, you have to define the location where to grab your data when setting up an account at the weather network.
* '''Push''': Data is actively transmitted at the given interval to the weather network. This is mostly done by HTTP get request but can also be plain socket connections. In both cases sending station has to identify itself by an ID and password, which will be selected when setting up an account at the weather network.
* '''E-Mail''': Data is send by an email to weather network. Authentification can be done by sender address and or other credentials in the mail.

Changes are made effective after having pressed "Save".

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Weather Network''' !! '''Scope''' !! '''Mode''' !! '''Comment'''
|-
| [http://www.hetweeractueel.nl/ Hetweeractueel]
| Netherlands
| pull
|
|-
| [http://www.wetterpage24.de/ Wetterpage24] http://www.wetterpool.de/
| Germany
| pull
|
|-
| [http://www.wetterpool.de/ Wetterpool]
| Germany
| pull
|
|-
| [http://www.dmi.dk/dmi/index/danmark/borgervejr.htm Borgervejr]
| Denmark
| email
| Authentification by sender address
|-
| [http://www.regiowetter.ch/ Regiowetter]
| Switzerland
| push
| Authentification by ID
|-
| [http://www.wetterspiegel.de/de/nachrichten/ Wetterspiegel]
| Germany
| pull
| Authentification by ID
|-
| [http://www.meteoclimatic.com/ Meteoclimatic]
| Spain
| pull
| Authentification by ID
|-
| [http://www.wxqa.com/ CWOP]
| International
| push
| Authentification by ID
|-
| APRS
| Individual
| push
| Authentification by ID, target specified by server name/IP and port separated by a colon.
|-
| [http://www.wedaal.de/ Weedal]
| mainly Germany / Europe
| push
| Authentification by ID and password
|-
| [http://www.windfinder.com/ Windfinder]
| International
| push
| Authentification by ID and password
|-
| [http://www.sauerlandwetter.de/ Sauerlandwetter]
| Region in Germany: Sauerland
| push
| Authentification by ID and password
|-
| [http://www.internetwetter.de/home/s-h-netz.php SH-Netz]
| Region in Germany: Schleswig-Holstein
| push
| Authentification by ID and password
|-
| [http://www.awekas.at Awekas]
| International
| push
| Authentification by ID and password
|-
| [http://wetterarchiv.wetter.com/ Wetterarchiv]
| Germany
| push
| Authentification by ID and password
|-
| [http://www.hamweather.com/ HAMweather]
| International
| push
| Authentification by ID and password
|-
| [http://www.wunderground.com/ Weather Underground]
| International
| push
| Authentification by ID and password
|-
| [http://reg.backyard2.weatherbug.com/reg/PwsRegPage.aspx WeatherBug]
| US
| push
| Authentification by ID, Number and password
|}

==Selection of Sensors==

As Meteoplug can handle a lot of sensors from different stations you have to define which sensors to use for reporting data to weather networks. simply select sensor IDs from drop-down lists. As a minimum set "outdoor temperature", "outdoor humidity", "pressure" and "wind" need to assigned to valid sensor IDs. Otherwise weather networks will not accept data.

Changes are made effective after having pressed "Save".

==Upload Frequency==

Meteoplug supports upload frequencies up to every 10 minutes. Available frequencies are 10 minutes, 15 minutes, 20 minutes, 30 minutes, 45 minutes, 1 hour, 2 hours, 3 hours, 6 hours, 12 hours, and 24 hours.

When upload frequency is more often then data upload interval from client to server, Meteoplug will display a warning, as this will probably not make sense.

Weather Station

2024-12-04T18:06:56Z

Admin: Created page with "__NOTOC__ Here you define which weather station is connected to your Meteoplug client. ==Available Devices== This section lists devices which are momentarily connected to the client. Devices are listed sorted by it's type of physical connection: * '''USB serial''' lists devices that are connected via USB but have a serial-to-USB converter included. From a logical point of view these are serial connections tunneled via USB. When you connect a weather station with RS232 c..."

__NOTOC__
Here you define which weather station is connected to your Meteoplug client.

==Available Devices==
This section lists devices which are momentarily connected to the client. Devices are listed sorted by it's type of physical connection:
* '''USB serial''' lists devices that are connected via USB but have a serial-to-USB converter included. From a logical point of view these are serial connections tunneled via USB. When you connect a weather station with RS232 connector by means of a RS232-USB converter the station will be listed as "USB serial".
* '''Serial''' lists devices that are directly connected to a RS232 port of your client. As Bifferboard clients don't support native RS232 this list is irrelevant for typical Meteoplug usage.
* '''USB HID''' lists devices that are connected via USB and are communicating by a USB HID protocol. This protocol is very flexible and was originally designed for connecting "human interface devices" like keyboards or mice. However, most appearing new weather stations make use of this type of protocol.

<center>[[File:mp-weather-station.png]]</center>

==Select Weather Station==
Weather stations can be added by selecting one from the drop-down list at the bottom. You can select any station from the table below. Stations differ in type of connection as you can see from table below.

{| style="background:none" border="1" cellpadding="5" cellspacing="0"
! '''Station Name''' !! '''Company''' !! '''Serial''' !! '''USB serial''' !! '''USB HID''' !! '''TCP/IP'''
|- align="center"
| WMR-928, WMR-968 WMR-918N
| Oregon Scientific
| x
| RS232-USB converter
| -
| -
|- align="center"
| RFXCOM Receiver 433MHz
| RFXCOM
| -
| 80002
| -
| 81003, 82003, 83003, 84003
|- align="center"
| WMR-100
| Oregon Scientific
| -
| -
| x
|
|- align="center"
| WMR-200
| Oregon Scientific
| -
| -
| x
|
|- align="center"
| WMRS-200
| Oregon Scientific
| -
| -
| x
|
|- align="center"
| RMS-300
| Oregon Scientific
| -
| -
| x
|
|- align="center"
| TE-923, TE-821X, DV-928
| Hideki, Mebus, Irox, Honeywell
| -
| -
| x
|
|- align="center"
| Vantage Vue, Vantage Pro2, Vantage Pro1 (FW B)
| Davis
| WL Serial
| WL USB
| -
| WLIP
|- align="center"
| WN-1080, WH-1081, W-8681, Elecsa 6975, 265 NE
| Fine Offset Electronics
| -
| -
| x
| -
|- align="center"
| Ultimeter 100, 800, 2100
| Peet Bros
| x
| RS232-USB converter
| -
| -
|- align="center"
| MKIII
| Rainwise
| x
| RS232-USB converter
| -
| -
|- align="center"
| WS-2300, 2310, 2350
| LaCrosse
| x
| RS232-USB converter
| -
| -
|- align="center"
| WS300, WS400, WS444, WS500, WS550, WS777, WS888, etc.
| LaCrosse, ELV, Conrad
| -
| -
| x
| -
|}

==Select Device==
When you have a weather station selected that is connected via "serial" or "USB serial" you have to enter the name of the Linux device being used to connect. When the device is listed as available device, you can simply select it from the "select" drop-down list. Otherwise please type in device name.

When you have a "TCP/IP" connection selected please type in IP address or symbolic name of the weather station followed by the port number, separated by a colon. Example: "192.168.1.99:10001" might connect to a Vantage WLIP datalogger at IP 192.168.1.99 and is configured to serve data on port 10001.

==Additional Parameters==

* '''Hold Time''' specifies how long data delivered by a sensor should be regarded being actual. When client doesn't receive data during that period, weather is considered stalled and Meteoplug client will try to restart weather station connection.
* '''Altitude''' given in meters above zero is needed for sea level pressure calculations.
* '''Sealevel''' gives you the option to decide how sealevel pressure should be computed from pressure measured at station height. There are three modes available:
** Sealevel Pressure can be directly taken from weather station (if weather station can handle station height and delivers corrected sealevel pressure via its interface).
** Sealevel pressure is computed from station pressure and altitude.
** Sealevel pressure is computed from altitiude and outdoor temperature using sensor th0
* '''Windchill''' can be taken from the weather station or can be computed by Meteoplug from wind speed and outdoor temperature.
* '''Stopped''' gives you an option to have data from weather station dropped and not being reported to Meteoplug server application. This option can be useful for trouble shooting.

==Special "Stations"==
Beside real weather stations Meteoplug also supports an number of special "stations" that log interesting data not being connected to a meteorological topic at all.

===System===
As a special weather station you can select a "System" module that reports statistical data about client's uptime, number of processes, system load, etc. This station reports values as unspecified "data" values. Logged data can be used for computation and graphing and might indicate down time, peak load situation etc of your client.

===EM1000, EM1010===
These energy monitoring devices from ELV and Conrad can also be logged by Meteoplug. They do report power and energy consumption as data values. These values can be used for graphing and computation like true weather data sensors.

Sensors

2024-12-04T18:06:23Z

Admin: Created page with "__NOTOC__ The idea of "Sensors" page is to define unique IDs to the sensors reported from your weather station, resp. your weather stations if you have more than one connected to your Meteoplug client. <center>File:mp-sensors-2.png</center> Each connected station is displayed in a rectangular field which lists all sensors reported. Coumns have meaning as follows: * '''Type''' displays what type of sensor you are facing. * "'''#'''" indicated the channel number sel..."

__NOTOC__
The idea of "Sensors" page is to define unique IDs to the sensors reported from your weather station, resp. your weather stations if you have more than one connected to your Meteoplug client.

<center>[[File:mp-sensors-2.png]]</center>

Each connected station is displayed in a rectangular field which lists all sensors reported. Coumns have meaning as follows:
* '''Type''' displays what type of sensor you are facing.
* "'''#'''" indicated the channel number selected to the sensor itself. If no channel selection can be done, 0 is reported. This channel number helps to identify which of your sensors is reported here.
* '''ID''' is the field where you have to give the sensor a unique identifier needed to address this sensor in all kinds of computation and graphing inside Meteoplug. Please select "th0" to be your primary outdoor temperature/humidity sensor. This is necessary as some kinds of wind chill computation might take the sensor as reference. You can assign IDs to all other sensors as you like.
* '''Name''' gives you an option to give sensor a speaking name which might make remembering what sensor the ID represents more easy later on.
* '''Last Signal''' tells you when the last update of sensor data has been provided by the client.
* '''Sensor Data''' reports last received data per sensor.

Additional Sensors field gives you the option to define IDs for sensors that are actually not reported by your station. This is helpful if you have a sensor that has failed shortly and you want to use it's data of the past in graphing or computations. Unless there is an ID defined for this data there is no way to address this data. Please make sure that you don't have duplicate sensor ID settings in any of the ID selection fields.

Press "Save & Restart Data Logging" to make your changes effective. Changes will be reported to your Meteoplug client next time it connects the server. Pressing "Refresh" just updates sensor readings without making changes to any settings.

==Sensors of a Meteohub System==
When data is delivered by a Meteohub system, assignment of sensors is not done by Meteoplug server but has already been done with Meteohub locally. In this case "Sensors" page is a pure display without option to change settings. When settings should be changed, this has to be done directly on your local Meteohub system.

<center>[[File:mp-sensors-3.png]]</center>

Inspect Data

2024-12-04T18:05:46Z

Admin: Created page with "__NOTOC__ Inspect data tab allows to view client's raw data for a given period in time and a selected set of sensors. You can also import or export data to your PC and can mark data as deleted. Data is marked by a "*" if it s regarded as deleted and is marked by a "i" if it is data imported from a Meteohub or WSWIN system. Data marked with "z" are zero setting entries which set current counter value (rain total for example) as a a new starting point for measuring future..."

__NOTOC__
Inspect data tab allows to view client's raw data for a given period in time and a selected set of sensors. You can also import or export data to your PC and can mark data as deleted.
Data is marked by a "*" if it s regarded as deleted and is marked by a "i" if it is data imported from a Meteohub or WSWIN system. Data marked with "z" are zero setting entries which set current counter value (rain total for example) as a a new starting point for measuring future value increases.

<center>[[File:mp-inspect-data.png]]</center>

==Data Inspection==
When displaying raw data you select a point in time where to start display of data. First you select a year/month, then day of month and hour and minutes to start with. With sensor filter option you can decide if data of all sensors is displayed or just a subset of selected sensors. Scroll box allows to select multiple sensors by pressing SHIFT or CTRL while clicking onto a sensor name. You can also reduce the list of data to be displayed to data that has been recorded by a Meteoplug client (no imports) or to data that has been imported from a Meteohub or WSWIN system (imports only). Settings will be applied for display of data when you press "Display" button.

Data is displayed with time stamps in local time.

==Data Deletion==
Meteoplug allows to mark data as deleted. Please insert time stamp in format YYYYMMDDhhmmss into from field and add number of seconds preceded by a "+" as range to be used for deletion and press "Delete" button. Deleted data will marked with a "*" before sensor name and will not be used for computation and graphing.

Deletion marks can be removed by specifying a time frame as explained before and pressing "Undelete" button.

"Zero" button declares data at given time stamp to be a new starting count value for evaluating cumulatative data. For example, if you "zero" a rain data record with a total counter value of 110.5 mm, this will be taken as a new starting point for measuring future increases. The value of 110.5 mm itself will not be regarded as additional rainfall. This is feature extremely usefull to null accidential counter increases. A "zeroed" data record can be converted in a norma data record by undeleting it.

Deletion and "undeletion" are applied according to the specified filters. When you have a specific set of sensors specified or if you have a selection on imported or regular recorded sensor data in place, then the delte/undelete operation is just operation on the selected subset of data. This allows you to delete a specific sensor from a given period of time or to focus deleteion only to imported data, for example.

==Data Import==
You can import data from your Meteohub system, WSWIN (EXPMM_YY.CSV files, with ";" defined as field separator), Meteobase or previously saved Meteoplug data by selecting a file on your PC by pressing "Browse..." button. When you have selected a file, press "Import" to start data transfer. Uploading and import of data will take some time. You might look at server log file for messages documenting progress on scheduled data imports. Imported data will be marked with an "i" in the display.

Data can be plain text files or can be compressed. Supported compression formats are
* Regular zip format, extension ".zip"
* gnu zip format, extension ".gz"
* bzip2 format, extension ".bz2"

==Data Export==
When exporting data to your PC you have to select the month to take data from. When pressing "Export" you will be asked to define a file name used to store data onto your PC.

Exported data is organized in lines. Items in a line are separated by white space characters, line end is represented by a line feed character. See example below.

<pre>2010-01-01 00:00:01 data0 44 0 0 0 0 0 2
2010-01-01 00:00:01 data1 21040700 0 0 0 0 0 2
2010-01-01 00:00:01 data2 66 0 0 0 0 0 2
2010-01-01 00:00:01 data3 75 0 0 0 0 0 2
2010-01-01 00:00:01 data4 1 0 0 0 0 0 2
2010-01-01 00:00:01 data5 5400 0 0 0 0 0 2
2010-01-01 00:00:01 data6 500 0 0 0 0 0 2
2010-01-01 00:00:01 data7 100 0 0 0 0 0 2
2010-01-01 00:00:02 wind0 101 26 22 -33 0 0 2
2010-01-01 00:00:10 t0 107 0 0 0 0 0 2
2010-01-01 00:00:16 wind0 97 24 22 -31 0 0 2
2010-01-01 00:00:17 th0 -1 56 -78 0 0 0 2
2010-01-01 00:00:19 thb0 241 32 64 9970 2 10002 2
2010-01-01 00:00:21 rain0 0 0 35540 0 0 0 2
</pre>

Each line decomposes into a fixed schema of fields.
* '''Date''': First filed is the date in format YYYY-MM-DD given in UTC.
* '''Time''': Second field is timestamp informat hh:mm:ss given in UTC.
* '''Sensor''': Third field is sensor ID, which consists of a sensor type sting (wind, rain, thb, th, t, uv, sol, data) and an identification number.
* '''Values''': Fourth to ninth field are sensor data. Meaning of data depends on sensor type. Table below lists meaning of data for each sensor type.
* '''Flag''': This bitfield contains some status information about data record.
** Bit 0 indicates if record is marked as deleted.
** Bit 1 indicates if record has been backuped by Meteoplugs scheduled background data backups.
** Bit 2 indicates if record has been manually imported from a Meteohub, WSWIN or Meteobase system.

Meaning of values is as follows:

{| style="background:none;font-size:9px;" border="1" cellpadding="5" cellspacing="0"
! '''Sensor Type''' !! '''Value 1''' !! '''Value 2''' !! '''Value 3''' !! '''Value 4''' !! '''Value 5''' !! '''Value 6'''
|-
| '''t''' (thermo) || temp [1/10 °C] || 0 || 0 || 0 || 0 || 0
|-
| '''th''' (thermo/hygro) || temp [1/10 °C] || hum [%] || dew[ 1/10 °C] || 0 || 0 || 0
|-
| '''thb''' (thermo/hygro/baro) || temp [1/10 °C] || hum [%] || dew [1/10 °C] || press [1/10 hPa] || forecast symol || sealevel [1/10 hPa]
|-
| '''rain''' (rain) || rate [1/10 mm] || 0 || total [1/10 mm] || 0 || 0 || 0
|-
| '''wind''' (wind) || dir [°] || gust [1/10 m/s] || wind [1/10 m/s] || chill [1/10 °C] || 0 || 0
|-
| '''uv''' (UV) || uvi [1/10 uvi] || 0 || 0 || 0 || 0 || 0
|-
| '''sol''' (solar) || radiation [W/qm] || 0 || 0 || 0 || 0 || 0
|-
| '''data''' (data) || value [1/100] || 0 || 0 || 0 || 0 || 0
|}

Log Files

2024-12-04T18:05:25Z

Admin: Created page with "==Meteoplug Client Log== Meteolug lists events of Meteoplug client in a separate log file. This can be of significant help to understand why data is not being received as expected. It also indicates transmission problem between weather station and Meteoplug client. <center>File:mp-client-log.png</center> In example above you can see that logger has been restarts several times. As this just happens every few days, presumably caused by changes on the Meteoplug server..."

==Meteoplug Client Log==
Meteolug lists events of Meteoplug client in a separate log file. This can be of significant help to understand why data is not being received as expected. It also indicates transmission problem between weather station and Meteoplug client.

<center>[[File:mp-client-log.png]]</center>

In example above you can see that logger has been restarts several times. As this just happens every few days, presumably caused by changes on the Meteoplug server application, it looks like normal operation. You can also see, that a Meteohub system has connected the client on 12th of January.

By pressing "Clear" client log file will be deleted. Pressing "Refresh" updates display to most recent values.

==Meteoplug Server Log==
Meteoplug manages each user separately. Therefore, you see just actions for your client's MAC in the server log of your account.

<center>[[File:mp-server-log.png]]</center>

In example above you see that certain processes that log information are working together. That is namely:
* '''LOGRAW''' receives data send from client and stores that locally on the server file system.
* '''IMPORT''' takes the raw data written by LOGRAW and imports these into the database.
* '''UPDATEDB''' propagates changes of raw data in database to higher level of aggregation.

Pressing "Refresh" updates the display to the most recent values.

Settings

2024-12-04T18:05:06Z

Admin: Created page with "__NOTOC__ System Information page gives you a compact view on the status of your Meteoplug client and some basic information about the server application <center>File:mp-systeminfo.png</center> ===Server Information=== Meteoplug displays following information about the server application: * Version and build number of server software * Date when license of use will expire and how many days are left. When license is close to expiration (less than 14 days left) or is..."

__NOTOC__
System Information page gives you a compact view on the status of your Meteoplug client and some basic information about the server application

<center>[[File:mp-systeminfo.png]]</center>

===Server Information===
Meteoplug displays following information about the server application:
* Version and build number of server software
* Date when license of use will expire and how many days are left. When license is close to expiration (less than 14 days left) or is already expired you will see yellow or red notifications on that here.
* Time zone you have selected. Each Meteoplug user defines his own time zone, which usually is the time zone that applies to the position the weather station is located at.
* Local time (regarding to selected time zone)
* World time (UTC)

===Client Information===
Meteoplug displays key information about your Meteoplug client. To present this information it is necessary that the Meteoplug client did make a successful connection to the server.
* Version of client software
* Type of client HW and Bogo Mips of the client hardware
* MAC of the client hardware
* LAN IP, Gateway IP and DNS IP which has been given Meteoplug client by your router resp. DHCP server.
* WAN IP of your router
* Uptime of your Meteoplug client
* time that has passed since last connection of your Meteoplug client with Meteoplug server

Beside looking at the Meteoplug server application to view information about the status of the Meteoplug client in your LAN you can also browse directly the Meteoplug client. Just take the displayed LAN IP and browse to it. To make this a success your browsing PC has to be in the same LAN and subnet, but I guess this will be the case in most situations. Meteoplug client will report following information when directly connected from your browser:

<center>[[File:Client-webinterface.png]]</center>
* '''System''' section displays client software version including build number, type of hardware, Bogo Mips and license expiration date.
* '''Network''' section displays MAC, LAN IP, Gateway IP and DNS IP. If Gateway and DNS IP are not set correctly, Meteoplug will not be able to contact the outside world. You will have your DHCP server (mostly your router) with a model that provides DHCP data correctly. Meteoplug operation depends on a sufficient DHCP server. Without that, no operation can be done.
* '''Activity''' section displays client date & time settings (in UTC), percentage of usage of clients RAM disk, uptime, system load, last connection to server and scheduled next server connect.
* '''Connected Devices''' section lists USB devices connected to Meteoplug client.
* '''Sensor Readings''' section lists all weatherstations that have been configured by Meteoplug server application for this specific Meteoplug client. You see for each sensor
** sensor type
** assigned ID
** time that has passed sense last data reception
** actual sensor data

System Info

2024-12-04T18:04:44Z

User Admin

2024-12-04T18:04:21Z

Admin:

__NOTOC__
This page manages Meteoplug user accounts. The look of the page adapts to the situation you are in: '''not logged in''' and '''logged in'''.

=="Not logged in" Mode==
When you browse to Meteoplug you will start with the following interface which allows you register an account, login to a registered account and to request a new password for your account because you can't remember the old one.

<center>[[File:mp-user-admin.png]]</center>

===Login===
As an exiting user you have to login with your user name and password. If user name or password is wrong an error message will appear asking you to try again.

===Register===
When you are a first time user, you have to register an account first. Registration is done by providing following data:
* '''MAC''': Each user account at the Meteoplug server is connected to a Meteoplug client device. The client device is specified by it's MAC. MAC has to specified in standard format which is six two-digit hex numbers separated by a colon (like 1A:2B:3C:4D:5E:6F). You will find the MAC of your client device printed on it, in the documentation of the device, or by browsing the the device in your LAN (you have to know it's IP for that). Apart from finding out the MAC yourself, Meteoplug supports you by comparing the Internet IP you are using to login to Meteoplug server with actual internet IPs of Meteoplug sending data. When your client is already powered on and it is using the same internet connection as your browsing PC then Meteohub will be able to propose the MAC of your Meteoplug client in the drop-down box named "select MAC". In most cases the MAC you are looking for will be presented there.
* '''User Name''': Here you have to specify a user name not used so far. If it is already in use or it contains invalid characters an error message will appear when pressing "Register". User name should not contain special characters and/or blanks.
* '''Password''': Password has to entered twice. It should be at least 6 characters long and should not contain special characters. If passwords do not match, don't have necessary length or contain invalid characters an error message will appear when pressing "Register"
* '''E-mail''': E-mail address needs to be a valid address you have access to. When doing registration it will be necessary for account activation that you follow a link provided in that mail. When e-mail address looks invalid an error message will appear.

===Reset Password===
When you lost your password you can request a new one. In order to make that happen it needs your user name and the e-mail address connected with this user. If user name and e-mail address do match, a new password will be send to given e-mail address, otherwise an error will appear.

=="Logged in" Mode==
Logged in mode gives you a couple of options to make changes on certain tapes of information.

<center>[[File:mp-user-admin-2.png]]</center>

===Logout===
Meteoplug displays your user name and gives you the option to logout. This is necessary when you want to login as an alternative user. When you leave the session more than 20 minutes untouched the session will be terminated and a new login is required.

===Change Password===
You can alter your password. Password checks (as explained in "not logged in" mode) are applied. Specification of actual password is not required. Meteohub assumes that you are an authorized user.

===Change E-Mail===
You can change e.mail address. There are no additional checks done. It is assumed that you know what you do. When you direct this to an e-mail address you don't have access to, you will not be able to revoke your password etc. So please check that your input is correct, when changing email addresses.

===Change Client Device===
Your Meteoplug account is bound to a MAC when you do registration. When you change your Meteoplug client device you will have a need to switch to it's new MAC to get data from that and to combine it with your previously received data in graphs and computations. Please make sure that the MAC you insert is the correct one. When having done the MAC change a lot of recomputation will happen behind the scenes. It might take quite a few minutes until your complete data (from old and new MAC) will be available for graphing etc. You can can consult your server log files to see if computation has been finished.

===Manual Activation===
Normally purchase of additional usage time will be done by PayPal as explained in the next chapter. However, there is an alternative way that allows manual add of licenses keys which result in additional usage time.

===License Purchase via PayPal===
When you like Meteoplug's features and are willing to use it after the 30 days of test period, you can add additional 12 months of usage by following the PayPal link at the bottom. You will be guided through the complete process. When payment has been done Meteoplug will instantly add the 12 months to your license period. A purchase e-mail documenting this transaction will be sent to you. This will also include a VAT statement, if that applies to your country (mainly EU countries). If unexpected trouble occurs during PayPal processing, please contact "info(at)meteoplug.com".

User Admin

2024-12-04T18:03:51Z

Admin: Created page with "=="Not logged in" Mode== When you browse to Meteoplug you will start with the following interface which allows you register an account, login to a registered account and to request a new password for your account because you can't remember the old one. <center>File:mp-user-admin.png</center> ===Login=== As an exiting user you have to login with your user name and password. If user name or password is wrong an error message will appear asking you to try again. ===R..."

=="Not logged in" Mode==
When you browse to Meteoplug you will start with the following interface which allows you register an account, login to a registered account and to request a new password for your account because you can't remember the old one.

<center>[[File:mp-user-admin.png]]</center>

===Login===
As an exiting user you have to login with your user name and password. If user name or password is wrong an error message will appear asking you to try again.

===Register===
When you are a first time user, you have to register an account first. Registration is done by providing following data:
* '''MAC''': Each user account at the Meteoplug server is connected to a Meteoplug client device. The client device is specified by it's MAC. MAC has to specified in standard format which is six two-digit hex numbers separated by a colon (like 1A:2B:3C:4D:5E:6F). You will find the MAC of your client device printed on it, in the documentation of the device, or by browsing the the device in your LAN (you have to know it's IP for that). Apart from finding out the MAC yourself, Meteoplug supports you by comparing the Internet IP you are using to login to Meteoplug server with actual internet IPs of Meteoplug sending data. When your client is already powered on and it is using the same internet connection as your browsing PC then Meteohub will be able to propose the MAC of your Meteoplug client in the drop-down box named "select MAC". In most cases the MAC you are looking for will be presented there.
* '''User Name''': Here you have to specify a user name not used so far. If it is already in use or it contains invalid characters an error message will appear when pressing "Register". User name should not contain special characters and/or blanks.
* '''Password''': Password has to entered twice. It should be at least 6 characters long and should not contain special characters. If passwords do not match, don't have necessary length or contain invalid characters an error message will appear when pressing "Register"
* '''E-mail''': E-mail address needs to be a valid address you have access to. When doing registration it will be necessary for account activation that you follow a link provided in that mail. When e-mail address looks invalid an error message will appear.

===Reset Password===
When you lost your password you can request a new one. In order to make that happen it needs your user name and the e-mail address connected with this user. If user name and e-mail address do match, a new password will be send to given e-mail address, otherwise an error will appear.

Main Page

2024-12-04T17:27:46Z

Admin: Changed redirect target from Home to Introduction

#REDIRECT [[Introduction]]

Main Page

2024-12-04T17:27:28Z

Admin: Redirected page to Home

#REDIRECT [[Home]]

Meteoplug Wiki:About

2024-12-04T17:26:35Z

Admin: Redirected page to Contact - Impressum

#REDIRECT [[Contact_-_Impressum]]

Contact - Impressum

2024-12-04T17:25:45Z

Admin: Created page with "<pre>smartbedded GmbH Querweg 35 24632 Lentföhrden Germany USt-ID/VAT-ID: DE278026783 Registergericht Kiel HRB 13085 Geschäftsführerin: Anke Pasternak Tel: ++49-4192-8192250 Fax: ++49-4192-819356 email: info(at)meteohub.de</pre>"

<pre>smartbedded GmbH
Querweg 35
24632 Lentföhrden
Germany

USt-ID/VAT-ID: DE278026783
Registergericht Kiel HRB 13085
Geschäftsführerin: Anke Pasternak

Tel: ++49-4192-8192250
Fax: ++49-4192-819356
email: info(at)meteohub.de</pre>

Server Status

2024-12-04T17:25:20Z

Admin: Created page with "<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=7c7e7d7b7976323b3f3620267a2b2c74382c2424302221372276212720282a" height="820" width="730" /> Please notice, time is given in UTC (GMT). Depending on your geographical location your local time will differ from that. If you are interested, the chart above does give some usefull information about the Meteoplug server status. You can read the chart as follows: * <b>Processes</b> shows the number of processes running o..."

Meteoplug License

2024-12-04T17:24:46Z

Admin: Created page with "==Meteoplug License Fee== To license Meteoplug for additional 12 months of usage (beyond free evaluation period of 30 days) the web administration interface of Meteoplug provides a payment connection ([https://smartbedded.onfastspring.com/meteoplug-cloud-service link]) that allows instant activation of the license. Additional 12 months of usage do cost 29 Euro. ==Meteoplug Application License== SCOPE OF THE USER LICENSE AGREEMENT FOR METEOPLUG This license agreement co..."

==Meteoplug License Fee==
To license Meteoplug for additional 12 months of usage (beyond free evaluation period of 30 days) the web administration interface of Meteoplug provides a payment connection ([https://smartbedded.onfastspring.com/meteoplug-cloud-service link]) that allows instant activation of the license. Additional 12 months of usage do cost 29 Euro.

==Meteoplug Application License==

SCOPE OF THE USER LICENSE AGREEMENT FOR METEOPLUG
This license agreement covers the "Meteoplug server application" as it
can be reached at "www.meteoplug.com" and the "Meteoplug client application"
components on your local Meteoplug weather data ackquisition device that
uploads weather data to "meteoplug.com".

===User License Agreement===
You should read the following terms and conditions before using this software.

YOUR INSTALLATION AND/OR USE OF THIS SOFTWARE INDICATES YOUR ACCEPTANCE OF THIS
LICENSE AGREEMENT AND WARRANTY.

You may not alter this software in any way.

You may not decompile, reverse engineer, disassemble or otherwise reduce this
software to a human perceivable form. You may not modify or rent for profit
this software, or create derivative works based upon this software.

You may not publicise or distribute any algorithms or information used by this
software without permission of the author/s.

Copyright Notice: "Meteoplug" is the sole Copyright of smartbedded UG (haftungsbeschränkt)
all rights reserved.

===Warranty Disclaimer===
THIS SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND TO THE MAXIMUM
EXTENT PERMITTED BY APPLICABLE LAW, THE AUTHOR/S FURTHER

DISCLAIM ALL WARRANTIES, INCLUDING WITH OUT LIMITATION ANY IMPLIED WARRANTIES
OF MERCHANT ABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY OF INFORMATION
AND NON INFRINGEMENT. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE
OF THIS SOFTWARE AND DOCUMENTATION REMAINS WITH THE RECIPIENT. TO THE MAXIMUM
EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL THE AUTHOR/S BE LIABLE
FOR ANY CONSEQUENTIAL, INCIDENTAL, DIRECT, INDIRECT, SPECIAL, PUNITIVE OR
OTHER DAMAGES OR COSTS WHATSOEVER (INCLUDING, WITH OUT LIMITATION, DAMAGES OR
COSTS FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS
INFORMATION OR OTHER PECUNIARY LOSS) ARISING OUT OF THIS AGREEMENT OR THE USE
OF OR INABILITY TO USE THE SOFTWARE, EVEN IF THE AUTHOR/S OF THE SOFTWARE HAVE
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE AUTHOR/S DO NOT TAKE ANY
RESPONSIBILITY AGAINST ANY DAMAGE THIS SOFTWARE MAY DO TO YOUR SYSTEM OR
ANOTHER.

THIS SOFTWARE IS NOT WARRANTED TO BE FAULT-TOLERANT, AND IS NOT INTENDED
FOR THE DESIGN, CONSTRUCTION, MAINTENANCE, OPERATION, CONTROL, OR ANY
OTHER USE IN CONNECTION WITH HIGH RISK SYSTEMS. WE SPECIFICALLY DISCLAIM
ANY EXPRESS OR IMPLIED WARRANTY OF FITNESS FOR PURPOSE IN CONNECTION WITH
HIGH RISK SYSTEMS.

High Risk Systems means systems in environments requiring fail-safe performance
(such as nuclear facilities, aircraft navigation or communication systems,
air traffic control, direct life support machines, storm chasing or weapons
systems), in which the failure of the software could lead directly to death,
personal injury, or severe physical or environmental damage. You agree that
you will not use the software for any purpose in connection with High Risk
Systems.

ALTHOUGH the author/s DO NOT WARRANT THAT THIS SOFTWARE SUPPLIED HEREUNDER
SHALL BE FREE FROM ALL KNOWN VIRUSES WE HAVE USED COMMERCIALLY REASONABLE
EFFORTS TO CHECK FOR THE MOST COMMONLY KNOWN VIRUSES. YOU ARE NEVERTHELESS
SOLELY RESPONSIBLE FOR VIRUS SCANNING THIS SOFTWARE.

===Data Privacy & Security===
THERE IS ALSO NO WARRANTY THAT UPLOADED DATA WILL BE STORED FOR ANY
PERIOD OF TIME. YOU CANNOT RELY ON HAVING DATA STORED AT THE SERVER
APPLICATION. THERE IS ALSO NO WARRANTY THAT YOUR UPLOADED DATA MIGHT
NOT BE DOWNLOADED AND USED BY OTHERS. METEOPLUG SERVER APPLICATION DOES NOT
WARRANT PRIVACY OR SECURITY OF ANY UPLOADED DATA. BY USING METEOPLUG
YOU ARE AWARE THAT YOUR UPLOADED DATA MIGHT BE MADE PUBLIC BY INTENTION OR
BY ACCIDENT. YOU WILL MAKE SURE NOT TO UPLOAD SENSIBLE DATA OF ANY KIND
ONTO METEOPLUG'S SERVER APPLICATION.
WHILE NOT WARRANTING ANY OF THE THINGS MENTIONED ABOVE, METEOPLUG PUTS
SOME WEAK MECHANISMS IN PLACE TO PROVIDE A VERY MINIMAL LEVEL OF DATA
PRIVACY AND SECURITY, BUT WHICH CAN BE BROKEN BY HACKERS FOR SURE.

===Warranty Disclaimer for 3rd Party components===
THIS SOFTWARE IS PROVIDED `AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ANY
PERSON WHO HAS CONTRIBUTED TO OR IS THE OWNER OF ANY PART OF THIS SOFTWARE
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

===Evaluation and Registration===
This software is an evaluation version when no activation key is provided
or a full version (with activation code). Subject to the terms in this
document, you are hereby licensed to use this software for
evaluation purposes without charge or as a full featured version
equipped with an activation code you can purchase from the author/s.
You are not permitted to use the software with activation keys, not
purchased from the author/s or an official reseller. You are not allowed
to modify this software to work in full featured mode without the need
of a purchased activation code.

You are specifically prohibited from distributing the software and/or
documentation with other products (commercial or otherwise) with out
prior written permission from the author/s.

===Acknowledgements===
You acknowledge that you have had the opportunity to evaluate the Software
without charge, and that you have satisfied yourself that it meets your
requirements in all material respects. It is not technically practicable
to guarantee software to be error-free, and you agree that if any such
errors are found to exist they shall not constitute a breach of this License.

You acknowledge that these terms supersede all prior agreements, and are
complete and exclusive. No oral or written information given by the author/s
or on our behalf shall create a warranty or collateral contract, or in any
way increase the scope of this warranty in any way, and you may not rely
on any such advice.

This License shall be governed by the laws of Germany. Court of jurisdiction
is Hamburg.

===Contact===
Email: info(at)meteoplug.com

Web Site: http://www.meteoplug.com/

==GPL for Open Source SW being part of Meteoplug Client Image==
Meteoplug's client image is a Linux distribution including BusyBox - covered by GPL - plus a couple of non-derived software components in folder "/home/metehub" which are NOT Open Source but under copyright of smartbedded UG (haftungsbeschränkt) and are already covered by license terms and conditions as outlined above.

Open Source / Linux components of the distribution have been build by development tools and materials provided by the manufacturer of Bifferboard. As this tool chain for kernel 2.6.30.5 is no longer availabe from the manufacturer side, you can download the complete kernel sources (including config files), BusyBox components and GPL part of default root filesystem from [http://meteohub.de/files/meteoplug-gpl-tool-chain.bz2 here] (about 500 MB).

===GNU GENERAL PUBLIC LICENSE===
Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license
document, but changing it is not allowed.

===Preamble===
The licenses for most software are designed to take away your freedom to
share and change it. By contrast, the GNU General Public License is intended to
guarantee your freedom to share and change free software--to make sure the
software is free for all its users. This General Public License applies to most
of the Free Software Foundation's software and to any other program whose
authors commit to using it. (Some other Free Software Foundation software is
covered by the GNU Library General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not price. Our
General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for this service if you wish),
that you receive source code or can get it if you want it, that you can change
the software or use pieces of it in new free programs; and that you know you can
do these things.

To protect your rights, we need to make restrictions that forbid anyone to
deny you these rights or to ask you to surrender the rights. These restrictions
translate to certain responsibilities for you if you distribute copies of the
software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for
a fee, you must give the recipients all the rights that you have. You must make
sure that they, too, receive or can get the source code. And you must show them
these terms so they know their rights.

We protect your rights with two steps: (1) copyright the software, and (2)
offer you this license which gives you legal permission to copy, distribute
and/or modify the software.

Also, for each author's protection and ours, we want to make certain that
everyone understands that there is no warranty for this free software. If the
software is modified by someone else and passed on, we want its recipients to
know that what they have is not the original, so that any problems introduced by
others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We
wish to avoid the danger that redistributors of a free program will individually
obtain patent licenses, in effect making the program proprietary. To prevent
this, we have made it clear that any patent must be licensed for everyone's free
use or not licensed at all.

The precise terms and conditions for copying, distribution and modification
follow.

===TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION===

0. This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms of
this General Public License. The "Program", below, refers to any such program
or work, and a "work based on the Program" means either the Program or any
derivative work under copyright law: that is to say, a work containing the
Program or a portion of it, either verbatim or with modifications and/or
translated into another language. (Hereinafter, translation is included without
limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by
this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents
constitute a work based on the Program (independent of having been made by
running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as
you receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License
along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it,
thus forming a work based on the Program, and copy and distribute such
modifications or work under the terms of Section 1 above, provided that you also
meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that
you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or
in part contains or is derived from the Program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this License.

c) If the modified program normally reads commands interactively when run,
you must cause it, when started running for such interactive use in the most
ordinary way, to print or display an announcement including an appropriate
copyright notice and a notice that there is no warranty (or else, saying
that you provide a warranty) and that users may redistribute the program
under these conditions, and telling the user how to view a copy of this
License. (Exception: if the Program itself is interactive but does not
normally print such an announcement, your work based on the Program is not
required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable
sections of that work are not derived from the Program, and can be reasonably
considered independent and separate works in themselves, then this License, and
its terms, do not apply to those sections when you distribute them as separate
works. But when you distribute the same sections as part of a whole which is a
work based on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the entire whole,
and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your
rights to work written entirely by you; rather, the intent is to exercise the
right to control the distribution of derivative or collective works based on the
Program.

In addition, mere aggregation of another work not based on the Program with the
Program (or with a work based on the Program) on a volume of a storage or
distribution medium does not bring the other work under the scope of this
License.

3. You may copy and distribute the Program (or a work based on it, under
Section 2) in object code or executable form under the terms of Sections 1 and 2
above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source
code, which must be distributed under the terms of Sections 1 and 2 above on
a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to
give any third party, for a charge no more than your cost of physically
performing source distribution, a complete machine-readable copy of the
corresponding source code, to be distributed under the terms of Sections 1
and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to
distribute corresponding source code. (This alternative is allowed only for
noncommercial distribution and only if you received the program in object
code or executable form with such an offer, in accord with Subsection b
above.)

The source code for a work means the preferred form of the work for making
modifications to it. For an executable work, complete source code means all the
source code for all modules it contains, plus any associated interface
definition files, plus the scripts used to control compilation and installation
of the executable. However, as a special exception, the source code distributed
need not include anything that is normally distributed (in either source or
binary form) with the major components (compiler, kernel, and so on) of the
operating system on which the executable runs, unless that component itself
accompanies the executable.

If distribution of executable or object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the source code
from the same place counts as distribution of the source code, even though third
parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as
expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense or distribute the Program is void, and will automatically terminate
your rights under this License. However, parties who have received copies, or
rights, from you under this License will not have their licenses terminated so
long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it.
However, nothing else grants you permission to modify or distribute the Program
or its derivative works. These actions are prohibited by law if you do not
accept this License. Therefore, by modifying or distributing the Program (or
any work based on the Program), you indicate your acceptance of this License to
do so, and all its terms and conditions for copying, distributing or modifying
the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program),
the recipient automatically receives a license from the original licensor to
copy, distribute or modify the Program subject to these terms and conditions.
You may not impose any further restrictions on the recipients' exercise of the
rights granted herein. You are not responsible for enforcing compliance by third
parties to this License.

7. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues), conditions
are imposed on you (whether by court order, agreement or otherwise) that
contradict the conditions of this License, they do not excuse you from the
conditions of this License. If you cannot distribute so as to satisfy
simultaneously your obligations under this License and any other pertinent
obligations, then as a consequence you may not distribute the Program at all.
For example, if a patent license would not permit royalty-free redistribution of
the Program by all those who receive copies directly or indirectly through you,
then the only way you could satisfy both it and this License would be to refrain
entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply and the
section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or
other property right claims or to contest validity of any such claims; this
section has the sole purpose of protecting the integrity of the free software
distribution system, which is implemented by public license practices. Many
people have made generous contributions to the wide range of software
distributed through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing to
distribute software through any other system and a licensee cannot impose that
choice.

This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain
countries either by patents or by copyrighted interfaces, the original copyright
holder who places the Program under this License may add an explicit
geographical distribution limitation excluding those countries, so that
distribution is permitted only in or among countries not thus excluded. In such
case, this License incorporates the limitation as if written in the body of this
License.

9. The Free Software Foundation may publish revised and/or new versions of the
General Public License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address new problems
or concerns.

Each version is given a distinguishing version number. If the Program specifies
a version number of this License which applies to it and "any later version",
you have the option of following the terms and conditions either of that version
or of any later version published by the Free Software Foundation. If the
Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs
whose distribution conditions are different, write to the author to ask for
permission. For software which is copyrighted by the Free Software Foundation,
write to the Free Software Foundation; we sometimes make exceptions for this.
Our decision will be guided by the two goals of preserving the free status of
all derivatives of our free software and of promoting the sharing and reuse of
software generally.

===NO WARRANTY===
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE
STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE
PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL,
SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF
THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Gallery

2024-12-04T17:08:31Z

Admin: Created page with "__TOC__ This section contains a couple of Meteoplug graphs to give you an impression what Meteoplug can do with your weather data. You will also see Meteoplug graph definitions that produced these interactive graphs. ==Line Graphs== Meteoplug supports classic line graphs to display change of weather data over time. Meteoplug adds interactivity to this. Please give the scroller a try to drag and expand or compress time frame. You can also hide lines by deselecting these..."

__TOC__
This section contains a couple of Meteoplug graphs to give you an impression what Meteoplug can do with your weather data. You will also see Meteoplug graph definitions that produced these interactive graphs.

==Line Graphs==
Meteoplug supports classic line graphs to display change of weather data over time. Meteoplug adds interactivity to this. Please give the scroller a try to drag and expand or compress time frame. You can also hide lines by deselecting these in the legend.

===Classic: Temperature, Humidity and Dew Point===
This graph makes use of both y-axis. Left one displays temperature, right one is displaying relative humidity.

<iframe key="meteoplug" path="examples/example-4.html" height="440" width="560" border="0" />

Definition:
<pre>timeframe=3D # set total time frame to 3 days
zoom=1D # select actual day

gtitle=Temp/Hum # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=line # type of graph
gtrim=0

sid0=th0 sname0=temp ssel0=temp # sensor 0, temperature
sid1=th0 sname1=dew ssel1=dew # sensor 1, dew point
sid2=th0 syaxis2=r sname2=hum ssel2=hum # sensor 2, humidity</pre>

Using JavaScript as engine the chart looks this way and can include min/max markers, which show up a balloon with data when moving the mouse onto it. "gnight" commands do add a dimmed display of time frames between sunset and sunrise.

<iframe key="meteoplug" path="examples/example-4js.html" height="420" width="570" border="0"/>

Definition:
<pre>timeframe=3D # set total time frame to 3 days
zoom=1D # select actual day
engine=js # selects JavaScript engine
gtitle=Temp/Hum # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=line # type of graph
gnightalpha=10 # set intensity of additinal colorization of area between sunset and sunrise
gnightcolor=#000000 # set color of area between sunset and sunrise
gtrim=0

sid0=th0 sname0=temp ssel0=temp sminmarker0=MIN smaxmarker0=MAX smarker0=circle # sensor 0, temperature
sid1=th0 sname1=dew ssel1=dew # sensor 1, dew point
sid2=th0 syaxis2=r sname2=hum ssel2=hum # sensor 2, humidity</pre>

===Classic with different color schema===
You can change colors for overall background, plot area background, grid lines and text to fit your home page design. You can also disable period selector and scroller at the bottom to make your chart looking less complicated. Although the scroller is missing you still can drag the graph to scroll along the time line. Zooming is not possible without the scroller.

<iframe key="meteoplug" path="examples/example-20.html" height="440" width="560" />

Definition:
<pre>timeframe=3D # set total time frame to 3 days
zoom=1D # select actual day

gtitle=Temp/Hum # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=line # type of graph
gtrim=0 # no trimming
periodselector=0 # no period selector at the bottom
scrollerselector=0 # no scroller at the bottom
bgcolor=#000000 # overall background is black
textcolor=#FFFFFF # text color is white
gbgcolor0=#333333 # background color of first plot area is dark gray
gridcolor=#FFFFFF # color of grid lines is white...
gridalpha=20 # ...but with only 20% intensity (results in gray)

sid0=th0 sname0=temp ssel0=temp # sensor 0, temperature
sid1=th0 sname1=dew ssel1=dew # sensor 1, dew point
sid2=th0 syaxis2=r sname2=hum ssel2=hum # sensor 2, humidity</pre>

By changing the engine to JavaScript and adding a min/max marker on temperature the chart looks like this. As there is no scroller bar at the bottom, the chart can be scrolled by clicking the mouse into the chart and dragging the chart while keeping the mouse button pressed:

<iframe key="meteoplug" path="examples/example-20js.html" height="420" width="570" />

Definition:
<pre>timeframe=3D # set total time frame to 3 days
zoom=1D # select actual day

gtitle=Temp/Hum # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=line # type of graph
gtrim=0 # no trimming
periodselector=0 # no period selector at the bottom
scrollerselector=0 # no scroller at the bottom
bgcolor=#000000 # overall background is black
textcolor=#FFFFFF # text color is white
gbgcolor0=#333333 # background color of first plot area is dark gray
gridcolor=#FFFFFF # color of grid lines is white...
gridalpha=20 # ...but with only 20% intensity (results in gray)
engine=js # use JavaScript engine
gnightcolor0=#000044 # paint night arae in dark blue
gnightalpha0=100 # show night arae in full intensity

sid0=th0 sname0=temp ssel0=temp sminmarker0=MIN smaxmarker0=MAX smarker0=square # temperature
sid1=th0 sname1=dew ssel1=dew sminmarker1=MIN smaxmarker1=MAX smarker1=circle # dew point
sid2=th0 syaxis2=r sname2=hum ssel2=hum sminmarker2=MIN smaxmarker2=MAX smarker2=diamond # humidity</pre>

===Stepped: Rain Fall and Rainy Days===
This graphs displays total rain fall of each month by a stepped line with filled area below and number of days with rain as a smoothed line.

<iframe key="meteoplug" path="examples/example-6.html" height="440" width="560" />

Definition:
<pre>timeframe=3Y # set total time frame to 3 years
zoom=1Y # select actual year
res=month1 # get monthly data

gtitle=Rain # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=mm # unit of left y-axis
grunit=_days # unit of right y-axis
gtype=step # type of graph
gtrim=1

sid0=rain0 scolor0=AADDFF sfill0=50 sline0=100 sname0=rain_fall ssel0=total # sensor 0, rainfall
sid1=rain0 ssmooth1=1 stype1=line syaxis1=r sname1=rain_on ssel1=days # sensor 1, raindays</pre>

===Stacked: Number of Days per Month===
Stacked graphs are line graphs that are drawn on top of another graph. This is like graphically adding values. Stacked graphs are useful, when you want to compare values with each other and if you want to see how much each line contributes to the total. This graph sorts days of a month into temperature zones according to their maximum outdoor temperature. Zones are
* maximum temperature of day is below -5°C
* maximum temperature of day is between -5°C and 0°C
* maximum temperature of day is between 0°C and 5°C
* maximum temperature of day is between 5°C and 10°C
* maximum temperature of day is between 10°C and 15°C
* maximum temperature of day is between 15°C and 20°C
* maximum temperature of day is between 20°C and 25°C
* maximum temperature of day is between 25°C and 30°C
* maximum temperature of day is above 30°C

<iframe key="meteoplug" path="examples/example-5.html" height="440" width="560" />

Definition:
<pre>timeframe=3Y # set total time frame to 3 years
zoom=1Y # select actual year
legendpos=left # legend left to graph
legendwidth=120 # 120 px width
res=month1 # get data per month (in a daily mode as defined by daycount on sensor level)

gtitle=Days_per_Temp-Zone # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=_days # unit of left y-axis
grunit=°C # unit for right y-axis
grmin=-10 # min temp
grmax=30 # max temp
gtype=line # type of graph
gtrim=1 # trim graph to data
gscroller=9 # use sensor 9 for display on scroller

scolor0=0000FF # colors for sensors
scolor1=3399FF
scolor2=00FFFF
scolor3=00E573
scolor4=A6FF4C
scolor5=FFFF00
scolor6=FFC080
scolor7=E57300
scolor8=E50000

sid0=th0 sname0=max_-5°C sfill0=90 sline0=0 sdaycount0=day.tempmax<-5.0
sid1=th0 sstack1=0 sname1=max_0°C sfill1=90 sline1=0 sdaycount1=day.tempmax>=-5.0&&day.tempmax<0.0
sid2=th0 sstack2=1 sname2=max_5°C sfill2=90 sline2=0 sdaycount2=day.tempmax>=0.0&&day.tempmax<5.0
sid3=th0 sstack3=2 sname3=max_10°C sfill3=90 sline3=0 sdaycount3=day.tempmax>=5.0&&day.tempmax<10.0
sid4=th0 sstack4=3 sname4=max_15°C sfill4=90 sline4=0 sdaycount4=day.tempmax>=10.0&&day.tempmax<15.0
sid5=th0 sstack5=4 sname5=max_20°C sfill5=90 sline5=0 sdaycount5=day.tempmax>=15.0&&day.tempmax<20.0
sid6=th0 sstack6=5 sname6=max_25°C sfill6=90 sline6=0 sdaycount6=day.tempmax>=20.0&&day.tempmax<25.0
sid7=th0 sstack7=6 sname7=max_30°C sfill7=90 sline7=0 sdaycount7=day.tempmax>=25.0&&day.tempmax<30.0
sid8=th0 sstack8=7 sname8=over_30°C sfill8=90 sline8=0 sdaycount8=day.tempmax>=30.0
sid9=th0 ssmooth9=1 sname9=Ø_Temp syaxis9=r ssel9=temp scolor9=000000</pre>

===Colored: Temperature with Color Bars===
This chart uses left y-axis for temperature and the right one for displaying colored bars realized as stepped lines with filled area below. Color bar is a result of overlapping stepped and filled line charts of sensors 1 to 3. You can inspect how this works by deselecting single sensors from the legend at the top.

<iframe key="meteoplug" path="examples/example-21.html" height="440" width="560" />

Definition:
<pre>timeframe=3W # set total time frame to 3 weeks before today until today
zoom=10D # select 10 day range
res=hour1 # maximum resolution is 1 hour

gtitle=Temp # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=none # disables right axis numeration and grid
grmin=0 # set right axis min to 0
grmax=10 # set right axis max to 10
# bars of sensors 1-3 range from 0 to 1 and cover lower 1/10 of chart
gtype=line # type of graph
gtrim=1

sid0=th0 sname0=temp ssel0=temp # sensor 0, temperature
sid1=th0 syaxis1=r stype1=step scolor1=99FF33 sfill1=50 sline1=50 sname1=cold ssel1=temp
supbound1=15 # only values below 15 are considered
slegend1=0 # no values of sensor in the legend
scursoralpha1=0 # no visible cursor
sid2=th0 syaxis2=r stype2=step scolor2=FFFF33 sfill2=50 sline2=50 sname2=warm ssel2=temp
slowbound2=15 # values between lower boundary 15 ...
supbound2=20 # ... and upper boundary 20 are considered
slegend2=0 # no values of sensor in the legend
scursoralpha2=0 # no visible cursor
sid3=th0 syaxis3=r stype3=step scolor3=FF6633 sfill3=50 sline3=50 sname3=hot ssel3=temp
slowbound3=20 # only values above 20 are considered
slegend3=0 # no values of sensor in the legend
scursoralpha3=0 # no visible cursor</pre>

==Min-Max Graphs==
Meteoplug supports graphs the illustrate minimum and maximum values as bottom and top of floating bars.

===Temperature Ranges per Day===
This graph displays daily minimum and maximum temperature as a red bar and shows daily average temperature by a blue line.

<iframe key="meteoplug" path="examples/example-9.html" height="440" width="560" />

Definition:
<pre>timeframe=3M # set total time frame to 3 months
zoom=1M # select actual month
res=day1 # maximum resolution is 1 day

gtitle=Daily_Min/Max # name of graph
gheight=400 # height in pixels of graph
gwidth=550 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=minmax # type of graph
gcolwidth=50 # make bars 50% wide
gtrim=1

sid0=th0 sname0=temp_range sfill0=50 sline0=50 sselmin0=tempmin sselmax0=tempmax
sid1=th0 sname1=Ø_temp stype1=step ssel1=temp</pre>

==Radar Charts==
Meteoplug provides radar charts to display distribution of wind to 16 wind directions.

===Main Wind Direction===
This chart shows main wind directions during last month. Percentage show what percentage of time each direction has been registered.

<iframe key="meteoplug" path="examples/example-10.html" height="430" width="430" />

Definition:
<pre>timeframe=-1M # set total time frame to previous month
dirlist=N,NNO,NO,ONO,O,OSO,SO,SSO,S,SSW,SW,WSW,W,WNW,NW,NNW

gtitle=Main_Wind_Direction # name of graph
gheight=400 # height in pixels of graph
gwidth=400 # width in pixels of graph
glunit=_% # show percent as unit on axis and balloons
gtype=radar% # radar graph shows directional distribution in percent
res=day1

sid0=wind0 sfill0=20 sname0=main_wind_dir ssel0=maindir sprec0=0</pre>

===Direction of Highest Gust Speed per Day===
This chart shows direction direction of highest gust speed for days of last month. Radar chart displays number of days per direction

<iframe key="meteoplug" path="examples/example-11.html" height="430" width="430" />

Definition:
<pre>timeframe=-1M # set total time frame to previous month

gtitle=Direction_of_Highest_Gust_Speeds # name of graph
gheight=400 # height in pixels of graph
gwidth=400 # width in pixels of graph
glunit=_days # show "days" as unit on axis and balloons
gtype=radar # radar graph shows directional distribution in days
res=day1

sid0=wind0 sfill0=20 sname0=top_gust_speed ssel0=highdir sprec0=0</pre>

==Color Maps==
Meteoplug can draw colored 2-dimensional arrays, where color indicates a values (like temperature, humidity, wind speed, etc). Rows represent duration of a day, which can be a resolution between min5 and day1, and each columns represents a signle day. These color maps are useful to compare values at a certain time between neigbouring days.

===Color Map for Temperatures in Summer 2008===
This chart presents temperatures of days of summer 2008. First column is 1st of June 2008, last column is 31th of August 2008. Temperature colors start from blue (cold), via green, yellow to red (hot). Time resolution is 1 hour.

Color maps are interactive, when you move the cursor on the map a red balloon will show selected date, time and represented value.

<iframe key="meteoplug" path="examples/example-12.html" height="250" width="800" />

Definition:
<pre>timeframe=20080601000000-20080901000000 # select Jun/Jul/Aug of 2008
res=hour1 # user hourly values
gtrim=0 # no trimming

gtitle=Heatmap_Summer_2008 # name of graph
gheight=200 # height in pixels of graph
gwidth=550 # width in pixels of graph (will be adapted to height in colormap mode
gtype=colormap # type of graph
glunit=°C # unit to be displayed in balloon
glmin=-15 # lower temperature boundary
glmax=35 # upper temperature boundary
grmin=#0022AA # select a modest blue as color for lower boundary
grmax=#FF0000 # select pure red as color for upper boundary
grunit=#EEEEEE # select a light grey for periods without data

sid0=th0 sname0=Temp ssel0=temp # select temperature of outdoor sensor (th0)</pre>

==Distribution Charts==
Meteoplug can generate graphs, that how how long a sensor has reported values in a certain range. This allows a separation of weather data into buckets that represent defined value ranges. Each bucket represents the total duration of sensor data in value range defined by the bucket. This kind of data analysis allows to compute an expectation how much power a wind power generating device will produce at that location. This kind of "Weibull" analysis is not just useful for wind sensors, but can also be used for other sensor data.

===Weibull Distribution as Graph===
Attached chart displays how long wind speed of ranges 0.0-0.5, 0.5-1.0, ... (and so on) have been measure at my location in complete January 2010. Red curve displays averaged wind speeds, blue lines is based on wind gust measurement.

<iframe key="meteoplug" path="examples/example-19.html" height="340" width="560" />

Definition:
<pre>timeframe=20100101000000-20100201000000 # set total time frame to January 2010
res=min15

gtitle=Weibull_Distribution_Januray_2010 # name of graph
gheight=300 # height in pixels of graph
gwidth=550 # width in pixels of graph
gtype=line # type of graph
glunit=_h # unit of y-axis
grunit=%.1f_m/s # format string for x-axis data
xymode=40 # set xy-mode and define 40 iterations
xstart=0.0 # start value for x-axis
xinc=0.5 # increment
gcolwidth=20 # width of bars
gtrim=0 # don't skip buckets with zero counts

sid0=wind0 sunit0= sname0=Wind_Duration ssel0=wind sprec0=1 sfactor0=0.25 sfill0=20 # wind
sid1=wind0 stype1=bar sunit1= sname1=Gust_Duration ssel1=gust sprec1=1 sfactor1=0.25 sline1=50 # gust
</pre>

==Non-Interactive Graphs==
Beside interactive Flash graphs presented in sections 1-4, Meteoplug also supports a graphing feature that produces static graphs in terms of ".png" images. Meteoplug makes use of [http://www.gnuplot.info gnuplot] to achieve this. Definition language for these non-interactive graphs is mostly as explained for interactive graphs before.

Advantage of non-interactive graphs is, that they can be included into a users homepage by HTML IMG-tag. It does not need any Flash Player or JavaScript and will, therefore, even work fine on mobile browsing devices.

===Line Graph: Yesterdays Temperature and Humidity===
Please have a look at this simple but detailed line graph that explains yesterdays temperature, humidity and dew point.

[[File:example-15.png]]

Definition:
<pre>timeframe=-1D # view yesterday's data

gtitle=Yesterdays_Temperature_and_Humidity # name of graph
gheight=450 # height in pixels of graph
gwidth=700 # width in pixels of graph
glunit=°C # unit of left y-axis
grunit=% # unit of right y-axis
gtype=gpline # type of graph
gtrim=0 # don't trim
grmin=0 # set min of right y-axis to 0
grmax=100 # set max of right y-axis to 100
gfontsize=9 # set font size to 9pt

ggpformat=set_locale_"en__US" # use US-English weekday/month descriptors

sid0=th0 swidth0=2 sname0=temp ssel0=temp # sensor 0, temperature, thick line (2px)
sid1=th0 sname1=dew ssel1=dew # sensor 1, dew point
sid2=th0 sprec2=0 syaxis2=r sname2=hum ssel2=hum # sensor 2, humidity, use right y-axis, no decimals
</pre>

===Bar Graph: Monthly Rainfall of Last 3 Years===
Graph below outlines rainfall of months of last 3 years in mm and number of rainy days per month. Unfortunately, summer brings more rain than winter, which is a characteristic of weather in northern Germany.

[[Image:example-16.png]]

Definition:
<pre>timeframe=-3Y # set total time frame to last 3 years
res=month1 # get monthly data

gtitle=Rain # name of graph
gheight=300 # height in pixels of graph
gwidth=750 # width in pixels of graph
glunit=mm # unit of left y-axis
grunit=_days # unit of right y-axis
gtype=gpbar # type of graph
gtrim=1

sid0=rain0 sfill0=40 sname0=rain_fall ssel0=total # sensor 0, rainfall # sensor 0, total rainfall
sid1=rain0 ssmooth1=1 stype1=line syaxis1=r sname1=rain_on ssel1=days # sensor 1, rainy days
</pre>

===Needle and Point Graph: Wind of 3 Days===
Graph below outlines average wind speed as filled area, max gust speed as needles and main wind direction as points. As you see direction of strongest wind during that time was 270°, which is west.

[[Image:example-17.png]]

Definition:
<pre>timeframe=3D # set total time frame to 3 days
res=hour1 # get hourly data

gtitle=Rain # name of graph
gheight=300 # height in pixels of graph
gwidth=750 # width in pixels of graph
glunit=km/h # unit of left y-axis
grunit=° # unit of right y-axis
gtype=gpline # type of graph
grmin=0 # set minimum of right y-axis to 0
grmax=360 # set maximum of right y-axis to 360

ggpformat=set_key_out_horiz|set_key_bot_center|set_y2tics_(0,45,90,135,180,225,270,315,360)

sid0=wind0 sfill0=20 sname0=wind_speed ssel0=wind # sensor 0, wind speed
sid1=wind0 stype1=gpneedle sname1=gust_max ssel1=gustmax # sensor 1, max gust speed
sid2=wind0 stype2=gppoint syaxis2=r swidth2=2 sname2=wind_dir ssel2=maindir sfactor2=22.5 sprec2=0
</pre>

==Tables==
Meteoplug provides a table generation feature when selecting "table" as chart type. Design and content of table can be widely adapted.

===Monthly Report===
This table displays central Weather data of January 2010. Layout an content of table can be adapted in wide ranges.

<iframe key="meteoplug" path="examples/example-7.html" height="900" width="560" />

Definition:
<pre>timeframe=-1M # set total time frame to previous month
res=day1

gtitle=Monthly_Report # name of graph
gheight=800 # height in pixels of graph
gwidth=550 # width in pixels of graph
gtype=table # type of graph
glunit=Date # set header string for first column
grunit=%e._%b # set date format string for notation on months (ala gnu c strftime)
gtrim=0
gtablestyle=cellpadding=4_style="background-color:#fafafa;border-collapse:collapse"
gtdheadstyle=style="background-color:#336699;font-weight:bold;text-align:center;color:#FFFFFF;"
gtdstyle=style="border:1px_#CCCCCC_solid;text-align:right;font-size:.9em;color:#404040;"

sid0=th0 sunit0=°C sname0=Temp<br>Ø ssel0=temp
sid1=th0 sunit1=°C sname1=Temp<br>Max ssel1=tempmax
sid2=th0 sunit2=°C sname2=Temp<br>Min ssel2=tempmin
sid3=th0 sunit3=% sname3=Hum ssel3=hum sprec3=0
sid4=thb0 sunit4=hPa sname4=Press ssel4=seapress
sid5=rain0 sunit5=mm sname5=Rain ssel5=total
sid6=wind0 sunit6=km/h sname6=Wind<br>Ø ssel6=wind sfactor6=3.6
sid7=wind0 sunit7=km/h sname7=Wind<br>Max ssel7=gustmax sfactor7=3.6</pre>

===Rain Last Year===
This table lists last year's rain fall. Layout is very minimalistic, compared to previous example.

<iframe key="meteoplug" path="examples/example-8.html" height="420" width="560" />

Definition:
<pre>timeframe=-1Y # set total time frame to previous year
res=month1

gtitle=Rain_Day_Last_Year_Report # name of graph
gheight=800 # height in pixels of graph
gwidth=550 # width in pixels of graph
gtype=table # type of graph
glunit=Month
grunit=%Y-%m
gtrim=0

gtablestyle=cellpadding=3_border=1_bgcolor=#eeeeee
gtdstyle=align=right

sid0=rain0 sunit0= sname0=Rain_Days ssel0=days sprec0=0
sid1=rain0 sunit1=_mm sname1=Rain_Fall ssel1=total
sid2=rain0 sunit2=_mm/h sname2=Maximum_Rain_Rate ssel2=ratemax
sid3=rain0 sunit3= sname3=Date_of_Heaviest_Rain ssel3=ratemaxtime sprec3=16</pre>

==CSV Exports==
Meteoplug provides a csv export generation feature when selecting "export" as chart type. Design and content of export data can be widely adapted.

===Weather Display Export Format===
This export definition generates a Weather Display compatible export file with data of January 2010. Data of that format can be imported as "12010lg.txt" into Weather Display.

Generated Data:
<pre style="background-color:#F0F0F0;">1 1 2010 0 0 -0.2 63 -6.3 999.7 5.1 7.0 90 0.00 -999 -999 -999
1 1 2010 0 5 -0.1 63 -6.4 999.8 4.5 5.8 90 0.00 -999 -999 -999
1 1 2010 0 10 -0.1 62 -6.6 999.7 4.5 7.0 90 0.00 -999 -999 -999
1 1 2010 0 15 -0.1 61 -6.7 999.8 4.5 5.4 90 0.00 -999 -999 -999
1 1 2010 0 20 -0.1 60 -7.0 999.8 4.7 5.8 90 0.00 -999 -999 -999
1 1 2010 0 25 -0.1 59 -7.2 999.8 4.4 5.4 112 0.00 -999 -999 -999
1 1 2010 0 30 -0.1 58 -7.4 999.7 4.8 6.2 90 0.00 -999 -999 -999
1 1 2010 0 35 -0.1 57 -7.6 999.7 4.2 5.4 90 0.00 -999 -999 -999
1 1 2010 0 40 -0.1 57 -7.6 999.8 4.3 5.4 90 0.00 -999 -999 -999
1 1 2010 0 45 -0.1 57 -7.6 999.8 4.4 5.4 90 0.00 -999 -999 -999
1 1 2010 0 50 -0.1 57 -7.6 999.8 4.4 5.4 90 0.00 -999 -999 -999
1 1 2010 0 55 -0.1 56 -7.8 999.7 4.1 5.4 112 0.00 -999 -999 -999
1 1 2010 1 0 -0.1 57 -7.7 999.8 3.9 5.1 90 0.00 -999 -999 -999
1 1 2010 1 5 -0.2 57 -7.7 999.8 3.6 5.1 90 0.00 -999 -999 -999
1 1 2010 1 10 -0.2 57 -7.7 999.8 3.3 5.1 90 0.00 -999 -999 -999
1 1 2010 1 15 -0.2 57 -7.7 999.8 3.2 4.3 90 0.00 -999 -999 -999
1 1 2010 1 20 -0.2 57 -7.7 999.7 2.8 3.5 112 0.00 -999 -999 -999
1 1 2010 1 25 -0.2 58 -7.6 999.8 2.9 4.7 90 0.00 -999 -999 -999
1 1 2010 1 30 -0.2 58 -7.5 999.8 2.6 3.5 90 0.00 -999 -999 -999
1 1 2010 1 35 -0.3 58 -7.6 999.8 3.2 5.1 90 0.00 -999 -999 -999
1 1 2010 1 40 -0.3 58 -7.6 999.8 3.2 4.7 90 0.00 -999 -999 -999
1 1 2010 1 45 -0.3 58 -7.6 999.7 3.1 4.7 90 0.00 -999 -999 -999
1 1 2010 1 50 -0.3 58 -7.6 999.8 3.7 5.1 90 0.00 -999 -999 -999
1 1 2010 1 55 -0.3 58 -7.5 999.7 3.4 5.1 90 0.00 -999 -999 -999
1 1 2010 2 0 -0.3 59 -7.4 998.8 4.1 5.4 90 0.00 -999 -999 -999
1 1 2010 2 5 -0.3 58 -7.6 998.7 4.0 5.4 112 0.00 -999 -999 -999
1 1 2010 2 10 -0.4 58 -7.7 998.7 3.9 5.1 90 0.00 -999 -999 -999
1 1 2010 2 15 -0.4 58 -7.7 998.7 3.6 4.7 90 0.00 -999 -999 -999
1 1 2010 2 20 -0.4 58 -7.8 998.8 4.7 6.6 90 0.00 -999 -999 -999
...</pre>

Definition:
<pre>timeframe=20100101000000-20100131235959
res=min5

gtitle=WD-Export # name of graph
gtype=export # type of graph
glunit=_ # delimiter
grunit=%-d_%-m_%Y_%-H_%-M # date/time stamp
gtrim=1 # cut empty records at start and end

sid0=th0 sname0=-999 ssel0=temp sprec0=1 # temp
sid1=th0 sname1=-999 ssel1=hum sprec1=0 # hum
sid2=th0 sname2=-999 ssel2=dew sprec2=1 # dew
sid3=thb0 sname3=-999 ssel3=seapress sprec3=1 # sea pressure
sid4=wind0 sname4=-999 ssel4=wind sfactor4=1.944 sprec4=1 # wind in kt
sid5=wind0 sname5=-999 ssel5=gustmax sfactor5=1.944 sprec5=1 # gust in kt
sid6=wind0 sname6=-999 ssel6=maindir sfactor6=22.5 sprec6=0 # wind dir
sid7=rain0 sname7=-999 ssel7=total sprec7=2 sunit7=_-999_-999_-999 # rainfall</pre>

===Weibull Wind Distribution Data===
Following definition of an export format delivers Weibull wind distribution data for January 2010. This data is helpful to predict expected electric power generation of certain equipment at that location. First column displays wind speed in m/s, second column gives duration in hours.

Generated Data:
<pre style="background-color:#F0F0F0;">
0.0,359.8
0.5,42.2
1.0,63.0
1.5,99.8
2.0,81.8
2.5,32.2
3.0,17.0
3.5,24.0
4.0,13.0
4.5,9.0
5.0,2.0
5.5,0.0
6.0,0.0
...</pre>

Definition:
<pre>timeframe=20100101000000-20100201000000 # set total time frame to January 2010
res=min15 # go with time buckets of 15 minutes

gtitle=Weibull_Distribution_January_2010 # name of graph
gheight=800 # height in pixels of graph
gwidth=550 # width in pixels of graph
gtype=export # type of graph
glunit=, # set delimiter character
xymode=40 # set xy-mode and go with 40 samples
xstart=0.0 # start with 0.0 on first first row
xinc=0.5 # increment by 0.5
gtrim=0 # don't skip buckets with zero counts

sid0=wind0 sunit0= sname0= ssel0=wind sprec0=1 sfactor0=0.25 # 15 min buckets, divided by 4
</pre>

==Templates==
Meteoplug supports a template mechanism that allows you to fill weather data into a given HTML file and to report this modified HTML file to the requesting browser. Template mechanism can also be used for picture templates where a ImageMagick graphic definition can be modified with weather data and a picture file containing this data is returned to the requestor.

===HTML Templates===
Meteoplug allows to replace variables in HTML templates with data. This comes handy when you have web pages you want to have weather data filled in in. instead of calling the template page directly a Meteoplug chart definition is called that delivers the template file with variables filled in.

Content of template file stored as http://www.meteoplug.com/examples/example-15.html
<pre><html>
<head>
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<title>Meteoplug HTML Mini-Dashboard</title>
</head>
<body bgcolor="#ffffff">
<table border="1" cellpadding="0" cellspacing="2" width="550">
<tr>
<td>Actual Temperature</td>
<td>[actual_min5_th0_temp_1:--] °C ([actual_min5_th0_temp_1_1.8_32:--] °F)</td>
</tr>
<tr>
<td>Todays Max Temperature</td>
<td>[actual_day1_th0_tempmax_1:--] °C ([actual_day1_th0_tempmax_1_1.8_32:--] °F)
at [actual_day1_th0_tempmaxtime_11_5:--]</td>
</tr>
<tr>
<td>Todays Min Temperature</td>
<td>[actual_day1_th0_tempmin_1:--] °C ([actual_day1_th0_tempmin_1_1.8_32:--] °F)
at [actual_day1_th0_tempmintime_11_5:--]</td>
</tr>
<tr>
<td>This Month's Max Temperature</td>
<td>[actual_month1_th0_tempmax_1:--] °C ([actual_month1_th0_tempmax_1_1.8_32:--] °F)
at [actual_month1_th0_tempmaxtime:--]</td>
</tr>
<tr>
<td>This Month's Min Temperature</td>
<td>[actual_month1_th0_tempmin_1:--] °C ([actual_month1_th0_tempmin_1_1.8_32:--] °F)
at [actual_month1_th0_tempmintime:--]</td>
</tr>
<tr>
<td>Actual Humidity</td>
<td>[actual_min5_th0_hum_0:--] %</td>
</tr>
<tr>
<td>Actual Pressure</td>
<td>[actual_min5_thb0_seapress_1:--] hPa ([actual_min5_thb0_seapress_2_0.02952] in/Hg)</td>
</tr>
<tr>
<td>Actual Average Wind Speed</td>
<td>[actual_min5_wind0_wind_1_3.6] km/h ([actual_min5_wind0_wind_1_2.237] mp/h)</td>
</tr>
<tr>
<td>Todays Rainfall</td>
<td>[actual_day1_rain0_total_1:--] mm ([actual_day1_rain0_total_2_0.0394:--] in)</td>
</tr>
<tr>
<td>This Month's Rainfall</td>
<td>[actual_month1_rain0_total_1:--] mm ([actual_month1_rain0_total_2_0.0394:--] in)</td>
</tr>
</table>
</body>
</html></pre>

Meteoplug chart definition used to deliver a version of the template with data filled in:

<pre>template=http://www.meteoplug.com/examples/example-15.html</pre>

Result:

<websiteFrame>
website=http://www.meteoplug.com/examples/example-16.html
align=top
border=0
height=265
width=565
scroll=no
</websiteFrame>

===Picture Templates===
Meteoplug can generate picture files (i.e.: png, jpg) according to ImageMagick convert program specifications. You can find details on available parameters at http://www.imagemagick.org/script/convert.php.
Picture template is a selection of convert options. Most of the options are available with Meteoplug, if you select one not available an error message will be prompted. Specification is just a bunch of options plus an initial picture to start with (like "gradient:white-lightblue". File operations and some special characters are forbidden and will throw an error.
By using ImageMagick's convert Meteoplug gains an enormous richness of options to generate pictures.

===="Weather Data Thumb" Example====

Meteoplug chart definition used to derive a png picture from the template above with data filled in. This example makes use of the "inline" directive, where template data is stored inside the chart definition:
<pre style="white-space:normal;">picture=png
template=inline
-size 150x170 gradient:white-lightblue -bordercolor black -border 1 -fill white -pointsize 9 -draw "text 5 165 'powered by MeteoPlug'" -fill black -pointsize 10 -draw "text 30 15 '[actual_min5_misc_uploadlocaltime_0_16#3600]'" -pointsize 11 -draw "text 5 30 'Luft:'" -draw "text 80 30 '[actual_min5_th*_temp#3600]°C'" -draw "text 5 45 'Wind:'" -draw "text 80 45 '[actual_min5_wind*_wind_1_3.6#3600] km/h'" -draw "text 5 60 'Windspitze:'" -draw "text 80 60 '[actual_day1_wind*_gustmax_1_3.6#86400] km/h'" -draw "text 5 75 'Feuchte:'" -draw "text 80 75 '[actual_min5_th*_hum_0#3600]%'" -draw "text 5 90 'Barometer:'" -draw "text 80 90 '[actual_min5_thb*_seapress#3600] hPa'" -draw "text 5 105 'Regen/1h:'" -draw "text 80 105 '[actual_hour1_rain*_total_0#7200] mm'" -draw "text 5 120 'Regen/24h:'" -draw "text 80 120 '[actual_day1_rain*_total_0#86400] mm'" -draw "text 5 135 'Solar:'" -draw "text 80 135 '[actual_min5_sol*_rad_0#3600] W/qm'" -draw "text 5 150 'UV:'" -draw "text 80 150 '[actual_min5_uv*_uvi_1#3600] uvi'"
</pre>

Result:

<iframe key="meteoplug" path="examples/thumb.png" height="190" width="170" />

===="Webcam Overlay" Example====

Meteoplug's picture template feature can also be used to embed textual overlay onto pictures already existing in the Internet (i.e. webcam output). Example below modifies a published webcam picture by a bottom line stating temperature, wind chill and daily rain fall.

Content of picture template file stored as http://www.meteoplug.com/examples/overlay.def:
<pre style="white-space:normal;">http://www.hansaport.de/webcam.jpg?0.41418396601110785
-fill black -draw "fill-opacity 0.5 rectangle 0 463 640 480"
-pointsize 9 -fill orange -draw "text 5 475 'MeteoPlug'"
-pointsize 11 -fill lightgrey -draw "text 70 475 '[actual_min5_misc_uploadlocaltime_0_16#3600]'"
-fill white -draw "text 180 475 'Temp: [actual_min5_th*_temp_1#3600] °C Wind Chill: [actual_min5_wind*_chill_1#3600]°C Rain Today: [actual_day1_rain*_total_1#86400] mm'"
</pre>

Meteoplug chart definition that produces the overlayed webcam picture:

<pre>template=http://www.meteoplug.com/examples/overlay.def
picture=jpg</pre>

Result (stored image, not live):

<iframe key="meteoplug" path="examples/overlay.jpg" height="495" width="660" />

==Maps==
When users have given their station a "map name" on settings page their station can appear on maps the user itself or other users of the same group are requesting. When you don't have a group account your station is always attached to the default group. If you have a Meteoplug group account, only yourself can see the other stations of your group on the map. By that the position and data of your group's stations is not visible to other users.

Meteoplug's map feature is based on Google Maps. Registered Meteoplug accounts appear as red markers, non registered Meteohub stations that send up weather data to Meteoplug are represented as blue markers. Accounts going through registration process or with an outdated activation are displayed in yellow. Apart from numerical data displayed on the right when the mouse touches a marker, registered accounts also display an summarizing interactive graph when being clicked.

This map definition build a map and defines the sensors to be displayed on the right. You can change this definition to your needs, if you want to display other values or different map sizes and positions:

<pre>gtitle=Maps # name of graph
gheight=600 # height in pixels of graph
gwidth=750 # width in pixels of graph
gtype=map # type of graph
zoom=4

gtitle=Maps
sid0=th* sunit0=_°C sname0=Temperature ssel0=[actual_min5_th0_temp_1:--]
sid1=th* sunit1=_% sname1=Humidity ssel1=[actual_min5_th0_hum_0:--]
sid2=thb* sunit2=_hPa sname2=Pressure ssel2=[actual_min5_thb0_seapress_1:--]
sid3=wind* sunit3=_km/h sname3=Wind_Speed ssel3=[actual_min5_wind0_wind_1_3.6:--]
sid4=rain* sunit4=_km/h sname4=Todays_Gust ssel4=[1D_day1_wind0_gustmax_1_3.6:--]
sid5=rain* sunit5=_km/h sname5=Monthly_Gust ssel5=[1M_month1_wind0_gustmax_1_3.6:--]
sid6=rain* sunit6=_km/h sname6=Yearly_Gust ssel6=[1Y_year1_wind0_gustmax_1_3.6:--]
sid7=rain* sunit7=_mm sname7=Todays_Rain ssel7=[1D_day1_rain0_total_1:--]
sid8=rain* sunit8=_mm sname8=Monthly_Rain ssel8=[1M_month1_rain0_total_1:--]
sid9=rain* sunit9=_mm sname9=Yearly_Rain ssel9=[1Y_year1_rain0_total_1:--]
sid10=th* sunit10=_°C sname10=Monthly_Max_Temp ssel10=[1M_month1_th0_tempmax_1:--]
sid11=th* sunit11=_°C sname11=Monthly_Min_Temp ssel11=[1M_month1_th0_tempmin_1:--]
sid12=th* sunit12=_°C sname12=Yearly_Max_Temp ssel12=[1Y_year1_th0_tempmax_1:--]
sid13=th* sunit13=_°C sname13=Yearly_Min_Temp ssel13=[1Y_year1_th0_tempmin_1:--]
</pre>

Result (needs a moment to be computed):

<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=79757a776920306d0e763b272b2426" height="610" width="760" />

==Live Data==
Based on FusionWidget Toolkit Meteoplug provides gauges, dials and meters to display weather station live data. Below you see an example of using template "*instruments-black" with one of the test weather stations. Live data visualiziation can be done via Flash or Javascript.

<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=e3e7e2e3eff1b3babbb7bef0adab8e848f967297918f89f5f8b3b9bfa8b1bdb8b0a1bab6be&engine=js" height="360" width="620" />

==Hardcore Examples==
This section presents some more advanced examples for a user who is familiar with basic chart definition techniques.

===Tables With Icons===
Meteoplug allows to embed icons according to forecast values and moon phases. "phaseiconlist" and "fciconlist" are used to point to icons. Adders "width" and "height" are used to scale down icons.

Definition:

<pre>timeframe=20100101000000-20100131235959
phaseiconlist=http://www.meteoplug.com/mp0.png_width=20_height=20,http://www.meteoplug.com/mp1.png_width=20_height=20,http://www.meteoplug.com/mp2.png_width=20_height=20,http://www.meteoplug.com/mp3.png_width=20_height=20,http://www.meteoplug.com/mp4.png_width=20_height=20,http://www.meteoplug.com/mp5.png_width=20_height=20,http://www.meteoplug.com/mp6.png_width=20_height=20,http://www.meteoplug.com/mp7.png_width=20_height=20
fciconlist=http://www.meteoplug.com/fc0.png_width=20_height=20,http://www.meteoplug.com/fc1.png_width=20_height=20,http://www.meteoplug.com/fc2.png_width=20_height=20,http://www.meteoplug.com/fc3.png_width=20_height=20,http://www.meteoplug.com/fc4.png_width=20_height=20,http://www.meteoplug.com/fc5.png_width=20_height=20,http://www.meteoplug.com/fc6.png_width=20_height=20,http://www.meteoplug.com/fc7.png_width=20_height=20,http://www.meteoplug.com/fc8.png_width=20_height=20
res=day1

gtitle=January_2010_Report
gheight=1500 # height in pixels of graph
gwidth=550 # width in pixels of graph
gtype=table # type of graph
glunit=Date
grunit=%e._%b
gtrim=0
gtablestyle=cellpadding=4_style="background-color:#fafafa;border-collapse:collapse"
gtdheadstyle=style="background-color:#336699;font-weight:bold;text-align:center;color:#FFFFFF;"
gtdstyle=style="border:1px_#CCCCCC_solid;text-align:right;font-size:.9em;color:#404040;"

sid0=th0 sunit0=°C sname0=Temp ssel0=temp
sid1=misc sunit1= sname1=Sunrise ssel1=sunrisestandardlocaltime
sid2=misc sunit2= sname2=Sunset ssel2=sunsetstandardlocaltime
sid3=misc sunit3= sname3=Moon_Phase ssel3=lunarphasetext
sid4=misc sunit4= sname4=Phase<br>Icon ssel4=lunarphaseicon
sid5=thb0 sunit5= sname5=Forecast ssel5=forecasttext
sid6=thb0 sunit6= sname6=Forecast<br>Icon ssel6=forecasticon
</pre>

Result:

<iframe key="meteoplug" path="examples/example-17.html" height="980" width="575" />

===Multiple Graphs in one Chart===
Meteoplug allows to position multiple graphs stacked one over the over in one chart sharing one common time line. Global definitions per graph (all start with "g") are added by a number to express which graph is mentioned. If the number is missing, Meteoplug assumes that first graph (with implicit number "0") should be used. Sensor definition (all start with "s") allow for an additional specification of the graph where the sensor should belong to. Example: "sid1_2=th0" specifies a sensor "th0" to be accessed as sensor "2" of graph "1". "sid3" is a simplified notation of "sid0_3" as long as just one graph (with number "0") is defined.

Definition:

<pre>timeframe=-3M # set total time frame to 3 months before today until today
zoom=MAX # select full scope
res=day1 # get data per day

gtitle0=Temperature
gheight0=150 gwidth0=700 glunit0=°C gtype0=line
sid0_0=th0 ssmooth0_0=1 sname0_0=Temp scolor0_0=880000 sfill0_0=10 ssel0_0=temp
sid0_1=th0 ssmooth0_1=1 sname0_1=Temp_Max scolor0_1=FF0000 sline0_1=40 ssel0_1=tempmax
sid0_2=th0 ssmooth0_2=1 sname0_2=Temp_Min scolor0_2=8800FF sline0_2=40 ssel0_2=tempmin

gtitle1=Pressure
gheight1=150 gwidth1=700 glunit1=hPa gtype1=line
sid1_0=thb0 ssmooth1_0=1 sname1_0=Press scolor1_0=008800 sfill1_0=10 ssel1_0=seapress
sid1_1=thb0 ssmooth1_1=1 sname1_1=Press_Max scolor1_1=00FF00 sline1_1=40 ssel1_1=seapressmax
sid1_2=thb0 ssmooth1_2=1 sname1_2=Press_Min scolor1_2=0088FF sline1_2=40 ssel1_2=seapressmin

gtitle2=Rain
gheight2=100 gwidth2=700 glunit2=mm gtype2=bar
sid2_0=rain0 scolor2_0=AADDFF sfill2_0=70 sline2_0=100 sname2_0=Rain_Fall ssel2_0=total

gtitle3=Wind
gheight3=150 gwidth3=700 glunit3=km/h gtype3=line
sid3_0=wind0 ssmooth3_0=1 sname3_0=Wind scolor3_0=000088 sfill3_0=10 ssel3_0=wind
sid3_1=wind0 ssmooth3_1=1 sname3_1=Gust_Max scolor3_1=0000FF sfill3_1=10 sline3_1=80 ssel3_1=gustmax</pre>

Result:

<iframe key="meteoplug" path="examples/example-18.html" height="580" width="715" />

===Interactive Selection of Time Periods and Graphs===
This example makes use of predefined chart template "__dashboard-1", which allows to select a certain day by a JavaScript calendar application, plus selection a period of time (day, week, month, year) on the left side and selection of a chart type. Charts can be replaced by individual charts, if you like.

Live example of "__dashboard-1" of my weather station:

<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=a5a6a0abacbdadb0faedc1cec0cbd7c4c1fbfc84cfc5fbecf5f9f4fcedf6f2fa&engine=js" height="950" width="825" />

FAQ

2024-12-04T17:08:10Z

Admin: Created page with "__TOC__ == How is Meteoplug related to Meteohub? == To say it a bit simplified in just one sentence: Meteoplug is a cloud-based version of Meteohub. Meteohub has a focus to integrate a complete weather server including interface to weather stations, storage of data and computation of derived weather data and graph drawing into one single computing device that consumes below 10 watts. The challenge for a Meteohub system is to find a cheap and low power demanding hardwar..."

__TOC__
== How is Meteoplug related to Meteohub? ==
To say it a bit simplified in just one sentence: Meteoplug is a cloud-based version of Meteohub.

Meteohub has a focus to integrate a complete weather server including interface to weather stations, storage of data and computation of derived weather data and graph drawing into one single computing device that consumes below 10 watts.
The challenge for a Meteohub system is to find a cheap and low power demanding hardware setup that provides 4GB storage and enough processing power to handle data computation and graph generation. All Meteohub platforms do somehow fit into this but we reached something like a roadblock here, that prevents going significantly down in hardware costs and power demand, the two most important cost drivers when running such a system.

Meteoplug goes a step further by splitting the universal weather server approach of Meteohub into a client that just needs minimal computing power without need of permanent storage and an application server in the internet that receives logged data from the client and does all the computation and graphing requested by the user. While the client is an individual piece of hardware, the server gets shared by all users, although it provides separate individual services to each user.

When you look at the web interfaces of Meteohub and Meteoplug you will find that they are quite similar. This is because the applications share a lot of code which allows to more easy maintain both software development paths. A positive side effect is for example, that Meteoplug can handle all the weather stations that are compatible with Meteohub. So you have a lot of weather station support right on from the beginning. It is planned that future weather stations will also be available for both development paths.

== Can I feed weather data from a Meteohub or Meteobridge to Meteoplug server? ==
Yes. By selecting corresponding data upload option on Meteohub's settings page or Meteobridge's weather network page. Data upload bound to a fixed schedule (every 10 minutes). You also need to create an account at https://www.meteoplug.com/cgi-bin/meteoplug.cgi to have data logged.

Meteohub:<BR>
[[File:Meteohub-data-upload.png]]

Meteobridge: <BR>
[[File:meteobridge.png]]

== Can I import data from my Meteohub to Meteoplug server? ==
Yes, it is possible to upload Meteohub logged raw data (to be found as files named "/public/weather/YYYYMM/raw") to Meteoplug server. You need to have an account at Meteoplug server. Upload of data can be done as text or in a compressed format (.gz, .zip, .bz2). Import feature is located on "Inspect Data" tab of Meteoplug.

[[File:Meteohub-import-data.png‎]]

==Where can I buy a Meteoplug client?==
Most users buy hardware as lined out in hardware section themself and flash the Meteoplug image onto it. If you don't want to do that (because you will not like using warranty by flashing a device), you can check with "swisswetter.com" who sell Meteoplug clients including a one yoear license as "weatherBoxx Light".

Once you have this piece of client hardware you can test Meteoplug 30 days without a license for free. For operation past this demo period you will have to purchase a Meteoplug license.

== Is my weather data save on Meteoplug? ==
Meteoplug does not guarantee that data will not be lost and/or will not be copied by any third party. That sounds poor, but please realize that it is "just" weather data, not your bank account. Therefore, resilience and data security are handled at a reasonable level for that purpose.

In regard to data security and privacy Meteoplug protects your personal data and weather data by a password you define when creating an account. Password can be changed by you, any time you like. Your account password will be stored as a hash in the database. In case of a security breech that might grant access to the database, just these hashes are stolen and your password is not compromised in general. Meteoplug web interface makes use of HHTPS, which gives additional security by preventing that netto data gets inspected on its way through the internet. Meteoplug is hosted on a dedicated root server, which also reduces chances of being hacked. However, this all just reduces risks but does not eliminate these. When you put it to the yes-or-no question if Meteoplug can guarantee data security, the answer is NO. Don't use Meteoplug when your data is vital in any purpose.

In regard to availability Meteoplug also cannot guarantee that server outages won't happen. Meteoplug server runs on mirrored (Raid 1) disks, which might reduce risk of down time by disk failure but other system faults might bring the system to a stand still at anytime. There is no backup system jumping in when Meteoplug server has died. Repair times can vary, no promises on services levels according availability can be given. This also might sound poor, but Meteoplug clients will do local storage of weather data for a couple of days until internal buffers wrap around and data is finally lost. When Meteoplug server is back online, clients will report buffered data. As a result there is a good chance that no data is lost due to a limited server outage.

In regard to protection against data loss Meteoplug also cannot guarantee anything (as you might have already expected). Apart from Raid 1 which covers data loss caused by single disk failures Meteoplug does a backup of a day's logged raw data onto a separate backup server every night. These incremental backups allow for reconstruction and rebuilding of derived data. However, shit can happen and these backup mechanisms are far from being perfect. Meteoplug will also drop raw data (because of space limitations) after two years, but you will get notice about that and you can download raw data and store it locally on your PC. All derived data used for computation and graphing will not be deleted at all (not reflecting the risk of loosing data by accident). Meteoplug allows to download logged raw data to your PC (on "Inspect Data" tab), so you can do your own data backup.

As you see, Meteoplug is not a suitable solution for handling mission critical data. '''You are explicitly not allowed to use Meteoplug in any high risk situations or environments, where malfunction can have a noticeable impact''', because it is not designed for scenarios like that.

== Is my weather data visible for all Internet users? ==
You decide on that. In general your administration account is locked by a password und not public available. Access to your data can only be realized by graphing or other display functions. When designing these display functions you get an URL that shows the graph/data. This URL does not have your user name or graph name in it but is encoded in a certain way. Now it depends on you, if you publish this URL (for example by placing this inside an IFRAME on your home page) or if you just keep that in the bookmarks of your browser, just for your personal use. You can also send the URL to friends via email to give them a look at this one graph. Each graph has a unique and encrypted URL.

== How long will Meteoplug be offered as a service? ==
We don't plan to quit Meteoplug any time soon, but as all things in life Meteoplug will come to an end, might be replaced by a more advanced concept or might be quit because of technical problems (what we don't believe at the moment) or because it does not make sense anymore from an economical point of view. I can't look into the future, so I cannot foresee what will happen. At the moment it is my strong intent to have this service up and running and I am very optimistic that it will find a sufficient user base to cover costs in short- and midterm. I am also convinced that Meteoplug will be a success in the market, as it provides unique features and addresses coming demands of environmental friendly computing in an unmatched way so far. However, when it comes to a situation where shutting down the services is inevitable, users will get notice at least 3 months before quitting service. A refund of license fees will not be done, but honestly we are speaking about a quite unlikely situation at all. I am sure Meteoplug will make it's way. Please use the free trial period to convince yourself.

== How can I login to my Meteoplug client? ==
There should be no need to login to the Meteoplug client as it gets completely managed by Meteoplug server application. However, if you like you can browse to LAN IP of Meteoplug client and you will find something like the screen dump below. If you don't know your client's IP, you can consult your DHCP server (mostly your router) which might have a list of requested IPs. You can also consult Meteoplug server application. At tab "System Information" you will find the client's LAN IP.

Meteoplug client's web interface provides some status information. You can see system load, up-time, last update to Meteoplug server, actual sensor readings etc.

<center>[[FILE:client-webinterface.png]]</center>

==What happens to my data when license expires?==
I general Meteoplug purges data of not licensed accounts after 30 days. This is necessary to keep storage demand on Meteoplug server at a reasonable level. When you create a Meteoplug account for the first time, you are granted a free 30 day evaluation period. If you have had a Meteohub system running in a mode on settings page that already does upload to Meteoplug server, you will find weather data of last 30 days already being available for evaluation on Meteoplug. During 30 days evaluation period incoming data will be logged and evaluated. one or two days before license expires you will get a notification email, which tells you that evaluation period is going to expire. When you purchase additional usage time, logging and evaluation of data will go on until Meteoplug license expiration date. Once license period has expired, data will be kept in Meteoplug storage for another 30 days and your user account can be reactivated by purchasing a license. This gives you the chance to continue working with your account although you have passed license expiration date. 30 days after license expiration, all you weather and account data will be deleted from Meteoplug server. You will receive an email on this about 10 days before data will be finally removed. When 30 days reactivation period after license expiration has passed, your data has been gone and there is no way to get it back.

Meteoplug provides you an easy feature to download logged weather data of any month. It is highly recommended that you download these monthly data from time to time as this makes you independent from Meteoplug's necessary data removal features after license expiration.

Getting Started

2024-12-04T17:07:40Z

Admin: Created page with "This section describes how to setup your Meteoplug client hardware and how to get it connected to Meteoplug server. It also explains basic settings to be done. If your are interested in a complete functional description of Meteoplug, please have a look at the Documentation, also presented in the menu on the left. This section just describes the first steps to do, to get operational with Meteoplug. When you follow the steps on this page you should have a running Meteoplug..."

This section describes how to setup your Meteoplug client hardware and how to get it connected to Meteoplug server. It also explains basic settings to be done. If your are interested in a complete functional description of Meteoplug, please have a look at the Documentation, also presented in the menu on the left. This section just describes the first steps to do, to get operational with Meteoplug. When you follow the steps on this page you should have a running Meteoplug system without any major hassle.

==Setup of Meteoplug Client Hardware==
This section describes the steps necessary to setup your Meteoplug client.

===Meteohub System as Meteoplug Client===
When you have a Meteohub system this can also be used to feed Meteoplug server application. Please goto "settings tab and enable upload of data to Meteoplug server.
<center>[[File:Meteohub-data-upload.png]]</center>

Having done this you should notice the MAC of your Meteohub system. Meteohub displays the MAC on tab "System Information". You will need the MAC when registering for an account at Meteoplug server application.

===Meteobridge System as Meteoplug Client===
When you have a Meteobridge system (version 1.8 or newer) this can also be used to feed Meteoplug server application. Please goto tab "weather network" on your Meteobridge and select "Meteoplug Cloud Graphing", to have Meteobridge to send every single piece of weather data it receives from the weather station to the Meteoplug server. You can specify an upload intervall for complete sets of data and a live data update interval to feed dashboards. When you add a station name, your station will also be visible on the Meteoplug map.
<center>[[File:meteobridge.png]]</center>

Having done this you should notice the MAC of your Meteohub system. Meteohub displays the MAC on tab "System". You will need the MAC when registering for an account at Meteoplug server application.

===Meteoplug Clients TL-MR3020, TL-WR703N and WL-330N3G===
Tiny and cheap TL-MR3020 and TL-WR703N platforms from TP-Link and WL-330N3G from ASUS are well supported by openwrt project. Openwrt-based Meteoplug client software is provided as a file that can be directly uploaded from a stock TL-MR3020 or TL-WR703N as a new firmware. By doing so you will void the warranty TP-Link/ASUS provides for the unit, but havng the cheap price in mind you will certainly not face a substantial financial risk by that.

====Flashing Meteoplug Client Firmware to TL-MR3020====
Please consult the TP-Link manual to understand how to get access with your browser to its web interface. What the manual will tell you is basically that you have to connect your PC/Laptop via ethernet cable, and log in to the router's web interface (IP is 192.168.0.254, login name is "admin", password: "admin").

Meteoplug firmware has to be installed, exactly like a firmware from TP-Link. Please use Meteoplug-Client Image [http://www.meteohub.de/files/meteoplug-tl-mr3020-v1.4.bin meteoplug-tl-mr3020-v1.4.bin]. Please make sure path name is very short and ends with ".bin", otherwise router might not accept the firmware image file.
Wait until unit restarts. After that it will be a Meteoplug client in standard configuration (LAN mode).

When you ever decide to revert Meteoplug client back to a stock like TL-MR3020 router, you can follow steps explained in [http://wiki.openwrt.org/toh/tp-link/tl-mr3020#restoring.original.firmware this] posting. Please understand that all you do here is at your own risk, nothing guaranteed.

====Flashing Meteoplug Client Firmware to TL-WR703N====
As TL-WR703N does only come with a Chinese web interface, it might be a bit tricky to find the right menu item to initiate firmware update. First you have to login with your browser. To achieve that you have to connect your PC/Laptop via ethernet cable, and log in to the router's web interface (IP is 192.168.1.1, login name is "admin", password: "admin").
When you have access to web interface of TL-WR703N, you select the item at the bottom of the left menu items, marked in light red on the left picture below (system screen). Next you choose sub menu item as marked in light red in the right picture below (flash screen) and browse to target file by pressing light red marked file select dialog in the middle of the screen. You find Meteoplug firmware for this device here: [http://www.meteohub.de/files/meteoplug-tl-wr703n-v1.3.bin meteoplug-tl-wr703n-v1.3.bin]. When error message 18005 occurs, please shorten file name and filepath, as manufacturer firmware can't handle longer file path names.

<gallery>
File:wr703n-p1.png|system screen
File:wr703n-p2.png|flash screen
</gallery>

Finally, a "are you sure" dialog will pop up, please press "yes" button and wait until progress bar has reached 100%. Unit will reboot automatically. After reboot it will be a Meteoplug client in standard configuration (LAN mode).

====Flashing Meteoplug Client Firmware to WL-330N3G====
As ASUS WL-330N3G cannot be flashed by its stock web interface, it is necessary that you setup a TFTP environment on your Host PC to transfer the flash data via the ethernet to WL-330N3G. Using TFTP is quite simple.

First of all the router needs to toggled into "TFTP update mode". This is done by keeping the button on the top pressed for 5-10 seconds while doing a power cycle. After a couple of seconds the power LED starts a very slow blinking. You can now release the button. Router now waits for being firmware-updated via TFTP.

Image to be flashed can be downloaded here: [http://www.meteohub.de/files/meteoplug-wl-330n3g-v1.3.sys meteoplug-wl-330n3g-v1.3.sys]
Sections below describe how to do flashing for Linux and Windows 7.

=====Flashing via TFTP on Linux=====
TFTP update does not need any additional software installed, your Linux already has all you need. Flashing is very straight forward, just execute the script below.<pre>#!/bin/sh
#
if [ "$1" = "" ]
then
echo "error: flash sys file missing as parameter"
exit 1
else
echo "power cycle WL-330N3G with button pressed and wait"
echo "until power LED does go off and on again. Then "
echo "release button and press <RETURN>."
read a
echo "start flashing..."
ifconfig br0:0 192.168.1.20
echo -ne "binary\ntrace\nrexmt 1\nput $1\nquit\n" | tftp 192.168.1.1
echo "...transfer done."
echo "Wait until unit does reboot (will take at least 2 minutes). "
echo "Do not remove from power during flash process!"
fi
</pre>

The script needs to be called with the downloaded image file as parameter. Please execute the script as root, otherwise "ifconfig" and "tftp" will not do or will ask for root password. "ifconfig" sets a virtual ethernet adapter with IP 192.168.1.20 on your Linux box, which is the IP the router expects to get the firmware update from.

=====Flashing via TFTP on Windows 7=====
First you have to enable the TFTP service of your Windows 7. You can do that by
# Open Control Panel > Programs and Features
# Click "Turn Windows features on or off" on left side menu
# Enable "TFTP Client" then click OK button

Next step is to set the IP of your hosts Ethernet adapter to "192.168.1.20". This will disconnect your Host from your network (as far as your equip is not in the 192.168.1.x class c subnet) but it is necessary to use this distinct IP address in order to make the WL-330N3G to accept the flash data transfer.
If you dont know how to set your Ethernet adapter to a static IP, please have a look [http://blog.mclaughlinsoftware.com/2009/11/26/windows-7-static-ip/ here].

When TFTP is enabled and IP of your host PC is set to 192.168.1.20 we can start flashing. Please open a CMD shell and type in the command <pre>tftp -i 192.168.1.1 put flash-file-name</pre> where ''flash-file-name'' is the name of the image to flash. When command is done successfully, number of transferred bytes is displayed.

=====Final Flashing Tasks=====
IP of router in update mode is 192.168.1.1, which hopefully will not do a collision with one of your other devices. If there is a collision, switch off the other devices during flash. After data has been transferred via TFTP you have to wait a couple of minutes until flash process inside the router is done and router restarts itself. Restart switches off all LEDs for a short time. Now it is safe to disconnect the router from power. Interrupting the flash processes by a power cycle will brick the router.

====First Login to Meteoplug Client====
When Meteoplug is connected to your LAN it will try to receive a dynamic IP from your DHCP server during boot. Wait until blinking of the largest LED changes into constant on. Press and release the transparent pushbutton on top of the large LED (TL-MR3020) or the reset button behind the pinhole at the back (TL-WR703N) or button on top of the device (WL-330N3G). Now LED will start signaling the unit's IP as explained [http://wiki.meteoplug.com/Hardware#Findout_IP here].

If Meteoplug client cannot be connected to your LAN or your LAN does not provide a DHCP service, then large LED will not leave fast-blinking mode. To get network settings fixed, you can setup network settings with the network cloud simulator, which is available here: [[Network Cloud Simulator]]. Having done the corrrect network settings with the simulator, you can store these onto a FAT formatted USB stick, plug that stick into your Meteoplug client and do a reboot. Settings stored on USB stick will be transferred to your Meteoplug client during boot. When credentials are OK it will leave blinking mode and large LED will turn constantly on, which indictaes that boot and load of application stack from Meteoplug server in the Internet went fine.

When you manage to reach the meteoplug client with your browser and if you are fimilar with openwrt, which does all the network handling of your Meteoplug client, you can also browse to "http://lan-ip-of-your-meteoplug-client/cgi-bin/luci" and do even more advanced network settings. Password for access via luci is "meteoplug". The headline of each sreen inside openwrt includes a push button named "Open Meteoplug Client" to open a screen, where status of data logging and received sensor values can be inspected. It is the same page you get displayed when you browse to the IP of your Meteoplug client. This page does not provide great features to display data (this is done by the Meteoplug cloud service in the Internet) but it allows you a quick chek if connection to Meteoplug is fine and if weather station sensors do deliver data.

[[File:openwrt-screen-6.png]]

===Bifferboard as Meteoplug Client===
Bifferboard development environments are well described on [http://www.bifferos.com/ Bifferboard Product] and [http://sites.google.com/site/bifferboard Bifferboard Wiki]. Actual Meteoplug client Image is a minimal Linux 2.6.30.5 kernel with the proposed patches applied and a minimal loader, that loads the recent Meteoplug client software from the Meteoplug server. This takes care that each time your Meteoplug client gets rebooted, you will get the most recent SW version. So you never have to bother yourself with applying SW updates.

When you are using a Bifferboard as Meteoplug client you are facing one of these situations
* Your Bifferboard is already flashed with a Meteoplug client image. In that case you can skip flashing instructions chapter. You will find Bifferboards already flashed with Meteoplug client software and ready to [http://www.bifferos.com/buy/ here].
* Your Bifferboard has a standard image installed and needs to be flashed with a Meteoplug image as explained in next paragraphs.

====Flashing Meteoplug Client Image to Bifferboard====
Flashing is done by a Python script that connects to a just booting Bifferboard via LAN and sends the packets to be stored in flash storage as ethernet packets. You need a Linux system running, which has Python installed. Furthermore you need following files:
* Python script that does the flashing: [[File:bb-eth-upload.zip|bb-eth-upload.zip]] (please download and unzip)
* Meteoplug client image for Bifferboard: [[File:mp-bb-image.zip|mp-bb-image.zip]] (please download and unzip)
* MAC of your Bifferboard. Mac has format xx:xx:xx:xx:xx:xx where "xx" stands for a two digit hexadecimal number. You will find MAC of your Bifferboard written on a sticker on one of the chips on the PCB or in the documentation received with it.

Connect Bifferboard to be flashed to your LAN, reboot Bifferboard by repowering it, and start downloaded script on your Linux box by <code>python bb_eth_upload.py eth0 a1:b2:c3:d4:e5:f6 mp-bb-image</code>, where "a1:b2:c3:d4:e5:f6" must be replaced by MAC of your Bifferboard. The MAC is needed to address the correct board. Without a correct MAC, no flashing will start. You will see on your console that buckets from flash storage first being erased and then written the new data to. After flashing is complete Bifferboard will reboot.

When you discover problems during flashing, please consult [http://sites.google.com/site/bifferboard/Home/howto/flash-kernel this page] as you are facing a Bifferboard related issue, I can provide very limited help on.

====Start Meteoplug Bifferboard Client====
Connect your flashed Bifferboard to your LAN and weather station and power it on.

Meteoplug client will connect Meteoplug server in the Internet. This requires that your LAN is connected to the Internet by a router, which also provides an IP address by DHCP service. All routers out there have a DHCP feature. Please make sure that it is enabled. As an alternative you might have a dedicated DHCP server in your LAN, which is also fine. In addition to the IP address Meteoplug client also needs the IP of the gateway to address the Internet and IP of a DNS (domain name server) in the Internet. But don't worry, your router normally provides all this information and your Meteoplug client will probably be able to connect Meteoplug server in the Internet. If this does fail for some reason you don't have much options. Meteoplug client is fully controlled by the server application. It cannot work without this.

What you might check in case of trouble is that your router is not blocking outgoing HTTP traffic on port 80. Normally, that kind of traffic is allowed for all IPs in the LAN, but your router might have some special settings (like "Kindersicherung" in AVM Fritz!boxes) blocking this until you explicitly select a LAN IP to be able to access the Internet. Meteoplug client does not need any incoming ports opened, as it is not going to be connected from the outside. Direction of traffic is outgoing only.

=== Regular Linux System as Meteoplug Client (no longer supported) ===
When you want to use an already running X86 Linux box as Meteoplug client, you simply have to download this package:[[File:generic-image.tgz|generic-image-tgz]]. Installation is described in the attached README. According to the distribution you are using, some individual changes might be necessary, hopefully not too complicated ones. You can also post into the Meteoplug forum, when you need help or want to share experiences about this.

=== Fritz!Box 7270 as Meteoplug Client (no longer supported)===
You can use a Fritz!Box 7270 as Meteoplug client. All you have to do is to install this package [[File:meteoplug-7270-install.img|meteoplug-7270-install.img]] on the 7270. You simply do that by the web interface used for AVM updates. When you upload the package, your 7270 will warn you that it is not a regular AVM image. When you accept that, Meteoplug client will be installed as an additional package on your 7270. If you have a non-stock firmware running or have other additional packages installed there might be problems. However, by installing Meteoplug client you accept that this can happen and in worst case can "brick" your 7270. When you want to uninstall Meteoplug, please install this uninstaller package [[File:meteoplug-7270-uninstall.img|meteoplug-7270-uninstall.img]]. A few minutes after installation you can view Meteoplug client dashboard by browsing to your 7270 LAN IP on port 7770. When this works, installation of Meteoplug client on 7270 has gone fine.

==Meteoplug Server Application==
When you have done steps above you should leave your Meteoplug client powered and connected. You can merely forget about it, because no interaction with it will be necessary in the future. It will just be there and sends data.

===Create an Account===
Please login at [http://login.meteoplug.com http://login.meteoplug.com]. You will see a screen like this were you can login or - as a first time user - can register an account.

<center>[[File:mp-user-admin.png]]</center>

To register an account first step is to specify the MAC of the device the account should be created for. If you are lucky - and most times you will be - your Meteoplug client has already made a first contact with Meteoplug server an have told the server its MAC and which IP your router does use to connect from the Internet. If your browsing PC and your Meteoplug client share the same connection to the Internet, the server application already knows the MAC of your client and will present as in a "select MAC" drop-down menu for selection. If no MAC is provided, you will have to type in the MAC of your Meteoplug client. Please use standard MAC notation (xx:xx:xx:xx:xx:xx).

Next things to fill in are a user name of your choice. User names are restricted to alphas and numbers, please don't make use of special characters as these will be rejected and/or might produce trouble later on. Password has to be at least 6 characters long and has to consist of alphas and numbers only. Next is your email address. This has to be a valid address, because your account will need an activation by replying to an email that will be send to the given address.

When you have finished input in the register section, please press "register". An email will be send to the given address. This email contains a link which activates the requested account for operation. The email also includes the user name and password for your personal reference. Please keep this data at a secure place. It might take a few minutes until the email will arrive at your mailbox. I you don't find it there after 15 minutes, please check your spam folder. The mail might have been dropped there for unknown reasons. Clicking the link in the email will activate your account. Now you have a free demo period of 30 days activated and can make full use of Meteoplug's features. This allows you to do a intensive test drive before licensing Meteoplug for a 12 months period.

When you have logged in at Meteoplug for the first time, please go to "license" page. You will be asked to accept license conditions by setting a mark at the corresponding check box and have to press the "I accept" button. When you don't accept the license terms, your usage of Meteoplug comes to an end now as this is mandatory and you will not be able to reach the other admin pages without that.
<center>[[File:mp-license.png]]</center>

===Complete Initial Settings===
Go to "Settings" tab and provide following information:
<center>[[File:mp-settings.png]]</center>
* Select your preferred language (German and English is available from the beginning, more languages might be added later on).
* Select your time zone, resp. the timezone your weather station is positioned in. This setting is very important to make graphs etc right later on.
* Give exact coordinates of the position of your weather station. Coordinates are entered in degrees, minutes and seconds (just as integers). If you have decimal positions, please use a service like [http://www.fcc.gov/mb/audio/bickel/DDDMMSS-decimal.html this] to compute the needed numbers from that.
* Select a standard upload interval and a shorter interval being used during first 10 minutes after reboot of the client and after a change in client configuration.
Finally, press "Save" to make your changes effective.

When you use a Meteohub or Meteobridge system to feed data into your Meteoplug account, geographical coordinates and upload intervals are defined on the client and are just shown here, without the option todo changes.

===Select Weather Station===
Select the weather station connected to your Meteoplug client from the drop down list. You will see that the screen updates and allows for additional settings for the selected weather station. In the example below a WMR-928 weather station has been selected and a module reporting system status data has been selected as a second "weather station".
<center>[[File:mp-weather-station.png]]</center>
Depending on your weather station you have to make further settings.
* Type of Connection: Here you specify how your weather station is connected. Normally that will be USB serial or USB HID. When you have a look at the top of the screen you will see a report from your Meteoplug client that indicates what type of connection has been detected. If "USB serial" is listed with a device, you should make use of "USB serial". When you see a device listed as USB HID, please make use of "USB HID". When you do connect to an IP enabled weather station, you should use "TCP/IP".
* Device: This defines the exact device Meteoplug should connect to. If you have "USB serial" selected as connection type you can choose from a drop-down list. Usually the device will be "/dev/ttyUSB0". When it is a "USB HID" connection type, no further device information needs to be specified. When using an IP weather station. please enter IP or name of weather station and port number to connect to, separated by a colon (example, 192.168.1.99:10001).

When you press "Save" your settings will be stored and Meteoplug client will apply settings next time it connects to Meteoplug server. This will happen at intervals yous have defined on "Settings" tab.

When you use a Meteohub or Meteobridge system to feed data into your Meteoplug account, this page is missing, as selection of weather station has been already done with the client.

===Assign Sensors===
The idea of "Sensors" page is to define unique IDs to the sensors reported from your weather station, resp your weather stations if you have more than one connected to your Meteoplug client.

Each connected station is displayed in a rectangular field which lists all sensors reported. To help you finding out which sensor is reported where, the type of the sensor is displayed as well as the given number, if it is a sensor that has been given a certain number by the weather station. Your task is to select an ID from the drop-down list of all received sensors. Please select "th0" to be your primary outdoor temperature/humidity sensor. This is necessary as some kinds of wind chill computation might take the sensor as reference. All other IDs you can select as you like. In addition to selecting an ID you can also specify a Name which might make remembering what sensor the ID represents more easy later on.

<center>[[File:mp-sensors.png]]</center>

Press "Save" to make your changes being stored. Changes will be reported to your Meteoplug client next time it connects the server.

When you use a Meteohub or Meteobridge system to feed data into your Meteoplug account, you cannot change sensor IDs and recent settings are just displayed here.

This video demonstrates server setup step-by-step as described above.

<center><wikiflv width="640" height="468" >/flv-videos/bbstart2.flv</wikiflv></center>

===Instruments===
On "Instruments" page you have to select the sensor IDs to be taken for display as weather instruments. This needs some amount of weather data being recorded. If you don't get meaning full values right after setup, please wait some minutes (depends on chosen data upload interval).

You have to select sensor IDs to take values from. In addition to that you can also provide:
* a station name to be displayed
* Language to be used for instruments display
* Measurement units to be used

<center>[[File:mp-instruments.png]]</center>

When you want to embed the instruments display into your website, just copy the URL available at "Call instruments as URL" into following IFRAME statements on your home page.
<pre>
<iframe src="http://www.meteoplug.com/cgi-bin/meteochart.cgi?draw=...your...specific...code..."
allign="top"
scrolling="no"
frameborder="0"
width="550"
height="400">
Browser does not support IFRAMEs
</iframe>
</pre>

Maps and Groups

2024-12-04T17:07:18Z

Admin: Created page with "__NOTOC__ ===Meteoplug Maps=== Meteoplug can draw Maps to show all clients that have given their station a name to be used on the map. So each station can decide, whether to be part of a map or not. I guess most users would like to be on the map, but it is up to you. The default map, you can access as "_map" in your set of pre-defined Meteoplug charts, you will get this information about stations participating: * <b>Map Marker</b>: On the map you can see the position of..."

__NOTOC__
===Meteoplug Maps===
Meteoplug can draw Maps to show all clients that have given their station a name to be used on the map. So each station can decide, whether to be part of a map or not. I guess most users would like to be on the map, but it is up to you. The default map, you can access as "_map" in your set of pre-defined Meteoplug charts, you will get this information about stations participating:

* <b>Map Marker</b>: On the map you can see the position of a station its status: red=registered Meteoplug, yellow=outdated Meteoplug registration, blue=just feeding data from a Meteohub without Meteoplug registration. Red markers can be clicked and show most important weather data of the last couple of months as an interactive chart.
* <b>Station Name</b>: Name that has been given by the owner of the station. Stations names are not checked for uniqueness.
* <b>Latitude, Longitude, Time Zone, Local Time</b>: Data to explain where your station is.
* <b>Station Type, Logger HW</b>: Some interesting detail about the rig used.
* <b>Data Since, Latest Update</b>: Tells when data logging for Meteoplug has started and when the last data upload was done.
* <b>Actual and Historical Weather Data</b>: This part can be customized by changing map definition. This allows every registered Meteoplug user to select which weather data should be shown on his individualized map.

Beside selecting weather data to show on an individualized map, also the size, center position, zoom factor can be adapted to your preferences in your individual map definition. You might have a look at [[http://wiki.meteoplug.com/Gallery#Maps this]] and [[http://wiki.meteoplug.com/Define_Chart#Maps_2 this]] section to get more details how to do that.

====Standard Map====

<iframe key="meteoplug" path="cgi-bin/meteochart.cgi?draw=79757a776920306d0e763b272b2426" height=600 width=750 />

Feel free to embed this map into your web presence, by i-framing this link http://www.meteoplug.com/cgi-bin/meteochart.cgi?draw=79757a776920306d0e763b272b2426. You might also add URL parameters "&latitude=" and "&longitude=" and "&zoom=" to give a new center position and zoom factor (as integers from 1 to 15) that fits your needs.

===What are Meteoplug Groups?===
As you have learned in the introduction, Meteoplug allows you to collect weather data with a minimal client (typically a Bifferboard or a patched TP-Link or ASUS device) and gives you tons of options to work with this data by the Meteoplug server application. This exactly matches the typical end-user situation where someone has a single weather station and wants to get data out of this and wants to publish that into the Internet.

But there is another very interesting aspect on Meteoplug. Think of the situation that you have lots of weather stations, each at different places and you want to manage these group of weather stations. Of course, you could setup a Meteoplug account for each single weather station. But this will put the burden on you to manage access, licenses, chart definitions, etc for each of these accounts separately. When you think of a hundred stations this will be very impractical.

====Features of a Meteoplug Group====
Therefore, Meteoplug provides group accounts. A group account bundles a set of Meteoplug clients to this single account which makes administration much more easy and straight forward. Group accounts provide these features for you:

* <b>One license</b>: There is no need to do a separate licensing for each Meteoplug client. You get a license for the total group and don't have to bother with keeping licenses for all clients up to date.
* <b>On-demand pricing</b>: Charging of usage fees is done based on number of clients in the group and number of days used. So you can start with very small expenses during prototyping phase of your project and will have to pay more, when you add more and more clients while going into production phase. This is a very flexible on-demand model, you just pay for current size of your group, measured each day. Please contact "info(at)meteoplug.com" for details.
* <b>One account to manage</b>: You just have to setup one single group account. So there is no need to keep track of many user-ids and/or passwords. Having logged-in into your group account, you can simply select the client you want to work with without need of authentification for that individual client.
* <b>One set of charts</b>: All clients of a group do share the same chart definitions. When you define a new chart for one of your group's clients, all other clients of your group can also make use of this new definition. This is extremly helpful to keep chart definitions up-to-date and consistent for all your clients.
* <b>Easy setup of new clients</b>: When you have setup a client (weather station definition, sensor ids, general settings) you can define this as a default template for setting up new clients. This dramatically reduces your effort when installing lots of clients.
* <b>Easy application of chart definition to clients</b>: In normal, non-group operation each chart definition of a client is given a unique draw token you can use to generate this specific chart for this specific client. In group mode, you can call a chart definition of a client by its draw token as usual. When you want that same chart being computed for another client named "beach1" in the group you can add "&client=beach1" to get the same graph for that specific client. This feature frees you from storing draw token for all your clients. Just remember the draw token for one client in the group and apply that to all clients by means of the "client" URL parameter. The client name can also be used for chart variables "title" and "gtitle" by including "[client]" into the chart's title definition. "[client]" will be replaced by the client name inside the chart. When using "[Client]" first letter of client name will be capitalized, when using "[CLIENT]" the whole client name will be in capital letters.
* <b>Data from various clients in one chart</b>: When graphing your clients you can setup charts that make use of data from various clients of the group. This allows an easy comparision of data of different stations, etc.
* <b>Groups are private</b>: Clients attached to a group can only be managed by the group account. Their data is not available to anyone outside, as long as you don't publish the encrypted draw token for your chart definitions. As special feature you can also restrict access to charts to a defined requesting IP, which is a very strong security feature if you want to include Meteoplug as a chart generating engine which acts as a data provider into your own services. Allowing only your sever to request charts from Meteoplug will guarantee, that data of your Meteoplug group can be requested by your service only.
* <b>Map your clients</b>: Clients of a Meteoplug group can be displayed on a Map. You can adapt that map to display the weather data you like. The map is private to your group, Meteoplug users outside your group can't see your clients on maps they might construct for themselves.

====Setup Your own Weather Network====
Meteoplug group feature provides services that make it very easy for you to setup your own "Weather Network" when you are:
* a water sport club with a couple of locations where you want to monitor weather conditions
* a group of farmers who want to monitor weather conditions of your fields
* any organization that wants to monitor weather conditions at various places in the world and want have that managed centrally
* and thousand situations I can't think of ;-)

All weather network ideas mentioned above will certainly have a server in the Internet that provides their community an entry point where they can register, login, ask for support, get information, etc. Meteoplug is not meant to replace that, but it provides a customizable chart service that can be easily included into your service offering. What makes this very easy is the fact that one of your team can administer the complete Meteoplug group on the Meteoplug server. You can change charts, add new clients, etc. without interaction with the Meteoplug staff. This gives you a great deal of autonomy and flexibility. Your customers don't even have to know, that all this is delivered by Meteoplug, you can include Meteoplug output into your own design and give it your own branding. Meteoplug is just a back-end service taking care of your weather data and making nice charts of it.

====Sounds good, but...====
If you are not sure, if Meteoplug does fit into your ideas, please drop a mail at "info(at)meteoplug.com" to find out.

Features

2024-12-04T17:06:54Z

Admin: Created page with "<big>'''Meteoplug's Main Feature List'''</big> Beside the fact that Meteoplug allows you to configure your weather station and to log it's data, Meteoplug provides a handful of services that might be interesting for you. When you want to understand how to setup these features in detail, please have a look at the web interface documentation that guides you though all the administration steps needed to get things working. This section focuses more on the results that ca..."

<big>'''Meteoplug's Main Feature List'''</big>

Beside the fact that Meteoplug allows you to configure your weather station and to log it's data, Meteoplug provides a handful of services that might be interesting for you. When you want to understand how to setup these features in detail, please have a look at the web interface documentation that guides you though all the administration steps needed to get things working.

This section focuses more on the results that can be achieved to give you an impression if Meteoplug fits your basic demands.

__TOC__
== Sensor Assignment ==
Meteoplug supports a lot of weather stations and can handle multiple stations at the same time. Therefore, it is not predefined what your primary outdoor temperature sensor is and which weather station should be used for reporting wind data. Meteoplug provides you with all sensor from all your connected stations and you have to give these sensors IDs (and also names if you like) to identify the sensor you have in mind when using data of it. After having assigned an ID to a sensor it is still characterized by it's type, but to which weather station the sensor belongs and if it is a standard or extra sensor is hidden away from that point on. There are just sensors of specific type and unique IDs.

This kind of abstraction is necessary to have a well defined starting point for further computation and graphing on sensor data.

== Calibration ==
Meteoplug allows a calibration of raw sensor data. Calibration is useful if a sensor does not show real values but has some kind of variance. This very often happens to pressure sensors, which can easily differ a few hPa from the correct values. Calibration can be done as a linear formula which is specified by a factor and an offset. Calibration also has a time stamp, that indicates from what point in time on, this calibration should be used. If there are multiple calibrations for a single sensor the most recent will be applied.

<center>[[File:calib.png]]</center>

Time stamped calibration is a nice feature. Think of adding a funnel to your rain gauge to improve precision of rain fall detection. This will be applied at a certain point in time. Before that rain fall should be measured as usual, after that modification rain fall will be measured by applying an calibration that reflects the increased funnel diameter.

== Logging ==
Meteoplug logs a lot of events that happen at the client. Each time data logging failed, gets restarted or terminated a log entry will be written. This provides good help in understanding and trouble shooting of data logging problems.

<pre>logger (30.01.2010 08:42:51): data logger started.
logger (30.01.2010 08:42:52): connect station 0 (WMR-928 via USB serial).
logger (30.01.2010 18:39:30): child process received reload config signal (10).
logger (30.01.2010 18:39:38): data logger started.
logger (30.01.2010 18:39:39): connect station 0 (WMR-928 via USB serial).</pre>

In addition to that you can also see what kind of processing is going on at the server side. May be not all entries are self explanatory, but these again give a good chance to understand what was going wrong, if something unexpected happens.

<pre style="overflow: auto;">info: Feb 1 11:49:15 gamma IMPORT-BETA 6A:B3:F6:00:xx:xx: 8 records imported (20100201104822 - 20100201104904) in 0s
info: Feb 1 11:49:15 gamma UPDATEDB 6A:B3:F6:00:xx:xx: time 0s/0.000s [2010-02-01 10:48:22 - 2010-02-01 10:49:04]: 4 sensors, 40 selects (33+84 rows), 44 inserts
info: Feb 1 11:50:02 gamma LOGRAW 6A:B3:F6:00:xx:xx: WAN IP 91.38.121.98: 9 records into 20100201115002-6A:B3:F6:00:xx:xx-20100201104905-20100201104959-9
info: Feb 1 11:50:05 gamma IMPORTLOOP : 20100201115002-6A:B3:F6:00:xx:xx-20100201104905-20100201104959-9
info: Feb 1 11:50:05 gamma IMPORT 6A:B3:F6:00:xx:xx: 9 records imported (20100201104905 - 20100201104959) in 0s
info: Feb 1 11:50:06 gamma UPDATEDB 6A:B3:F6:00:xx:xx: time 1s/0.020s [2010-02-01 10:49:05 - 2010-02-01 10:49:59]: 4 sensors, 40 selects (42+84 rows), 44 inserts
info: Feb 1 11:50:10 gamma LOGRAW 6A:B3:F6:00:xx:xx: WAN IP 91.38.121.98: 1 records into 20100201115010-6A:B3:F6:00:xx:xx-20100201104958-20100201104958-1
info: Feb 1 11:50:16 gamma IMPORTLOOP : 20100201115010-6A:B3:F6:00:xx:xx-20100201104958-20100201104958-1
info: Feb 1 11:50:16 gamma IMPORT 6A:B3:F6:00:xx:xx: 1 records imported (20100201104958 - 20100201104958) in 0s
info: Feb 1 11:50:16 gamma UPDATEDB 6A:B3:F6:00:xx:xx: time 0s/0.000s [2010-02-01 10:49:58 - 2010-02-01 10:49:58]: 4 sensors, 40 selects (43+84 rows), 44 inserts</pre>

Server logs can have two types of entries. Entries beginning with "info" are for your information only, entries beginning with "warn" should have you attention as something does not run as expected.

== Data Import ==
Meteoplug can import data from existing Meteohub systems, Meteobase accounts and from very popular WSWIN software.

== Data Inspection ==
At any time you like you can inspect logged raw data with Meteoplug server application. Data is displayed in a timestamped easy to understand notion. You can also download raw data to your PC or upload data from your PC to Meteoplug server. This gives you a lot of freedom how to backup and process your private weather data. As all other server functions of Meteoplug, it is just you who can see, alter or delete your weather data.

<pre>2010-01-01 11:02:02 th10 21.2°C 34% 4.7°C
2010-01-01 11:02:03 wind0 101° 1.4m/s 1.6m/s -3.0°C
2010-01-01 11:02:09 th0 -1.2°C 71% -5.8°C
2010-01-01 11:02:11 t0 10.8°C
2010-01-01 11:02:17 wind0 99° 1.8m/s 1.6m/s -3.6°C
2010-01-01 11:02:37 thb0 22.4°C 32% 4.9°C 998.0hPa 1001.2hPa
2010-01-01 11:02:41 t0 10.8°C
2010-01-01 11:02:44 rain0 0.0mm/h 3554.0mm
2010-01-01 11:02:45 wind0 103° 1.4m/s 1.6m/s -3.0°C
2010-01-01 11:02:46 th0 -1.2°C 71% -5.8°C
2010-01-01 11:02:59 wind0 94° 1.8m/s 1.6m/s -3.6°C
2010-01-01 11:03:11 t0 10.8°C
2010-01-01 11:03:13 wind0 102° 1.6m/s 1.6m/s -3.3°C
2010-01-01 11:03:15 thb0 22.4°C 32% 4.9°C 998.0hPa 1001.2hPa
2010-01-01 11:03:23 th0 -1.2°C 71% -5.8°C
2010-01-01 11:03:27 wind0 105° 1.8m/s 1.6m/s -3.6°C</pre>

== Weather Networks ==
Meteoplug collects data from various users but it is not meant to be a weather network in a classical sense. Typical weather networks get data from many different kinds of clients that have different weather station software running. This data is used to draw weather maps that show coverage of supporting stations in country or continent. While Meteoplug might offer services like that later on, the focus of Meteoplug is to allow low power, environmental friendly weather data measurement. It's scope is limited to Meteoplug application and suitable hardware. From that perspective it makes sense for Meteoplug to feed other weather networks.

You can select from a broad range of weather network. Some of them have true international coverage (Weather Undergroud, CWOP, ...) others are very local. Meteoplug will add new weather networks over time. If you would like to have a weather network supported not mentioned so far, please contact "info(at)meteoplug.com". At the moment meteohub supports these weather networks:
* Hetweeractueel (NL)
* Wetterpage24 (D)
* Wetterpool (D)
* Borgervejr (DK)
* Regiowetter (CH)
* Wetterspiegel (D)
* Meteoclimatic (ES)
* CWOP (US)
* Weather Underground (US)
* Wedaal (D)
* Windfinder (EU)
* Sauerlandwetter (D)
* SH-Netz (D)
* Awekas (EU)
* Wetterarchiv (D)
* HamWeather (US)
* Weatherbug (US)

Feeding data to a weather network is done by selecting the network in the list, defining sensors to grab the data from and some credentials like user name and password that the target weather network has given you to identify yourself when sending data.

Update frequency can be set to an interval down to "every 10 minutes". As data from Meteoplug client is also updated every 10 minutes as shortest interval, Meteoplug is not useful when you have a focus on true live weather data in a network (like Weather Underground rapid fire) where updates are expected every few seconds or so. While one can argue what kind of sense extremely short update intervals have, it is important to understand that the design of Meteoplug will not deliver that kind of real-time reporting.

== Weather Graphing ==
Meteoplug has a very powerful graphing mechanism build in that uses flash applets from [http://amcharts.com amcharts.com]. This charts allow for some kind of interaction. You can select and deselect parts of the graph (by click on bullets in the top legend), you can zoom into data and you can shift period of inspection by shifting and resizing scroller on the time line. Just have a look at the example below and discover what kind of interaction it supports.

<iframe key="meteoplug" path="examples/example-1.html" height="430" width="740"/>

Fine thing about this graphing facility is, that you can define individual graphs inside Meteoplug and can use these to visualize your actual data with. Each defined graph has an unique URL. By just calling this URL inside some IFRAME tags on your homepage you can embed these graphs onto your homepage very easily. You can for example embed to graph above onto your homepage with following snippet
<pre>
<iframe src="http://admin.meteoplug.com/mpexamples/example-1.html"
allign="top"
scrolling="no"
frameborder="0"
width="740"
height="430">
Browser does not support IFRAMEs
</iframe>
</pre>

Flash-based interactive graphs is not what you are looking for, but you need graphs which show-up as simple graphics that can also be displayed on your mobile device. In that case you can make use of line graphs generated by gnuplot. Below you find a simple line graph which is provided as a ".png" file, which all browsers, even on portable devices can handle.

[[File:example-13.png]]     [[File:example-14.png]]

Integration of this type of graphs is extremely easy:
<pre>
<img src="https://admin.meteobridge.com/mpexamples/example-13.png">
</pre>

Meteoplug does also support creation of tables with weather data. This can be useful if you want to list data of each day for a certain month. Below you see an example for January 2010. As before, this table can also be included into your homepage as an IFRAME. You also can define the style of the table. How to define and customize graphs and tables according to your needs is explained in detail in Meteoplug's documentation.

<center><iframe key="meteoplug" path="examples/example-2.html" height="740" width="550"/></center>

== Weather Instruments ==
Meteoplug can also display actual weather data in terms of weather instruments. This feature is realized by a preconfigured [http://www.weather-display.com/wdlive.php WDLive] applet. Beside selecting sensors to be displayed, name of station and units to be used for display no further customization is provided at the moment.

<center>[[File:instruments.png]]</center>

Instruments can also be imported onto your Homepage by a simple IFRAME mechanism. You won't have to do any complicated installation of applets, configuration files etc.

Hardware

2024-12-04T17:06:29Z

Admin: Created page with "__TOC__ == Weather Stations == Meteoplug supports exactly the same weather stations as Meteohub. As current Meteoplug clients just have USB, weather stations with USB connector (serial and HID type) or TCP/IP connection (connected via a hub, switch or router to Meteoplug client) are directly supported. To have a RS232 connected weather station supported a Meteoplug compatible RS232-to-USB converter is needed. Attached you find a list of supported weather stations. Inte..."

__TOC__
== Weather Stations ==

Meteoplug supports exactly the same weather stations as Meteohub. As current Meteoplug clients just have USB, weather stations with USB connector (serial and HID type) or TCP/IP connection (connected via a hub, switch or router to Meteoplug client) are directly supported. To have a RS232 connected weather station supported a Meteoplug compatible RS232-to-USB converter is needed. Attached you find a list of supported weather stations.

Internal data logger of weather stations is in general not supported. Exception is Davis Vantage/Vue. Here Meteoplug checks for data in the internal logger of the weather station before doing reading regular live data.

=== Supported Weather Stations ===
{| style="background:none" border="1" cellpadding="5" cellspacing="0"
|+ align="bottom"|''supported weather stations''
!colspan="2"|Weather station
! Description
|-
|<center>[[File:vantage.png]]</center>
|'''Davis''' Vantage Pro2, Pro1 (except firmware A)
|Vantage Pro including wind, rain, pressure, UV, solar radiation, indoor temperature, outdoor temperature and 7 extra temp/hum sensors are fully supported. Additional "Soil" and "Leaf" sensors as well as pure temperature sensors are also supported. Meteoplug can handle RS232, USB and TCP/IP (WeatherLinkIP) variants of Vantage. Data internally logged in Vantage is checked by Meteoplug when Meteoplug starts operation. If there is historical data not available to Meteoplug so far, this logged data will be transferrred to Meteoplug before logging of live data starts. RS232 Vantage must have set baud rate to 19.200.
|-
|<center>[[File:vue.png]]</center>
|'''Davis''' Vantage Vue
|Vantage Vue including all available sensors is fully supported. Meteoplug can handle RS232, USB and TCP/IP (WeatherLinkIP) variants of Vantage. Data internally logged in Vantage is handled by Meteoplug as explained for Vantage Pro. RS232 Vantage must have set baud rate to 19.200.
|-
|<center>[[File:envoy8x.png]]</center>
|'''Davis''' Envoy8x
|New Envoy8x receiving unit from Davis is supported. Connection to Meteoplug client is done via RS232 or USB data logger from Davis. Historical data stored in the receiving unit are not considered at the moment. Initial configuration of Envoy8x regarding connected weather stations has to be done upfront with the PC programs provided by Davis. Meteoplug client is not capable to do this.
|-
|<center>[[File:wmr928.png]]</center>
|'''Oregon''' WMR928 (EU), WMR968 (US)
|This model has a RS232 connector that needs a RS232-to-USB converter (based on CP2101, FTDI or PL2303 chipset). Serial protocol of this weather station is well understood and widely documented. As a result Meteoplug does support all of it's features. Disadvantage of the station not to have a data logger included is compensated by Meteoplug. Station is limited in terms of sensor variety. It can handle a maximum of 3 additional thermo/hygro sensors and is lacking support of an UV sensor.
|-
|<center>[[File:wmr200.png]]</center>
|'''Oregon''' WMR200
|This model has a USB connector that can directly connected to the Meteoplug client. Internal Datalogger of WMR200 will not be used by Meteoplug. WMR200 has problems in reporting actual sensor readings, when data logger is completely filled. It is recommended to set the data logging interval to the maximum (longest duration). This takes care that the data logger will not reach its capacity for months. However, you should take care to empty the data logger's buffer from time to time manually at the WMR 200 base station. All sensors for WMR200 are supported, including additional thermo/hygro sensors as well as an UV sensor.
|-
|<center>[[File:wmr100.png]]</center>
|'''Oregon''' WMR100
|This model has a USB connector that can directly connected to the Meteoplug client. Meteoplug supports all available sensors for WMR100, including additional thermo/hygro sensors as well as an UV sensor
|-
|<center>[[File:wmrs200.png]]</center>
|'''Oregon''' WMRS200
|This station is like a WMR100 with sensors from WMR200 but without any display. WMRS200 is powered from Meteoplug via USB connector. All sensors applicable to WMRS200 are supported by Meteoplug.
|-
|<center>[[File:rms300.png]]</center>
|'''Oregon''' RMS300
|This station gets directly connected by an USB cable and is just capable to report data from a maximum of 3 temp/hygro sensors. Out-door sensor is included in the package (THGN-132N) and mapped to channel 0 by Meteoplug. Sensors for wind, rain, UV, pressure are not supported. Additional temp/hygro sensors have to be of type THGR810. temp/hygro sensor included in the console is reported on channel 9.
|-
|<center>[[File:te923.png]]</center>
|'''Hideki''' TE923
|TE923 weather station from Hideki is connected via USB and is sold with various brand names (Mebus, Irox, Honeywell, Nexus). TE923 had various hardware revisions over time. Meteoplug supports hardware versions 3, and 4. Very old version 1, that does not provide live weather data on the USB port, and version 2 are not supported.
Meteoplug just makes use of the live data of TE923, internal data logger functionality of TE923 is not used by Meteoplug.
|-
|<center>[[File:wh1080.png]]</center>
|'''Fine Offset Electronics''' WH1080, WH1081
|WH1080 weather station from Fine Offset Electronics is also branded as Watson W-8681, WX-2008, National Geographic 265 NE, Elecsa 6975/ 6976, Ambient Weather WS-1080/WS-2080. Meteoplug just makes use of live data of the WH-1080, internal data logger functionality of the WH1080 is not used by Meteoplug. Weather forecast icon is not supported as well.
|-
|<center>[[File:ultimeter.png]]</center>
|'''Peet Bros''' Ultimeter 100, 800, 2100
| Ultimeter weather stations from Peet Bros are supported. Wind, rain, pressure, indoor and outdoor temperature and humidity are used. Supported Peet Bros data protocols are "data logging", "packet", "complete record".
|-
|<center>[[File:mk3.png]]</center>
|'''RainWise''' MkIII
|MkIII weather station from RainWise is supported including wind, rain, pressure, outdoor temperature and humidity. Meteoplug uses classical CRC communication type. Sensor thb0 reports pressure and outdoor temp/hum. Sensor th0 also reports outdoor temp/hum.
|-
|<center>[[File:ws2300.png]]</center>
|'''La Crosse''' WS2300
|WS2300 weather station is supported. Data is received by a plug-in available under GPL. Source code can be at download from download section of "meteohub.de".
|-
|<center>[[File:ws300.png]]</center>
|'''ELV''' WS300PC/444/500 and various clones (WS550/777/888)
|WS300 weather station and clones are supported and connected via USB.
|}

=== Supported Data Acquisition Devices ===
{| style="background:none" border="1" cellpadding="5" cellspacing="0"
|+ align="bottom"|''supported data ackquisition devices''
!colspan="2"|Device
! Description
|-
|<center>[[File:rfxcom.png]]</center>
| '''RFXCOM''' 433MHz-Receiver for Oregon Scientific sensors (USB/LAN/WLAN)
| RFXCOM Receiver in 433MHz band can read all kinds of Oregon Scientific sensors and RFXmeter sensors, which can do monitoring of energy consumption. Receivers are available with USB connection (80002), LAN connection (81003), WLAN (82003)
|-
|<center>[[File:rfxtrx.png]]</center>
| '''RFXtrx433 USB''' 433MHz-Transceiver for a broad range of sensors
| RFXtrx433 USB is the follow-on product of older RFXCOM above and can handle a lot of RF sensors in 433MHz band. Supported sensors are the ones from Oregon Scientific, TFE and other companies. RFXtrx connects via USB to Meteoplug client.
|-
|<center>[[File:em1010PC.png]]</center>
| '''ELV, Conrad''' Energy monitors EM1010PC and EM1000
| Meteoplug can read data from these USB connected energy monitoring devices. Information provided is actual power demand and total energy consumption.
|-
|<center>[[File:envi.png]]</center>
| '''Current Cost''' Energy monitor Envi CC128
| Meteoplug can read data from this USB connected energy monitoring device. Information provided is indoor temperature and actual power demand.
|-
|}

=== '''Not''' Supported Weather Stations ===
These weather stations are not supported:
* WS2800 and WS3600 from La Crosse and/or ELV are not supported.
* Labjack U3 which is supported by Meteohub is not supported by Meteoplug.
* 1wire weather stations are not supported.

== Meteoplug Client Hardware ==

=== Meteohub ===
Any Meteohub system can also feed the Meteoplug server with data. This allows to make use of Meteoplug's data storage capabilities as some kind of a raw data backup and this will also allow you the to make use of Meteoplug graphing features that are somehow more powerful than gnuplot based graphing on a Meteohub.

Definition of weather stations and sensors has to be done on the Meteohub. Meteoplug just mirrors settings you have done on your Meteohub. When you change settings on your Meteohub it might take some time until these changes are effective on Meteoplug.

You will find more information about Meteohub at [http://www.meteohub.de meteohub.de].

===TP-Link TL-MR3020===
[[File:tl-mr3020-w250.png|left]] Tiny router TL-3020 from TP-Link is currently most recommended Meteoplug client hardware. TL-MR3020 is word-wide available for less than $50. Flashing the unit with Meteoplug firmware makes the router a Meteoplug client, providing the feature to send data from a weather station via wired or wireless LAN to Meteoplug cloud services in the Internet. Currently sold TL-MR3020 are version 1.7. Meteoplug client was tested with version 1.7 models. If previous versions do also work with Meteoplug client image has not been tested yet. What makes the TL-MR shine beside its features is extremely low power consumption. According to [https://apollo.open-resource.org/lab:argus this site] it takes below 1 Watt without USB and only slightly more with WLAN and USB operating.
TL-MR3020 has a limitation concerning USB devices. It can just handle USB 2.0 devices, low speed USB 1.x devices will not be handled correctly. This is very easy to overcome by adding a small cheap, unpowered external USB 2.0 HUB, which translates USB 1.x from your weather station to USB 2.0. Weather stations known to be impacted by this are:
* Vantage and Vue when used with original Davis USB datalogger
* Fine Offset Electronics WH-1080 and alike stations
* Oregon WMR 88/100/200 stations
* Hideki TE923 and alike stations

The core of the image to be flashed into the router is an openwrt Linux distribution with some specific Meteoplug software components on top. Connectivity to the Internet via LAN or WLAN is handled by the openwrt functions, while doing readout of data from a weather station and holding connection with Meteoplug cloud on an application level is done the software components provided by smartbedded.com. Most part of the application software is not inside the flashed image but gets downloaded during client startup from Meteoplug cloud service. This has the great advantage that most software updates can be realized without reflashng the client hardware again. Each time a Meteoplug client boots, it downloads the most recent software version and starts running it.

Meteoplug client operation needs a LAN or WLAN connection to the Internet. To achieve this Meteoplug client on TL-MR3020 can be started in two different modes of operation regarding network usage. Apart from that it is also possible to configure the network features in any way that is supported by openwrt. So beside the easy mainstreet approached outlined here, there are tons of options to get a Meteoplug client operational in nearly every network environment you might think of.

=====LAN-Mode (default): Meteoplug is a DHCP client in your LAN=====
As default Meteoplug client starts in LAN mode, where it gets IP, Gateway and DNS information from the DHCP server (mostly the router) in your LAN network. If these conditions are met, seeting up Meteoplug client is dead simple. Just connect it to your LAN with an ethernet cable, power it on and a few minutes later it will have connected to Meteoplug cloud and can be used there. In order to make this contact happed, Internet needs to be available for the IP given to the Meteoplug client. Especially, port 80 must not be blocked for outgoing traffic from the IP Meteoplug client uses. Any proxies in-between will also block communication and need to be disabled.

=====Reset Password Mode: Meteoplug password is reset to default=====
When you login to Meteoplug's underlying openwrt to adjust network settings, you need to authenticate by a password. This mode resets password back to "meteoplug" regardless what it has been set to before.

====Toggling Modes====
When having installed Meteoplug client firmware on TL-MR3020 for the first time, Meteoplug is in "LAN mode" as described above. However, you can switch to any of the other explained modes by pressing the button and not releasing it until the LED blinks. You toggle between modes by waiting until the LED has done a distinct number of blinks, before you release the button. After release of the button Meteoplug client will reboot and start in selected mode:
* Release button after first blink: LAN mode (factory default)
* Release button after second blink: reset password to "meteoplug", no change in network settings

====Findout IP====
In order to connect with your web bowser to a Meteoplug to change settings or check status, you need to know its IP. By pressing (and releasing it again quickly) of the transparent illuminated button on the top of the Meteoplug cover (TL-MR3020) or the reset button at the back (TL-WR703N), Meteoplug will signal its IP by pulsing the lead beneath the pressed button. Sequence begins with LED going off, then each of the four numbers (delimited by a dot) will be signaled one by one. The dot between the numbers will be signaled by a "H" (LED shines bright). Each number is signaled by blinking digit per digit. Each digit is represented by a "M" (LED shines medium dimmed) repeated as often as the digit tells us. The zero digit is signaled by ten blinks. After having done this for all digits of all numbers of the IP, the end is signaled by LED staying off a while like it started with. When Sequenze is done, the LED is constantly turned on again.

Example: IP 192.168.10.77 Legend: M = LED medium dimmed, H = LED shines bright, _ = LED is dark

<pre>Signal: Comment
___M___M_M_M_M_M_M_M_M_M___M_M___H 192
___M___M_M_M_M_M_M___M_M_M_M_M_M_M_M___H 168
___M___M_M_M_M_M_M_M_M_M_M___H 10
___M_M_M_M_M_M_M___M_M_M_M_M_M_M___ 77</pre>

When Meteohub does not have a valid IP this will be signaled with three blinks shortly following each other.

In addition to optical signaling the MAC, LAN IP and WLAN IP is stored in a file "network.log" when a FAT formatted USB stick is insterted into the USB port. Example:<pre>Sat Jan 5 00:23:16 UTC 2013
MAC: 90:F6:52:C5:2A:B7
LAN IP: 192.168.123.245
</pre>

====Open Source Obligations====
Meteoplug client image is an openwrt with some application extensions. openwrt Linux distribution including cross compilation toolchain can be dowloaded as described [https://forum.openwrt.org/viewtopic.php?id=33429&p=10 here]. Adaptions on top of openwrt are done inside directory "files", located inside "trunk" directory. an archive of Meteoplug specific "files" directory plus "config" files for TL-MR3020 und TL-WR703N which holds kernel configuration can be downloaded from [http://www.meteohub.de/files/meteoplug-openwrt-addon.tgz here]. Meteoplug components being intellectual property of smartbedded.com and not licensed as Open Source are not part of the archive. TL-MR3020 and TL-WR703N operating Meteoplug can be fully inspected by ssh login as user "root" with password "meteoplug".

===TP-Link WR703N (produced for China market only)===
[[File:tl-wr307n-w180.png|left]] This is TP-Links little brother of the TL-3020. These units come with a really appealing minimal form factor and beside the missing 3-step switch and the missing additional LEDs for USB, WLAN and LAN it has the same features as the TL-MR3020 but comes at prices down to $25. TP-Link does not sell the units in US and Europe, but you will find lots of them on ebay. Currently sold TL-WR703N are version 1.6. Meteoplug client was tested with version 1.6 models. If previous versions do also work with Meteoplug client image has not been tested yet. Please make sure that you don't get a WR-702 (which is widely sold in Europe and US), because that model is not capable of running openwrt and Meteoplug. What makes the TL-WR703N shine beside its features is an extremely low power consumption, even slightly below TL-MR3020 values.

TL-WR703 has a limitation concerning USB devices (like TL-MR3020). It can just handle USB 2.0 devices, low speed USB 1.x devices will not be handled correctly. This is very easy to overcome by adding a small cheap, unpowered external USB 2.0 HUB, which translates USB 1.x from your weather station to USB 2.0. Weather stations known to be impacted by this are:
* Davis Vantage and Vue when used with original Davis USB datalogger
* Hideki stations
* Oregon WMR 88/100/200 stations
* TE923 and alike stations

Meteoplug client operation needs a LAN or WLAN connection to the Internet. To achieve this, Meteoplug client on TL-WR703N can be started in different modes of operation regarding network usage, exactly as described for TL-MR3020. Toggling modes and finding out IP work as described for TL-MR3020, the only difference is that the button is behind the pin hole at the back.

====Open Source Obligations====
Please see section on this for TL-MR3020, Open Source aspects are covered there for both types of devices.

===ASUS WL-330N3G===
[[File:wl-330N3g-w180.png|left]] This tiny router from ASUS has all the features of the ones from TP-link discussed above but can handle all kind of USB 1.x and 2.0 devices without need for a USB hub. WL-330N3G is widely available in Europe for prices down to 40 Euro (and sometimes below) but a bit harded to get for a fair prce in the US. It is important not to buy the similar looking predecessor named "WL-330N" as this does not have the needed RAM capacity. Form factor of WL-330N3G is really appealing and considerably smaller then TL-MR3020. As WL-330N3G has a different processor in MIPSEL architecture (while the TP-Link routers above use MIPS) is needs distinct compiled executables. Nothing you need to worry about, as the provided Meteoplug images take care of these differences.

Meteoplug client operation needs a LAN or WLAN connection to the Internet. To achieve this, Meteoplug client on WL-330N3G can be started in different modes of operation regarding network usage, exactly as described for TP-Link routers described above. Toggling modes and finding out IP work does work identical to TP-Link routers.

====Open Source Obligations====
Please see section on this for TL-MR3020, Open Source aspects are covered there for devices from TP-Link and ASUS in the same way.

=== Bifferboard (no longer available)===
[[File:bb.png|left]] Bifferboard was the first true Meteoplug client hardware. Bifferboards are extremely small, low cost and take just 1 watt of power. If you are interested in that technology you might start reading here: [http://www.bifferos.com/]

When used with Meteoplug Bifferboard's internal flash storage has to be flashed with a Meteoplug client image. This Meteoplug client image takes care that Bifferboard connects to Meteoplug server during boot and loads the most recent Client applications into the Bifferboard. That means, you don't have to update your Bifferboard client software to get advantage of new features, but Bifferboard will just need a reboot to get the most recent Meteoplug client application.

Unfortunately, the inventors have stopped selling Bifferboards. Details are lined out [http://www.bifferos.co.uk/buy/ here]. If you are going for large quantaties direct order from the manufacturer might be an option, as explained on the web page the above link points to.

As Meteoplug client needs Meteoplug server to start up correctly it is vital that your Meteoplug client is embedded into a LAN where it gets an IP and necessary gateway and DNS information from your router via DHCP. When you don't have a router that keeps internet contact 24/7 or you don't have a DHCP server (mostly your router) in your LAN, then Meteoplug client will not work. In addition to that Meteoplug client relies on the capability to connect to the Meteolug server in the internet. Normally you don't have to make a setup for this in your firewall, as this is just outgoing http traffic on standard port 80. You just have to make sure that your router is not blocking http internet access on port 80 for the Meteoplug client. In 95% of domestic setups, Meteoplug client will work without any hassle, just plug in Meteoplug client into your LAN and login on the Meteoplug server with your browser to start setting up your account and receiving weather data.

[[File:bb-x.png|bottom]] [[File:nslu2-x.png|bottom]] [[File:bb-hand.png|bottom]] [[File:bb-inside-1.png]] [[File:bb-inside-2.png]]

As you can see, Bifferboard is really tiny, even when compared to the small NSLU2 or when holding it in your hand. Bifferboard has one USB and one LAN connector. When using a USB hub, more than one weather station can be connected. Power is attached by a small external power adapter that can handle 110-240 volts. Bifferboard has a tiny hole in the cover to allow for reset with a paperclip. A blue LED indicates power on and a yellow one blinks on LAN traffic. The unit gets hand warm during operation and is completely noiseless. Bifferboards come with 1, 4or 8 MB (latest model) of internal flash storage and 32 MB of RAM. All variants are working well with Meteoplug. Meteoplug client is loaded into RAM disk which eliminates risk of wearing out flash cells. As there are no write operations on flash storage there is no risk of flash storage going bad over time. Bifferboard automatically reboots after power failure. It has a watchdog running that reboots when system appears to be stalled. All in all Bifferboard brings all the features needed to provide a reliable data logging client.

===Bifferboard Twin-USB (reduced availability)===
There is a variant of Bifferboard that has two USB ports and a SD card slot. Meteoplug does not make use of SD card slot (using this will disable on of the USB ports), but can drive both USB ports. This is very usefull, if you plan to connect two weather stations to Meteoplug client. Apart from twin USB feature this Bifferboard is identical to single USB Bifferboard.
This product also seems to be close to EOL, but it is still available in the UK [http://www.omnima.co.uk/store/product.php?productid=16194 here] (flashing of Meteoplug client SW has to be done by the user himself).

[[File:bb2-outside.png|bottom]] [[File:bb2-lan.png|bottom]] [[File:bb2-usb.png|bottom]] [[File:bb2-hand.png|bottom]] [[File:bb2-inside-1.png]] [[File:bb2-inside-2.png]]

Twin-USB Bifferboard provides a red LED that Meteoplug client software makes use of to signal client's LAN IP. This red LED is also on PCB of standard Bifferboards, but its case does no provide a hole to have a look at it. When you look straight into the not connected USB port of a standard Bifferboard you can see the red light of this LED a bit (will not work in bright sun light). Numbers are signaled by blinking red LED. Each of the four blocks of numbers is signaled with a slightly dimmed red blinking. Each digit inside a number block is represented by a corresponding number of blinks ("0" is ten blinks), Separation of digits is done by a short additional pause. Dot between number blocks is represented by a full-powered, undimmed red blink. When signaling of IP is done, red LED stays powered-on. This indicates, that Meteoplug client has booted correctly and is operational.

=== Regular Linux System (discontinued, no longer supported) ===
You can also use your X86 Linux system to act as a Meteoplug client. Just download a small package and follow instruction in the README.

=== Fritz!Box 7270/7240 (discontinued, no longer supported)===
{| style="background:none" border="0" cellpadding="5" cellspacing="0"
|-
|<center>[[File:fb7270.png]]</center>
|As Fritz!Box 7270/7240 has a USB port, pretty much RAM (64MB) and sufficient processing power (350 BogoMIPS) I made a port of the Meteoplug client to this platform. Meteoplug client package can be installed by Fritx!Box regular web interface like other software updates. When doing so a message appears, telling you that this is not a regular update from AVM, which is certainly true. When you continue installation, a Meteoplug client software package will be installed on your 7270/7240. Please wait a couple of minutes after reboot and then try to browse to your Fritz!Box's IP at port 7770. You should see a not populated Meteoplug client dashboard there. Having that you should register an account at Meteoplug. Details about all that is outlined in "Getting Started" section of this wiki. Installation of Meteoplug client on your 7270/7240 is done at your own risk. Please notice that there always is a possibility to "brick" your 7270/7240 when flashing non AVM packages onto it. Meteoplug package is just for 7270/7240, other Fritz!Boxes are not supported.
|}

Introduction

2024-12-04T17:05:50Z

Admin: Created page with "=='''Meteoplug - Store and Compute Weather Data in the Cloud'''== Meteoplug is a cloud-based approach for logging and processing weather data from automated weather stations. The client application needs minimal storage and computing power, which allows for embedding into "computers" of minimal size and with minimal power demands down to <font color=red>'''1 watt'''</font> (depending on efficiency of power supply it can be 1-2 watts more on mains). These clients upload w..."

=='''Meteoplug - Store and Compute Weather Data in the Cloud'''==
Meteoplug is a cloud-based approach for logging and processing weather data from automated weather stations. The client application needs minimal storage and computing power, which allows for embedding into "computers" of minimal size and with minimal power demands down to <font color=red>'''1 watt'''</font> (depending on efficiency of power supply it can be 1-2 watts more on mains). These clients upload weather data to a server on the internet which stores it and provides a broad range of computations and services. The server application is based on a professional database and can handle hundreds of clients simultaneously. Each user has access to his private weather data and the server application acts like being a dedicated device. The server is a fully-fledged computer which consumes quite some power, but by being shared by hundreds of users this just adds another 1 watt on total power consumption per user.

<center>[[File:meteoplug-cs3.png||Meteoplug client server model]]</center>

'''Having a weather data logging and an evaluation service around the clock in the internet for just 1+1 watt per user is something that has not been possible before'''. In that way Meteoplug is a breakthrough in doing weather observations at a minimum environmental foot print.

Meteoplug provides support for many weather networks, can generate user-defined graphs and allows download and upload of data to and from your PC. Meteoplug is compatible with a long list of weather stations. One Meteoplug client can handle multiple weather stations simultaneously if you have more than one station at hand.

The only prerequisite to be met is that the client device is connected to a router that provides a connection to the internet. Configuration of the client can be easily done by the server application, you don't even need to know the IP nor other details of your client. After having created an account for the server application, setup is mainly done by a couple of clicks. This dead simple operation - just plug in your weather station and connect the client to your LAN - gave this solution the name "Meteoplug".

You try Meteoplug free for 30 days of usage. After that, you have to decide if you want to continue to use it. The fee for 12 months of usage is 29 Euros. As the internet server that acts as the backbone of Meteoplug generates significant monthly cost, licenses are valid for limited time. That might be seen as a disadvantage first, but please keep in mind that your investment in hardware is very low, so it might turn out to be more economical than buying and owning hardware capable of doing all the weather storage and computation yourself.

'''When you want to start using Meteoplug, get a Meteoplug client and start setting up your account [http://login.meteoplug.com here]'''.

'''A Meteoplug forum, where users discuss setups, exchange ideas and support each other, can be found [http://forum.meteoplug.com here]'''.

MediaWiki:Sidebar

2024-12-04T17:02:21Z

Admin:

MediaWiki:Sidebar

2024-12-04T17:02:03Z

Admin:

MediaWiki:Sidebar

2024-12-04T17:01:47Z

Admin:

MediaWiki:Sidebar

2024-12-04T17:00:55Z

Admin:

MediaWiki:Sidebar

2024-12-04T17:00:12Z