Error while calling SET_CUSTOM_MODE with [xxx]

[modo1302]

Version of the custom_component

1.0.14

What vacuum are you using?

Roborock S7 MaxV Ultra

Describe the bug

Randomly (30% of time) experiencing an error while changing the vaccum fan speed.
When changing to 'max_plus' i get Error while calling SET_CUSTOM_MODE with [108]
When changing to 'off' i get Error while calling SET_CUSTOM_MODE with [105]

Is someone else experiencing this issue? Maybe i'm setting vacuuming mode in a wrong way? If so - what;s the correct way to do it?
Usually the fan is set correctly, sometimes however the error occurs which stops an automation entirely.
Any advice?

Debug log

Rejestrator: homeassistant.components.automation.roborock_codzienne_kuchnia
Źródło: helpers/script.py:2026
integracja: Automatyzacja (dokumentacja, Problemy)
Pierwsze zdarzenie: 13:43:06 (1 zdarzenia)
Ostatnio zalogowany: 13:43:06

Roborock - CODZIENNE - Kuchnia: Error executing script. Error for call_service at pos 4: Error while calling SET_CUSTOM_MODE with [105]

---

Rejestrator: homeassistant.components.automation.roborock_codzienne_kuchnia
Źródło: components/automation/__init__.py:763
integracja: Automatyzacja (dokumentacja, Problemy)
Pierwsze zdarzenie: 13:43:06 (1 zdarzenia)
Ostatnio zalogowany: 13:43:06

Error while executing automation automation.roborock_codzienne_kuchnia: Error while calling SET_CUSTOM_MODE with [105]

---

Rejestrator: homeassistant.components.automation.roborock_codzienne_przedpokoj
Źródło: components/automation/__init__.py:763
integracja: Automatyzacja (dokumentacja, Problemy)
Pierwsze zdarzenie: 11:13:39 (1 zdarzenia)
Ostatnio zalogowany: 11:13:39

Error while executing automation automation.roborock_codzienne_przedpokoj: Error while calling SET_CUSTOM_MODE with [108]

[modo1302]

Actually after months of frustration i think i managed to solve my issue. I brutally put the fan speed setting in a loop and checking if the fan speed actually changed. If it did - exit the loop and continue with the rest of automation (oh yes, also needed to put the continue_on_error: true in the troublesome task).
Still not sure why the error randomly occurs in the first place though.