| Re: [hawkbit-dev] Choosing soft action for auto assigned distribution sets |
|
Hi Kai, thanks for your feedback. This is crucial for us, so in a first step, we will change the auto assigned action from forced to soft. In a second step, we might make it configurable and contribute that. Regards Thomas Von: hawkbit-dev-bounces@xxxxxxxxxxx [mailto:hawkbit-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Kai Zimmermann Hi Thomas, I fear you are right. Autoassign does not support these additional options as of now. Please feel free to open a github issue or of course go ahead and add the feature directly
😊 Kai Kai Zimmermann Commercial Software Engineering
http://news.microsoft.com/de-de/
From:
hawkbit-dev-bounces@xxxxxxxxxxx <hawkbit-dev-bounces@xxxxxxxxxxx>
On Behalf Of Thomas Molkenbur Hi Hawkbit Devs, Today, as I understand, an auto assigned distribution set is always a forced action. We have devices, that we want to update with Hawkbit, which are onboarded using a mobile app. The user is guided through the onboarding process and during this process the device will be connected to the internet for
the first time. Then it will connect to the Hawkbit and a new firmware is automatically assigned to this device. If the update is forced, it will occur immediately.
This might break the guided onboarding process. Our idea is, that the auto assigned DS should be a processed as a soft action, thus we could guide the user through the update process and warn him to power off the device while the update is running. Have I overseen something in the UI or API which could solve the problem? Regards Thomas |