Posts made by Roalnd Baldin

Roalnd Baldin

Hi,

instead of creating and deleting complete subscriptions after you added or deleted devices you can add or remove the device to or from from the existing subscription.

In the following the Nokia IMPACT API samples

to get the devices of an existing subscription,
list itemto add a devices to an existing subscription,
list itemto delete a devices from an existing subscription (important: if the last device of a subscription is delete the subscription it-self is deleted as well).

Get devices of an existing subscription

GET https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
HEADERS: {
 "Content-Type": "application/json", 
 "Accept": "application/json", 
 "Authorization": "Basic QVBJX0NPTsl8wMDssAswMDAbxNcTU4XzNlZmEzOkpySS9YOC45Y19CrrRmI0OEY="
} 
BODY: {
 "serialNumbers": [
 "IMEI:452749630137052", 
 "IMEI:351938100191440"
 ]
}

RETURN STATUS CODE: 200
RETURN BODY: {
  "serialNumbers": [
    "IMEI:454596441983713",
    "IMEI:351938100191440",
    "IMEI:866425033313638",
    "IMEI:452749630137052",
    "IMEI:352656100979544"
  ]
}

Add devices to an existing subscription

POST https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
HEADERS: {
  "Content-Type": "application/json", 
  "Accept": "application/json", 
  "Authorization": "Basic QVBJsX0NPTl8wMDsssswMDAbxNcTU4XzNlZmEzOkpySS9YOfgC45Y19CRmI0OEY="
}
BODY: {
  "serialNumbers": [
    "IMEI:452749630137052", 
    "IMEI:351938100191440"
  ]
}

RETURN STATUS CODE: 200
RETURN BODY: {
  "subscriptionId": "f37b094d-307f-4d43-82c5-73f81104e22f",
  "msg": "Success",
  "code": 1000
}

Delete devices from an existing subscription

DELETE https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
HEADERS: {
 "Content-Type": "application/json", 
 "Accept": "application/json", 
 "Authorization": "Basic QVBJsX0NPTl8wcMDssAwMDAbxNabcTU4XzNlZmEzOkpySS9YOC45Y19CRmI0OEY="
} 
BODY: {
 "serialNumbers": [
 "IMEI:452749630137052", 
 "IMEI:351938100191440"
 ]
}

RETURN STATUS CODE: 200
RETURN BODY: {
  "subscriptionId": "f37b094d-307f-4d43-82c5-73f81104e22f",
  "msg": "Success",
  "code": 1000
}

Roalnd Baldin

@magnatron It was never possible to store the application url if the application didn’t return 200.

In the old version the inital request contained an empty body to test if the URL is valid. This has actually changed. No an empty dictionary structure is put as payload.

Regads, Roland

Roalnd Baldin

Hi,

for your information:

IoT Creators platform (SCS) times out the message forwarding POST request to the application URL if the application doesn’t response within 5 seconds.

In case of timeout SCS tries to re-POST the message 5 times. Every minute one retry is performed.

While the systems trys to re-send the message no new messages are POSTed to the application. There are queued.

Roalnd Baldin

Hi Peter,

I just contacted you via our support channel so I can do some additional tests to your connection.

Can you please send my your IMEIs as a response to the email which you just got.

Many thanks!

Regards, Roland

Roalnd Baldin

Currently the API supports the following for functions/URLs to send downlink messages to the device

downlinkMsg/0/data
Sends regular queued downlink messages to device when uplink is received.
downlinkMsgBase64/0/data
Sends queued binary data blob message to device when an uplink is received. The function expects base64 encoded payload from the applaction as input into this function. Before the message is sent to the device it is decoded back to binary and sent to the device.
downlinkMsgDrx/0/data
Same like downlinkMsg/0/data but without queuing.
downlinkMsgBase64Drx/0/data
Same like downlinkMsgBase64/0/data but without queuing.

Roalnd Baldin

@Lauwie007 For my understanding there is no difference if the function transfers “hi” or “01AB” as value.
Regards, Roland

Roalnd Baldin

Hi guys,

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
AT+QCFG="band",0,0,80,1					

# Set our APN
AT+CGDCONT=1,"IP","scs.telekom.tma.iot"

# Use 0 for GSM  ...
AT+COPS=1,2,"26201",0

# ... or 8 for LTE-M
AT+COPS=1,2,"26201",8

# ... or 9 for NB-IoT
AT+COPS=1,2,"26201",9              

# Connect to our UDP server
AT+QIOPEN=1,1,"UDP","172.27.131.100",15683,1001,0

# Send "hello world" as hex
AT+QISENDEX=1,"48616c6c6f20576f726c64"

This is really cool !!

Cheers, Roland

Roalnd Baldin

@Lauwie007 Hi,

If I send “hi” with

PUT https://iot.netwerk.t-mobile.nl:443/m2m/endpoints/IMEI:867997031341158/downlinkMsg/0/data
and
BODY {
“resourceValue”: “hi”
}

I receive

AT+QISENDEX=1,11,48656c6c6f20576f726c64
OK
SEND OK
+QIURC: “recv”,1
AT+QIRD=1,100
+QIRD: 2
hi
OK

on the device.

Regards, Roland

Roalnd Baldin

Hi,

we just published in our Documentation Library the description how to integrate development kit SODAQ SARA AFF R410M with LTE-M network and send and receive messages via MQTT.

It is located at https://docs.iotcreators.com/docs/sodaq-sara-r410m.

If you find bugs please let us know by sending an email to doclib@iotcreators.com.

Many many thanks to Erik!!

Regards, Roland

Roalnd Baldin

@Gijs-Mos
I checked the UDP logs for your device and I agree. Your device doesn’t send the messages twice.

If your application end-point doesn’t return to our platform within 1 second we go into a re-try loop to re-deliver the message. We re-try max. 5 times. Every minute ones. If within the period of re-trieng additional messages from other devices arrive they are put into the same post request and delivered as an additional element of the “reports” array. But in this case you would see different serialNumbers and timestamps.

Is it possible that your callback returns sometimes slower than 1 second. In this case our platform would re-deliver the message a second time.

I saw cases where the application end-point didn’t publish the message into a queue for asynchronous processing. It processed the message directly and stored it away into a DB. Sometimes the DB blocked. By the this the response time was bad and the messages have been delivered a second time.

Regards, Roland

Roalnd Baldin

Hi,

many users ask via which IP address IoT Creators SCS forwards received uplink messages to the registered application callback URL:

IoT Creators SCS forwards the uplink messages to your application callback URL via one of the two IPs

18.195.119.162
18.195.17.174

Hope this helps you to configure the IP whitelists of your application.

Regards, Roland

Roalnd Baldin

Before activating radio module Set APN with AT+QCGDEFCONT rather than **AT+CGDCONT
Set frequency band explicity with AT+QBAND
Configure first APN, fequency band and mobile operator ID before switching on automatic attachment

Roalnd Baldin

As you know the very-first-attachment to the network can take multiple minutes. Sometimes this creates problems in the production process.

Out of this reasons we are looking for possible measures to improve the very-first-attachment time.

Regards, Roland

Roalnd Baldin

@Rasyid Do you have a valid network connection ?

For Quectel BG96 you can verify the network connection with the following AT commands

AT+CGPADDR                    //check IP address
AT+CGATT?                     //check if attached to network
AT+COPS?                      //check current set MNO
AT+COPS=?                     //scan network for mobile operators
AT+CGDCONT?                   //check APN
AT+QPING=1,"172.27.131.100"   //ping UDP server

Regards, Roland

Roalnd Baldin

@David-Netten

Hi David,

you are right, that the UDP server of IoT Creators doesn’t send back an acknowledgment for a received messages.

BUT: The CoAP/Leul server of IoT Creators acknowledges a received messages with a “2.05 Content” acknowlegment.

Be aware that CoAP/Leul is the Huawei flavor of CoAP and it is supported by Huawei chipset such as HiSilicon which are used in moduls such ublox N211 or Quectel BC95.

For many customers it is not enough to have an acknowledgment between the device and the IoT middleware. The implement an asynchronous acknowledgment between the application and the device on the basis of a downlink message. If you would need the asynchnronous application acknowledgment it wouldn’t make a difference between CoAP/Leul and pure UDP.

Regards, Roland

Roalnd Baldin

@David-Netten be aware the both the CoAP/Leul server and the UDP server are hosted on the same IP 172.27.131.100. But the port of the CoAP/Leul server is 5683 and the port of the UDP server is 15683.

CoAP/Leul is special CoAP flaviour from Huawei. Some of the Huawei chipset such as HiSilicon which are used e.g. in ublox N211 or Quectel BC95 support it.

The AT commands for the Quectel BC95 to send and receive messages via CoAP/Leul looks like the following:

# Read current configuration
AT+UCOAP?

# Set OceanConnect CoAP server and port   
AT+NCDP="172.27.131.100",5683

# Activate send message indicator
AT+NSMI=1

# Send Hello World message
AT+NMGS=11,"48656c6c6f20576f726c64"

+NSMI: SENT                                                                      

# Activate receive message indicator 
# and display received message 
AT+NNMI=1 
                                                                                 
# Receive downlink message
+NNMI: 16,"48616C6C6F20766F6E20536572766572"                                     

# Activate receive message indicator with message display 
AT+NNMI=2
+NNMI     
                                                                       
AT+NMGR
16,"48616C6C6F20766F6E20536572766572"

Regards, Roland

Roalnd Baldin

Hi,

just published the first version of a tutorial how to integrate a “real” comfort sensor with IoT Creators, AWS Lambda, AWS Timestream DB and Grafana in our documentation library.

Step 1: Register and activate sensor device
- Register device in IoT Creators
- Activate IMBUILDING comfort sensor

Step 2: Create AWS user and role with IAM
- Create Role for Lambda Function
- Create User for Grafana Client

Step 3: Create AWS Timestream DB
- Create IoT DB
- Create IoT Table

Step4: Create AWS Lambda function for data decoding and injection
- Create Lambda function
- Create up-to-date boto3 library Layer and bind it to Lambda function

Step 5: Make Lambda function accessable from the internet

Step 6: Add static authentication token to Lambda function

Step 7: Integrate IoT Creators with AWS Timestream DB
- Register your AWS Lambda function as application callback in your IoT Creators project
- Test the integration

Step 8: Integrate Grafana with AWS Timestream
- Add Amazon Timestream Plugin to your Grafana
- Add Amazon Timestream Data Soruce to your Grafana

Step 9: Create an IoT Dashboard in Grafana

Step 10: Integrate AWS Simple Queue Service

Roalnd Baldin

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

With the username and password from the projects API credentials

Bildschirmfoto vom 2020-11-25 14-00-22.png

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
}

Roalnd Baldin

@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

Roalnd Baldin

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

Roalnd Baldin

@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

Roalnd Baldin

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

Roalnd Baldin

@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