@Crowdsourcer If you see 15 mA it means there is a problem. I measured an average of 6.7 uA in PSM

@Martijn-Kooijman I solved it by checking the return message after sending “AT+USOCR=17,7000”. Once it is contains “+USOCR: 0” in the returning string I know it is ok: (it takes about 5 s after a reset) added code: String check_sara=cmd("AT+USOCR=17,7000"); while ((check_sara.indexOf("+USOCR: 0",1)<0)) { delay(500); check_sara=cmd("AT+USOCR=17,7000"); Serial.println(check_sara);//just for checking }

@thijsbuuron Deel je bevindingen!

@afzal_m Proprietary sucks I hope more open protocols are added, UDP is pretty limiting

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.

Does it also work for @trick2011 now?

United Kingdom just confirmed!!!

@Timo-Siekmann said in Limited Data Rate after to many messages on aday?: Quectel BG96 Hi, please try: AT+QCSCON=1 AT+CEREG=4 I highly suggest to plot the current too.

@mels-liefaard said in AT commands gezocht om SIM7020E te verbinden: 1752B06SIM7020E Ik kan bevestigen dat het ook werkt met firmware versie 1752B07SIM7020E. Ik heb er gisteren een berichtje mee verzonden met hulp van dit topic. (Bedankt !)

@supersjimmie Hoi Sjimmie. Mooi dat je het werkend hebt gekregen. {“latitude”: 52.136421, “longitude”: 5.262903} Ik zou dit anders aanpakken. Aan de kant van NB-IoT wil je enkel kale bytes sturen, het sturen van JSON data creëert onnodig veel overhead. Je zou het ook zo kunnen doen namelijk: AT+CIPSEND=16 031B89E500504E37 Is maar 8 bytes. In je python flask kun je dit vervolgens weer scheiden omdat je weet dat beide variabelen 4 bytes zijn: latitude = 031B89E5 longitude = 00504E37 Dan converteren naar decimale notatie en de komma weer terugplaatsen.

@afzal_m said in Add subscriptions via api: Thanks a lot @JeroenD. Maybe you are not aware of it but last month with did a major update on the document library after two years. But we only focused on the devices part. In August we will update the API part as well @Roalnd-Baldin is already working on it. Nice @afzal_m

@pieterhoenderken Sorry! We hadden wel je device verwijderd, maar dat vergat ik hier te melden!

@Holger-Wech you can use LTE-M instead of the 2G/3G fallback that is described in our quick start guide. Please use the APN internet.m2mportal.de for LTE-M.