Hey @amrtaleb and @residualimages
So bad to hear that!
Matt asked all the good questions, so I’m coming by to give some extra info before @amrtaleb adds the answers to help it better.
We’re seeing some issues with updating the FW on versions before 2.17.4, but didn’t find a workaround yet, just trying some times and it works.
I can work with the CS team to trigger the FW update requests until it works, but need your authorization, @amrtaleb . If you prefer, you can contact the CS team directly, like @residualimages mentioned.
You’re right! The v2.32.0 will have this feature, but I’m not sure this can help with the issue, since the cause seems to be in the current version and not the target one.