FAQ

Answers to frequently asked questions about our products

General information

All from Lobaro products sold, with the exception of the Wireless M-Bus Concentrator Gatewaycan always choose between the LoRaWAN mode and the Cellular IoT mode (= NB-IoT & LTE-M) can be switched. In the LoRaWAN mode all devices are Bridgeswhich collect wireless MBus, wired MBus or Modbus data and forward it to an existing LoRaWAN gateway via LoRaWAN. The LoRaWAN gateway is connected to the LoRaWAN Network Server (LNS). The amount of data to be transmitted by 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 user data is limited to 51 - 222 byte limited. However, the packet size of e.g. wireless M-Bus data from a meter can be up to 255 byte are required. 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. Integration of the following LNS is implemented in the IoT platform (see also here):

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

In the Cellular IoT mode or mobile phone mode, a IoT SIM card be inserted into the respective device. An exception to this is the Solar Gateway, which is supplied with a SIM card. In mobile radio mode, the devices are Gatewayswhich sends the payload directly to the Lobaro IoT platform transmitted. The data packets are not split here. The IoT platform is the direct remote station for all Lobaro products and can decrypt, decode and parse the raw data. The IoT platform is constantly evolving and can now process all meters that use wireless MBus, Sensus RF or Müller Funk. As the data provided by Lobaro devices distributed both Bridges as well as Gateways can be, the designation Hybrid Gateway introduced.

You can 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:

  • Ideal for initial tests, as setting parameters can be changed very quickly without having to constantly restart the devices with the reset button or wait for the next uplink/downlink cycle
  • enables the LOG to be read out to quickly identify problems, in particular this document helps colleagues in the customer support team
  • Fast flashing of firmware updates

You need the Config adapter not necessarily if you are operating all your devices in Cellular IoT mode and you are using the Lobaro-IoT platform use. This is because you can very easily create a downlink with the corresponding configuration parameters and use this via a bulk operation remote to all your devices in your next upload/download cycle. If you do not want to use the Lobaro IoT platform and the devices in Cellular IoT mode, the config adapter is strongly recommended.

The devices have many setting options. You can exclude meters and sensors from the upload or only transmit certain meters/sensors. This not only saves a lot of upload time, but also saves battery capacity in a battery-operated version and data volume in mobile phone mode. You can also specify the frequency of data transmission. There are many more functions. Feel free to contact us or read about them in our Documentation read more.

In the LoRaWAN mode the platform is not necessary. Nevertheless, it offers some advantages, such as reassembling the payload or using 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 Platform FAQ compiled.

Yes, this 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 surcharge we can 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 make you an offer.

Solar Wireless M-Bus Gateway

The Solar Gateway is supplied in standby mode with a fully charged LIC (energy storage). It can be charged using the enclosed magnet be put into operation. Through a five-second The device is woken up by holding the magnet against the round housing marking on the side. You can also find more information on 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 term of 10 years for the SIM card. In the other case, there is the option of using 500 MB over 10 years. The data volume can be topped up by the customer at any time or automatically recharged by the respective provider when critical thresholds are reached.

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

  • Uplink cycles per day / How often is 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 the Cellular-IoT mode (exceptions for "LoRaWAN Only" applications without SIM card on request). Therefore, you already give us 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 coordinated configuration with your own customer firmware, we will still equip the device with a SIM card, even though you want to use it in LoRaWAN mode. This allows us to keep the Solar Gateway configurable for you between the two modes, LoRaWAN and NB-IoT/LTE-M. This is because it then remains accessible via our platform. You can restore the default configuration of a device in LoRAWAN mode by contacting the magnet for 12 seconds.

The speed at which the solar gateway recharges depends on the environment and the amount of daylight and internal room lighting. As a rule, hourly transmissions during the day are not a problem. At night, 2-3 data transmissions are usually achieved. If the charge of the Solargateway is not sufficient for the planned upload-dowload 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 canceled until the required voltage is reached again.

To use the Solar Gateway outdoors, we have decided to bond the device. In this way, we can guarantee the independently tested and certified IP protection class 66 over the entire service life of the product.

We can also offer a non-glued alternative for tests and purely indoor applications.

Wireless M-Bus Gateway V3

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

In general, the battery runtimes are comparable to NB-IoT operation. They also tend to be slightly longer than those with an average NB-IoT signal coverage rate. You can therefore use our Battery calculator can also be used for LoRaWAN mode.

We are also planning 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. Please follow the instructions in our Quick Start data sheet

To do this, you first 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 the keys required for integration into your Lorawan network either as a CSV file attached to your delivery bill or in the Lobaro IoT platform under the respective devices or under the Hardware activation tab. The parameters can also be read out via the config adapter.

No, this feature can be provided by downstream systems.

Lobaro IoT platform

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

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

In the 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 from a meter can be up to 255 bytes. Consequently, the data packets are split. The Lobaro IoT platform can reassemble the raw data downstream of your LoRaWAN Network Server (LNS). You can also store the wMBus keys for decrypting the data in the platform. It is also possible to use the wMBus parser by purchasing the Lobaoro IoT platform. Integration in the LNS is simple and you can find out how it works here here read more.

Yes, we will support you with the integration, as 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. Should it nevertheless become necessary to create a new parser for your device type, we will be happy to make you an offer.

We will do 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 the customer, you determine who is responsible for the Role of the Org Admin and can create users.

You have the option of blacklisting the counters via a or whitelist before transmission. You can do this using the parameters mFilter, typFilter, devFilter or ciFilter. Devices are excluded by setting a "!” before the respective parameter. Please note that you cannot mix blacklists and whitelists within a filter parameter. Further information on the syntax can be found here.

Blacklisting is only available since firmware v0.17.0.

There are numerous advantages of Lobaro IoT platformthat support your business model. We have included some of them in our Documentation for you. In addition, bulk operations can also be used for the remote configuration of all your devices, for example, to save time. You only need to create a single downlink and can transfer it to all devices.

Troubleshooting

We have a Troubleshooting Guidewhich we update on an ongoing basis and thus implement the initial error analysis and rectification.

If the initial troubleshooting measures are not effective, we offer a return process. Please note the following: In order to offer you the best possible customer service, we work with local sales 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 using the config adapter and Lobaro before of the return. You can find out how to create a LOG file here. You can find the storage location by clicking on 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 on where / when the problems occurred

Returns

If you have purchased your device directly from us, please report your returns by e-mail support@lobaro.de to. Otherwise, please follow the Requirements for the return of the respective sales partnerfrom whom you purchased the device. Your e-mail should contain the following information:

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

Please leave us the required information for each product single by e-mail. Based on the data you provide, we will create a Return slip for you and send it to you within three working days.

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

The devices are basically without battery to be returned. This means that the devices are not subject to dangerous goods shipment. Please also note the products appropriate to pack. For returns with batteries, we must charge the full shipping costs incl. dangerous goods surcharge.

If it is a device error that falls under our Warranty guidelines falls, there is for you no costs.

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

Can No error on the device are identified following our internal audits, we would like to take the liberty of Allowance for expenses to be invoiced.