Open lorenzopagliai opened 2 months ago
Correct. the OTA operation is performed in 2 steps: 1) upload the image to the cloud 2) send the request to the device If the image upload is interrupted (for example by a page refresh) there will be nothing to send to the device.
Sadly, the image upload is handled by the browser, so reloading the page stops our frontend from performing any action.
In an effort to improve the user experience, what's the behavior you'd like to have in that form? Was the page refreshed by mistake? or were you trying to do something else while performing an OTA?
Thank you very much for the clarification.
As far as the desired behaviour is concerned, even just a banner or an information panel (which perhaps only appears when a software update is triggered) telling the user not to refresh the page after the previous behaviour has occurred could be useful. If there is no way to manage such behaviour as it is dependent on factors outside the portal (browser) already this addition could be of value.
In the case of an OTA update via the ‘Software Updates’ tab of the Clea Edgehog portal, if the user performs a web page refresh (e.g. via the F5 button) while the image is being uploaded (see image below), the upload operation is cancelled and no OTA update is performed.