Difference between revisions of "Meteobridge NBIOT"
| (44 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
| − | + | We are happy to announce an updated Meteobridge PRO2 version that has a NBIOT module installed which allows to acquire and share data in situations were no Internet connection is available. NBIOT equipped Meteobridge PRO2 will be available from the Meteobridge resellers in Europe soon. | |
| − | + | ||
The upgrade module is an internal option. Only thing that changes from the outside is that the right 2.4 Ghz antenna (when looking from behind) changes to a bit more bulky one that supports NBIOT frequencies. | The upgrade module is an internal option. Only thing that changes from the outside is that the right 2.4 Ghz antenna (when looking from behind) changes to a bit more bulky one that supports NBIOT frequencies. | ||
| − | ===What is | + | |
| − | So far Meteobridges were relying on an Internet connection in order to send acquired weather data to external services. The need for an Internet connection does hurt in remote locations where no LAN/WLAN is available and setting up a mobile Internet access is too costly, too cumbersome or not possible because of weak mobile signal levels. To cope with situations like this many providers in Europe make use of an extension of the LTE/4G standard which also defines "Narrow Band - Internet of Things" transmissions which just allow for small data throughput but at much larger distances than mobile LTE/4G. These standard has been widely rolled out in many parts or Europe (Germany, Benelux, Austria, Switzerland, Italy) and 1NCE does provide SIM cards that have a prepaid data volume and life time of 10 years. During the last year we worked on making use of NBIOT as a plugin option for our Meteobridge PRO2 product line and we are now ready to launch. | + | ===What is NBIOT good for?=== |
| + | So far Meteobridges were relying on an Internet connection in order to send acquired weather data to external services. The need for an Internet connection does hurt in remote locations where no LAN/WLAN is available and setting up a mobile Internet access is too costly, too cumbersome or not possible because of weak mobile signal levels. To cope with situations like this many providers in Europe make use of an extension of the LTE/4G standard which also defines "Narrow Band - Internet of Things" transmissions which just allow for small data throughput but at much larger distances than mobile LTE/4G. These standard has been widely rolled out in many parts or Europe (Germany, Benelux, Austria, Switzerland, Italy) and [https://1nce.com 1NCE] does provide SIM cards that have a prepaid data volume and life time of 10 years. During the last year we worked on making use of NBIOT as a plugin option for our Meteobridge PRO2 product line and we are now ready to launch. | ||
[[File:nbiotschema.png||800px]] | [[File:nbiotschema.png||800px]] | ||
| − | ===Why no | + | ===Why no LoRaWAN?=== |
| − | LoRaWAN is | + | LoRaWAN is much hyped but despite also offering good connectivity in offsite locations it always needs a central gateway which acts like an access point that needs to be installed first in order to have LoRaWAN devices connected to it. The gateway needs access to the Internet by any of the classical ways. Therefore, you have to setup an Internet connected LoRaWAN infrastructure first or have to find someone providing this for you. We don't think that this is the simple solution we are looking for. NBIOT lets the clients directly connect to the Internet, it does not need a setup of in-between gateways and infrastructure. |
| − | ===How to make use of | + | ===How to make use of NBIOT data?=== |
| − | When the Meteobridge | + | When the Meteobridge sends data via NBIOT there also needs to be a place where to drop this data and where the users can access the collected data. For Meteobridge we operate a server in the Internet, where the data is collected and you can pickup your data via simple HTTP GET requests. This service is free of charge. Instead of writing your own program to pickup data via a public available API from this server you can simply use a second Meteobridge at home (connected to the Internet) and select "NBIOT" as weather station. Now your Meteobridge at home is reading data the remote Meteobridge PRO2 NBIOT has sent. |
===NBIOT Restrictions=== | ===NBIOT Restrictions=== | ||
| − | As the 1NCE data volume restriction for the 10 years of life time is 500 MB the Meteobridge can just report abt 30 sensors in 1 minute resolution and is based on massive compression. Furthermore the light weight UDP protocol is used, which is a "fire and forget" protocol where it is not checked if the data packet reaches the server. NBIOT takes care that the RF portion is done in hand shake, so no data is lost in the air. But data losses because it is lost somewhere in the Internet are not visible to the sender. We tested how big this "packets lost in the Internet" issue is and it turned out that 99% of packets are received fine, gaps are really minor. | + | As the 1NCE data volume restriction for the 10 years of NBIOT SIM life time is 500 MB the Meteobridge can just report abt 30 sensors in 1 minute resolution and is based on massive compression. Furthermore the light weight UDP protocol is used, which is a "fire and forget" protocol where it is not checked if the data packet reaches the server. NBIOT takes care that the RF portion is done in hand shake, so no data is lost in the air. But data losses because it is lost somewhere in the Internet are not visible to the sender. We tested how big this "packets lost in the Internet" issue is and it turned out that 99% of packets are received fine, gaps are really minor. |
| − | But keep in mind, that a NBIOT connection can just transport compressed data of some sensors to our | + | But keep in mind, that a NBIOT connection can just transport compressed data of some sensors to our NBIOT server in the Internet. As a result you cannot reach the Meteobridge GUI via remote login, the Meteobridge cannot feed weather networks, it cannot send emails, it cannot do FTP uploads or http requests. It is fully isolated apart of being able to send selected data to the NBIOT server. This might sound like a major downside, but when you have another Meteobridge connected with the Internet, this one can do all the things mentioned before when being told to make use of the data the NBIOT Meteobridge has sent to the NBIOT server. |
===NBIOT Costs?=== | ===NBIOT Costs?=== | ||
| − | NBIOT equipped Meteobridges come | + | NBIOT equipped Meteobridges come with a 10 year lifetime SIM from [https://1nce.com 1NCE]. That way all NBIOT costs are covered for the first 10 years (may be a few months less because the 10 year period starts when we buy a bulk of SIMs and the one in your Meteobridge might already be a few months old). After 10 years a new SIM will be needed. I really cannot say what a NBIOT SIM will cost in 10 years and what data volume one will get. Nevertheless, being fine for 9-10 years without additional costs is a compelling offering IMHO. |
==Setup== | ==Setup== | ||
| − | Setting up a | + | Setting up a NBIOT equipped Meteobridge PRO2 starts exactly like for any Meteobridge PRO2. Once you have your PRO2 connected to your LAN/WLAN you have to do the following steps to setup NBIOT operation. Having done that you bring the PRO2 in "stand alone" mode and can ship it to the remote location. |
| + | |||
| + | ===WiFi implications=== | ||
| + | A NBIOT equipped Meteobridge PRO2 has an external RF antenna to receive weather data from an Vantage station and a bit less cylindrical-shaped NBIOT antenna which replaces the external WiFi antenna. When you operate your NBIOT Meteobridge in your WLAN it is recommended that you tell Meteobridge to use the internal chip antenna for WiFi. As the internal antenna is crumbled between PCBs and the Meteobridge aluminum housing it is recommend to switch to internal antenna for WiFi and to reduce tx power to keep RF noise in the Meteobridge within reasonable bounds. You find the switch for internal/external antenna and tx power on "Network - LAN/WLAN" tab in WLAN section. | ||
| + | |||
| + | [[File:nbiotwlan.png||]] | ||
===NBIOT connection=== | ===NBIOT connection=== | ||
| − | + | When your PRO2 is equipped with a NBIOT module you will see an additional "NBIOT" tab in the "Network" section. This tab shows some data about the NBIOT module, the used SIM and allows to select your countries NBIOT provider. Please wait until the "NBIOT module busy" warning disappears (can take a few minutes, please reload the tab to see updates). Next choose the provider for your country and press "save". By reloading the NBIOT tab you will see that the NBIOT module prints out some log info. When your provider has been successfully connected a corresponding message will appear next to "Current Connection" instead of the "module busy" notice. | |
| − | + | [[File:nbiot1.png||]] | |
| − | When you are interested in an inspection which NBIOT provider are in range of your NBIOT module, you can press "Scan". This will block the NBIOT module for quite minutes. When done the result is shown on "System - Logging" tab like this | + | Now you can select if NBIOT upload is enabled (every 5 minutes in per minute resolution) or disabled. Furthermore you can specify a password that protects your uploaded data. When the password is set data can only be downloaded from the Meteobridge NBIOT server when correct MAC and password is specified. |
| + | |||
| + | When you are interested in an inspection which NBIOT provider are in range of your NBIOT module, you can press "Scan". This will block the NBIOT module for quite some minutes. When done the result is shown on "System - Logging" tab like this | ||
<pre>nbiot (25.04.2024 01:13:23): provider scan started, can take up to 60 minutes | <pre>nbiot (25.04.2024 01:13:23): provider scan started, can take up to 60 minutes | ||
nbiot (25.04.2024 01:21:30): * Telekom.de (26201 LTE NB-IOT) | nbiot (25.04.2024 01:21:30): * Telekom.de (26201 LTE NB-IOT) | ||
nbiot (25.04.2024 01:21:30): Vodafone.de (26202 LTE NB-IOT) | nbiot (25.04.2024 01:21:30): Vodafone.de (26202 LTE NB-IOT) | ||
nbiot (25.04.2024 01:21:30): o2 - de (26203 LTE NB-IOT)</pre> | nbiot (25.04.2024 01:21:30): o2 - de (26203 LTE NB-IOT)</pre> | ||
| − | Switching between | + | Switching between providers is not expected to bring any benefit as the NBIOT infrastructure is shared between providers. So you mostly always operate on the same hardware/network. |
NBIOT tab also displays an approximation how much of the available NBIOT data volume has been used so far. | NBIOT tab also displays an approximation how much of the available NBIOT data volume has been used so far. | ||
The "Show Options" button connects to the Meteobridge NBIOT server and explains how to receive uploaded data from the server. When you plan to use your own program to access the NBIOT transmitted data this will be of interest to you. If you use another Meteobridge to extract the NBIOT data, then you can probably ignore this documentation. | The "Show Options" button connects to the Meteobridge NBIOT server and explains how to receive uploaded data from the server. When you plan to use your own program to access the NBIOT transmitted data this will be of interest to you. If you use another Meteobridge to extract the NBIOT data, then you can probably ignore this documentation. | ||
| − | By pressing the "Open URL" button a browser window opens that | + | By pressing the "Open URL" button a browser window opens that requests and displays a certain chunk of the data you have already uploaded. This helps to easily check, if data has been uploaded via NBIOT. Both functions "Open URL" and "Show Options" access the Internet, they will not be available in stand-alone mode as they need Internet access. |
The log section of the NBIOT tab can help debugging in case of connection problems but is not something you need to bother much about. | The log section of the NBIOT tab can help debugging in case of connection problems but is not something you need to bother much about. | ||
===Select Sensors for NBIOT Upload=== | ===Select Sensors for NBIOT Upload=== | ||
| − | + | Once general NBIOT connectivity has been setup you have to specify which of the sensors should be reported via NBIOT. There is a limit of 30 sensors in order to stay in the restricted data volume bounds. On "Station - Mapping" tab you will find a new column called "NBIOT" where you mark sensors to be reported. In the current example all indoor data, primary outdoor temp/hum data, wind data and rain data has been selected. Press "save" once you made your selection. | |
| + | [[File:nbiotsensors.png||600px]] | ||
===Monitoring NBIOT Uploads=== | ===Monitoring NBIOT Uploads=== | ||
| + | As mentioned before Meteonbridge uploads logged data in 5 minute chunks to the Meteobridge NBIOT server. On "Monitoring - Uploads" tab you can inspect how uploads are doing. Please remember that it is a list of sent data. As using UDP protocol the server does not confirm having received it. | ||
| + | |||
| + | [[File:nbiotupload.png||]] | ||
| + | |||
| + | Let us have a look at the first entry to understand its meaning. | ||
| + | * First date/time entry tells when the data has been sent out ("2024-04-25 10:57:12") followed by the status on that ("Success") | ||
| + | * Next date/time info in square brackets tells which data chunk was uploaded ("[2024-04-25 10:50]"). As data is uploaded in 5 minute chunks a timestamp of "10:55" indicates that data from "10:55" up to "11:59" has been sent. | ||
| + | * Last date/time entry ("2024-04-25 10:56:00") tells when the upload job has been placed into the upload scheduling queue, where all service requests are managed and scheduled for execution. | ||
| + | |||
| + | There is also a predefined display script which shows some NBIOT information on the Meteobridge PRO2 display. | ||
| + | |||
| + | [[File:nbiotdisplay.png||]] [[File:mbpro2nbiot.png||350px]] | ||
| + | |||
| + | Presented information includes: | ||
| + | * MAC of the NBIOT Meteobridge | ||
| + | * IMSI of the internal 1NCE SIM card | ||
| + | * selected Provider number (26201 is German Telekom), provider status (Online) and signal strength (-75db, which is pretty strong) | ||
| + | * last NBIOT upload date/time (25.04. 13:36) and number of sensors being transmitted (#14) | ||
| + | * approximation of consumed NBIOT data volume in MB and in percentage of granted data volume of 500MB | ||
===Using NBIOT data=== | ===Using NBIOT data=== | ||
| + | Easiest way to make use of the NBIOT data is to add a "NBIOT Station" to an existing Meteobridge setup as shown below. | ||
| + | [[File:nbiotstation.png||]] | ||
| + | |||
| + | Please make sure that NBIOT password matches the one you specified on the NBIOT Meteobridge on "Network - NBIOT" tab. In this example password is "test". | ||
| + | |||
| + | [[File:nbiotpassword.png||]] | ||
| + | |||
| + | If you do not specify a password for NBIOT on the NBIOT Meteobridge, you can leave out the password when defining the NBIOT station on the data receiving Meteobridge. | ||
| + | |||
| + | Once you have the NBIOT station configured, Meteobridge will start loading data. You can watch incoming NBIOT data as for all the other weather stations on "Monitoring - Live Data" tab. The example below has station #1 as the NBIOT station. You see data for internal sensors, outdoor temperature and humidity, rain and wind coming in. As the data is sent in 5 min chunks and it takes time until the chunk is scheduled, sent, received by the NBIOT server and finally requested and evaluated by the Meteobridge data is 5 - 10 minutes "late". Timestamps of data are fine, they just appear a bit delayed in the target Meteobridge. | ||
| + | |||
| + | [[File:nbiotlive.png||]] | ||
| + | |||
| + | Meteobridge provides a metachart (named "nbiot-daystat") that allows to inspect how many packets have been received from the NBIOT Meteobridge during the course of April 25. Example below shows accumulation of received NBIOT packets during a day in orange (percentage) and a display of the received 5 minute NBIOT data chunks in blue. Don't be concerned that only 92% of expected packets arrived at the server. This is not because of transmission issues but because of running some SW tests and installs on the sending system which had an impact on NBIOT uploads. | ||
| + | |||
| + | [[File:nbiotchart.png||]] | ||
| + | |||
| + | When you want to read NBIOT data with a 3rd party program, please consult the API as explained [https://www.meteoplug.com/nbiot.php?help here]. Communication is easy, just send a HTTPS GET request with parameters and receive the requested set of data. API is protected against polling data too often (current wait interval is 5 seconds) and trying to retrieve too much data in one chunk. Maximum ist set to 2000 for incremental "first/next" requests and 20000 for "start/stop" requests on a dedicated time frame. | ||
===Stand-Alone Operation=== | ===Stand-Alone Operation=== | ||
| − | + | Once you have completed setup and you want to place the PRO2 into the LAN/WLAN-free wild, you just have to enable "Stand-Alone" mode on "Network" tab and press "Save and Apply and Reboot". After that Meteobridge will of course not connect to your LAN/WLAN anymore. You still can reach it by connecting your mobile device to the WiFI network the Meteobridge does setup. You find credentials (SSID, Passphrase) on network tab. | |
| + | |||
| + | [[File:nbiotstandalone.png||]] | ||
Latest revision as of 13:26, 7 May 2024
We are happy to announce an updated Meteobridge PRO2 version that has a NBIOT module installed which allows to acquire and share data in situations were no Internet connection is available. NBIOT equipped Meteobridge PRO2 will be available from the Meteobridge resellers in Europe soon. The upgrade module is an internal option. Only thing that changes from the outside is that the right 2.4 Ghz antenna (when looking from behind) changes to a bit more bulky one that supports NBIOT frequencies.
What is NBIOT good for?
So far Meteobridges were relying on an Internet connection in order to send acquired weather data to external services. The need for an Internet connection does hurt in remote locations where no LAN/WLAN is available and setting up a mobile Internet access is too costly, too cumbersome or not possible because of weak mobile signal levels. To cope with situations like this many providers in Europe make use of an extension of the LTE/4G standard which also defines "Narrow Band - Internet of Things" transmissions which just allow for small data throughput but at much larger distances than mobile LTE/4G. These standard has been widely rolled out in many parts or Europe (Germany, Benelux, Austria, Switzerland, Italy) and 1NCE does provide SIM cards that have a prepaid data volume and life time of 10 years. During the last year we worked on making use of NBIOT as a plugin option for our Meteobridge PRO2 product line and we are now ready to launch.
Why no LoRaWAN?
LoRaWAN is much hyped but despite also offering good connectivity in offsite locations it always needs a central gateway which acts like an access point that needs to be installed first in order to have LoRaWAN devices connected to it. The gateway needs access to the Internet by any of the classical ways. Therefore, you have to setup an Internet connected LoRaWAN infrastructure first or have to find someone providing this for you. We don't think that this is the simple solution we are looking for. NBIOT lets the clients directly connect to the Internet, it does not need a setup of in-between gateways and infrastructure.
How to make use of NBIOT data?
When the Meteobridge sends data via NBIOT there also needs to be a place where to drop this data and where the users can access the collected data. For Meteobridge we operate a server in the Internet, where the data is collected and you can pickup your data via simple HTTP GET requests. This service is free of charge. Instead of writing your own program to pickup data via a public available API from this server you can simply use a second Meteobridge at home (connected to the Internet) and select "NBIOT" as weather station. Now your Meteobridge at home is reading data the remote Meteobridge PRO2 NBIOT has sent.
NBIOT Restrictions
As the 1NCE data volume restriction for the 10 years of NBIOT SIM life time is 500 MB the Meteobridge can just report abt 30 sensors in 1 minute resolution and is based on massive compression. Furthermore the light weight UDP protocol is used, which is a "fire and forget" protocol where it is not checked if the data packet reaches the server. NBIOT takes care that the RF portion is done in hand shake, so no data is lost in the air. But data losses because it is lost somewhere in the Internet are not visible to the sender. We tested how big this "packets lost in the Internet" issue is and it turned out that 99% of packets are received fine, gaps are really minor.
But keep in mind, that a NBIOT connection can just transport compressed data of some sensors to our NBIOT server in the Internet. As a result you cannot reach the Meteobridge GUI via remote login, the Meteobridge cannot feed weather networks, it cannot send emails, it cannot do FTP uploads or http requests. It is fully isolated apart of being able to send selected data to the NBIOT server. This might sound like a major downside, but when you have another Meteobridge connected with the Internet, this one can do all the things mentioned before when being told to make use of the data the NBIOT Meteobridge has sent to the NBIOT server.
NBIOT Costs?
NBIOT equipped Meteobridges come with a 10 year lifetime SIM from 1NCE. That way all NBIOT costs are covered for the first 10 years (may be a few months less because the 10 year period starts when we buy a bulk of SIMs and the one in your Meteobridge might already be a few months old). After 10 years a new SIM will be needed. I really cannot say what a NBIOT SIM will cost in 10 years and what data volume one will get. Nevertheless, being fine for 9-10 years without additional costs is a compelling offering IMHO.
Setup
Setting up a NBIOT equipped Meteobridge PRO2 starts exactly like for any Meteobridge PRO2. Once you have your PRO2 connected to your LAN/WLAN you have to do the following steps to setup NBIOT operation. Having done that you bring the PRO2 in "stand alone" mode and can ship it to the remote location.
WiFi implications
A NBIOT equipped Meteobridge PRO2 has an external RF antenna to receive weather data from an Vantage station and a bit less cylindrical-shaped NBIOT antenna which replaces the external WiFi antenna. When you operate your NBIOT Meteobridge in your WLAN it is recommended that you tell Meteobridge to use the internal chip antenna for WiFi. As the internal antenna is crumbled between PCBs and the Meteobridge aluminum housing it is recommend to switch to internal antenna for WiFi and to reduce tx power to keep RF noise in the Meteobridge within reasonable bounds. You find the switch for internal/external antenna and tx power on "Network - LAN/WLAN" tab in WLAN section.
NBIOT connection
When your PRO2 is equipped with a NBIOT module you will see an additional "NBIOT" tab in the "Network" section. This tab shows some data about the NBIOT module, the used SIM and allows to select your countries NBIOT provider. Please wait until the "NBIOT module busy" warning disappears (can take a few minutes, please reload the tab to see updates). Next choose the provider for your country and press "save". By reloading the NBIOT tab you will see that the NBIOT module prints out some log info. When your provider has been successfully connected a corresponding message will appear next to "Current Connection" instead of the "module busy" notice.
Now you can select if NBIOT upload is enabled (every 5 minutes in per minute resolution) or disabled. Furthermore you can specify a password that protects your uploaded data. When the password is set data can only be downloaded from the Meteobridge NBIOT server when correct MAC and password is specified.
When you are interested in an inspection which NBIOT provider are in range of your NBIOT module, you can press "Scan". This will block the NBIOT module for quite some minutes. When done the result is shown on "System - Logging" tab like this
nbiot (25.04.2024 01:13:23): provider scan started, can take up to 60 minutes nbiot (25.04.2024 01:21:30): * Telekom.de (26201 LTE NB-IOT) nbiot (25.04.2024 01:21:30): Vodafone.de (26202 LTE NB-IOT) nbiot (25.04.2024 01:21:30): o2 - de (26203 LTE NB-IOT)
Switching between providers is not expected to bring any benefit as the NBIOT infrastructure is shared between providers. So you mostly always operate on the same hardware/network.
NBIOT tab also displays an approximation how much of the available NBIOT data volume has been used so far.
The "Show Options" button connects to the Meteobridge NBIOT server and explains how to receive uploaded data from the server. When you plan to use your own program to access the NBIOT transmitted data this will be of interest to you. If you use another Meteobridge to extract the NBIOT data, then you can probably ignore this documentation. By pressing the "Open URL" button a browser window opens that requests and displays a certain chunk of the data you have already uploaded. This helps to easily check, if data has been uploaded via NBIOT. Both functions "Open URL" and "Show Options" access the Internet, they will not be available in stand-alone mode as they need Internet access.
The log section of the NBIOT tab can help debugging in case of connection problems but is not something you need to bother much about.
Select Sensors for NBIOT Upload
Once general NBIOT connectivity has been setup you have to specify which of the sensors should be reported via NBIOT. There is a limit of 30 sensors in order to stay in the restricted data volume bounds. On "Station - Mapping" tab you will find a new column called "NBIOT" where you mark sensors to be reported. In the current example all indoor data, primary outdoor temp/hum data, wind data and rain data has been selected. Press "save" once you made your selection.
Monitoring NBIOT Uploads
As mentioned before Meteonbridge uploads logged data in 5 minute chunks to the Meteobridge NBIOT server. On "Monitoring - Uploads" tab you can inspect how uploads are doing. Please remember that it is a list of sent data. As using UDP protocol the server does not confirm having received it.
Let us have a look at the first entry to understand its meaning.
- First date/time entry tells when the data has been sent out ("2024-04-25 10:57:12") followed by the status on that ("Success")
- Next date/time info in square brackets tells which data chunk was uploaded ("[2024-04-25 10:50]"). As data is uploaded in 5 minute chunks a timestamp of "10:55" indicates that data from "10:55" up to "11:59" has been sent.
- Last date/time entry ("2024-04-25 10:56:00") tells when the upload job has been placed into the upload scheduling queue, where all service requests are managed and scheduled for execution.
There is also a predefined display script which shows some NBIOT information on the Meteobridge PRO2 display.
Presented information includes:
- MAC of the NBIOT Meteobridge
- IMSI of the internal 1NCE SIM card
- selected Provider number (26201 is German Telekom), provider status (Online) and signal strength (-75db, which is pretty strong)
- last NBIOT upload date/time (25.04. 13:36) and number of sensors being transmitted (#14)
- approximation of consumed NBIOT data volume in MB and in percentage of granted data volume of 500MB
Using NBIOT data
Easiest way to make use of the NBIOT data is to add a "NBIOT Station" to an existing Meteobridge setup as shown below.
Please make sure that NBIOT password matches the one you specified on the NBIOT Meteobridge on "Network - NBIOT" tab. In this example password is "test".
If you do not specify a password for NBIOT on the NBIOT Meteobridge, you can leave out the password when defining the NBIOT station on the data receiving Meteobridge.
Once you have the NBIOT station configured, Meteobridge will start loading data. You can watch incoming NBIOT data as for all the other weather stations on "Monitoring - Live Data" tab. The example below has station #1 as the NBIOT station. You see data for internal sensors, outdoor temperature and humidity, rain and wind coming in. As the data is sent in 5 min chunks and it takes time until the chunk is scheduled, sent, received by the NBIOT server and finally requested and evaluated by the Meteobridge data is 5 - 10 minutes "late". Timestamps of data are fine, they just appear a bit delayed in the target Meteobridge.
Meteobridge provides a metachart (named "nbiot-daystat") that allows to inspect how many packets have been received from the NBIOT Meteobridge during the course of April 25. Example below shows accumulation of received NBIOT packets during a day in orange (percentage) and a display of the received 5 minute NBIOT data chunks in blue. Don't be concerned that only 92% of expected packets arrived at the server. This is not because of transmission issues but because of running some SW tests and installs on the sending system which had an impact on NBIOT uploads.
When you want to read NBIOT data with a 3rd party program, please consult the API as explained here. Communication is easy, just send a HTTPS GET request with parameters and receive the requested set of data. API is protected against polling data too often (current wait interval is 5 seconds) and trying to retrieve too much data in one chunk. Maximum ist set to 2000 for incremental "first/next" requests and 20000 for "start/stop" requests on a dedicated time frame.
Stand-Alone Operation
Once you have completed setup and you want to place the PRO2 into the LAN/WLAN-free wild, you just have to enable "Stand-Alone" mode on "Network" tab and press "Save and Apply and Reboot". After that Meteobridge will of course not connect to your LAN/WLAN anymore. You still can reach it by connecting your mobile device to the WiFI network the Meteobridge does setup. You find credentials (SSID, Passphrase) on network tab.
