Creacion de Actuadores en ARM64

[AlexHernandez2698632494]

Hi,

I am having an issue when provisioning a device of type actuator using IoT Agent JSON only when running the ARM Docker image.

The same configuration works correctly when running the IoT Agent from source code on the same ARM machine, but fails when using the prebuilt ARM image.
Error observed

When trying to create the device, I get the following error in the IoT Agent logs:
time=2025-12-12T21:00:23.343Z | lvl=DEBUG | corr=4817411f-89b6-41e2-b14d-6763cadd45d5 | trans=4817411f-89b6-41e2-b14d-6763cadd45d5 | op=IoTAgentNGSI.Request | from=n/a | srv=n/a | subsrv=n/a | msg=Response {
"error": "BadRequest",
"description": "/url/ field of /http/ is invalid"
} | comp=IoTAgent

time=2025-12-12T21:00:23.343Z | lvl=ERROR | corr=4817411f-89b6-41e2-b14d-6763cadd45d5 | trans=4817411f-89b6-41e2-b14d-6763cadd45d5 | op=IoTAgentNGSI.Registration | from=n/a | srv=n/a | subsrv=n/a | msg=Registration error connecting to the Context Broker: 400 | comp=IoTAgent

time=2025-12-12T21:00:23.343Z | lvl=DEBUG | corr=4817411f-89b6-41e2-b14d-6763cadd45d5 | trans=4817411f-89b6-41e2-b14d-6763cadd45d5 | op=IoTAgentNGSI.DeviceProvisioning | from=n/a | srv=n/a | subsrv=n/a | msg=Device provisioning failed due to the following error: Request error connecting to the Context Broker: 400 | comp=IoTAgent
Expected behavior

The device provisioning should succeed, as it does when running the IoT Agent directly from source on the same ARM machine.
Is there any known issue or difference in the ARM Docker image regarding actuator provisioning or HTTP endpoint validation?

Is there any additional configuration required for actuators when using the ARM image, or could this be a bug in the ARM build?

Any guidance would be appreciated.
thanks

prueba2.txt

[AlvaroVega]

Some url are weird, maybe chat is not valid for an url: orion_ and iot_agent_json_

2025-12-12T20:47:28.045Z | lvl=INFO msg=Setting IOTA_CB_HOST to environment value: orion_ 

and

2025-12-12T20:47:28.045Z | lvl=INFO msg=Setting IOTA_PROVIDER_URL to environment value: http://iot_agent_json_:4041 

[AlexHernandez2698632494]

If that's censorship, the name is Orion_, the name of the project we're developing. The error only occurs with actuators. We've created multi-architecture images, and the same error only happens with ARM; it doesn't happen with sensors, and AMD actuators don't produce the error.

[AlvaroVega]

Orion CB can not reach provided provider URL as says in "/url/ field of /http/ is invalid"

Your iota seems to be 3.3.0 version, latests version is 3.11.0, maybe you could try to update.

[fgalan]

For some reason that URL is not valid for Orion Context Broker.

Digging into CB code, this comes from https://github.com/telefonicaid/fiware-orion/blob/master/src/lib/jsonParseV2/parseRegistration.cpp#L181

  if (parseUrl(httpP->url, host, port, path, protocol) == false)
  {
    *errorStringP = "/url/ field of /" + fieldName + "/ is invalid";
    return false;
  }

The parseUrl() is https://github.com/telefonicaid/fiware-orion/blob/master/src/lib/common/string.cpp#L386

@AlexHernandez2698632494 I'd suggest to analyse that logic to see why that string is not valid. This would end in a conclusion about why http://iot_agent_json_:4041 is not valid or a potential flaw in the URL parsing logic at CB (in which case, we, as developers of CB, can solve it).

Another thing you can try to debug this is with simpler URLs, like http://iot_agent_json:4041 or http://iotagentjson:4041.

Please keep posting your findings :)

[fgalan]

In addition, upgrade both IOTA (as @AlvaroVega suggets) and CB to its newest versions at the present moment is also a good idea.