I know you worked your butts off to get this platform to where it should be: In the hands of committed, community-focussed, knowledgable peeps.
I’m looking forward to (getting back to) being able to share ideas, report and curse about hiccups, celebrate victories and tackle backlash!
And I wonder what you got up your sleeve for us!

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

NOICE!

Only thing left is some descriptive labels in the English locale

(And what are those mysterious crossroads DELETEing?)

Hi all,
We’ve been promised a lot of things about the ability to communicate with T-Mobile but nothing seems to have changed in the last few months.
Can we please get an update on how “upscaling” and “making T-Mobile IOT more fitting with corporate structure” is going? There’s still no regular means to contact support. I’m not getting any response to mails.
Please let us know what’s going on. (Aaaayaiaiaiaiai)

Is there a EU coverage map available?

@afzal_m said in AT+CSQ:

AT+NUESTATS

Inmiddels erachter dat de AT+COPS command een issue lijkt te hebben. Geeft niet de goede info terug. (1,2,""). Pas als ik een error trigger met AT+COPS=1,1,20416 (Dus zonder quotes om de ID) geeft ie daarna wel de goede info terug +COPS:1,2,"20416". Beetje weird?
Anyways, hier de NEUSTATS vanuit 4G-void Eefde:

Signal power:-1026
Total power:-941
TX power:20
TX time:3577
RX time:157135
Cell ID:2217061
DL MCS:0
UL MCS:0
DCI MCS:2
ECL:0
SNR:104
EARFCN:3747
PCI:249

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

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

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?”)

It’s a lot faster as well! It never crossed 5 seconds. So I’m not sure what will happen when one is set to import hundreds and crosses a time limit.

I’m very happy I received an announcement from Afzal yesterday. Not happy at all with the fact that you keep doing maintenance in the middle of the day and that you keep announcing way to short before the interruption. But hey, at least I received an email.

However, when I want to know more about the interruption and find out if it went as planned, where can I go??

There’s nothing on the forum and nothing on the discord. Not even the announcement.

Is there a new platform somewhere that I didn’t hear about?

@magnatron Ah, not here but in the mail. Thanks.

Any update on the update? Is it done? Did it go well?
Thanks

@afzal_m very happy to hear this. As there was no change in the announcement I could only respond to what was stated.

@Florian-Duecker Again: unacceptable the way this is handled. 1,5 working day ahead announcement. Not in the “Announcement” channel. Expecting understanding. No buffering.

Please explain how we should inform our customers their device won’t be working in the middle of a working day tomorrow?
Also please help us to deal with the anger and frustration our customers will show. Oh, and please tell where we can collect lost revenue because customers are walking out.

Thanks for your understanding

Hi @Ronan-Lacroix,

Thank you for your elaborate reply. I think I understand now. We produce a device which is aimed at staying in the same place so the choice for automatic selection seems most appropriate.
Kind regards, Maarten Wolzak

What is industry standard to select a band and an operator?
Should we leave it up to the network and the modem to negotiate or is there a standard process we should follow to iterate over bands and operators programmatically?

@Jeroen-van-Bussel
I experience the same issue. However, deleting and recreating the device doesn’t solve it. Can you share as what type you recreated the device?

There’s an announcement in the portal which is not shared here.
For those that only work via API and have a notification on the forum:

We’ll update our backend on Wednesday 8th December, 2021 from 8:30 to 9:30 am CET. During that time window we expect a short outage of all device communication for not longer than 5 minutes.

@florian-duecker The IMEI was still registered at a separate account (hw developer account)
So, there might be a small bug in the register-device procedure that the response is a successful one (green prompt) while the device cannot actually be registered.
(just a guess)