Wireless mBUS over LoRaWAN Bridge
The latest firmware version is v2.4.0 (since 2020-02-25)
Which firmware version am I using right now?
You can see the firmware version of your device by inspecting the USB log output in our PC maintenance tool. Or use the information send in the daily status uplink message send on LoRaWAN port 1 (see Status Packet).
How do I update the firmware?
Please refer to Updating Firmware on the page about our Lobaro Maintenance Tool.
Select correct Hardware revisions
Due to permanent development there exist two main hardware revisions of the Lobaro wMBUS over LoRaWAN bridge hardware. Please use the images below to select the right firmware file for your given hardware.
The (dedicated) revision 2.x has a simpler production process which helped us to optimize bigger deployments.
Hardware Revision 2.x (active since 2020)
- app-wMbusLoraBridge-2.4.0+hw2.hex (hardware v2.x) [current release]
Hardware Revision 1.x (active since 2017)
- app-wMbusLoraBridge-2.4.0+hw1.hex (hardware v1.x) [current release]
Please note revisions 1.x are no longer the default variant since 02/2020
The v1 hardware revisions are still active but only on special sales inquiry!
Please contact Lobaro if you are interested in revisions 1.x hardware.
E-Mail release notifications
Firmware Release Notifications
We normally send e-mail notifications upon release of new firmware versions. To receive this mails you can sign up to the Lobaro newsletter here.
Make sure to select the "Firmware Updates" checkbox!
- Add new Payload Format 2, that includes RSSI of received wMBus telegrams.
- Change naming of firmware-files to match naming of hardware variants (hw1/hw2).
- Minor fixes of some edge cases in underlying library on very high values.
- Add version number of Lobaro LoRaWAN-Stack to log.
- Fix minor memory Leak in wMBus parser
- Fix issue in mbus store which triggered raw system resets
- Internal use only
- Increase wireless MBUS C1/T1 mode receive bandwidth
- Change detection method for incoming C1/T1 mode telegrams
- Improve wireless M-BUS C1/T1 mode receive sensitivity
- Improve reset line usage (dedicated only)
- Fix issue with bad measurement timing for status message battery voltage
- Optimize LoRaWAN RX1/RX2 window timing + add more precise downlink logs
- Fix crash on receiving certain long non-standard telegrams.
- Improve Filtering of non-standard wMBus-telegrams
- Migrate to alternative dedicated board
- Fix Deep Sleep settings on dedicated board
- Fix rx/handling of S1-mode CRCs of unencrypted telegrams in wMBUS driver
- Integrated with new LoRaWAN stack, now supporting v1.1, Class C, downlinks, ...
- New Parameter: learnedListenSec to define how long to listen when meters was learned
- Packet size depending on SF with payloadFormat = 1
- New Parameter: timeSync - request time with status packet and upload status packets until we got a valid time
- New Parameter: payloadFormat - 0 = as in older versions, 1 = new split format including receive timestamp (see below)
- The upload is randomly delayed by 1-30 seconds to avoid collisions
New payload Format "1":
LoRaWAN Port: 101
Message: <5 byte Timestamp UTC>
Messages are split into chunks with 1 prefix byte: Prefix byte bits: <7..2 RESERVED><1 LAST><0 FIRST> The FIRST bit is set on the first packet. The LAST bit is set on the last packet. Together with the LoRaWAN frame counter, a whole message can be reconstructed in the backend.
- Leanring mode to learn up to 20 devices with their intervals.
- New Parameter: learningMode - set to true to allow deep sleep based on learned intervals (default: false)
- New Parameter: meterIntervalSec - predefine the sending interval of the meter, so it needs not to be learned (default: 0 = learn intervals)
Learning mode: Up to 20 devices are learned. When received the first time, the device is added to the list. When received the second time the interval is calculated. The second step is omitted when "meterIntervalSec" ist set to any value but 0. When learning was completed during one listening interval the device will only wakeup 10 seconds before and after receiving the learned meters in future. When missing one device for whatever reason, the bridge will start the learning mode again and stay awake for one full listening period.
While receiving learned sensors the maximum receive interval is doubled but ends as soon as all learned devices are received.
Older v1.x firmware
Old v1.x firmware version
The v1.x firmware branch is no longer recommended for use.
If you rely on these older version you can find it at the end of the outdated v1 documentation.