Jeroen Laverman

Hi @sergeysedoy97 - good catch and thanks for providing the PR. However, in order to merge it you need to sign the eclipse contributor agreement cf. [link](https://github.com/eclipse/hawkbit/blob/aaa023732e3e265e60fa8895664e5062306f94d1/CONTRIBUTING.md#legal-considerations-for-your-contribution). Thanks in advance!

Dear @AnbazhakanSubramaniam, first of all, sorry for the delay! Thanks for providing such a well prepared idea for improving the onboarding of new users to hawkBit. I had a thorough...

Thanks for providing this fix! 👍🏻 However, in order to merge it, you need to sign the eclipse contributor agreement cf. [link](https://github.com/eclipse/hawkbit/blob/aaa023732e3e265e60fa8895664e5062306f94d1/CONTRIBUTING.md#legal-considerations-for-your-contribution). Would be great, if you could adapt that....

Hi @ctron - we definitely need to improve our documentation here. Sorry for that. If the server sends a cancel request the idea is, that the device cancels the update...

When the update is assigned, the root resource of the devices `/controller/v1/{controllerId}` exposes a link to the `deploymentBase`. \[First Interaction\] If the update is canceled from hawkBit side, the next...

@kaizimmerm & @schabdo I would like to get your opinion on this, too. 🙂

Yes, you are right. Currently, the concept of and update type `forced`/`soft` is only present in the DDI-API. Just to understand your setup a little bit better: Are your devices...

I agree, that doesn't sound optimal. So I guess, it would make sense here, to extend the DMF-API to also communicate the update type (`forced`/ `soft`) in the `DOWNLOAD_AND_INSTALL` payload....