Feature request: Support changing target name via DDI API

[hldh214]

Currently, hawkBit only allows changing a target's name using the Management API. However, this requires credentials that cannot be securely embedded on devices, which makes it impractical for device-originated updates.

We would like to request support for changing a target's name via the Device Direct Integration (DDI) API. Being able to do this from the device side (using only DDI authentication and no embedded Management API credentials) would help in scenarios where the human-readable name needs updating dynamically based on device state or configuration.

Is there a way to achieve this currently, or are there plans to support it? If not, please consider adding this capability to the DDI API.

[strailov]

Hello @hldh214!
Thanks for using hawkBit!
Currently there are no plans to support such thing for the following reasons :

• We are not really confident that the device should update such things like its name - this seems more like responsibility of the operator, which should use Mgmt API.
• For the device state & configuration there are things like device status & device attributes which DDI supports for update.
• DDI is pretty stable and finalized API used by huge part of the community - so any changes should be carefully considered.

Can you share with us your use case ? Maybe we could provide some options for your solution ?

[hldh214]

Hi,

Thank you for your reply.

We are currently using Hawkbit with swupdate (suricatta) for OTA package updates. Our device has a name that can be changed by the user. We want to sync the name stored on the device with Hawkbit’s target name.

We know we can put this into attributes, but it is a sub-tab under each target and requires a click to display. Therefore, we are considering if we can change the target’s name directly.

Since the DDI API doesn’t support this, we have also considered implementing a private HTTP service that uses the device controller ID for authentication and accepts a name as a parameter. This HTTP service would be deployed on our own cloud and use the Mgmt API to update the corresponding target’s name.

This summarizes our current situation. We understand that the DDI API is stable and finalized, so we may adopt the private HTTP service approach.

Thanks again for your response.