@Jeroen-van-Bussel of course you can work on automatic mode, the modem would scan through the whole PLMN list until it finds a network. This can take a while and I agree, it’s the only thing that makes sense for devices in non-static use cases.

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

@derko-drukker

Volgens mij wordt het forum wel gelezen door T-Mobile. Ik heb wel ooit een email adres gehad van Afzal maar deze werkt ondertussen niet meer voor T-Mobile dacht ik.
Het zou wel makkelijk zijn dat er een ingang is voor het melden van problemen. Wij gebruiken de device voor het meten van CO2 en Methaan en dit is een continue meting waarbij er eigenlijk zo weinig mogelijk meting verloren moeten gaan.

Groeten Gerrit

@eric-barten Ok, clear, thanks!

@rijsman https://www.linkedin.com/in/stefan-de-lange/

@WEB1736359896030080 The maximum of 120 messages per device per day is a fixed number and cannot be changed. The frequency on how often you sent your data needs to be managed on your device.

@IoT-Arista Interesting combination. You are right, nRF9160 requires a very different development strategy. It uses Zephyr RTOS and c-api’s to control the cellular modem. In my opinion it is much better to work with than the ancient, slow, outdated AT interface. But if you want to use AT commands on nRF9160 you still can:
https://github.com/nrfconnect/sdk-nrf/tree/master/applications/serial_lte_modem

If you don’t want to redesign you should contact SIMCOM and t-mobile ( @Eric-Barten ) to fix your issue

@Roalnd-Baldin Cool! Nice to see it works now.

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

Unfortunately it didn’t work out, what we tried yesterday. Please follow this topic for new updates.

So sorry that this affected you in this way. I’m really sorry!

Mistakes like this should not - but can happen. Our whole team is truely dedicated to provide the best service to all our users! We are working hard on it to make it a truely magical experience for everyone.

As I have said we are in a process of migration and restructuring. This includes considering a new pricing model as well. We are hearing our customers and strive hard to make things happen. However, we are not a connectivity provider offering pure LPWA connectivity. There are several elements our solution offers that is not part of traditional connectivity-only solutions. Therefore, we will probably never be able to cut those prices.

We are happy that you are part of the IoT Creators community and we hope we can continue to be a reliable partner at your side!

Hello @Ahmed-Elhaddad,

We do these tests in parallel to normal network maintenance and improvement measures and we can share some preliminary results in CE-0 conditions from measurements in our Labs.

• Up to 200 devices can attach successfully simultaneously within 10 minutes under the condition that they do not immediately send data after a successful attach.
• Average round trip time (RTT) increases with increasing number of parallel transmitting devices. A randomization of transmission attempts leads to reduction of RTT and potentially improvement of battery lifetime
• With regards to the initial attach, only a small number of devices should be activated simultaneously (max. 60 devices)
• With regards to the regular data transmission with good signal level the following was observed:
• Failure rates increase with more than 160 devices trying to send 100 byte of data within one second
• Introducing a randomization timer of at least 40 seconds solves this limitation
• Avoiding synchronized data transmission results in better share of coverage levels across all devices
• Implication - Customers should avoid synchronized attaches and data-transmission of their devices

Best,
Dominik

@Uta - Hello! Yes, the activity is expected as a field is test is ongoing (yesterday and today). Additional logs from the 2 SIMs at of the day today via email would be again appreciated.

@aliza-izaton As mentioned earlier, I strongly recommend using a python-based solution.