5. LoRaWAN Data Upload Formats
If you nd that the data rate LoRaWAN oers is a limitation for your setup, we could also
provide you with a wireless M-Bus solution that uses alternate data transmission technologies,
for example GSM/LTE or NarrowBand-IoT.
Find our contact information under
https://www.lobaro.com/contact/
, or simple send us
an email to
either English or German is ne.
5.2.3. Decoding wireless M-Bus
After receiving the raw wireless M-Bus telegrams from your LoRaWAN network provider
the actual metering data has to be decrypted and decoded by a backend service for further
processing. The details of this are described in the EN 13757 norm and the newer OMS
specication, which is a clarication of the original underlying norm.
A universal wireless M-Bus decoder is a relatively complicated piece of software if you start
implementing it from scratch since the norm covers many dierent use cases, units, meter
types and data formats. If you know in advance the exact telegram format of the deployed
meters in your setup a hard coded data decoding may be a feasible approach. This is because
wireless M-Bus devices often send the same telegram format in every transmission. Please
contact the manufacturer of your meters for the needed telegram format details.
Figure 6: Lobaro wirless M-Bus decoder REST-API
An an alternative to support a quick evaluation of our hardware Lobaro oers a easy to use
webservice which is designed to decode all sorts of wMBUS input data including decryption
if the correct key has been provided (see gure 6). This REST API returns a JSON object
https://oms-group.org/en/download4all/oms-specification/
wMBUS over LoRaWAN Bridge
17