Group Details Private


System administrators


Member List

  • RE: Kan ik ook nano SIMs bestellen?

    Als het goed is, zijn ze onderweg… (begreep ik vab Eric).

    posted in T-Mobile NL Connectivity Workplace and API
  • RE: CoAp documentatie

    Hoi @JeroenD ,

    Er staat informatie over hoe data verstuurd wordt in onze documentatie.
    Over CoAp is niet veel beschreven, onze CoAp server is een vrij specifieke implementatie van CoAp voor HiSilicon chipset devices en daarmee niet te gebruiken alse een generieke CoAp server, ik zou je willen aanraden om met UDP aan de slag te gaan en CoAp te termineren op jouw application server.

    posted in T-Mobile NL Connectivity Workplace and API
  • RE: No connection to the Cloud of Things


    Thank you very much for your request. The MQTT-SN CONNECT packet looks right so far and since you get an answer from the gateway, the communication works well. It seems that the registration in the cloud of things is not quite correct, especially the field ICCID. Quote from the user manual:

    ICCID: The ICCID of the device (equal to the ID of the device)

    Important here is the addition in brackets “equal to ID of the device”. In this case, the ID of the device is the IMSI and must also be specified when registering the device. Please try the registration of the device again with the IMSI in the field ICCID, then it should work.

    posted in Cloud of Things
  • RE: Events covered by menu

    unfortunately our UI is sometimes not working the way we have wished to.

    You can fold the menu by using the toggle button or use zoom in/out option of your browser to view full content. In this case, however, it seems to me that there is no additional incoming message, but the UI falsely suggests that there is additional message.

    posted in Cloud of Things
  • RE: Device is not displayed on map

    A “pin” can only appear if the Device has sent a position. This ability is related to the functions of the device. Whether this was the case is not clear from the question.

    For devices that are connected to the CoT via NB-IoT or MQTT-SN, the IMSI is the identifier to which the respective password is linked. If you use a different IMSI for the same device, you also need separate credentials for this identifier, i.e. you must register a second device in the CoT. The IMSI must be unique.

    When registering, it is sufficient to first create only the credentials based on the IMSI. An IMEI does not necessarily have to be specified. In this case, no devices need to be deleted from the CoT either, since you then have two different devices in the CoT which are either online or offline depending on the SIM card used. It is only important that the device also uses the credentials coupled with the respective IMSI.

    posted in Cloud of Things
  • RE: Device registration in the Telekom Cloud

    unfortunately, IMEI alone is not enough for the registration of NB-IOT devices but must be created with credentials. In the attached manual you will find the exact instructions for the registration of the NB-IoT devices.

    posted in Cloud of Things
  • RE: Dashboard shell functionality

    The shell command functionality is currently part of the Device Management app. There is currently no dedicated shell widget in the Cockpit app, however we may consider it in the future.

    To access “Shell”, switch from Cockpit to Device Management and under “All devices” pick the device you want to administer. “Shell” appears as one of the tabs.

    For more information please refer to the user guide.

    posted in Cloud of Things
  • Release announcement: Activation of NB-IoT network features for AT, CZ, DE & NL

    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

    More information can be found in the attached document: Feature Release Communication

    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!

    posted in Announcements
  • RE: Kan ik ook nano SIMs bestellen?

    We hebben ze wel! Alleen nog niet in de webshop. Ik laat je snel even weten hoe we ze jouw kant op kunnen krijgen.

    posted in T-Mobile NL Connectivity Workplace and API
  • RE: NON-IP Maximum bytes size

    Weet het niet zeker, maar ik dacht 317 bytes.

    posted in T-Mobile NL Connectivity Workplace and API

Looks like your connection to Internet of Things was lost, please wait while we try to reconnect.