Awesome news ahead: LwM2M v1.2 specification is finally released! One of the headlining features of LwM2M v1.2 is LwM2M over MQTT! This is a good opportunity for LwM2M to get way more visibility, as MQTT (arguably the most popular IoT protocol) is currently missing any real data model.
LwM2M 1.2 feature highlights: 
State-of-the-art energy-efficient security—Leveraging (D)TLS 1.3 and Connection ID enhances security while reducing the challenges and energy losses of connecting devices over LPWAs like NB-IoT.
MQTT as a transport protocol—MQTT users can now add LwM2M device management functionality. Inversely, using MQTT as a transport mechanism for LwM2M simplifies connecting to the cloud in some scenarios.
Single-step device commissioning—Now, bootstrapping a device requires just a single bi-directional session instead of the previous five exchanges, saving time, energy, and other resources.
Optimized data reporting—LwM2M data-format optimizations shave bytes from each message, increasing energy-efficiency, device lifespan, and return-on-investment (ROI).
More details: 
New transports for LwM2M; this allows LwM2M messaging to be conveyed over MQTT and over HTTP.
Optimizations for the bootstrapping interface; this reduces the amount of data and the number of messages transmitted during the bootstrapping exchange.
Optimizations for the registration interface; this reduces the amount of data transmitted during registration exchanges.
Optimizations for the information reporting interface; observation attributes may now be included in an Observe operation.
Support for LwM2M gateway functionality; this allows non-LwM2M IoT devices as well as LwM2M devices behind a gateway to be connected to the LwM2M ecosystem and to manage those devices remotely.
New, highly optimized encoding format based on CBOR called LwM2M CBOR.
Enhanced functionality for firmware updates.
Definition of new notification attributes (edge, confirmable notification, and maximum historical queue). Edge allows notifications to be triggered on rising and falling edges. Confirmable notifications allow the control of reliable transmissions of notifications.
Maximum historical queue allows the control of time-series data usage. Clarifications of object versioning rules.
Updates to use the latest communication security protocols based on TLS and DTLS 1.3 (as well as the use of the Connection ID).
Flexibility to control the use of TLS and DTLS 1.3 through configuration information.
Untangling the relationship of security credentials and their server configuration.
the first version of documentation for SIMCom SIM7022 how to
attach the device to Telekom NB-IoT network of IoT Creators and get assigned an IP address.
Send “Hello World” uplink message via UDP from device to IoT Creators UDP server.
Send “Hello Device” downlink message via UDP from IoT Creators portal to device.
Receive “Hello Device” downlink message on device via UDP from IoT Creators UDP server.
is available now in IoT Creators documentation library.
We do these tests in parallel to normal network maintenance and improvement measures and we can share some preliminary results in CE-0 conditions from measurements in our Labs.
• Up to 200 devices can attach successfully simultaneously within 10 minutes under the condition that they do not immediately send data after a successful attach.
• Average round trip time (RTT) increases with increasing number of parallel transmitting devices. A randomization of transmission attempts leads to reduction of RTT and potentially improvement of battery lifetime
• With regards to the initial attach, only a small number of devices should be activated simultaneously (max. 60 devices)
• With regards to the regular data transmission with good signal level the following was observed:
• Failure rates increase with more than 160 devices trying to send 100 byte of data within one second
• Introducing a randomization timer of at least 40 seconds solves this limitation
• Avoiding synchronized data transmission results in better share of coverage levels across all devices
• Implication - Customers should avoid synchronized attaches and data-transmission of their devices
after we integrated the connectivity from Magenta Austria in the last days with IoT Creators/SCS platform succesfully I tryed with my devkit Quectel BG96 not only NB-IoT but also LTE-M and GSM - unfortunately pure LTE is not supported by the devkit.
It worked immediatly 🙂
With following AT commands I could connect to our Telekom network in Germany and send UDP messages to our server:
# Set frequency band for Telekom Germany
# Set our APN
# Use 0 for GSM ...
# ... or 8 for LTE-M
# ... or 9 for NB-IoT
# Connect to our UDP server
# Send "hello world" as hex
Together with The Things Industries we are combining LTE-M and LoRaWAN capabilities to provide an out-of-the-box connectivity solution allowing for easy to setup and secure device-to-cloud communication.
LTE-M features very good signal penetration, well-suited for standalone, managed gateways inside, for example, smart buildings. The solution will therefore start with a pre-configured LoRaWAN gateway from Mikrotik, connected over a LTE-M backhaul to LoRa devices and The Things Industry platform.
Use of LTE-M reduces costs compared to LTE because of more affordable hardware, and lower usage costs. Ease of use for the customer is guaranteed through no-touch provisioning of gateways, as they come pre-registered and only need powering up when installed. The gateway optionally supports LoRa 2.4GHz for global deployments.
To support IoT deployments in Germany and the Netherlands, an Early Access offer will be launched with LTE-M backhaul for solution providers and system integrators - learn more and get started 👈
Rise to the challenge and solve global problems concerning Covid-19, Environmental Sensing, or Habitat Destruction using the new SODAQ N3 board. It leverages the advantages of upcoming LTE Cat NB2 networks such as mobility enhancement, E-Cell ID, larger TB size, two HARQ processes, multi-carrier enhancement, single-tone and multi-tone uplink. The SFF board features an integrated Microcontroller (Microchip Atmel SAMD21), GPS (uBlox EVA 8M for GPS (Galileo, GLONASS, and Beidou support) and sensors including LSM303AGR digital magnetometer and accelerometer.
In collaboration with Sodaq and u-blox we are hosting a competition in which 3 participants can win 10 new SODAQ N3 boards to prove their concept to the world. In addition, the winners will receive 10 Deutsche Telekom SIM cards with one year connectivity. Any developer, for fun or for commercial purposes, can participate in the contest until December 4, 2020. More details: http://sodaq.com/n3-launch-contest/
from December 6th, 2020 on, our IoT Forum will only be reachable via direct URL forum.iotcreators.com.
The former URL iotbytelekom.com, which was used to redirect you to the forum, will be phased out.
If you have any questions, let us know. Simply start a discussion in the forum or contact email@example.com.
From 09.06.2020 our IoT Forum will be reachable under the new address: forum.iotcreators.com
With this jump we will get yet another step closer to the international community. Your account on IoT Forum will stay the same. You don’t have to change your password or any settings. Simply follow the new URL. If you are using https://iotbytelekom.com, this link will remain valid for the next months and will be redirected to our forum.
To make our online platform more attractive and informative, we are planning to host our Install Fest, publish more and more content relevant to you, like interviews with experts, industry insights and surveys. Thanks to the new URL and contents we hope to welcome more new members of the community and hence win more expertise, knowledge-sharing and discussions.
Stay up to date for news and our events at forum.iotcreators.com subscribe and share the new web address with your colleagues, partners or on your social media channels.
If you have any questions, comments or topics you would like to get more information about, let us know. We are looking forward to your feedback! Simply start a discussion in the forum or contact us.
Take a look to our IoT Technology Cards to learn more about the Internet of Things.
Dear IoT Community,
Recently we published Technology Cards, which is an overview of all relevant technology topics about IoT. We’ve assembled a library of knowledge and resources to support your technology and implementation decision-making. We keep pace with the industry’s leading edge to present you what we learn.
Looking for information on specific technology topics, or just curious to learn more IoT trends? We welcome you to explore our IoT wiki and research what drives the IoT industry.
Explore our collection of IoT topics to gain insights into technology trends and features
Understand key technology concepts and how to implement them successfully
Make a more informed decision while setting-up for your IoT solution
Take part in our survey about localization services!
Dear Stefan, Thank you for you feedback. This is true, that all depends on the use case. Maybe you would like to share your ideas with us, about which use cases you’ve been thinking of? Nevertheless we just would like to undestand how important is the localization for our customers to improve our services.
Release announcement: Activation of NB-IoT network features
Dear IoT Community,
please note that we will soon be activating new features, as well as will update the configuration of already available features in the NB-IoT network. With the transition, you’ll be able to manage your NB-IoT devices even more flexibly and efficiently. The activation is currently planned for beginning of November and will affect our networks in Austria, Czech Republic, Germany and the Netherlands.
The changes at a glance:
• Switch to dynamic Power Saving Mode (PSM) - the network will now accept the values suggested by devices
• Switch to dynamic (long-periodic) Tracking Area Update (TAU/LP-TAU) - the network will now accept the values suggested by devices
• Introduction of Data Packet Buffering - the network will buffer up to 10 data packets for the sleeping devices in the PSM
If you already use PSM and / or TAU / LP-TAU, then please note that your devices may behave differently than usual after activating the network functions. We recommend checking the settings on your devices.
If you have questions, don’t hesitate to ask in our IoT Forum!
There are a few ground rules for participation in our forum. Please respect these rules, and each other.
The forum language is English. This is an international community, with members from all over the globe. To share the knowledge between all of us, we use English as primary language.
For specific topics according your country like Netherlands, please use the relating section. There are appropriate specialists to support you in your question.
All-important guides you can find in our IoT Documentation - that might help you at the beginning.
Be creative and have fun!
If you have a question but don’t want to place it publicly, you are more than welcome to write directly to us. Please use this e-mail address: firstname.lastname@example.org
@bob-mooij het heeft even geduurd maar ik wil hier toch op reageren.
De SIM kaarten die we tot op heden verstrekken kunnen alleen gebruik maken van deze APN : “cdp.iot.t-mobile.nl”.
Dit is ongeacht welk netwerk er geroamed wordt. (Onze global SIM kaarten roamen altijd overal).
Wat wel aangepast moet worden is de netwerkselectie.
Of handmatig (is sneller de eerste keer) maar land specifiek:
De lijst met codes is publieke informatie bijvoorbeeld hier: PLMN lijst
Voor NB-IOT kan er geroamed worden op alle Telekom netwerken waar NB-IOT beschikbaar is.
Er kan wel een aanpassing nodig zijn van de geselecteerde banden (B3, B8 of B20).
De AT commandos verschillen hiervoor per module.