deviceWISE Cloud 26.09 Release Notes
A number of improvements and fixes were added to the deviceWISE Cloud 26.09 release.
Production Release Date: October 2026
-
[Things] - Updated the delete confirmation for a thing to warn that deleting it causes a loss of historical data and cannot be undone.
-
[Developer - External SMS] - When adding multiple MSISDNs on the Known MSISDNs tab, the result message now identifies which MSISDNs were added and which failed, such as those that already existed.
-
[Connections] - The Set Active profile action and the Add MNO profile tab are not visible if the disableEsimLifecycleManagement is set to true at the Organization Profile level.
-
[Developer - Campaigns] - Fixed an issue where a non-blocking campaign that had been paused or canceled continued to run actions against devices for tasks that were in the waiting status; those tasks now stop in the pending status.
-
[Administration - Users] - Fixed an issue on the Administration > Users page where updating your own user record displayed the message "Please select at least one role." and the changes were not saved.
-
[Remote AT] - Fixed an issue on the Things > View > Remote AT tab where sending an AT command to an LwM2M device could leave the terminal showing the loading icon indefinitely instead of displaying the device response.
-
[VAS Packages] - Fixed an issue on the Administration > VAS packages page where, when only one package was listed, the hover tooltip covered the View, Edit and Delete buttons so they could not be clicked.
-
[Administration - Sessions] - Fixed an issue on the Administration > Sessions page where the date filter controls disappeared when a search returned no sessions, so a new search could not be run without refreshing the page.
-
[LwM2M] - Fixed an issue where requests to an LwM2M device connected over DTLS could fail with a "DTLS peer not found" error shortly after the device sent a registration update.
-
[Triggers] - Fixed an issue where the dynamic.exec trigger action and the trigger.dynamic.exec command did not return the sub-trigger's trigger.result output.