Downlink broken, via UDP

Jurriaan Vollebregt

Downlink messages used to work fine with:

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

I could receive them and decode them to ascii, recently i noticed that the downlink messages became gibberish.
Does anyone else have this same problem?
Where the incomming message should look like: 0,172.27.131.239,15683,5,68616c6c6f,0
Now I receive this: Hb⸮⸮⸮r⸮⸮r⸮⸮⸮r⸮⸮⸮b⸮⸮⸮b⸮b⸮²⸮⸮⸮C6F,5

Seems there is some encoding via api calls which turned sour…

Eric Barten

Hi @Jurriaan-Vollebregt could you check the protocol you used when you registered your device? The protocol selected determines the encoding for downlink. We didn’t have changes that I m aware of.

Jurriaan Vollebregt

@Eric-Barten can I see this somewhere in the api? I havent vhanged it since it worked.

Jurriaan Vollebregt

@Eric-Barten Just checked, sending to 172.27.131.100 Port 15683, which is UDP. Also, I get my messages correctly in my api. Only the donwlink messages are going wrong.

Martijn Kooijman

Maybe this is related to my problem I dont receive downlinks since a couple of days on my device at all since a couple of days ago

Jurriaan Vollebregt

I found the problem, I use an arduino leonardo with a dragino nbiot shield. For incomming/outgoing messages i use SoftwareSerial.h, to change the tx/rx pins to pins 10/11.

I fixed the problem by using the normal rx/tx pins and it works. Hence the library seems to be my problem.

Hope this helps anyone.