Hi Yosiel,
You will need a sim from iotcreators.com. It is included in the free starterkit project
Hi Yosiel,
You will need a sim from iotcreators.com. It is included in the free starterkit project
@MeneerJacco thanks for making us aware. This is because of the rollback. You probably registered the device on the new version of our service capability server.
Can you pls send me the IMEI numbers via PM or via hello@iotcreators.com?
We’ll fix it right away!
Hi @magnatron I am very sorry to disappoint you. But there is chance that, the next time, it will happen again during office hours.
For many of our customers there is no difference between daytime device data and nighttime device data. They’re both equally important.
The problems of today lasted for a little bit longer than 4 hours. The risk of doing this during the night could mean that it can take 8 or 10 hours.
I don’t like the idea of losing data at all. But if I have to choose, then 4 hours is better than 8 hours.
Good to hear @BrodVictor… but it looks like I missed your post from yesterday?
Hey @magnatron
We understand your worries. Really. And that is exactly why the team picked this timeslot for the maintenance.
We’ve been planning this since October 2020. The reason why we are already working on this upgrade and migration for more than 7 (!!) months, is because we want to mitigate all risks during and after this maintenance.
Hence, we are very optmistic about our statement that the interruption will not last longer than just a few minutes.
However, in case something goes wrong… we’d like to solve the problem as quickly as possible. And to solve it as quickly as possible, we need to involve people from different parts of the world.
If we move the maintenance to another timeslot and something goes wrong, there us a high possibility that solving the problem will take more time than we want.
For this reason, we see the announced time-slot as the time-slot with the least risk.
But I promise you that we are doing everything to avoid problems.
Welcome, happy to have you here :-).
Unfortunately you can only use our UDP server with simcards from Deutsche Telekom.
We can send you one, but there is another problem: we do not have NB-IoT roaming in France (yet)…
@JakubT , in addition to @Ronan-Lacroix last post, he also checked the simcard numbers that you sent to me by email and he did not see any attempts to attach to the network so far…
@magnatron yes it is correct
But it still possible that in some places there is no network available at all.
Some operators only activated part of their networks.
We can find this out by looking up the connection info in our network.
Can you please send me the ICCID (number on the sim-card) or IMSI via DM or support@iotcreators.com?
Thanks!
Looks like I overpromised here… I am very sorry.
Last year we’ve been discussing the upgrade of our Service Capability Server many times internally. And initially the installation of the generic CoAP adapter was part of the overall upgrade plan in each of these discussions.
However, for some reason it was deprioritized when we started the upgrade.
The upgrade will be finished in April and bring along new protocols as MQTT and LWM2M but unfortunately not generic CoAP.
Tagging my colleagues @Roalnd-Baldin and @Saher-Salem to see if we can come up with a new timeline.
Hey @Lauwie007
If you use our GUI and click on the ‘actions’ button in the ‘devices’ you’ll see that it is possible to send downlink messages in HEX format.
However, the fact thad one needs to select an additional checkbox tells me that you’ll need to some additional things when you use the API as well.
Let me check this with @Yassine-Amraue or @Roalnd-Baldin this Monday and get back to you.
Yeap!
The thief can only re-use the sim-card when he registeres his own IMEI number and used the sim with his IMEI.
Good question!
If you remove an IMEI number the sim-card will keep the possibility to attach to the mobile network. However
the network will not process the device data because the IMEI is not registered
there will be no cost-charging for it, because we only charge based on registered IMEI’s
So removing an IMEI is the only thing you need to do to ‘block’ a connection.
Dear iotcreators.com users,
Some of you are lately experiencing problems with interruptions in receiving IoT device data. These problems will be solved after our Service Capability Server upgrade in April.
As some of you know, iotcreators.com is a platform that has been re-launched based onthe Minimum Viable Product of T-Mobile Netherlands back in 2018.
The re-launch happened in July 2020 and the first thing that we did was fixing the basics and making the platform more scalable.
When it comes to fixing the basics there is still one activity that has not been completed yet: the upgrade of the Service Capability Server.
This upgrade is not just a simple software installation. It requires extensive testing, new hosting environments, migration-planning and risk-mitigation.
We’re working on this upgrade already since October 2020 and the end is finally in sight. Mid-april we will be live with this new component which will make sure your device data arrives on time.
Feel free to reach out if you have any questions!
@CFH I think we need to do some troubleshooting on our side. Can you please send us the IMEI numbers via welovemail@iotcreators.com?
Thanks!
@Cees-Meijer can you pls let us know if you see a difference lately?
Thanks. We’re checking again. Get back to you soon…
I learned today, that this fix was never installed yet
I’m going to chase the team and will get back to you
Can you please send my one of your sim-numbers or explain to me via which DT-channel you received your sim’s?
For NB-IoT we have an UDP adapter. So with NB-IoT you’ll need to use APN cdp.iot.t-mobile.nl which will allow you to send device data to 172.27.131.100.
To retrieve the device data in your back-end/cloud server/iot platform, you’ll need to create an HTTP integration.
If you use the sim-card for LTE-M or 2G, you’ll need another APN: m2m.public.nl. By doing this, the device will get a public IP address just like any other device on the open internet. This means that you can send device data directly to your own server while using LTE-M or 2G.
Hope this helps!