I think you have been in touch with Roland already, right?
Just to be sure
Our Service Capability Server (IMPACT) doesn’t have the information whether a downlink message arrived or not.
This feature will be available in our new CoAP adapter (to avoid confusion: this is the pure version of CoAP and not the Neul version that you are used to). We do not have it commecially available yet, but is already available for testing. (I believe testing is a good idea for the future batches of your use case anyway.)
In the meantime I also checked with other customers how they are dealing with getting such confirmations. When they do a firmware update, it also includes a new configuration.In this configuration, there is a piece of code that ensures that the device from now on sends a new version number with each uplink.
Hope this helps!
That’s strange and annoying!
To me the order looks like it is completed. What do you see if you go to https://portal.iotcreators.com/portal?
With the simcard you cirrently have you only make a REST query to your host if you use NB-IoT. However, we can send you another simcard which allows you do this with LTE and LTE-M as well.
You can also write me directly: email@example.com
The status-page is on the backlog. But… have you forgotten you phone again?
With regards to you question: yes it is a general problem on the entire platform and it is even bigger then only iotcreators.com.
https://status.aws.amazon.com/#EU_block <=-- check out the health status of AWS resources in Frankfurt.
Hey @Cher first of all, warm welcome!
Question: where did you get the simcard from?
just found it that you got it from us, thanks to @Florian-Duecker
So… in that case there is no PIN required.
AFAIK, usually this means that the sim is broken or the part of your device which is supposed to read your sim is broken.
Should we send you another one?
Pls check your whatsapp message. I added you to our whatsapp broadcast for outages.
We have problems with our Neul Messaging CoAP traffic.
I will also keep you posted here
That is great. Just reach out when you need assistance again.
Just to be sure: now you are trying to send a message to the device, right?
I’ll ask my colleagues for assistance.
In the meantime: how did you try to send the downlink? Via our GUI/portal? Or did you use the API?
Positive feedback from all our customers. Most of them did not even notice the downtime.
It’s going very well!
We even checked devices of many of our customers individually and it looks like everything is fully back up & running.
No packet loss unlike last time.
Yeah, we just saw a successful message of this device coming in at 06:19!
I’s not the issue of being a registration message. In that case we’d have seen the message coming in.
And the last message before today 06:19 was from May 23rd…
Hence, the message never arrived. Maybe a temp. issue with the mobile network?
How is it going with the other devices?
With regards to the portal functionalities: we’re still bringing back the portal.
@magnatron the IMEI that you just provided was only active on the May 19th and 23rd of May.
Is this a device that sends uplinks to your platform only after you triggered the device with a downlink? If so, than maybe the problem is not the uplink but the downlink.
If not, do you have another IMEI example which was online more recently?
Thanks for providing this feedback, can you please send me some IMEI’s via DM or email?
You will need a sim from iotcreators.com. It is included in the free starterkit project