Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-15173

[fiware-stackoverflow] Setting up lwm2m-node-lib to FIWARE platform

    Details

    • Type: Monitor
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:

      Description

      Created question in FIWARE Q/A platform on 14-12-2018 at 10:12
      Please, ANSWER this question AT https://stackoverflow.com/questions/53777307/setting-up-lwm2m-node-lib-to-fiware-platform

      Question:
      Setting up lwm2m-node-lib to FIWARE platform

      Description:
      Having reached a stumbling block with my inherited wakaama LWM2M implementation for couple of weeks, as I reported in #154 I have no option than to try using telefonica lwm2m-node-lib instead.

      To make my point clear again, I have already IOTA, Orion, MongoDB, Cygnus all working fine. It is my client implementation that isn't sending measure to IOTA despite being able to connect. The scenario I want is LWM2M -> IOTA -> Orion -> Cygnus -> MongoDB.

      My issue now: I want have a precise explanation of configuration I need to do to have lwm2m-node-lib implementation work here, for instance where to input the server IP to connect to (where my FIWARE is running), which file to edit etc. I already picked a new device to use, keeping aside the other.

      My docker-compose file below:

      version: "3.1"

      services:

      mongo:
      image: mongo:3.4
      hostname: mongo
      container_name: fiware-mongo
      ports:

      • "27017:27017"
        networks:
      • default
        command: --nojournal

      orion:
      image: fiware/orion
      hostname: orion
      container_name: fiware-orion
      depends_on:

      • mongo
        networks:
      • default
        ports:
      • "1026:1026"
        expose:
      • "1026"
        command: -dbhost mongo -logLevel DEBUG

      lightweightm2m-iotagent:
      image: telefonicaiot/lightweightm2m-iotagent
      hostname: idas
      container_name: fiware-iotagent
      depends_on:

      • mongo
        networks:
      • default
        expose:
      • "4041"
      • "5684"
        ports:
      • "4041:4041"
      • "5684:5684/udp"
        environment:
      • "IOTA_CB_HOST=orion"
      • "IOTA_CB_PORT=1026"
      • "IOTA_NORTH_PORT=4041"
      • "IOTA_REGISTRY_TYPE=mongodb"
      • "IOTA_LOG_LEVEL=DEBUG"
      • "IOTA_TIMESTAMP=true"
      • "IOTA_MONGO_HOST=mongo"
      • "IOTA_MONGO_PORT=27017"
      • "IOTA_MONGO_DB=lwm2miotagent"
      • "IOTA_HTTP_PORT=5684"
      • "IOTA_PROVIDER_URL=http://lightweightm2m-iotagent:4041"

      cygnus:
      image: fiware/cygnus-ngsi:latest
      hostname: cygnus
      container_name: fiware-cygnus
      depends_on:

      • mongo
        networks:
      • default
        expose:
      • "5080"
        ports:
      • "5050:5050"
      • "5080:5080"
        environment:
      • "CYGNUS_MONGO_HOSTS=mongo:27017"
      • "CGYNUS_LOG_LEVEL_=DEBUG"
      • "CYGNUS_SERVICE_PORT=5050"
      • "CYGNUS_API_PORT=5080"

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        2h 59m 1 Backlog Manager 14/Dec/18 3:05 PM
        In Progress In Progress Answered Answered
        3h 1 Backlog Manager 14/Dec/18 6:05 PM
        Answered Answered Closed Closed
        5d 15h 50m 1 Jose Manuel Cantera 20/Dec/18 9:56 AM
        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        jmcantera Jose Manuel Cantera made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        fla Fernando Lopez made changes -
        Assignee Jose Manuel Cantera [ jmcantera ]
        fla Fernando Lopez made changes -
        HD-Enabler IDAS [ 10884 ]
        Description
        Created question in FIWARE Q/A platform on 14-12-2018 at 10:12
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/53777307/setting-up-lwm2m-node-lib-to-fiware-platform


        +Question:+
        Setting up lwm2m-node-lib to FIWARE platform

        +Description:+
        Having reached a stumbling block with my inherited wakaama LWM2M implementation for couple of weeks, as I reported in #154 I have no option than to try using telefonica lwm2m-node-lib instead.

        To make my point clear again, I have already IOTA, Orion, MongoDB, Cygnus all working fine. It is my client implementation that isn't sending measure to IOTA despite being able to connect. The scenario I want is LWM2M -> IOTA -> Orion -> Cygnus -> MongoDB.

        My issue now: I want have a precise explanation of configuration I need to do to have lwm2m-node-lib implementation work here, for instance where to input the server IP to connect to (where my FIWARE is running), which file to edit etc. I already picked a new device to use, keeping aside the other.

        My docker-compose file below:

        version: "3.1"

        services:

         mongo:
           image: mongo:3.4
           hostname: mongo
           container_name: fiware-mongo
           ports:
             - "27017:27017"
           networks:
             - default
           command: --nojournal

         orion:
           image: fiware/orion
           hostname: orion
           container_name: fiware-orion
           depends_on:
             - mongo
           networks:
             - default
           ports:
             - "1026:1026"
           expose:
             - "1026"
           command: -dbhost mongo -logLevel DEBUG

         lightweightm2m-iotagent:
            image: telefonicaiot/lightweightm2m-iotagent
            hostname: idas
            container_name: fiware-iotagent
            depends_on:
             - mongo
            networks:
             - default
            expose:
             - "4041"
             - "5684"
            ports:
             - "4041:4041"
             - "5684:5684/udp"
            environment:
             - "IOTA_CB_HOST=orion"
             - "IOTA_CB_PORT=1026"
             - "IOTA_NORTH_PORT=4041"
             - "IOTA_REGISTRY_TYPE=mongodb"
             - "IOTA_LOG_LEVEL=DEBUG"
             - "IOTA_TIMESTAMP=true"
             - "IOTA_MONGO_HOST=mongo"
             - "IOTA_MONGO_PORT=27017"
             - "IOTA_MONGO_DB=lwm2miotagent"
             - "IOTA_HTTP_PORT=5684"
             - "IOTA_PROVIDER_URL=http://lightweightm2m-iotagent:4041"

         cygnus:
            image: fiware/cygnus-ngsi:latest
            hostname: cygnus
            container_name: fiware-cygnus
            depends_on:
             - mongo
            networks:
             - default
            expose:
             - "5080"
            ports:
             - "5050:5050"
             - "5080:5080"
            environment:
             - "CYGNUS_MONGO_HOSTS=mongo:27017"
             - "CGYNUS_LOG_LEVEL_=DEBUG"
             - "CYGNUS_SERVICE_PORT=5050"
             - "CYGNUS_API_PORT=5080"

        Created question in FIWARE Q/A platform on 14-12-2018 at 10:12
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/53777307/setting-up-lwm2m-node-lib-to-fiware-platform


        +Question:+
        Setting up lwm2m-node-lib to FIWARE platform

        +Description:+
        Having reached a stumbling block with my inherited wakaama LWM2M implementation for couple of weeks, as I reported in #154 I have no option than to try using telefonica lwm2m-node-lib instead.

        To make my point clear again, I have already IOTA, Orion, MongoDB, Cygnus all working fine. It is my client implementation that isn't sending measure to IOTA despite being able to connect. The scenario I want is LWM2M -> IOTA -> Orion -> Cygnus -> MongoDB.

        My issue now: I want have a precise explanation of configuration I need to do to have lwm2m-node-lib implementation work here, for instance where to input the server IP to connect to (where my FIWARE is running), which file to edit etc. I already picked a new device to use, keeping aside the other.

        My docker-compose file below:

        version: "3.1"

        services:

         mongo:
           image: mongo:3.4
           hostname: mongo
           container_name: fiware-mongo
           ports:
             - "27017:27017"
           networks:
             - default
           command: --nojournal

         orion:
           image: fiware/orion
           hostname: orion
           container_name: fiware-orion
           depends_on:
             - mongo
           networks:
             - default
           ports:
             - "1026:1026"
           expose:
             - "1026"
           command: -dbhost mongo -logLevel DEBUG

         lightweightm2m-iotagent:
            image: telefonicaiot/lightweightm2m-iotagent
            hostname: idas
            container_name: fiware-iotagent
            depends_on:
             - mongo
            networks:
             - default
            expose:
             - "4041"
             - "5684"
            ports:
             - "4041:4041"
             - "5684:5684/udp"
            environment:
             - "IOTA_CB_HOST=orion"
             - "IOTA_CB_PORT=1026"
             - "IOTA_NORTH_PORT=4041"
             - "IOTA_REGISTRY_TYPE=mongodb"
             - "IOTA_LOG_LEVEL=DEBUG"
             - "IOTA_TIMESTAMP=true"
             - "IOTA_MONGO_HOST=mongo"
             - "IOTA_MONGO_PORT=27017"
             - "IOTA_MONGO_DB=lwm2miotagent"
             - "IOTA_HTTP_PORT=5684"
             - "IOTA_PROVIDER_URL=http://lightweightm2m-iotagent:4041"

         cygnus:
            image: fiware/cygnus-ngsi:latest
            hostname: cygnus
            container_name: fiware-cygnus
            depends_on:
             - mongo
            networks:
             - default
            expose:
             - "5080"
            ports:
             - "5050:5050"
             - "5080:5080"
            environment:
             - "CYGNUS_MONGO_HOSTS=mongo:27017"
             - "CGYNUS_LOG_LEVEL_=DEBUG"
             - "CYGNUS_SERVICE_PORT=5050"
             - "CYGNUS_API_PORT=5080"

        Hide
        backlogmanager Backlog Manager added a comment -

        2018-12-14 18:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-12-14 18:05|UPDATED status: transition Answered| # answers= 1, accepted answer= False
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2018-12-14 15:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-12-14 15:05|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        Hide
        backlogmanager Backlog Manager added a comment -

        2018-12-14 12:05|CREATED monitor | # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2018-12-14 12:05|CREATED monitor | # answers= 1, accepted answer= False
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            jmcantera Jose Manuel Cantera
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: