**Maintenance window: 05.07.2022, 09:00 to 13:00 CEST
There will be a short downtime of appr. 10 minutes at around 10 am.

Service Interruption:
The device communication will be interrupted during this downtime. We try to find a solution to avoid message loss for your devices but be prepared that you might lose some uplink packages during these 10 minutes.

Please contact me/us in case you’ve got any questions.

We apologize for the inconvenience.

If the demands for ipv6 grows, we will consider implement it

@Ravindra-Singh428 can you try to send data again please?

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.

Maintenance window:
May 10th, 2022 at 4:00 am CEST
May 17th, 2022 at 4:00 am CEST

Service Interruption:
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.

@MarcoPeli Thank you, this was the problem. ;)

@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 support@iotcreators.com and we will help you out with your order. Sorry for the inconvience.

BR
Florian

Hi Mikael,

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.

BR
Florian

@Jan-Kolorenc-0 hello Jan, i wrote you in private

@Philipp-Berg-0 All good, I have not been aware that clicking Save already triggers a validation of the URL and an sending an “empty” package to the endpoint.

Hi Rik,

can we have a conf-call about this topic. We are currently making customer interviews to understand your requirements better.

Yes, we can raise priority for this topic :)

I will send you and email to schedule a conf-call.

Regards, Roland

Now my additional hint about the AT commands: please have a look at our AT command guide for the modems
Please use the APN that I mentioned above because the one in the script is from IoT Creators.

By using eDRX the device is able to receive downlink messages without sending uplinks.

Let me know if this helps:

https://docs.iotcreators.com/reference/send-base64-edrx-downlink-message

@GrandPep I had a look to your configurations. I saw that you registered for your API account an application URL but I cannot see any subscriptions. I will verify it and come back to you…

Regards, Roland

Unfortunately, LTE-M is not commercially available yet. I will answer to your email to give you some options.

@roalnd-baldin It seems to work with curl in command if the data-raw is rewritten like so:

–data-raw “{
\“resourceValue\”: \“48656c6c6f20446576696365\”
}”

In command we get a nice “msg”:“Accepted”,“code”:1002 response but in Postman it does not work. And with the registration to https://{{base_url}}/m2m/applications/registration this was not an issue.

@jeroen-van-bussel it’s great to hear 👍

NB-IoT and LoRa - partners in crime🕵🏽

@lauwie007 It’s a new feature we added a while ago - at the moment, unfortunately, you need to set it when registering the devices and cannot be changed later. So you would need to re-add the devices to make it work.

Let’s set up a call and we can go through some options regarding the different end-points with multiple projects. Please just send me an email to florian@iotcreators.com with some meeting proposals.