I have a project that could really use CoAP’s Quality of Service, but my device doesn’t support OceanConnect’s Neul Messenger. I could port a library or something, but that would be quite an endeavor and I’d rather just use the in-built generic CoAP my device supports. Do we know anything about when T-Mobile will support non-Neul Messenger CoAP?

@Roalnd-Baldin Has this been rolled out already? Do you have any idea when we can expect it? Thanks in advance!

I have a project that could really use CoAP’s Quality of Service, but my device doesn’t support OceanConnect’s Neul Messenger. I could port a library or something, but that would be quite an endeavor and I’d rather just use the in-built generic CoAP my device supports. Do we know anything about when T-Mobile will support non-Neul Messenger CoAP?

Often, a packet will be “successfully” sent by my BK7020E, but not received by T-Mobile or my endpoint. In my ESP32, I simply get an OK back from my SIM and nothing shows up in the portal or my server. Is there any way to get a response back to my module so it knows if the packet has arrived? (From T-mobile for example)

This is a problem I’ve been having for a couple of months now. I’m catching errors and other messages from the BK7020 and retrying when necessary, but like I said, there’s still a lot of OK’s that don’t arrive. I simply have no idea if a packet has been successfully sent or not.

With kind regards,
Vincent

I’m building an IoT device that sends data to my server every 30 minutes. For this, I use a BK7020 on the T-Mobile network. The problem is, very often a lot of packets in a row don’t ever arrive at our server.
Then, sometimes a packet arrive two times, despite the function that sends data really only being called once. I have tried this with multiple BK7020’s, all have the same problem. The BK7020 doesn’t give me any error codes, and just returns an OK. I have added capacitors according to the BK7020’s documentation.

So, I am 100% sure I’m only telling my SIM Modem thing (the BK7020) to send the packet once. I am also 100% sure the packet sometimes arrives twice, with like one or two minutes inbetween. Could this be an error on the side of T-mobile? Or is it more likely internal fuckery of my BK-7020?

I should probably look into this myself, so would setting up AllThingsTalk be a productive way to help debug this? If not, do you have any other suggestions? The API is still opaque wizardry to me, but I’m willing to invest a couple of days to figure it out if that would help.

With kind regards,
Vincent

We have a server that we send our data to. Is it possible to have it send a simple OK message back to our device, so it knows to resend if it doesn’t get a response?