Unfortunately we cannot answer this question at the moment. Please be patient, as we need to discuss the topic with our network experts.
Posts made by Noah Marx
RE: How to connect
What exactly do you mean with eSIM? Could it be a MFF SIM card (embedded SIM)?
RE: How a 5G mobile can solve the network coverage and network security issue?
What exactly do you want to know? Can you please specify your question a little further?
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.
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.
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.
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.
RE: Only one alarm can be sent
You are right. This is exactly how it is currently implemented. The NB-IoT CoT access is currently only a test product and thus the behavior of the alarm is not scheduled to change anytime soon. I will forward your request to our internal team for further discussions.
RE: NB IoT Connector & Protocol MQTT-SN
MQTT-SN is a protocol for data transmission (specification available here:
It works in the publish/subscribe manner. A device which wants to send data to CoT, needs to have implemented this protocol. The easiest way to implement is to use the Open Source Paho Client from von Eclipse.
CoT can only be addressed over the REST interface and therefore the connector is needed to convert incoming MQTT-SN messages to CoT messages.
There is a second important function of the connector. It interprets data, so for example temperature can be identified as such. Prerequisite for that is that MQTT-SN messages are being formatted according a predefined convention. How this is to be accomplished is described in the NBIOT-Protocol-Developerguide.
If MQTT-SN messages are correctly formatted and compliant to the convention described in the developerguide, then data is transferred into the Cloud of Things.
The mentioned IP address belongs to a private network, since it is the tunnel endpoint of the IPSec-tunnel from private APN of the CoT. This server is only acceible via the private APN.
For sending UDP packets to a server residing in the Internet, you need to have SIM cards with public APN (internet.nbiot.telekom.de). Since you have ordered only SIM cards for CoT, you are only able to send data to the CoT with IP 172.25.102.151:1883
RE: No connection with Cloud of Things
First of all, before sending any data we need to open a socket with the command
Afterwards, IMSI and PW need to be converted into the hexstring format. This means the
IMSI(ascii) = 012345678912345
IMSI(hexstring) = 303132333435363738393132333435
and the password
PW(ascii) = abcdefgh
PW(hexstring) = 6162636465666768
putting these values into the AT+NSOST command yields:
This means the hexstring version of payload has twice as many symbols
(58) as specified in the number of bytes transferred (29).
I hope that we this guidance everything will be fine.