nrf9160 DK - cannot activate iBasis SIM

[Sergey Lyubka]

Trying to activate iBasis SIM in the nrfcloud.com, getting message "User cannot be updated" with no extra information.

I'm in Dublin, Ireland.

An activation dialog keeps spinning for ~5 minutes before spitting an error message, or sometimes spins forever and needs to be refreshed to start over. An extreme slowness of all nrfcloud registration operations, I guess, is "work as intended", so won't complain about it.

What can I do to make my SIM activated, and my nrf9160 DK working?

[Øyvind]

Hello, 

Sergey Lyubka, our nRF Cloud team reports that there might be an issue with the front end. They were able to reproduce the issue. The SIM was activated. The registration form gets sent successfully, however, the front end did not get correct event.

Can you please verify if SIM was added to SIM Cards list?

Kind regards,
Øyvind

[Sergey Lyubka]

Thank you!

Yes the SIM was added, but cannot be activated.

The issue is still there.

[Øyvind]

I've talked to our Regional Sales Manager for Ireland and the UK, and she informs me that iBasis SIM have limited coverage in the UK (LTE-m), while Ireland is not supported due NB-IoT.  For Ireland please contact you local network provider Vodaphone. This way you will not need to worry about registering the SIM in nRF Cloud.

Sorry for the inconvenience! 

Kind regards,
Øyvind

[njeester]

I had aThingy:91 working before...until the sim expired....waiting for a new one. So coverage for me is not an issue...at least where I'm developing.

[Øyvind]

As long as you are just sending sensor data then the iBasis SIM is sufficient. But if you intend to use GNSS, eDRX or PSM, then it is recommended to use i.e. an O2 SIM. 

[Sergey Lyubka]

So I have paid for a thing that did not supposed to work in the first place.

Whilst I understand that iBasis wants to make some business through Nordic, but for us as customers it is frustrating. It would be nice if DK lists all regions where bundled SIM works, so people know what they're buying.

Thanks for the clarification though.