• Samples of how to work with existing subscriptions via API

    Hi,

    instead of creating and deleting complete subscriptions after you added or deleted devices you can add or remove the device to or from from the existing subscription.

    In the following the Nokia IMPACT API samples

    • to get the devices of an existing subscription,
    • list itemto add a devices to an existing subscription,
    • list itemto delete a devices from an existing subscription (important: if the last device of a subscription is delete the subscription it-self is deleted as well).

    Get devices of an existing subscription

    GET https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
    HEADERS: {
     "Content-Type": "application/json", 
     "Accept": "application/json", 
     "Authorization": "Basic QVBJX0NPTsl8wMDssAswMDAbxNcTU4XzNlZmEzOkpySS9YOC45Y19CrrRmI0OEY="
    } 
    BODY: {
     "serialNumbers": [
     "IMEI:452749630137052", 
     "IMEI:351938100191440"
     ]
    }
    
    RETURN STATUS CODE: 200
    RETURN BODY: {
      "serialNumbers": [
        "IMEI:454596441983713",
        "IMEI:351938100191440",
        "IMEI:866425033313638",
        "IMEI:452749630137052",
        "IMEI:352656100979544"
      ]
    }
    

    Add devices to an existing subscription

    POST https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
    HEADERS: {
      "Content-Type": "application/json", 
      "Accept": "application/json", 
      "Authorization": "Basic QVBJsX0NPTl8wMDsssswMDAbxNcTU4XzNlZmEzOkpySS9YOfgC45Y19CRmI0OEY="
    }
    BODY: {
      "serialNumbers": [
        "IMEI:452749630137052", 
        "IMEI:351938100191440"
      ]
    }
    
    RETURN STATUS CODE: 200
    RETURN BODY: {
      "subscriptionId": "f37b094d-307f-4d43-82c5-73f81104e22f",
      "msg": "Success",
      "code": 1000
    }
    

    Delete devices from an existing subscription

    DELETE https://iot.netwerk.t-mobile.nl:443/m2m/subscriptions/f37b094d-307f-4d43-82c5-73f81104e22f/serialNumbers
    HEADERS: {
     "Content-Type": "application/json", 
     "Accept": "application/json", 
     "Authorization": "Basic QVBJsX0NPTl8wcMDssAwMDAbxNabcTU4XzNlZmEzOkpySS9YOC45Y19CRmI0OEY="
    } 
    BODY: {
     "serialNumbers": [
     "IMEI:452749630137052", 
     "IMEI:351938100191440"
     ]
    }
    
    RETURN STATUS CODE: 200
    RETURN BODY: {
      "subscriptionId": "f37b094d-307f-4d43-82c5-73f81104e22f",
      "msg": "Success",
      "code": 1000
    }
    
    posted in The Thing For IoT Creators
  • RE: IoT Creators Upgrade 26/05/2021 [STATUS UPDATES]

    @magnatron It was never possible to store the application url if the application didn’t return 200.

    In the old version the inital request contained an empty body to test if the URL is valid. This has actually changed. No an empty dictionary structure is put as payload.

    Regads, Roland

    posted in The Thing For IoT Creators
  • RE: Software Release Log

    Release Notes - IoT Creators - Version 1.0.15 - Released 02.06.2021

    Bug
    * [IC-5129] - [FE] deactivate IMPORT DEVICES button when no file selected
    * [IC-5135] - [BE] Store Starterkit name as Project name
    * [IC-5136] - [FE] After ending a project it is still shown after closing the modal
    * [IC-5155] - [FE] Order flow error related to postal code and country
    * [IC-5156] - [FE] Error on register form
    * [IC-5157] - [FE] Edit billing address on Invoices page not working

    Improvement
    * [IC-5128] - [FE] Inner margin for the iotcreators.com logo image

    posted in The Thing For IoT Creators
  • RE: Software Release Log

    Release Notes - IoT Creators - Version 1.0.14 - Released: 28.04.2021

    Bug
    * [IC-5099] - [BE] Bug: orders of more than one starterkit
    * [IC-5107] - [FE] “Save” button for password change in account settings not working properly
    * [IC-5110] - [FE] In a CoAP project the protocol is still selectable also for non-first devices
    * [IC-5113] - [FE] Green success message is NOT displayed after saving application URL successfully.
    * [IC-5117] - [FE] 404 on googletagmanager
    * [IC-5132] - [FE] Tab component does not show which tab is active
    * [IC-5142] - [BE] error on order edit in admin for orders when account is not yet created

    Task
    * [IC-5002] - [FE] LTE-M Starter Projekt FE Design
    * [IC-5003] - [BE] LTE-M Starter Project

    posted in The Thing For IoT Creators
  • Software Release Log

    Starting in May 2021 you’ll find here the release log for the IoT Creators portal and backend (bug tracker and release dates)

    posted in The Thing For IoT Creators
  • RE: Using NB-IOT for citizen-science

    @MarPi said in Using NB-IOT for citizen-science:

    Right - not right…to high - to low? It always depends. Which value exactly you doubt?
    Or maybe there is a chance to improve your values?

    The difference between nonIP and UDP is more than factor 2. The difference between nonIP and nonIP with RAI is negligible. This makes no sense. I suspect you used RAI for both nonIP cases?

    To be fair, UDP + RAI will be in the area of fourhundred something.

    I have achieved around 70 uWh (or 0.070 mWh) using nRF9160 using NB-IoT, UDP + RAI. 400 seems pretty high.

    posted in General discussion & other topics
  • RE: Using NB-IOT for citizen-science

    @MarPi Those numbers can’t be right. I thi

    @MarPi said in Using NB-IOT for citizen-science:

    Hi @Stefan-de-Lange …from my point of view it might not be such a big difference if you look at a single shot.

    It was averaged over 100’s of measurements. There was no difference.

               nonIP + RAI --> 0,303mWh
               nonIP       --> 0,314mWh
               UDP         --> 0,647mWh  (20Byte IP + 8Byte UDP header overhead)
    

    But that might differ between different setups and scenarios.

    Those numbers can’t be right. What modem is this?

    posted in General discussion & other topics
  • RE: Using NB-IOT for citizen-science

    @MarPi Although you are right I doubt the 20 bytes of IP header will make much of a difference. I have done some tests using various packet sizes and 10 or 100 bytes did not make a notable difference in power consumption.

    posted in General discussion & other topics
  • RE: TRP or TIS requirements for certifying hardware

    @HaraldNaumann maybe you’ve got some advice?

    posted in Hardware