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

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

We will do a system update on 13.12.2022 between 10 am and 12 pm. There will be a downtime of the API, the protocol adapters and the message forwarding of about 10 mins.

Messages are not buffered, but non-transmitted messages can be provided on request.

Thanks for your understanding

Release Notes - IoT Creators - Version 1.0.42 (directly follows after 1.0.39) - Released 05.12.2022

This was a bigger release with the main focus on rebuilding our portal backend. But we also have release some cool new features.

Here is the overview:

Bugs
*[IC-5495] - User with existing starterkit project land in order flow when clicking on “try for free” on homepage
*[IC-5366] - Non-IP device shows UDP in its details
*[IC-5489] - Shown number of devices does NOT meet real number

New Features
*[IC-5490] - Adding LoRaWAN (via the The Things Network) as protocol option
*[IC-5449] - LoRaWAN: Control with a checkbox if the device shall be created in LoRaWAN network server as well
*[IC-5473] - Create virtual Device via GUI
*[IC-5492] - Implement unscheduled uplink send in GUI
*[IC-5469] - Automatically add an uplink-message-tag when the user register a device
*[IC-4967] - Invoice due dates in portal

Story
*[IC-5487] - Adjusted dropdown options for protocol selection when registering devices
*[IC-4984] - Adjust the FE to work with integer instead of FP numbers
*[IC-5379], [IC-5381], [IC-5400], [IC-5448], [IC-5486] - Security Improvements
*[IC-5485], [IC-5311]- Data Privacy Improvements

Backend
*[IC-5344], [IC-5474], [IC-5475], [IC-5476], [IC-5477], [IC-5478], [IC-5479], [IC-5499] to [IC-5505] - BE refactoring tasks (Merge, simplify and merge services) and bugfixes based on testing
*[IC-4968] - invoices linked to a user instead to a contract

Finally some good news: the system has been up again since this morning around 9 and since 10 without further disturbance. The team was able to stabilize the system further and currently we don’t see any more issues.

We will come back to you in the next days to give you some more insights on what happened and what we plan to do in order to prevent this from happening again.

Thanks for being patient with us.

BR
Florian

The system is up again and you should be able to see messages coming back in (maybe at high quantity since they have been queued). To be transparent: the system is not stabilized a 100% yet, so there might be some issues going forward. But we will keep you informed.

Hi Creators,

unfortunately, we are experience issues again (messages are not being forwarded) since midnight last night and we are currently troubleshooting the system. UDP und Neul messages will be logged, so in case you need the messages, send me a message to florian@iotcreators.com and we will provide you with the necessary data as soon as we have the underlying issue fixed.

Apologies again.

We understand that this is a major disturbance and we are sincerely sorry about it. The team is working as hard as possible to fix the issue as soon as possible.

When I have any updates, I will let you know.

BR
Florian

Everything is back up running.

Thanks for your patience.

We are still fixing the system, but you should be able to see messages coming in again.

This is the current status:

• coap + udp + neul should work with both uplink and downlink messages
• mqtt + lwm2m are currently still disabled

Hi everyone,

unfortunately, we are still currently working on fixing the problem. I hope that I will be able to give you more information soon.

Apologies again.

During our maintenance work we encountered some problems with our database server and we’re working on restoring normal operation.

We’ll inform you as soon as the service is fully back online.

We apologize for the inconvenience.