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

FIWARE.Question.Tech.Disable Auto-provisioning of Devices in Fiware MQTT JSON IoT Agent.

    Details

      Description

      Created question in FIWARE Q/A platform on 26-05-2022 at 13:05
      Please, ANSWER this question AT https://stackoverflow.com/questions/72392339/disable-auto-provisioning-of-devices-in-fiware-mqtt-json-iot-agent

      Question:
      Disable Auto-provisioning of Devices in Fiware MQTT JSON IoT Agent

      Description:
      We are using FIWARE Orion NGSI V2 version and MQTT JSON IoT Agent. We have attached the version of Context Broker and IoT Agent we are using below.
      By default, whenever we send telemetry data through MQTT broker, for a device which does not exist in Fiware, the IoT Agent is automatically provisioning/creating the device in IoT Agent and corresponding entity in Context Broker.
      We want to restrict this behavior and do not want the IoT Agent to auto-provision devices, but to only accept telemetry data for already registered devices.
      We have already tried to set the IOTA_APPEND_MODE environment variable to false, also tried to set the autoprovision flag to false when creating the service group. None of these options are working and autoprovisioning is still happening.
      Need your help and guidance on how do we disable the auto-provisioning IoT Agent.
      IoT Agent version:

      {"libVersion":"2.12.0-next","port":"4041","baseRoot":"/","version":"1.14.0-next"}

      Context Broker Version:
      {
      "orion" : {
      "version" : "2.3.0",
      "uptime" : "12 d, 18 h, 50 m, 12 s",
      "git_hash" : "764f44bff1e73f819d4e0ac52e878272c375d322",
      "compile_time" : "Tue Nov 5 09:16:27 UTC 2019",
      "compiled_by" : "root",
      "compiled_in" : "cfe8becf7aae",
      "release_date" : "Tue Nov 5 09:16:27 UTC 2019",
      "doc" : "https://fiware-orion.rtfd.io/en/2.3.0/"
      }
      }

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2022-05-27 05:31|CREATED monitor | # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2022-05-27 05:31|CREATED monitor | # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2022-05-28 05:31|UPDATED status: transition Answer| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2022-05-28 05:31|UPDATED status: transition Answer| # answers= 1, accepted answer= True
        Hide
        backlogmanager Backlog Manager added a comment -

        2022-05-29 05:31|UPDATED status: transition Finish| # answers= 1, accepted answer= True

        Show
        backlogmanager Backlog Manager added a comment - 2022-05-29 05:31|UPDATED status: transition Finish| # answers= 1, accepted answer= True

          People

          • Assignee:
            Unassigned
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: