@afzal_m Yes and I like it! How can I send you a direct message? I tried going to your personal page and then a chat, but pushing the send button doesn’t do anything (even in a new private session)

@afzal_m Dank voor je hulp! De callback url met curl toevoegen werkt inderdaad. Het is misschien een goed idee dit beter te documenteren? Of nog beter: te veranderen dat een via de GUI toegevoegde URL ook werkt?

Getting started VII ‘Hello device’ is ook erg summier met alleen een postman voorbeeld…

Voor degenen die geinteresseerd zijn, dit is de API call die werkt:

curl -X PUT -H “Authorization: Basic xxx” -H “Content-Type: application/json” -d “{ “resourceValue” : “Hallo” }” https://iot.netwerk.t-mobile.nl/m2m/endpoints/IMEI%3a868333030xxxxxx/downlinkMsg/0/data

Met achter ‘Basic’ uiteraard je eigen Base64(username:password) ipv xxx en je eigen device IMEI. Voor de volledigheid: de downlink op je device komt pas binnen na de eerstvolgende uplink.

@techniek I am trying to use this board. I can get connected to the network but can not send a message. Commands like AT+NUESTATS, AT+NCDP=172.16.14.22, AT+NCONFIG=CR_0354_0338_SCRAMBLING,TRUE, or AT+NSMI=1 and AT+NMGS=11,48656c6c6f20576f726c64 do not work (ERROR). Is it still possible to use such a module to send messages to the CDP? Could you give an example?

@Stefan-de-Lange IMHO is it possible to do HTTP(S) over NB-IoT, however T-Mobile decided to limit the messages to 512 bytes, use UDP and not to allow connections to the public internet. I think it would be nice to do HTTP(S) over NB-IoT

@afzal_m Mijn IMEI was inderdaad veranderd. Na zoeken op internet begrijp ik dat de IMEI door het device bepaald wordt. Ik heb twee modems en ik denk dat ik deze door elkaar gehaald heb. Alles werkt weer

@techniek een beetje een newbie vraag, maar als ik alle topics goed gelezen heb kan ik alleen berichten van beperkte grootte via Ocean Connect naar mijn device sturen? Eigenlijk wil ik direct een HTTP POST en GET doen naar een (publieke) webserver, maar met NB-IoT kan dat niet? Kan dat wel met LTE CAT-M1? Is die techniek ook beschikbaar via het early access programma?

Alles werkt inmiddels, mijn IMEI zat in een wachtbak bij T-Mobile en het toevoegen van een endpoint URL is via de portal weer mogelijk

@techniek Dank voor je reactie. Ik wil alvast wat exerimenteren, kan je me helpen aan een link welke CoAp berichten er verstuurd moeten worden, maw welke inhoud de server van T-Mobile verwacht om een payload te ontvangen?

@afzal_m Yeah you’re right :), however the ‘refresh table’ button works correctly, so it is not related to cookies

@afzal_m I just checked again, for me the downlink is working (again?)

But I have to admit, for it it was just clicking a button on a GUI.

Lucky you, I used a HTTP PUT request to downlinkMsgBase64Drx

@Stefan-de-Lange IMHO is it possible to do HTTP(S) over NB-IoT, however T-Mobile decided to limit the messages to 512 bytes, use UDP and not to allow connections to the public internet. I think it would be nice to do HTTP(S) over NB-IoT

@afzal_m said in Add subscriptions via api:

Thanks a lot @JeroenD. Maybe you are not aware of it but last month with did a major update on the document library after two years. But we only focused on the devices part.

In August we will update the API part as well
@Roalnd-Baldin is already working on it.

Nice @afzal_m

I also found out how to remove a device. It is indeed the postman call but with a different method, not GET but DELETE. This is wrong in the postman collection also…

curl -X DELETE ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/rest/device/14053’

The only thing I am still looking for is how to remove a device. According to the postman collection this should be:

curl -X GET ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/rest/device/14050’

But this shows device information and does not delete it.

@afzal_m This one is also already solved. I took a look at the postman collection and distillated the curl command from it. This works! To those that are interested, it is possible to add a device using:

curl -X POST ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/impact/m2m/endpoints’ -H ‘Content-Type: application/json’ -d ’ {“additionalParams”: {“adaptationLayerName”:“TMNL_UDP_AL”},“address”: “”,“groupName”: “<group name>”,“identifier”: “”,“protocol”: “HTTP”,“serialNumber”: “IMEI:zzz”} ’

In this way the device is also shown in the portal

Maybe it is a good idea to update the (invalid) documentation!

@afzal_m I just checked again, for me the downlink is working (again?)

But I have to admit, for it it was just clicking a button on a GUI.

Lucky you, I used a HTTP PUT request to downlinkMsgBase64Drx

@afzal_m Also thnx Afzal!

@afzal_m Thnx Afzal!

@trick2011 Ik heb overigens nu ook de indruk dat een downlink niet werkt. @afzal_m @Eric-Barten kan het inderdaad zijn dat downlinks niet werken op het moment?

As promised the results of my test to try to register a brand new modem using API calls instead of using the portal. This was unsuccessful btw…

Using the API, I was successful in registering an IMEI of a brand new modem. If I used the API to return the registered IMEIs it was reported in the same way as the IMEIs that I did register through the portal. I was able to send messages but the messages where not forwarded to my cloud server.
Next I removed the IMEI from the subscriptions using the API and curl, and registered the IMEI in the portal. This was possible, however also now no data was forwarded to my cloud server. I think this is the already known issue that first you need to register and next to send the first message, and I already send messages in the first test as descibed above.

My question is: could T-Mobille please provide working API calls for registering IMEIs?

This is in detail what I did. Username, password, subscription Ids, group name and IMEIs have been removed from the logs below for obvious reasons.

Check my registered IMEIs
curl -X GET ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions?type=resources&groupName=<group name>’
Response
{“subscriptions”:[{“subscriptionId”:“<subscription 1>”,“resources”:[{“resourcePath”:“uplinkMsg/0/data”},{“resourcePath”:“downlinkMsg/0/data”}],“groupName”:“<group name>”,“criteria”:{“serialNumbers”:[“IMEI:xxx”,“IMEI:yyy”},“deletionPolicy”:0},{“subscriptionId”:“<subscription 2>”,“resources”:[{“resourcePath”:“uplinkMsg/0/data”},{“resourcePath”:“downlinkMsg/0/data”}],“groupName”:“<group name>”,“criteria”:{“serialNumbers”:[“IMEI:xxx”,“IMEI:yyy”},“deletionPolicy”:0}]}

I am surprised that TWO subscriptions exists, with exactly the same list of IMEIs. Why?

Above call gave me two subscription Ids that I used in the following calls

Register a new IMEI in <subscription 1>
curl -X POST ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions/<subscription 1>/serialNumbers’ -H ‘Content-Type: application/json’ -d ’ { “serialNumbers”: [ “IMEI:zzz” ] }’
Response:
{“subscriptionId”:“<subscription 1>”,“msg”:“Success”,“code”:1000}

Register a new IMEI in <subscription 2>
curl -X POST ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions/<subscription 2>/serialNumbers’ -H ‘Content-Type: application/json’ -d ’ { “serialNumbers”: [ “IMEI:zzz” ] }’
Response:
{“subscriptionId”:“<subscription 2>”,“msg”:“Success”,“code”:1000}

Check if it is registered with the API (yes it is):
curl -X GET ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions?type=resources&groupName=<group name>’
Response
{“subscriptions”:[{“subscriptionId”:“<subscription 1>”,“resources”:[{“resourcePath”:“uplinkMsg/0/data”},{“resourcePath”:“downlinkMsg/0/data”}],“groupName”:“<group name>”,“criteria”:{“serialNumbers”:[“IMEI:xxx”,“IMEI:yyy”,“IMEI:zzz”},“deletionPolicy”:0},{“subscriptionId”:“<subscription 2>”,“resources”:[{“resourcePath”:“uplinkMsg/0/data”},{“resourcePath”:“downlinkMsg/0/data”}],“groupName”:“<group name>”,“criteria”:{“serialNumbers”:[“IMEI:xxx”,“IMEI:yyy”,“IMEI:zzz”},“deletionPolicy”:0}]}

If I check in the portal at https://portal.iot.t-mobile.nl/projects the IMEI is NOT shown

If I put in a brand new T-Mobile sim card I was able to register with T-Mobile, and to send messages, using the regular AT commands. The messages where accepted by the network. I think this is expected behavior, even without registration.
HOWEVER: the messages where not forwarded to my cloud server, leading to the conclusion: registering IMEIs using the API does not work.

Next I removed the IMEIs from the subscriptions, for completeness I also give the commands for this:

Delete from subscription 1
curl -X DELETE ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions/<subscription 1>/serialNumbers’ -H ‘Content-Type: application/json’ -d ’ { “serialNumbers”: [ “IMEI:zzz” ] }’
Response
{“subscriptionId”:“<subscription 1>”,“msg”:“Success”,“code”:1000}

Delete from subscription 2
curl -X DELETE ‘https://<username>:<password>@iot.netwerk.t-mobile.nl/m2m/subscriptions/<subscription 2>/serialNumbers’ -H ‘Content-Type: application/json’ -d ’ { “serialNumbers”: [ “IMEI:zzz” ] }’
Response
{“subscriptionId”:“<subscription 2>”,“msg”:“Success”,“code”:1000}

Now I tried to register the same IMEI in the portal. This was successful but messages are again not forwarded to my cloud server. Also no IMSI, no first message, no last message nor payload is shown in the portal. This is probably because I sent messages in my test without a prior proper registration (this is a known issue)