ThingPark Enterprise SaaS changelog
This page references all the changes included in ThingPark Enterprise SaaS release 8.0, split per maintenance release version.
It includes new features, technical improvements and issues (bugs) resolved. More details about new features and technical improvements are also available in New features and Other technical improvements sections.
Release 8.0.2
New features
ID | Summary |
---|---|
RDTP-22321 | LRR support password personalization from the GUI |
Other technical improvements
ID | Summary |
---|---|
RDTP-22608 | All the MAC commands corresponding to the LoRaWAN relay protocol are displayed in decoded format in Wireless Logger, including the CtrlUplinkListReq/Ans MAC command pair. |
Resolved issues
ID | Summary |
---|---|
RDTP-23439 | DESC : [LoRaWAN relays] LRC does not send the “RootWorSKey” to the relay after rejoining. FIX: LRC considers that the relay resets the TrusedEndDeviceList after rejoining, then resends the devices' root keys when requested by the relay. |
RDTP-23385 | DESC : Email address does not accept apostrophe. FIX: Email address can now be written with an apostrophe, as per RFC 3696. |
RDTP-23574 | DESC : Keycloak and Abeeway device manager services are not available during platform maintenance. FIX: Allow access to Keycloak and Abeeway device manager services during maintenance. |
RDTP-23429 | DESC : When the downlink duty cycle limit is reached on the base station(s), the network server immediately reports an empty DL packet to WLogger/AS, with failure cause "DA", even if there is no DL packet to send to the device. FIX: No DL failure is wrongly reported on WLogger. Additionally, the downlink duty cycle is now correctly treated on LRC side. |
RDTP-23585 | DESC : [FULL FIX] Base station provisioning hit 500 Internal Server Error. FIX: All component like certificate and archive are now correctly deleted to allow the base station to be reprovisioned. |
RDTP-23582 | DESC : The export button shows wrong display of the labels at served devices widget level ( base station dashboard ). FIX: Labels have been corrected. |
RDTP-23332 | DESC : Device mass import fails if several deviceProfile with the same ThingparkID exist. FIX: Device mass import is now successful as only the visible deviceProfile is selected. The ThingParkID unicity is enforced, making it case insensitive. |
RDTP-23303 | DESC : TWA application stop working when HSM is unreachable. FIX: TWA application remains up even if HSM may be unreachable, but returns an error if HSM is required for some operations. |
RDTP-22858 | DESC : The device marker is no more visible in wlogger maps. FIX: As Google API https://chart.googleapis.com/chart is deprecated and return a 404 Not found response, we place instead a png marker image. |
RDTP-23406 | DESC : DX-ADMIN API should not mandate the preferred_username in validate_token endpoint. FIX: If preferred_username is not present, DX-ADMIN won’t raise exception anymore. |
Known issues and limitations
ID | Summary |
---|---|
RDTP-21977 | [LoRaWAN relays] When a downlink packet cannot be sent for an end-device via a relay because of the maximum payload size constraint, there is currently no delivery failure indication reported to AS nor visible in Wireless Logger at end-device level. This issue shall be fixed in the next release. |
RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection. |
Release 8.0.1
New features
None
Other technical improvements
ID | Summary |
---|---|
RDTP-23183 | Add a warning in the user interface about the required RF coverage overlapping when activating network-based geolocation feature. |
Resolved issues
ID | Summary |
---|---|
RDTP-23521 | DESC : Generating core manually create defunct processes still attached to LRC process. FIX: Prevent core generation to create defunct processes. |
RDTP-22238 | DESC : Map view of device/BS list does not switch to full screen when using “search this area”. FIX: When using “search this area” functionality, we now switch to full screen. |
RDTP-20355 | DESC : Wrong decimal precision for BS backhaul statistics graphs. FIX: Limit decimal precision to two digits. |
Known issues and limitations
ID | Summary |
---|---|
RDTP-21977 | [LoRaWAN relays] When a downlink packet cannot be sent for an end-device via a relay because of the maximum payload size constraint, there is currently no delivery failure indication reported to AS nor visible in Wireless Logger at end-device level. This issue shall be fixed in the next release. |
RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection. |
RDTP-23439 | [LoRaWAN relays] LRC should send the RootWorSKey to the relay after rejoining. |
Release 8.0.0
New features
ID | Summary |
---|---|
RDTP-11863 | Enriched configuration of Basic HTTPS connections |
RDTP-17339 | Improved monitoring of the device's battery history |
RDTP-16304 | Device management UI/UX enhancements |
RDTP-19911 | Enhanced MongoDB replication model |
RDTP-19650 | Allow managing domains, user accounts and service accounts through API |
RDTP-22478 | Use of distroless containers |
RDTP-21595 | OS upgrade to AlmaLinux 9 |
RDTP-17092 | Federated authentication |
RDTP-11865 | Support public connections predefined by Actility |
Other technical improvements
ID | Summary |
---|---|
RDTP-17092 | Ability to lock/unlock user accounts and service accounts by an administrator. |
RDTP-19911 | Upgrade MongoDB to version 7.0.5. |
RDTP-22298 | Upgrade MariaDB to version 10.11. |
RDTP-22299 | Upgrade Kafka to version 3.7.0. |
RDTP-22614 | Upgrade zookeeper to version 3.4.6. |
RDTP-22437 | Infrastructure cost savings thanks to rack-aware kafka consumers for the LRC subsystem. |
RDTP-22763 | Alignment of the roaming result codes for laggard Join-Request messages like regular uplink packets. Additionally, the sNS error code is now preserved by the fNS as is and shown in WLogger without any change. |
Resolved issues
ID | Summary |
---|---|
RDTP-23192 | DESC : Basics Station may stuck when no frame S received. FIX: Disconnect then automatically reconnect the Basics Station to avoid keeping any deadline situation. |
RDTP-23188 | DESC : Basics Station raising an error "Cannot send I : window 8 reached VS:30414 VA:30406". FIX: Implement the appropriate mitigation technique in the LNS-BRIDGE. |
RDTP-23184 | DESC : Bad UX during mass association of devices/BS with domains. FIX: Allow using the vertical scroll to move down on the drop-down list when selecting domains. |
RDTP-23003 | DESC : Inaccurate message returned when downlink payload size exceeds the allowed limit for device served by basics station . FIX: When sending a DL to the LRC cluster, TPE must first try the primary LRC node (LRC1) then backtrack to LRC2 if the LRC1 is down or if the BS is not connected to the LRC1. |
RDTP-22648 | DESC : Base station provisioning hit "500 Internal Server Error". FIX: Fix RCA-PROV to avoid certificate generation failure when the LRR-UUID is in lower case in the certificate username. |
RDTP-22622 | DESC : Wrong tooltip on BS list for "Packets (1h)". FIX: Fix the tooltip to indicate that both UL + DL packets are counted. |
RDTP-15984 | DESC : FTP URLs are not rejected by TPE GUI when configuring basic HTTPS connections, although they don't work. FIX: FTP URLs are not authorized by the GUI, the regex is updated to deny ftp addresses with basic https applications. |
RDTP-21154 | DESC : The base station appears connected to LRC when LRC is down. FIX: Rely on the LRR_wan report generated by the LRR base station to detect when it is disconnected from only 1 LRC node of the cluster. |
RDTP-22719 | DESC : The device count in the Connections list is sometimes wrong. FIX: Fix the GUI bug in the list of Connections. |
Known issues and limitations
ID | Summary |
---|---|
RDTP-21977 | [LoRaWAN relays] When a downlink packet cannot be sent for an end-device via a relay because of the maximum payload size constraint, there is currently no delivery failure indication reported to AS nor visible in Wireless Logger at end-device level. This issue shall be fixed in the next release. |
RDTP-23489 | [LoRaWAN relays] Endless Request/Answer loops in case of command rejection. |
RDTP-23439 | [LoRaWAN relays] LRC should send the RootWorSKey to the relay after rejoining. |