Release Notes - IoT Creators - Version 1.0.42 (directly follows after 1.0.39) - Released 05.12.2022
This was a bigger release with the main focus on rebuilding our portal backend. But we also have release some cool new features.
Here is the overview:
*[IC-5495] - User with existing starterkit project land in order flow when clicking on “try for free” on homepage
*[IC-5366] - Non-IP device shows UDP in its details
*[IC-5489] - Shown number of devices does NOT meet real number
*[IC-5490] - Adding LoRaWAN (via the The Things Network) as protocol option
*[IC-5449] - LoRaWAN: Control with a checkbox if the device shall be created in LoRaWAN network server as well
*[IC-5473] - Create virtual Device via GUI
*[IC-5492] - Implement unscheduled uplink send in GUI
*[IC-5469] - Automatically add an uplink-message-tag when the user register a device
*[IC-4967] - Invoice due dates in portal
*[IC-5487] - Adjusted dropdown options for protocol selection when registering devices
*[IC-4984] - Adjust the FE to work with integer instead of FP numbers
*[IC-5379], [IC-5381], [IC-5400], [IC-5448], [IC-5486] - Security Improvements
*[IC-5485], [IC-5311]- Data Privacy Improvements
*[IC-5344], [IC-5474], [IC-5475], [IC-5476], [IC-5477], [IC-5478], [IC-5479], [IC-5499] to [IC-5505] - BE refactoring tasks (Merge, simplify and merge services) and bugfixes based on testing
*[IC-4968] - invoices linked to a user instead to a contract
please do not post sensible data here such as your sim card iccid, i wanted to delete it but i deleted your port instead by mistake, sorry for that!
You should now be able to add your sim card, please try to register it again in your project.
If you need further assistance, i am glad to help you!
Finally some good news: the system has been up again since this morning around 9 and since 10 without further disturbance. The team was able to stabilize the system further and currently we don’t see any more issues.
We will come back to you in the next days to give you some more insights on what happened and what we plan to do in order to prevent this from happening again.
Deutsche Telekom will upgrade their NB-IoT platform in order to proactively increase the capacity and make it more scalable and robust for the future. Doing this, we benefit from better feature set (like using NB-IoT and LTE-M traffic through the same VPN tunnel) as well as security hardening.
The migration of our APN “cdp.iot.t-mobile.nl” to the new platform will be performed by the Deutsche Telekom Core Network team automatically. It does not require any activity from your side, so there is no need for new configuration of your IoT solution or anything alike.
May 10th, 2022 at 4:00 am CEST
May 17th, 2022 at 4:00 am CEST
There will be a service interruption for approx. 45 minutes during the night. The devices will lose the PDP connection and need to create a new IP session at the end of the maintenance window. After the new platform starts operation, the devices will re-login to the network automatically and will get a new IP address.
Experience from other customers:
This maintenance work was already performed for the customers located in Germany. We didn’t receive incident reports related to this change. That’s why we’re optimistic that it will run smoothly for the IoT Creators APN as well.
Please contact me/us in case you’ve got any questions or doubts and concerns.
We apologize for the inconvenience and are optimistic that you’ll benefit in the future from that change.
@Mikael-Guenais If you order a free starterkit (incl. 1 SIM) you should be able to do the order process directly in the standard order flow. If you want to buy SIM cards, please reach out to email@example.com and we will help you out with your order. Sorry for the inconvience.
you can order a Starterkit with “public internet access” (it’s a bit misleading, but you need to select LTE-M starterkit in the order process). However, this is only available for testing purposes and not for productive systems. So in our paid plans we cannot offer this at the moment.
In our standard setup you would usually trigger the downlink message via API call (or directly in the portal) and thus the device’s IP does not need to be fixed.