use of object_id for commands

Hey there,

"object_ids" and "name" are used as a translation layer between how things are called in field layer and in FIWARE, respectively.
That works well for attributes (measurement values coming from the field layer).
Nevertheless, this does not work for commands. When you register a device in the IoTA - let's say JSON - that has a command, this command get's posted as a registration in orion. This way, a PATCH on that command will trigger a request from orion to the IoTA.
In my case, all communication between FIWARE and the field layer is done via MQTT. So the IoTA forwards this command to the corresponding topic (which works fine) but the payload looks like
{"<attr_name>":}.
Since the API documentation (or at least the given examples) states that commands can have object_ids, I was expecting the payload to be {"<object_id>":}.
Am I missing something or is this just not implemented?
I'm seeking to use this feature since the system in use gets more and more complex using data models in FIWARE but different naming schemas on the field layer.

Thanks for clearing things up :)

Start with the API documentation examples for command registrations and trace the command path from Orion through the IoT Agent to MQTT. Compare the documented object_ids behavior with the observed <attr_name> payload, and confirm completion by reproducing the registration and PATCH flow with a command that defines object_ids.