All from Lobaro distributed products, with the exception of the Wireless M-Bus Concentrator Gateway, can always be set between the LoRaWAN mode and the Cellular IoT mode (= NB-IoT & LTE-M) can be switched. At LoRaWAN mode are all devices Bridgeswhich collect wireless MBus, wired MBus or Modbus data and forward them via LoRaWAN to an existing LoRaWAN gateway. The LoRaWAN gateway is connected to the LoRaWAN Network Server (LNS). The amount of data to be transmitted from a meter or sensor, the so-called payload, is often divided into individual packets. This is because in LoRaWAN the physical packet size of the pure payload data is limited to 51 - 222 byte limited. However, the packet size of e.g. wireless M-Bus data of a meter can be up to 255 byte is the same as the payload. It is therefore necessary to reassemble the payload on the server side. It can then be decrypted, decoded and parsed. The Lobaro IoT platform can take over these tasks. An integration of the following LNS is implemented in the IoT platform (see also here):

  • Chirpstack
  • Element-IoT
  • Actility
  • Everynet
  • TTN
  • Wanesy
  • Loriot.

At Cellular IoT mode or mobile mode must have a IoT SIM card be inserted into the respective device. An exception is the Solar Gateway, which is delivered with a SIM card. In mobile radio mode, the devices are Gatewayswhich sends the payload directly to the Lobaro IoT platform are transmitted. The data packets are not split here. The IoT platform is the direct counterpart to all Lobaro products and can decrypt, decode and parse the raw data. The IoT platform is under constant development and can now handle all meters that use wireless MBus, Sensus RF or Müller radio. Since the data collected by Lobaro distributed devices both Bridges as well as Gateways can be, the designation Hybrid gateway introduced.

You can very easily connect the devices with the Config adapter and the Lobaro Maintenancetool configure. Please do not forget to install the driver in advance. The Config adapter is compatible with all Lobaro products and offers the following additional advantages:

  • Excellent for initial tests, since setting parameters can be changed very quickly without constantly restarting the devices via reset button or waiting for the next uplink-downlink cycle
  • enables reading of the LOG for quick finding of problems, in particular this document helps the colleagues of the customer support team
  • fast flashing of firmware updates

You need the Config adapter not necessarily if you run all your devices in Cellular IoT mode and you use the Lobaro-IoT platform because here you can easily create a downlink with the appropriate configuration parameters. Because here you can very easily create a downlink with appropriate configuration parameters and use it via a bulk operation remote to all your devices in your respective next upload-download cycle. If you do not want to use the Lobaro IoT platform and devices in Cellular IoT mode, the config adapter is highly recommended.

The devices have many setting options. You can exclude both meters and sensors from the upload or transfer only certain meters / sensors. This not only saves a lot of upload time but also battery capacity in a battery-powered variant as well as data volume in mobile mode. Furthermore, you can specify the frequency of data transmission. There are many more functions. Please feel free to contact us or read in our Documentation read more.

At LoRaWAN mode the platform is not necessary. Nevertheless, it offers some advantages, such as the reassembly of the payload or the use of the wMBus parser. However, this can also be purchased separately under license. In the NB-IoT / LTE-M mode the platform is necessary. Why do we have in our Platform FAQ compiled.

Yes, that is possible with almost all devices. We can support you with the integration. Please feel free to contact us.

Our devices support LoRaWAN version 1.0.2

Yes, for a small additional charge we will create your own configuration and equip all your devices with it ex works.

Yes, you can purchase the wMBus parser as an annual license. Please contact us and we will be happy to provide you with an offer.

Solar Wireless M-Bus Gateway

The Solar Gateway is shipped in standby mode with the LIC (energy storage device) fully charged. It can be charged with the help of the enclosed magnet be put into operation. Through a five-second Holding the magnet to the lateral round housing maceration will wake up the device. You can also find more information about this in our Documentation.

In general, the length of time until the data volume of the SIM card is used up can only be determined roughly. Lobaro offers two contract models of IoT SIM cards for the Solar Gateway. One is the standard contract model with a capped monthly data volume of 5 MB. This guarantees a runtime of 10 years for the SIM card. In the other case there is the possibility to use 500 MB over 10 years. The data volume can be topped up by the customer at any time or automatically by the respective provider when critical threshold values are reached.

A rough calculation of the data volume consumed can look like this. We calculate with an average of 365 bytes per uplink:

  • Uplink cycles per day / How often are meter data required per day? e.g. every 4 h = 6 x per day
  • How many meters are transferred? e.g. 60
  • Data volume per month = 365 bytes * 6* 60*31 days/1,000,000 = 4.07 MB
  • Term of the 500 MB card = 500/4.07 = 10 years

Yes, this is possible. The default-config of the Solargateway is Cellular-IoT mode (exceptions for "LoRaWAN Only" applications without SIM card on request). Therefore you give us already at Your order Let us know that you want to integrate the device as a bridge into your existing LoRaWAN network. If it is not a tuned configuration with own customer firmware, even though you want to use the device in LoRaWAN mode, we will still equip it with a SIM card. This allows us to keep the Solar Gateway configurable for you between the two modes, LoRaWAN and NB-IoT/LTE-M. Because it then remains accessible via our platform. The default-config of a device in LoRAWAN mode can be restored by a 12-second contact of the magnet.

It is variable depending on the environment and daylight incidence as well as internal room lighting how fast the solar gateway recharges. As a rule, hourly transmissions during the day are no problem. At night usually 2-3 transmissions of the data are still achieved. If the charge of the solar gateway is not sufficient for the planned upload-download cycle, the next upload of the data takes place as soon as the required power is available again, i.e. the scheduled upload of the data is cancelled until the required voltage is reached again.

For the application of the solar gateway in the outdoor area, we have decided to glue the device. In this way, we can guarantee the independently tested and certified IP protection class 66 over the entire product lifetime.

For tests and indoor-only applications, we can also offer a non-glued alternative.

Wireless M-Bus Gateway V3

For this purpose we have Lobaro Documentation has set up an online calculator.

In general, battery runtimes are comparable to NB-IoT operation. Tendentially also slightly longer than those with a medium NB-IoT signal coverage rate. Therefore, you can use accordingly for your considerations our Battery calculator also use for LoRaWAN mode.

We also plan to create a separate computer for LoRaWAN operation.

To do this, you must first insert your IoT SIM card into the gateway and then connect the battery. To do this, follow the instructions in our Quick Start Data Sheet

To do this, you first only need to connect the battery and configure the device remotely to LoRaWAN mode using the config adapter or via the Lobaro IoT platform, i.e. change the WAN parameter to "lorawan". You will find all required keys for the integration into your Lorawan network either as CSV file in the attachment of your delivery bill or in the Lobaro IoT platform under the respective devices or under the tab Hardware Activation. The parameters can also be read out via the configuration adapter.

No, this feature can be provided by downstream systems.

Lobaro IoT platform

Yes, for your initial test and integration with Lobaro devices into your existing IT infrastructure, our Saas IoT platform solution is free of charge. Please feel free to contact us.

Lobaro offers its customers various solutions. Starting from the through Lobaro self-hosted Saas Solution for you up to integration as an on-premise solution on the respective customer servers. You can find an overview here. We will also be happy to advise you personally in order to find the best possible solution for you together.

In LoRaWAN, the physical packet size of the pure user data is limited to 51 - 222 byte is limited. However, the packet size of e.g. wireless M-Bus data of a meter can be up to 255 bytes. Consequently, the data packets are split. The Lobaro IoT platform can reassemble the raw data downstream to your LoRaWAN Network Server (LNS). In addition, you can store the wMBus Keys to decrypt the data in the platform. It is also possible to use the wMBus parser by purchasing the Lobaoro-IoT platform. The integration in the LNS is simple and how this works you can here read up.

Yes, we will support you with the integration, because only we can create new device types in the platform. In most cases, the appropriate parser for the payload of the third-party device is already available. Because Lobaro is constantly developing the platform for you. However, if it becomes necessary to create a new parser for your device type, we will be happy to make you an offer.

We will take care of this for you. You will receive an invitation link to access the platform from us as soon as your first devices have been produced and shipped. We will also add all gateways/bridges purchased from us to your IoT platform in the future.

Yes, as a customer, you determine who in your IoT platform will use the Org admin role receives and can create users.

You have the possibility to blacklist the counters via a or whitelist to be filtered before transmission. You can do this via the parameters mFilter, typFilter, devFilter or ciFilter. The exclusion of devices is done by setting a "!” in front of the respective parameter. Please note that you cannot mix blacklists and whitelists within a filter parameter. You can find more information about the syntax here.

Blacklisting is only available since firmware v0.17.0.

There are numerous advantages of the Lobaro IoT platformthat support your business model. Some we have included in our Documentation for you. In addition, Bulk Operations can also be used, for example, for the remote configuration of all your devices in a time-saving manner. To do this, you only need to create a single downlink and can transfer this to all devices.


We have a Troubleshooting Guidewhich we constantly update and thus implement the initial error analysis as well as rectification.

If the initial troubleshooting measures are not successful, we offer a return process. Please note the following in this regard: In order to provide you with the best possible customer service, we work with local distribution partners in various regions of the world. If you have purchased one of our products through a partner, please contact them before returning the product.

If possible, you should use the LOG file of the product with the help of the configuration adapter and read out Lobaro from of the return. How to create a LOG file, you will find here. You can find the location by clicking on the Show Log Files click.

For devices in the platform without access to the hardware please supply us:

  • URL of the platform instance
  • Address (alternatively serial number) of the device
  • Information where / when the problems occurred


If you bought your device directly from us, please report your returns by e-Mail an. Otherwise please follow the Requirements for the return of the respective distributorwhere you purchased the device. Your e-mail should contain the following information:

  • Short error description (key points)
  • Device type
  • Serial number / address
  • Optional: LOG file or further information in text form

Please let us know the required information for each product single by e-mail. On the basis of your transmitted data, we will send you a Return voucher for you and send it to you within three working days.

Please also note the information on returns in the question below.

Basically the devices are Without battery to be returned. This means that the devices do not fall under dangerous goods shipping. In addition, please note the products Properly to pack. For returns with batteries we have to charge the full shipping costs incl. dangerous goods surcharge.

Should it be a device error, which is covered under our Warranty policy falls, there are for you no costs.

Otherwise, depending on the effort involved, costs for troubleshooting including replacement of the damaged components must be expected.

Can No error on the device are determined after our internal audits, we take the liberty of providing you with a Expense allowance to be invoiced.