Posts made by GrandPep

Problem solved: iotcreators fixed the sim card registration and all works now.

@MarcoPeli thank you and I just send an email to the iotcreators support.

Hello, we cannot connect with T-mobile LTE-M anymore. Our system works fine with NB-IoT and we did LTE-M tests a few months ago without a problem. Now when we try to connect to LTE-M on band 20 or 8, we get a network service error:

AT+COPS=?
+COPS: (1,"T-Mobile NL","TMO NL","20416",8),(1,"NL KPN","NL KPN","20408",8),(1,"vodafone NL","voda NL","20404",8),,(0,1,2,3,4),(0,1,2)

AT+COPS=1,2,20416,8
+CME ERROR: no network service

Does anyone know why this might occur?

@roalnd-baldin Thank you and I have send the IMEI to the support mail. And indeed, the code 1002 indeed means that it is queued and ready to be received for the device it is meant to. The following steps were used:

1. through the Iotcreators platform, send a downlink message to device A.
2. device A sends an uplink messages and receives a +QIURC: “recv”,0 meaning there is a downlink message waiting.
3. use AT+QIRD=0 to get the downlink message for device A.
4. through the API, send a downlink message to device A and receive the API response: accepted, code 1002
5. device A sends an uplink message, however, device A does not repond with a +QIURC: “recv”,0 : there is no downlink waiting
   (6. still check it with AT+QIRD=0 but really there is no downlink message…)

@roalnd-baldin Yes indeed, as of normal (like in the same way we do with sending downlinks through the platform) we wait until our Quectel BG95-M3 receives a +QIURC: “recv”,0 after sending an uplink message and receive it with AT+QIRD=0.

Only when using the API to send downlink messages, the API response that everything was send good, however, no messages are waiting for the device so a +QIURC: “recv”,0 is never responded.

Hello,

I am trying to send downlink messages through the API and get the response:

{
“requestId”: “*****************************”,
“msg”: “Accepted”,
“code”: 1002
}

But at the device, the message is not received. If a downlink message is send through the portal with ‘action’ -> ‘send downlink message’ the message is received correctly.

I have double-checked the correct IMEI and that the messages are the same. Why can I not receive the messages through the API on my devices?

@roalnd-baldin It seems to work with curl in command if the data-raw is rewritten like so:

–data-raw “{
\“resourceValue\”: \“48656c6c6f20446576696365\”
}”

In command we get a nice “msg”:“Accepted”,“code”:1002 response but in Postman it does not work. And with the registration to https://{{base_url}}/m2m/applications/registration this was not an issue.

@roalnd-baldin No it was not the cookie unfortunately… I simply read the wrong reply (of the registration) in my last response, sorry about that… The error still exists and the HTTP snippet is:

curl --location --request PUT ‘https://api.scs.iot.telekom.com/m2m/endpoints/IMEI:<IMEI NUMBER>/downlinkMsg/0/data’
–header ‘Content-Type: application/json’
–header ‘Authorization: Basic <BASE64 user:pass>’
–data-raw ‘{
“resourceValue”: “48656c6c6f20446576696365”
}’

@roalnd-baldin Hello Roland, thank you for your help. I think I already found the problem: it seems that postman used an older cookie received from IoTcreators with which it returned the “Invalid Json format” error (altough I have no idea why a wrong cookie would cause such an error) but after removing all cookies, I received a new cookie and all seems to work now.

Hello,

I am trying to send a downlink message to our devices. First I followed the documentation of “6: Send message to devkit” by which I used postman with the following results:

{{base_url}} = api.scs.iot.telekom.com
{{user:pass}} = base64 of the given API credentials user:pass
{{IMEI}} = one of our registered IMEI’s

PUT: https://{{base_url}}/m2m/endpoints/IMEI:{{IMEI}}/downlinkMsg/0/data
HEAD: Content-Type: application/json
HEAD: Authorization: Basic {{user:pass}}
BODY RAW:
{
“resourceValue”: “48656c6c6f20446576696365”
}

RESPONSE:
{
“msg”: “Authentication error”,
“code”: “1005”
}

Afterwards I read in a different part of the documentation in “GETTING SERIOUS - IOTCREATORS.COM - Using the API” that first, a callback needs to be registered, which we deed and got a “msg”: “Success” response and I retried the previous call with the following response:

{
“msg”: “Invalid Json format”,
“code”: 1011
}

Why do I get this error?