Posts made by magnatron

Thanks for you response. Please, back to my original question:

Should auto-COPS work The Netherlands?

As for your suggestions/questions:

1. I’m under the impression that CSQ is somehow linked to the connection because the RSSI and QUAL will only be available when an MT is selected. (hard-coded or automatically) To find the actual signal strength of all available providers is done with other commands.

2. I’m using a ublox. it is reliable. as said “no problems” here.

3. Yes, I am roaming on band 20 VL NB-IoT using a TM sim. If you scroll up a bit you can read more about this. It’s only possible to test roaming auto-COPS on band 20 in NL as band 8 is only TM so this is not roaming as the SIM is TM.

Have you tried roaming in NL?

@Stefan-de-Lange, VL is offering NB-IoT on band 20, check this page for details: https://docs.iotcreators.com/docs/roaming-mobile-iot-networks-in-europe

What do you mean by CSQ goes below 99,99?

The signal quality hovers at 99,99 when a modem doesn’t find an MT to connect to. Once it finds an MT and is able to connect the signal quality will indicate RSSI and QUAL.

“auto-COPS” means that an MT will be automatically selected and the device will try to connect.

In my experience, on band 8 this is no problem and happens almost instantly. Tested in The Netherlands and in Germany.

But on band 20, in NL only available through VL, auto-COPS (AT+COPS=0) doesn’t work. The device will only connect when COPS is specified via AT+COPS=1,2,"20404".

Any tips?

Is everybody on a holiday?

Should auto-COPS work in NL?
I’ve inserted a roaming capable SIM, added IMEI to paid project.
On band 8 auto-COPS works fine but on band 20 I have to set COPS to 1,2,“20404” before the CSQ goes below 99,99.
When in Germany, auto-COPS also just worked.

We want to have auto-COPS for band 20 to be able to work and test in NL before we test in BE. (No band 8 in BE)

Any advise about this?

Thanks

Of all days, today is the day I forgot my phone. WhatsApp-free day for me. Please keep us posted in the forum. Thanks! And good luck with fixing

Since this morning 9:46, no messages are coming in. Anything wrong with the network?

Does a Pilot project count as paid plan?

I think there’s another change: Adding the application URL now sends an empty set of JSON where it used to send nothing? This to check if the application URL is valid.
Our application saw nothing as a valid hit but started working on the JSON only to find there was nothing in there, reporting an “error”. Which in turn disabled the saving of the application URL.

Not a bug but something to note in the docs. I think the docs should be super-clear about this:

I propose to change:

If you push the Save button in the YOUR APPLICATION SERVER tab IoT Creators will send an empty request to the URL to test if it is available.

️
If your application URL doesn’t return HTTP code 200 on the first test request the URL can not be saved in the "YOUR APPLICATION SERVER** tab.

Into something like:

If you push the Save button in the YOUR APPLICATION SERVER tab IoT Creators will send a POST request to the URL with the following JSON to test if it is available:
{"reports":[],"registrations":[],"deregistrations":[],"updates":[],"expirations":[],"responses":[]}

️
If your application URL doesn’t return HTTP code 200 on this first POST test request the URL can not be saved in the "YOUR APPLICATION SERVER** tab.

Unable to order Chip-Sim

I’m trying to order 10 chip-sims.
Different shipping address from billing address.
Chose iDeal > knab to pay.
Agreed to the T-Mobile NL terms (Which might be strange as iotcreators is promoted as being part of DT)
Clicked “Order”

Error message, also after trying multiple times:

@Yosiel Did you already power-on the device? Then it might be hanging in the catch-all tenant.

Is roaming also available within the Netherlands? We want to test a band-20 device but it doesn’t seem to attach to the NB-IOT network of vodafone-libertel. VL is listed on https://docs.iotcreators.com/docs/roaming-mobile-iot-networks-in-europe as a European roaming partner.

@Florian-Duecker I checked the email but there’s no e-mail from the 24th. Do you mean the 28th? The original announcement for the update? In that e-mail there is also no mention of a breaking change in the URL. There was no mention anywhere about changing the URL from /impact/m2m/endpoints to /m2m/endpoints and as we were not using the /m2m/endpoints endpoint, our logical conclusion was this change did not apply to us.
My point is that if you make breaking changes, please make sure you fully communicate the changes.
We did not “miss” the communication of the change, you just did not communicate it.
thanks!

@Florian-Duecker Thanks.

I would call this a small bug in the documentation, because the naming between the ordering page and the documentation page differs:

There’s a link on the order page beneath the Chip-Sim saying “All details”.
But when you click that link there is not a single mention of a chip-sim.

I know less of this matter than you do but I’m asked by my engineers to buy these. I’d like to know more about what I’m buying but there’s nothing to be found about this specific product.

@Florian-Duecker
It is probably the same looking at the “MFF2” tag, but i’m drowning in abbreviations already, so please can you confirm if the “eSIM” on that page is the same as the offered “Chip-Sim” on the SIM order page?

@Florian-Duecker

I did not read a mentioning of changing the actual URL.
The “also like to inform” made me think it was a side note.

I would like to request that a breaking change will get its deserved attention next time.

thanks

The portal does work now and then. Another device did register even after the error messages as you said. Thanks for the tip!

@Cees-Meijer I’m trying now but I do not see the device after refresh. The portal might use a shadow-API but the actual API is much more important to us as we use that for our devices in our production flow.

@Cees-Meijer “This” as in using the portal or the API?

Registering device via portal is defunct

URGENT!!

Also registering via the portal does not work and results in error messages:

API endpoint not working

URGENT!!
The API endpoint /impact/m2m/endpoints does not exist anymore.

A call like:

curl --location --request POST 'http://api.scs.iot.telekom.com/impact/m2m/endpoints' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Basic xxxxx' \
--header 'Cookie: xxxx' \
--data-raw '{    "additionalParams": {
         "adaptationLayerName":"TMNL_COAP_AL"
     },
     "address": "",
     "groupName": "CON_0000001xxx",
     "identifier": "",
     "protocol": "HTTP",
     "serialNumber": "IMEI:3588780801xxxxx"
} 
'

Results in a 404:

<html>

<head>
	<title>JBWEB000065: HTTP Status 404 - RESTEASY001185: Could not find resource for relative : /m2m/endpoints of full
		path: https://api.scs.iot.telekom.com/impact/m2m/endpoints</title>
	<style>
		<!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}
		-->
	</style>
</head>

<body>
	<h1>JBWEB000065: HTTP Status 404 - RESTEASY001185: Could not find resource for relative : /m2m/endpoints of full
		path: https://api.scs.iot.telekom.com/impact/m2m/endpoints</h1>
	<HR size="1" noshade="noshade">
	<p><b>JBWEB000309: type</b> JBWEB000067: Status report</p>
	<p><b>JBWEB000068: message</b> <u>RESTEASY001185: Could not find resource for relative : /m2m/endpoints of full
			path: https://api.scs.iot.telekom.com/impact/m2m/endpoints</u></p>
	<p><b>JBWEB000069: description</b> <u>JBWEB000124: The requested resource is not available.</u></p>
	<HR size="1" noshade="noshade">
</body>

</html>

Missing info about Chip-SIM

https://docs.iotcreators.com/docs/sim-cards doesn’t seem to have any info on the newest kid on the block…