Yes, we hide your devices from the public internet @Kkoen
So pinging directly to 8.8.8.8 will not work
Yes, we hide your devices from the public internet @Kkoen
So pinging directly to 8.8.8.8 will not work
Hi Cees, sorry for the delay. It took a while to find out if this works. Data buffering needs to be supported on different components in our network.
I am happy to confirm that this feature is fully activated.
Now I am going to find out how it works. I will post another update next week!
Strange… I noticed that your data is being forwarded to ATT, so we have to find out why you are not receiving it there.
I will try it myself in the next few days and keep you posted.
Hopefully someone will also reply in the meantime. I know that there are lot of users out there who created a successful integration with ATT before.
Hi @white apologies I did not see your post earlier. But according to my colleague you already received your card right? I will also send you an e-mail.
Hi Robin,
NB-IoT with an IP connection will be available in the summer. But, I will reach out to you next week to learn and find out together how we can make your downlinks easier in the current situation.
We do not have a message broker @Robin-Puthli. But we do use a SCS. The SCS is an essential component for NB-IoT (as also described by 3GPP). Without the SCS you will get in trouble with your battery.
Pleasure to help you!
Anyone else who is still having problems:
Just register a fake IMEI in your project and remove it again. Use https://dyrk.org/tools/imei/ to get a dummy IMEI.
Sorry! I had a direct chat with @Robin-Puthli today and didn’t update this topic on devices that did not come back.
@Bart-Abel yours should be fixed right now. I just needed to recover the subscription. Please have a double check.
@Robin-Finkers thanks for your patience! It should work now
The problem should be solved for now. It will take some minutes before all data will be received again. So it is possible that some devices are up again and some are still down.
Unfortunately this is only a workaround and we are still looking for a structural solution. I will keep you updated about this.
Hi Robin, this is problem in our back-end system. Apologies!
Will get back to you in a few hours on how to proceed.
This is unacceptable indeed and we are very sorry for the inconvenience. We are in touch with all involved engineers and suppliers and working on a structural solution.
Hi Inge, that is very odd. We don’t have eSIM’s for the Dutch IoT network yet…
Als het goed is, zijn ze onderweg… (begreep ik vab Eric).
We hebben ze wel! Alleen nog niet in de webshop. Ik laat je snel even weten hoe we ze jouw kant op kunnen krijgen.
Weet het niet zeker, maar ik dacht 317 bytes.
Yes, Stefan is right. Such frequencies are not good for the NB-IoT network.
Everything looks fine then… the only thing that I can come up with right now is maybe something with the format of the command line. The usage of quotation marks depend on the firmware version of the device.
Are you using the latest firmware?
Strange, should be fine.
What do you get back from
at+cereg? (with the question mark included)
Ok that’s correct. Which module are you using (e.g. Queclec BS 95, U-blox Sara N200, etc.)
It looks like you are trying to send an UDP message. Did you register the IMEI with the UDP protocol or CoAP protocol (during step 3)?
Hi Peter,
You have to do two things:
@JeroenD wat bedoel je precies met ‘verbinding te maken’? Krijg je geen netwerkregistratie of krijg je de data van je devices niet op het gewenste punt?
Het tweede kan kloppen, want in je community pakket zie ik dat je nog niet de IMEI nummers van je devices hebt geregistreerd.