Posts made by magnatron

Broken link(s?)

• Link(s) in the docs is (are?) broken.
  E.g: Page https://docs.iotcreators.com/docs/sim-cards has a link leading to https://forum.iot.t-mobile.nl/ (which has no valid SSL)

404 page

• incorrect spelling “We could not found what you are looking for”
• What is “the homepage” in “Try again from the homepage” and why is there a button “Go to your dashboard” if I should try from the homepage?

(as in “who is General Failure and why is he reading my drive?”)

1. Log in
2. Click on INVOICES in the left menu
3. Click on “Edit” beneath your “Billing address”
4. Witness a creative 404 page

Portal

• Billing address “edit” not functional

The portal is still not functional. Everybody sleeping?

Time for ️ + and getting the kids to school. Thanks to everybody for making this second time around a success!

Let’s keep it at an anomaly.
happy to say I see multiple devices getting their message across.
How’s the system holding up?

After another try, the device message did get through. Could this be the issue in which the first message by CoAp is seen as registration and then discarded before the message actually gets through?

No, it’s a device that sends an uplink after a human triggered it on location.

@Florian-Duecker said in IoT Creators Upgrade 26/05/2021 [STATUS UPDATES]:

also

Good morning. Great to read that the migration is completed successfully. I run into some issues:

• The portal errors on every search for a specific IMEI. (like https://portal.iotcreators.com/projects/<project-num>/devices - try to search for any IMEI)
• Device messages are not passed to our platform.
• Combination of those two leads me to not knowing if messages from devices are sent to your platform.

Thank you for looking into these issues.

@Cees-Meijer might have fallen prey to the Catch-All-Tenant

Haven’t tried this yet but might it have to do with the newline character after the serialNumber ?

It is up again since around 14:10
Thanks for the quick response

Hi,
All projects in the portal give error messages, not being able to load devices.
Either the platform is down or our account seems suspended.

API only returns errors.

On first call I got something like “License expired” (did not copy it)
Now it’s saying things like:

    "code": "FORBIDDEN",
    "localizedMessage": "JBAS014502: Invocation on method: public com.alu.mdm.rest.Page com.alu.mdm.rest.device.DeviceResource.query(javax.ws.rs.core.UriInfo) of bean: DeviceResource is not allowed"

or

{
    "msg": "Unauthorized group",
    "code": 1006
}

Does this mean that we were the only one who received the “we’re rescheduling the upgrade” email from @Roland-Baldin-as-Admin ?

So then I am the infamous one-star-rating-customer…

Ok. I understand your reasons for choosing office hours.

But please do take to heart for next time to not send out conflicting messages:

@afzal_m explained on 28/4 12:34 that office hours were the better choice
but hours later @Roland-Baldin-as-Admin sent us an email in which he said you were finding another time outside office hours.
Nothing after that.

So we were expecting another announcement and we had no reason to notify our customers.

Shock and awe when we started receiving complaints and received the update-email almost an hour after the end of the initial time frame stating you were trying to fix the resulting problems.

So, I’m happy @Cees-Meijer, that you feel you were updated during the process but I definitely do not feel we were kept in the loop.

And of course: “Shit happens!”

But to describe the process as “not as smooth as we all have wished for” does not really seem accurate to me.

I guess I’m not the only one who’s very unhappy with how all this went down.
We’re receiving complaint after complaint.

Hope this will mean you will never again do a major update during office hours.

Not to say “I told you so” but I told you so.

Hey @afzal_m,

Thanks for explaining. This helps.

Please consider making this a protocol when sending out emails about service interruptions (planned or not).

And please let us know what will happen with the sent data: Will devices need to send it again or will it arrive at our application after the update was successful?

Once we know this, we can tell our customers what to expect and how to act on degraded functionality,

@Roalnd-Baldin
We just received an email that you are planning to interrupt the service on 11-5 between 9AM - 11AM.

Please elaborate why you planned this during office hours? We have hundreds of primary school teachers counting on our service.
Why did you decide such a non-standard time frame to push a planned update?

We all know that “a few minutes” because of an update, especially with “exciting new features” can turn into a lot longer.

I’m worried about our customers not getting the “regular” service.

Please reconsider the time frame so we are free to party about the “exciting new features”.

Looking at the Roaming Network Info it looks like national collegial roaming is offered.
Is this conclusion correct? Does “roaming” also imply being able to use other collegial national networks when the “preferred supplier” is not available?

Is it possible to recover which operator transferred the message to the platform?
I have non-development hardware which works across the border in Germany but I’d like to verify which operator handled it.

IMEI: 358878080087361

Is there a EU coverage map available?

This what you looking for? (pseudo)

AT+CGDCONT=1,"IP","cdp.iot.t-mobile.nl"
AT+NCDP="172.27.131.100"
AT+NSMI=0
AT+NNMI=0
AT+CFUN=1
AT+NBAND=8
AT+COPS=1,2,"20416"
// Check for CSQ:
AT+CSQ
// until lower than 99.99
// Then wait for attach:
AT+CGATT
// until 1
// Then send message:
AT+NMGS=<message-size>,"<message>"
// And read response to check for OK