Skip to main content

ThingPark Enterprise SaaS changelog

This page references all the changes included in ThingPark Enterprise SaaS release 7.3, 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 7.3.3

New features

IDSummary
RDTP-21377Isolate Connections by domains
RDTP-18681Support remote access for gateways using Basics Station packet forwarder
RDTP-20905UI/UX improvement for gateways using Basics Station packet forwarder
RDTP-21151Explicit indication of UL/DL packets served via LoRaWAN relays

Other technical improvements

N/A.

Resolved issues

IDSummary
RDTP-21747 / RDTP-21482DESC : In TPE GUI, the “Network server” widget (under the backhaul statistics tab of the Base Station details) does not work when a base station uses TLS.
FIX : Adapt the identification mechanism of the master vs. backup network server nodes to the TLS mode.
RDTP-21359DESC : On multicast downlink, WLogger should display the effective transmission timestamp by the BS, not the LRC timestamp.
FIX : LRC behavior is fixed to report the correct LRR time/date of the downlink multicast packets to Wireless Logger and AS.
RDTP-21695DESC : Incorrect documentation link on new device import page.
FIX : Link is redirected to the correct place.
RDTP-21939DESC : During the device creation, the enforcement of DevEUI unicity does not properly handle lower case.
FIX : Lower case is now treated as upper case to ensure full enforcement of DevEUI unicity.
RDTP-21841DESC : In TPE GUI, the BS antenna name is wrongly displayed with the label “RF antenna ID”.
FIX : The label "RF antenna ID" is renamed “Antenna name“.
RDTP-21756DESC : During the device creation by QR code, the device model cannot be identified after scanning a QR code.
FIX : Fix the bug, which was a side effect of having multiple ISM bands associated with the same model.
RDTP-21748DESC : Login error when the first one-time code is not entered quickly enough.
FIX : The Login action timeout is now set to 30 min.
RDTP-21700DESC : BS Radio Traffic History graph shows inconsistent packet counts.
FIX : Aggregation data algorithm has been reworked.
RDTP-20838DESC : The GUI error displayed when adding an already-claimed OTA device using the "External Join Server" mode is not clear.
FIX : The error message is enhanced to simplify troubleshoot. The new error is "Claim failed: the DevEUI xxxxxxxx is already claimed".
RDTP-14992DESC : Base station health state is not updated in real-time.
FIX : By default, base station is set to “Active“ state as soon as it receives an uplink frame or successfully sends an OSS report to the system.
RDTP-21650DESC : Basics Station does not work with RF Regions activating LBT, such as K920.
FIX : Update the Basics Station configuration sent by the LNS to properly set the LBT carrier sensing level when LBT is activated .
RDTP-21774DESC : [LoRaWAN Relays] Missing delivery failure cause when the Join Accept fails.
FIX : The right DeliveryFailedCause4 (for RXR slot) is now displayed in Wireless Logger in case of Join Accept transmission failure.
RDTP-21646DESC : [LoRaWAN Relays] Relays provisioned in class C mode don't operate properly .
FIX : A relay may be provisioned as a class C device and may operate in class C like any conventional device. However, to comply with LoRaWAN Relay specifications, encapsulated DL frames (using Fport 226) only use RX1/RX2 of class A mode, not the extended RX2 slot of class C mode.
RDTP-21645DESC : [LoRaWAN Relays] Duplicate uplink frames sent by the relay are visible in WLogger.
FIX : Repeated uplink frames sent by relays on FPort 226 are deduplicated by the network server, so they are displayed only once in WLogger.
RDTP-21166DESC : [LoRaWAN Relays] The max DL payload size is not properly enforced when the end-device is served via a relay .
FIX : For each DL packet sent to the end-device via a relay, the DL max payload size correctly accounts for the constraints on both radio links: network -> relay and relay -> end-device. Hence, the transmission of a DL packet is rejected if at least one of the two links does not fulfill the max payload size (or dwell time) constraints. See the related limitation in the following section.

Known issues and limitations

IDSummary
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 maintenance release.

Release 7.3.2

New features

IDSummary
RDTP-18990New KPI dashboard for TPE-SaaS administrators
RDTP-2555New platform-wide notification banner
RDTP-16693UI/UX enhancements
RDTP-20376Decoding of relay-specific data in Wireless Logger
RDTP-20502Report to AS the count of missing UL packets

Other technical improvements

N/A.

Resolved issues

IDSummary
RDTP-21538DESC : Wrong error message when user tries to claim a device already claimed by an other subscriber.
FIX : The correct message is now “The DevEUI must be unique. A device with the same DevEUI already exists”.
RDTP-21529DESC : Occurrence of 502 Bad Gateway errors on clients.
FIX : Rollback to jre 11.0.16 version where the known issue is not present.
RDTP-21509DESC : Daily GUI stats do not work when time zone is different from Europe/Paris.
FIX : Associated caching issue has been solved.
RDTP-21449DESC : Links in DX-API and DX-CORE swagger must be removed.
FIX : Links in DX-API and DX-CORE swagger were removed.
RDTP-21346DESC : DX admin does not obfuscate secret in case of Bad request.
FIX : Secret is now correctly obfuscated in this specific case.
RDTP-21334DESC : LRR reports are ignored by ThingPark backend.
FIX : LRR reports are processed correctly and no more ignored by the backend.
RDTP-21333DESC : FCntUp information is present in clear state for alarm 006 ( or alarm 005) at level 0.
FIX : FCntUp information is no more present for these alarms at level 0.
RDTP-21332DESC : Base station creation with API may be rejected if created without RF Region.
FIX : OSS api documentation has been updated to highlight the correct way to process base station creation.
RDTP-21321DESC : LRC does not implement default relay parameters value that is needed when device supports the relay feature while its regional parameters version is earlier than lorawan specification RP2-1.0.4.
FIX : Implement default relay parameters value in LRC.
RDTP-21318DESC : Configuring alarm filters fully reloads the page, removing the focus on alarm list.
FIX : The page reload keeps the previous focus.
RDTP-21296DESC : DX documentation need enhancement with some wording changes.
FIX : DX documentation is now aligned with the TPE SaaS 7.3.2 capabilities.
RDTP-21280DESC : Tooltip on motion indicator configuration is not aligned with specification.
FIX : Tooltip is now correctly aligned with specification.
RDTP-21267DESC : Join accept and Downlink are not reported to AS.
FIX : Activate by default device notification in configuration file.
RDTP-21242DESC : Clearing criteria must be enhanced for device alarm 005.
FIX : Clearing criteria has been enhanced for device alarm 005 if "expected_SF" is not reported.
RDTP-21226DESC : LRC doesn't report SpfactExpected value.
FIX : LRC reports correctly SpfactExpected value.
RDTP-21203DESC : Exception in TWA while creating a connection via DX-API.
FIX : Fix issue in DX-API.
RDTP-21190DESC : Cannot delete or create a Base station/Device if incorrectly stored in a previous operation.
FIX : Allow to delete or create a Base sation/Device if incorrectly stored in a previous operation.
RDTP-21163DESC : “Signal strength and noise” and “duty cycle” drop down list are not readable.
FIX : Width has been increased to allow readability.
RDTP-21567DESC : DX-API documentation is unclear about BS provisioning.
FIX : Rfregion parameter in BS provisioning is now correctly described as an object in DX documentation.
RDTP-21565DESC : Wireless logger takes too much time to reload.
FIX : Packet type filtering has been enhanced.

Known issues and limitations

N/A.

Release 7.3.1

New features

N/A.

Other technical improvements

IDSummary
RDTP-20865Allow collecting LRC traces for a specific device
RDTP-16527[DX-API] New authentication flow based on Service Accounts

Resolved issues

IDSummary
RDTP-21279DESC : DX admin is deprecated in swagger UI.
FIX : Deprecation notification has been removed from swagger UI.
RDTP-21239DESC : Links to documentation from the user interface are wrong.
FIX : Links have been updated and tested as valid.
RDTP-21196DESC : Create base station operation return a HTTP 500 error.
FIX : Regression has been fixed.
RDTP-21114DESC : Auto-generated security certificate marked as downloaded before it is downloaded by the Base Station.
FIX : Generate certificate one day before it will be downloaded by the Base Station.
RDTP-20994DESC : Gateway's status not displayed correctly
FIX : LRR reports are now processed in the way that will avoid incorrect gateway's status display
RDTP-20963DESC : Class B downlinks not displayed on Wireless Logger in accordance to the sequence of downlinks being sent.
FIX : Fix incorrect date associated to downlink in wrong order.
RDTP-20891DESC : Antennas added in a Base Station profile are not available for BS previously created with this profile.
FIX : Antennas added in used Base Station are now propagated to Base Station already associated.
RDTP-20496DESC : Gateway Class B are activated after a TPW/TPE SaaS 7.2 update.
FIX : Update to 7.2 or 7.3 version will no longer activate wrongly Class B on Base Station.
RDTP-19927DESC : Device alarm 006 “Node uses lower data rate than expected” do not take into account UL confirmed mode with no DL Ack.
FIX : Algorithm has been enhanced in order to implement the case where UL confirmed mode does not receive DL Ack.
RDTP-19860DESC : Radio traffic history widget shows wrong data.
FIX : Take into account all BS antenna and implement new API end point to retrieve transmission failures.

Known issues and limitations

N/A.

Release 7.3.0

New features

IDSummary
RDTP-18706LoRaWAN relays (PoC)
RDTP-5254Alarm notification via IoT Flow connections
RDTP-16597Simplified integration with ThingPark APIs
RDTP-19333Improved monitoring of the OTA activation procedure
RDTP-2308Suspension of the device connectivity
RDTP-15298[Wireless Logger] Display Join-Accept messages in decoded format
RDTP-18975[Wireless Logger] More comprehensive icons/colors
RDTP-19585New color conventions for UL/DL packets in Network Manager
RDTP-14093Configuration of the motion indicator for each device
RDTP-16775Enrichment of the device dashboard
RDTP-16536Enrichment of the device dashboard
RDTP-11836Support custom Connectivity Plans

Other technical improvements

IDSummary
RDTP-19611Support any block of 32 type-7 NetIDs
RDTP-15321Keycloak upgrade to version 19.0.3
RDTP-18763EJBCA upgrade to version 7.11.0
RDTP-19910MongoDB upgrade to version 4.4
RDTP-20753Kafka, Zookeeper and RCA_PROV upgrade
RDTP-19849Use stdout for LRC logs

Resolved issues

IDSummary
RDTP-20913DESC : Device alarm 004 & BS alarm 103 should only be raised if device/BS joined the NS once.
FIX : Associated alarms are now triggered only if Base Station or Device connected at least before.
RDTP-15465DESC : Wlogger is displaying double arrow instead of red cross on downlink too late ( RX1 and RX2 ).
FIX : Red cross is now correctly used.
RDTP-20630DESC : Removing antenna coordinates throw an error.
FIX : No more error is raised now when removing antenna coordinates.
RDTP-18760DESC : Alarm event message for base station alarm 121 and 108 is missing "previousSeverity" value.
FIX : Previous severity is now correctly filled to allow SNMP trap to be sent.
RDTP-18761DESC : Wrong OID in SNMP trap for base station alarm Backhaul network interface status (121).
FIX : OID has been corrected to match with the MIB description.

Known issues and limitations

N/A.