[Bug]: Messages during OTA make user interface unusable

[AndreKR]

What happened?

I'm trying to disable a device, but the "Disabled" checkbox keep disabling itself about half a second after I enabled it.

2024-09-26-18-47-01-chrome.mp4

I believe this happens because I'm running some OTA updates that generate a lot of websocket messages, but they are not related to the device I'm trying to disable.

It seems that the UI state is somehow reset every time a message comes in, but that's a guess on my part.

What browsers are you seeing the problem on?

Chrome

Relevant stacktrace

No response

Did you download state.json.zip?

I will not attach state.json.zip

[Great-Chart]

I've also experienced this issue and don't believe it is related to OTA updates.
I have found that occasionally the Disabled checkbox would stay ticked long enough to scroll to the bottom of the page and hit Submit; (but not often)!
However, I have also discovered that (on Desktop implementation) ticking Disabled checkbox and then immediately hitting Enter key will apply the configuration change - with the red "Restart" button then becoming visible.

I'm not sure that the same workaround is practicable from within the mobile app