LuvitRED 2.22.0 has been released and is now available on CloudGate Universe.
Links accessible after logging into the universe:
Release date: May 28 2020
Minimum firmware: 2.93.2
The firmware has updated openssl to version 1.1.1 and so luvitred has been updated as well. This means that the minimum firmware for luvitred is bumped to 2.93.2.
This allows luvitred to use TLS 1.3 for connecting to servers.
The adr algorithm is very important in lora installations. This mechanism tries to find the highest datarate possible that the sensor can use in order to save as much battery life as possible. This also reduces the time on air for each sensor, which is important to limit the duty-cyles (EU regulations).
This new algorithm knows the minimum SNR for each datarate and can then immediately jump to the best datarate.
If there is still margin left, then it also reduced the TX power of the sensor so that the battery life is increased further.
The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation.
LuvitRED has implemented a node that performs cbor encoding and decoding. This will be useful in combination with a future COAP release.
Some expansion cards have usb ports, but they don't enable the USB to serial drivers automatically. The serial node now has an extra checkbox to do just that.
The sysinfo node has now learned which cloudgate it is running on and which expansion cards are enabled.
The flow node can output the current memory usage of luvitred. By doing so it will first perform a garbage collection. This is useful for debugging memory leaks.
The iothub node has been rewritten completely. It now supports x509 and DPS for authentication. DPS is useful because it only requires one symmetric key for all cloudgates allowing you to deploy the same flow on each cloudgate without having to modify the credentials.
The debug node allows you to select a specify value and not just msg.payload or the complete message to output to the debug tab.
There have been many fixes in the latest luvitred released for cumulocity. The most important one is to mention the tenant id.
Previously using manual provisioning, you would insert the tenant, username and password.
Now you have to use the tenant ID, username and password instead. This may be a breaking change, depending on your server.
The tenant id is usually a t followed by a number, but older cumulocity instances may use the tenant as the tenant id.
This change was required to support enterprise servers.