Self-hosted ThingPark Enterprise changelog
This page references all the changes included in self-hosted ThingPark Enterprise 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.0
New features
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. |