Posts made by 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

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

• 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

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

@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

@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

​

@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

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
    • Create updated boto3 library with Timestream support
    • Create Lambda Layer for updated boto3 library
    • Assign updated boto3 library Layer to Lambda function

• Step 5: Make Lambda function accessable from the internet
  • Create API Gateway
    
  • Bind Lambda function to API Gateway
  • Test Lambda function and verify if data is written to Timestream DB
    

• Step 6: Add static authentication token to Lambda function
  
  • Create Lambda authorizer function
  • Bind Lambda authorizer to API Gateway
  • Test the authorization

• 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

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

@Marijn many thanks for this . I am highly interested in this.

Regards, Roland

@Mert-Karabagli Hi,

IoT Creators is the bridge between the device/connectivity world and the application world. You can configure IoT Creators to forward the UDP payload of your device to any HTTP endpoint of your application (web-hook).

Beeceptor is only an example for an HTTP application endpoint to explain how the data is forwared from IoT Creators. It doesn’t provide any application logic to store or to visualize your data.

If you want store and visualize the data without develop your own application you need to integrate forward the data to an generic IoT platform such as Axonize, All Thinks Talk, Thingsboard, Cloud of Things, etc.

We are currently documenting how those integrations look like. Unfortunatelly we don’t have it available now.

Regards, Roland

The CoAP stack of the CoAP server is based on Californium version 1 and uses the implemenation as it has been pushed by OceanConnect from Huawei. Although this implementation is not 100% standard compliant there are ublox n211 and quectel bc95 in the market which support this floavor of CoAP

I checked the AT command guide of the SIM7070G. It looks like only the standard CoAP is supported.

IoT Creators will provide the standard complient CoAP stack in Q1 2021.

Hope this helps.

Regards, Roland

Hi Marijn, this is a very interesting question

I guess it is not that high as one would hope because the antennas of the radio stations are optimized for the horizontal propagation of the radio signals, not so much for the vertical.

Regards, Roland

@Cees-Meijer I just got an error message that the email couldn’t be delivered to you email address. Could you please send an email to support@iotcreators.com to make sure I am using the right address?

Thanks!

Cheers.