Hi,

today we took a nice comort sensor (CO2/Temp/Humidity/BodySense) in Barcelona into operation.

We configured

• 21401 as PLMN ID for Vodafone Spain
• and used 20 for the frequencyband (800Mhz).
• cdp.iot.t-mobile.nl as APN for IoT Creators

It worked immediately without any problems.

Regards, Roland

Hi Stefan,

you are a cool guy!! This solved the problem. It was the whitespace.

Many many thanks for your support!!

Regards, Roland

Hi Stefan,

again many thanks. It works now. I can send data to my App. The following sequence works for Quectel BC66:

Deactivate auto sleep mode

AT+QSCLK=0

Persistent network and APN setup

AT+QBAND=1,8
AT+CFUN=0
AT*MCGDEFCONT="IP","cdp.iot.t-mobile.nl"

Restart the module as some configurations only take place after a reboot.

AT+QRST=1

After reboot wakup from sleep, deactivate auto sleep mode again and wait for network connect

AT+QSCLK=0

+IP: 10.128.0.134

Create a UDP socket and for UDP server

AT+QIOPEN=1,1,"UDP","172.27.131.100",15683,1001,0,0

Send message “Hello World”

AT+QISEND=1,11,48656c6c6f20576f726c64

Hi Mario,

Tuino 096 is an Arduino Zero (M0) compatible board. Grove Base Shield V2.0 doesn’t support this explicitity.

I recommand to try"ARDUINO MKR CONNECTOR CARRIER (GROVE COMPATIBLE)" instead. With this shield you can bridge from Zero/M0 to sensors with Grove connectors.

Regards, Roland

Hi Joop,

I will fix this.

Could you please give me your IMEI?

Regards, Roland

@paulvha This URL and headers work for me:

To get the list of all devices:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1

Headers:
Content-Type:application/json
Authorization:Basic base64(<USERNAME>:<PASSWORD>)
Accept:application/json

This should work with your credentials:
curl -X GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1 -H 'Authorization:Basic base(<USERNAME>:<PASSWORD>)

As you can see the request works also without Content-Type and Accept.

To get the details of a single device:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device/<ID>

Headers:
Content-Type:application/json
Authorization:Basic base64(USERNAME:PASSWORD)
Accept:application/json

To get the details of the device don’t use the deviceId!

Regards, Roland

Hi Petr,

if I understood you right I see the following challenges:

1. find a location with NB IoT coverage.
2. attach your device to the NB-IoT network of T-Mobile Czech.
3. send messages via UDP to Cloud of Things
4. decode the payload of your UDP message and integrate it with Cloud of Things

Please let us get directly in contact, that we can speak about it (roland.baldin@t-systems.com).

Regards, Roland

To add a seconde application URL you can perform the following …

With the username and password from the projects API credentials

Put the following HTTP request:

PUT:
https://iot.netwerk.t-mobile.nl:443/m2m/applications/registration

HEADERS:
Content-Type: application/json
Authorization: Basic base64(<USERNAME>:<PASSWORD>)
Accept’: 'application/json

BODY:
{
‘url’: ‘<YOUR APPLICATION URL>’,
‘headers’: { <YOUR HEADER FIELDS>}
}

If everything works fine you should get returned from the API
{
“msg”: “Success”,
“code”: 1000
}

@Stefan-de-Lange Hi Stefan, nezwork specialists developed a simulation tool for NB-IoT devices with which it is possible to understand the power consumption and battery live time by simulating different protocolls and NB-IoT features.

Let me try ro access to it. We can have a conf-call and play a little bit with it. Maybe it is interesting for us.
I guess my colleagues are interested in our feedback about it.

Regards, Roland

@afzal_m said in Is there any way for my device to know if a packet it has sent has been received?:

https://docs.iotcreators.com/docs/ii-network-attach

The link to the documentation has changed to https://docs.iotcreators.com/docs/sodaq-sara-aff-n211-1

To add a seconde application URL you can perform the following …

With the username and password from the projects API credentials

Put the following HTTP request:

PUT:
https://iot.netwerk.t-mobile.nl:443/m2m/applications/registration

HEADERS:
Content-Type: application/json
Authorization: Basic base64(<USERNAME>:<PASSWORD>)
Accept’: 'application/json

BODY:
{
‘url’: ‘<YOUR APPLICATION URL>’,
‘headers’: { <YOUR HEADER FIELDS>}
}

If everything works fine you should get returned from the API
{
“msg”: “Success”,
“code”: 1000
}

@lbr hi, if you still have problems please contact me via support@iotcreators.com and provide me your imei. I will help you.

Regards, Roland

Hi,

today we took a nice comort sensor (CO2/Temp/Humidity/BodySense) in Barcelona into operation.

We configured

• 21401 as PLMN ID for Vodafone Spain
• and used 20 for the frequencyband (800Mhz).
• cdp.iot.t-mobile.nl as APN for IoT Creators

It worked immediately without any problems.

Regards, Roland

@Wessam Hi, have a look to https://forum.iotcreators.com/topic/626/how-long-does-it-take-that-the-network-detects-a-dead-ip-connection. Maybe it contains some info you are interested in.

Regards, Roland

Hi guys,

I made some test to the automatic release of IP addresses by the network.

With the “Tuino096 - Quectel BG96” I attached to the network with the following AT commands:

AT+CGDCONT=1,“IP”,“cdp.iot.t-mobile.nl”
AT+COPS=1,2,“26201”,9
AT+CGPADDR
+CGPADDR: 1,10.0.4.102

As a Telekom employee I am in the lucky situation that I can check the IP status of the device via some monitoring systems. Of cause I could see that the my device with its IMEI and IMSI got assigned the IP address 10.0.4.102.

After this I just unplucked my device from power and checked the IP connection status of the IMEI.
It took about ca. 2 hours the DCD of the network recognized that the device is dead and release the IP address to be used again by other devices.
I repeated this test a few times and I could reproduce the 2 hours.

BUT if I power up the device after I swiched it off and attach it bag to the network the network detects the same IMEI and IMSI requires a new IP. By this the provious IP is released immediately and a new IP is assigned to the device.

Hope this info helps you a bit to get a better understanding what is going on in the network.

Cheers, Roland

@paulvha This URL and headers work for me:

To get the list of all devices:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1

Headers:
Content-Type:application/json
Authorization:Basic base64(<USERNAME>:<PASSWORD>)
Accept:application/json

This should work with your credentials:
curl -X GET https://iot.netwerk.t-mobile.nl:443/rest/device?iDisplayLength=-1 -H 'Authorization:Basic base(<USERNAME>:<PASSWORD>)

As you can see the request works also without Content-Type and Accept.

To get the details of a single device:
URL:
GET https://iot.netwerk.t-mobile.nl:443/rest/device/<ID>

Headers:
Content-Type:application/json
Authorization:Basic base64(USERNAME:PASSWORD)
Accept:application/json

To get the details of the device don’t use the deviceId!

Regards, Roland

@Malte-Neumann Hi Malte, please send the 10 ICCIDs to support@iotcreators.com . I will check them .

Please use as PLMN IDs from page https://docs.iotcreators.com/docs/telekom-iot-networks-in-europe

Regards, Roland

@Ronan-Lacroix I have a question: The min value for T3412 is only valid for the “extended” version of TAU ? Does the 1 hour apply also to the min. value of standard TAU or is it shorter?
Having a min TAU of 1 hour seems to me for many use cases difficult because the devices in those use cases need to wakeup from sleeping much more often (e.g. every 10 minutes).

Many many thanks for your support!

Regards, Roland
I

@Eben-van-Ellewee @Stefan-de-Lange Many many thanks for this hints! I will take this to our doc and dev team.

Regards, Roland

@Eben-van-Ellewee I opened the page with Chrome, Internet Explorer, Firefox. Additionally I did a “Save as” with Chrome and I also did a “GET” of the URL with Postman. In any of those cases I didn’t get any security complains of my HTTP client or the proxy.

Two days ago we had an outage for some hours of our documentation library. Maybe your problem has been caused by this.

Regards, Roland