...
| Note | ||
|---|---|---|
| ||
Other Batteries or accumulators with a nominal voltage of more or less than 3.6V must not used with the device under any circumstances. In particular, lithium based cells with a nominal voltage of 3.7V must not be used! |
...
| name | type | bytes | description | example |
|---|---|---|---|---|
| version | uint8[3] | 0-2 | Version of the firmware running on the device | 1, 5, 1 ≡ v1.5.1 |
| v_bat | uint16 | 3-4 | Battery voltage in mV | 2947 ≡ 2:947V |
| temp | int16 | 5-6 | Temperature measured inside the device in 1/10 °C | 246 ≡ 24.6°C |
| flags | int8 | 7 | Bit 7 (e.g. 0x01) = No wMbus Telegram received (added in v2.5.0) | 0x01 |
| Note | ||
|---|---|---|
| ||
The temperature sensor is not present anymore on dedicated V2 hardware, instead 0xffff will be returned. We provide a JavaScript reference implementation of a decoder for this status packet on GitHub, which can be used directly for decoding in The Things Network. |
Data Packet (Format 0)
After each wMBUS collecting phase, all saved telegrams (up to 500 can be stored) will be uploaded via LoRaWAN uplink messages as fast as possible. The received wMBUS telegrams that did pass the configured white list filters will be uploaded without any modification in one or more LoRaWAN messages. If a wMBUS telegram is bigger than the bridge configuration parameter loraMaxMsgSize the transmission will be done using multiple LoRaWAN messages. This parameter is limited to ≤ 50 bytes due to LoRaWANs maximum payload size restrictions. In case of telegram splitting is needed the receiving backend application server as to reassemble the original wMBUS telegram before decryption & parsing of the meter data. This is done by simply joining the messages together in the order of receive. The LoRaWAN port encodes identifies a LoRaWAN fragment of the original wireless M-Bus telegram. This way partial messages can be identified using the LoRaWAN Port:
...