Posts made by Marijn

@Roalnd-Baldin Thanks for your reply. I’ll try to test it when I have an opportunity and I’ll let you know about it.

@Uta said in At what altitude can I expect to send and receive messages above the Netherlands:

dio signal strengths up until 3000 m height above base stations. They concluded that the network works reliably between 1000-3000 m height at the location of their experiment (Spain). More insight can be found in their article.

Thank you for your information. 3000 meters would be enough for what I have in mind (nothing specific yet, but it’ll be aboard a glider plane). It’s the question is whether there is a lower maximum altitude in flat countries like the Netherlands where the networks are optimized for the flat lands.

@Ronan-Lacroix Thanks!

@Marijn Sorry for the half baked title. I can’t edit it anymore.

Hello. I am curious what the maximum altitude is at which I can send and receive messages above the Netherlands. Any idea?

Hi Afzal,

My device is still running fine. But I remember my hardware being named specificly 6 months ago. Under item I of the Getting Started guide, there is a line:

A list of certified devices can be found here:
https://iot.telekom.com/iot-en/products/iot-hardware

But the link does not seem to work and returns you to a general landing page, not a page about tested IoT hardware. I like to try out some more devices so I was wondering if any new devices were tested in the meanwhile.

Best regards
Marijn

Hello IoT Community Team,

About half a year ago I did set up an application server on Google Apps Script which works fine. I can send and receive messages. I remember going through some steps regarding my hardware (Quectel BC95). Now, I can no longer find this guide.

Then this week, I tried to replace the application server with an Azure backend. Unfortunately, I wasn’t able to to set it up succesfully this time. The current documentation regarding Azure seems outdated and I get lost. The printscreens no longer match the actual menu’s. Also, I wonder if the c sharp script (link to download is broken) is still up to date as well.

So an improvement of the Azure documentation would be greatly appreciated.

@eric-barten said in Application binding with Google Apps Script:

cript and point us towards how you did the set-up?
Thanks, Eric

Hello Eric,
Sure I can share a skeleton example.

But there is one problem I haven’t properly solved yet. Google Apps Script is unable to check the ip address of the client. So I cannot authenticate the request when T-Mobile forwards the message to the callback_url.

I can raise the security level in the GAS application, but I am not sure how the request can authenticate then. Adding headers seems to me the way to do this, but I am not sure yet.

I’ll look into this en post an example later.

Best regards
Marijn

@marijn Problem is solved, my bad. The payload is available in e.postData.contents.

Hello all,
I would like to use Google Apps Script (GAS) as a backend for the callback url. My first attempt to bind to this application failed. I do receive the requests but the payload is missing. The problem seems that GAS does not supprt gzip and/or deflate (https://issuetracker.google.com/issues/36757236).

If that’s correct, I think that would mean I cannot use Google Apps Script.

Has anybody else managed to get this to work or any tips how I could work around the problem?

Thanks for any feedback.

@eric-barten Thank you Eric. Creating the socket without quotes was the solution. See my reply to @afzal_m.

@afzal_m Thanks! It’s working now:)

I didn’t upgrade the firmware. That step seemed a bit complicated when I started. I wasn’t succesful at reading the current firmware to begin with. In the meanwhile, I had contact with the vendor, who told me the module is running the latest firmware (packaging was sealed).

Earlier, I had already tried the AT+CGDCONT command with and without quotes (all kinds of), all resulting in ERROR. Then I noticed that changing the 0 into an 1 returns OK, with and without quotes. I don’t know if that’s significant. The result of at+cereg? was still +CEREG:0,5.

But creating the socket without quotes returned OK now and the remaining steps were easy now. I was able to deliver the Hello World message.

To be clear, I never had a positive result from AT+CGDCONT=0,IP,cdp.iot.t-mobile.nl. at+cereg? still returns +CEREG:0,5. Is that okay?

Thanks again for your time.

@afzal_m Any suggestions on how to proceed?

@afzal_m That gives +CEREG:0,5

@afzal_m said in Unable to make it to Hello World:

Queclec BS 95

I am using the QUECTEL BC95-B8.

@afzal_m said in Unable to make it to Hello World:

UDP

Hi, thanks for replying quickly. I did choose UDP. I thought I was supposed to do so.

Hello,

In part 2 of the Getting Started, setting the APN throws an error:
AT+CGDCONT=0,“IP”,“cdp.iot.t-mobile.nl”
ERROR

The other steps in part 2 went without errors. AT+CGATT? results in 1, so I am attached. I also got an ip and was able to ping. Then I did part 3, registering the imei.

But then in the Hello World part 4,
AT+NSOCR=“DGRAM”,17,7000,1 throws ERROR
and
AT+NSOST=0,“172.27.131.100”,15683,11,“48656c6c6f20576f726c64” throws ERROR.

Any suggestions on how to proceed? Thanks!