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 10: Integrate AWS Simple Queue Service
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.
Hi,
today we took a nice comort sensor (CO2/Temp/Humidity/BodySense) in Barcelona into operation.
We configured
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:
AT+QSCLK=0
AT+QBAND=1,8
AT+CFUN=0
AT*MCGDEFCONT="IP","cdp.iot.t-mobile.nl"
AT+QRST=1
AT+QSCLK=0
+IP: 10.128.0.134
AT+QIOPEN=1,1,"UDP","172.27.131.100",15683,1001,0,0
AT+QISEND=1,11,48656c6c6f20576f726c64
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.
Hi,
currently the customers split up firmware images into chunks of eg. 512 byte and push them to the device via downlink API requests (https://docs.iotcreators.com/reference/using-the-cdp-api).
We are currently working on a better support for FOTA in our IoT Creators portal. The portal will provide a capability to upload to and manage files in the device-download-space. From there the devices are able to download the files via e.g. HTTP or CoAP.
Regards, Roland
Hi Joop,
I will fix this.
Could you please give me your IMEI?
Regards, Roland
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,
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
@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:
Please let us get directly in contact, that we can speak about it (roland.baldin@t-systems.com).
Regards, Roland
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
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
Hi,
the first version of documentation for SIMCom SIM7022 how to
is available now in IoT Creators documentation library.
https://docs.iotcreators.com/docs/simcom-sim7022
Would be great if you check it and give me some feedback for improvements and corrections.
Regards, Roland
@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
@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
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.
Hi,
I did “normal” TCP/IP MQTT on top of NB-IoT connection with the Quectel BC66. So TCP/IP is possible. But I didn’t try to post a normal HTTP request.
LWM2M is implemented on top of CoAP and UDP. By this it works perfectly on NB-IoT. It is also supported by Quectel BC66. We tested it successfully with Eclipse Leshan server and the Nokia Impact LWM2M server.
Regards, Roland
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
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"
]
}
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 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
}
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
@Lauwie007 Can you please send your IMEIs to support@iotcreators.com? I like to analyse the problem in more depth and fix it.
Many many thanks for your support!
Regards, Roland