[ https://jira.fiware.org/browse/HELP-20120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fernando Lopez reassigned HELP-20120: ------------------------------------- Assignee: Stefan Wiedemann > [fiware-stackoverflow] How to enable NGSIv2 in iotagent-ul helmchart? > --------------------------------------------------------------------- > > Key: HELP-20120 > URL: https://jira.fiware.org/browse/HELP-20120 > Project: Help-Desk > Issue Type: Monitor > Components: FIWARE-TECH-HELP > Reporter: Backlog Manager > Assignee: Stefan Wiedemann > Labels: fiware, fiware-orion > > Created question in FIWARE Q/A platform on 09-10-2022 at 08:10 > {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/74003335/how-to-enable-ngsiv2-in-iotagent-ul-helmchart > +Question:+ > How to enable NGSIv2 in iotagent-ul helmchart? > +Description:+ > I received {"name":"BAD_REQUEST","message":"Request error connecting to the Context Broker: 501"} error when when I send a POST to iotagent-ul deployed via iotagent-ul helm chart. > time=2022-10-08T09:03:18.182Z | lvl=DEBUG | corr=d7ed414d-a132-45ea-b4a3-38ee14a828dc | trans=d7ed414d-a132-45ea-b4a3-38ee14a828dc | op=IoTAgentNGSI.Request | from=n/a | srv=openiot | subsrv=/ | msg=Response { > "error": "NotImplemented", > "description": "Only NGSIv1-based forwarding supported at the present moment. Set explictely legacyForwarding to true" > } > Following the iotagent-ul documentation to enable NGSIv2, it must be set ngsiVersion in contextBroker: > { > host: '192.168.56.101', > port: '1026', > ngsiVersion: 'v2' > } > Now, I get this error: > time=2022-10-08T18:17:24.614Z | lvl=ERROR | corr=841d2b61-463e-42ff-acd7-d0f4b867b7b3 | trans=841d2b61-463e-42ff-acd7-d0f4b867b7b3 | op=IoTAgentNGSI.DeviceService | srv=openiot | subsrv=/ | msg=Registration error connecting to the Context Broker: {"code":"400","reasonPhrase":"Bad Request","details":"missing isDomain value for registration attribute"} | comp=IoTAgent -- This message was sent by Atlassian JIRA (v6.4.1#64016)
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy