Best posts made by Florian Duecker

Hi, the only thing that that I know of are these individual coverage maps right here: https://iotcreators.com/en/coverage-eu/.

@Ronan-Lacroix: Do we have anything else beside that available?

It’s not like we really have a choice (just kidding, of course!)

Thanks for your nice words! We do appreciate this kind of feedback and are happy that our effort and dedication is shown We are all super excited to be part of this community and help you making your ideas come to live!

I will pass this feedback back to the rest of the team. The last few days were really stressful and I’m sure that everybody will be happy to hear your kind words!

I second what Uta said for roaming use-cases.

For non-roaming use-cases, I would recommend to always set the band and the PLMN ID to ensure faster attach. So please be more patient with the attach time if you don’t set these values.

Hi @magnatron and everybody else who was affected:

I’m really sorry that the process was not as smooth as we all have wished for. And if it caused any inconvience, I apologize for this.

We have planned and tested this for month, but you never know how a productive system behaves even though everything went smoothly in a testing environment.

As Afzal said, we had our reasons to do this during “office hours”. We have discussed other options, but that seemed to be the most reasonable way for us to do it as we do have critical devices sending data 24h (so from that perspective our office hours are 24/7).

Did everything go as planned today? No. But we will learn from this and hopefully we can make it better next time. We were super transparent as soon as we realized that there were some problems and updated our community as much as possible while troubleshooting the problems.

Hopefully the next attempt will more smooth. Thanks for your understanding.

@karoly-molnar Hi, you will receive a SIM with a triple-form factor which you can „break apart“ to get your preferred size.

I can confirm that roaming is also working in Greece!

As Afzal said, our SIMs are PIN-free and should work out-of-the-box. So make sure the SIM card is installed correctly and all of the components do work correctly.

I also recommend to check out our documentation library.

We have a step-by-step tutorial for the BG-96: https://docs.iotcreators.com/docs/_-quectel-bg96-tuino096

Good luck!

@Cees-Meijer Thanks for the motivating words!

@rgb93 No worries, the IMEI is gone. Have you tried to change it to CoAP via the portal’s interface?

Hi all,

we know that bugs are frustrating, but let’s keep track on them together so we can fix them ASAP. If you encounter any other problems, please let us know here.

These are the bugs that we are aware of and working on

PORTAL

• Search device by IMEI not functional (28.05 fixed with limitation; 02.06 fully fixed)
• Device overview not consistent (i.e., empty pages) (28.05 fixed for most cases)
• Broken Link to edit billing address in invoice overview (02.06 fixed)
• Confusing 404 wording (fixed)
• Adding devices in project results in error message and site needs to reload in order to see all devices (Hotfix deployed: 31.05)
• Refresh Table link on the portal does not work (02.06 fixed)
• Minor issues with the CSV import

 
DOCUMENTATION

• Page https://docs.iotcreators.com/docs/sim-cards has a link leading to https://forum.iot.t-mobile.nl/ (28.05. URL fixed with newest version)

Florian

Hi Artur,

one of our customers have been using https://opencellid.org/ in the past for cell-id localization. Telekom is also working together with Polte which offer an IoT localization API. You can learn more here: https://iotcreators.com/en/iot-location-api/ and sign up if you want to try it.

Florian

@magnatron I sent you an email with more info on the MFF2 sims and I will manually sent you some MFF2. Please don’t be mad at me, but I need to moderate this thread a little bit as we now start to talk also about other stuff like migration communication which nothing has to do with bugs - I move some of the posts to the migration thread.

I can second what Uta says. Automatic scanning can take a while as well as a re-attach when crossing borders. Therefore, it is favorable to use a PLMN.

The Dutch network usually attaches the fastest as this is a native T-Mobile Netherlands SIM.

We see the system is coming back again (uplink should be fine; downlink is still recovering) - do you still encounter any problems?

Hello everyone,

this is an important notice! The API URL iot.netwerk.t-mobile.nl will be retired by the end of February 2022.

We already asked you to switch from iot.netwerk.t-mobile.nl to api.scs.iot.telekom.com by the end of May 2021, but we still see some traffic on our old API URL.

In order to make sure of uninterrupted usage, please switch to api.scs.iot.telekom.com as soon as possible.

Thanks a lot.

BR
Florian

Release Notes - IoT Creators - Version 1.0.47 - Released 16.03.2023

Hi all, we had some internal re-alignment in responsibilities, for this reason we missed some release notes. I hope you had all seen the cool new features offered. I will ask @Erik-Steinbring to post an update after this including all the changes between this release and the release in December.

Here are the release notes for 1.0.47:

Features
*[IC-5445] Download message history as CSV (paid plans only)
*[IC-4953] Change the „name“ property of a device
*[IC-5512] Message/options for run-time of virtual devices

Bugs & Admin functions
*[IC-5536], [IC-5537], [IC-5542], [IC-5539], [IC-5534], [IC-5540] Admin Functionality
*[IC-5547] CSV device registration
*[IC-5557] Invalid credentials error message
*[IC-5550], [IC-5546] Error messages should be always visible/on top
*[IC-5549] Device details view of lorawan devices
*[IC-5533], [IC-5553] “Unique email” error on registration page
*[IC-5543], [IC-5551] Starterkit Flow