Updating Dock Firmware: Component Error: 5 Request failed with status code 503

[uvjim]

Is there an existing issue for this?

• I have searched the existing issues

Description

When attempting to update the dock firmware from 0.9.0 to 0.9.2 a blank window pops up and an error message appears at the bottom of the screen (see screenshot).

How to Reproduce

1. Open the Web Configurator
2. Navigate to Integrations & Docks
3. Click on one of the available docks
4. Click Update

Expected behavior

Expecting the firmware to update

System version

v1.2.1

What part of the system affected by the problem?

No response

Additional context

No response

[uvjim]

This had happened multiple times across multiple browsers. However, after leaving it a while and going to get some lunch, I tried again and it has now worked.

I'm not sure whether to close this or whether it is something that you can investigate.

[xBitwinSDKx]

i have the same issue with both my docks

[xBitwinSDKx]

I found something... If I add the dock manually it will not work.
What I did to make it work:
! Be quick with all the steps you do!

• reset dock
• immediately search for the new dock --> found it then, before I couldn't find it automatically
• Add the new dock
• immediately Update device --> it worked

i just updated my 2 docks like that.... just dont wait too long inbetween the steps

[zehnm]

@uvjim do you see anything in the "Core service" logs (Web-configurator settings, Development: Logs) while the update was running?

Unfortunately the web-configurator currently doesn't show more information than the generic error code. Something we definitely have to improve!
If you still encounter this error, please enable the browser developer tools to inspect the returned error payload. Most of the time it contains more useful information.

The 503 error while updating docks means that the "update service is currently not available" and is caused either by low battery of the remote (< 20%), or if there's an issue with the dock communication.

The 0.9.2 firmware contains a few OTA improvements, so it might be possible that this behaviour is related to the older firmware.

[uvjim]

@zehnm the Core service log only goes back to yesterday (even after changing the date range to include the last 4 days) so I can't see back far enough for that. However, I have a strong suspicion that it may have bee the low battery.

Interestingly the remote does warn of the low battery when trying to update the remote firmware but does not when attempting to update the dock firmware.

[zehnm]

Fixed in the just released version 1.6.4