Xiaomi G Pro 27i unstable feature detection

[Bert-Proesmans]

Repeatedly querying monitor details through DDC/CI returns missing, corrupt, or valid VCP capabilities string (verified using softMCCS). The cause seems to be manually configuring settings for brightness, colors, color mode, toggling windows hdr. All these codes are valid, the robustness quality of the firmware seems to be very low (if existent).

This causes Twinkle Tray to either not detect- or detect an incomplete set of features, not even brightness. Also the flyout window doesn't appear.
Setting brightness through scrolling on top of the icon works (as the vcp code 0x10 is correct) as expected.

I understand the flyout window probably hanging/crashing on the inconsistent set of detected features, but I kinda expected manually configured features to be 'static' (like an override and/or fallback).
Since the monitor firmware is basically beyond saving (not update-able), to recover the flyout construction for this monitor the user has to be able to define (entirely) manually- and disable automatic detection of features.

Here is a twinkle tray report generated at a random point in time; tt-report-1770478620135.txt

EDIT;
In my case it would be cool to have brightness and input selection (also valid vcp capability, i got it detected by twinkle tray a few times and it even included input names WOW!) working statically for this monitor.

[monitorguy-tech]

DDC/CI-protocol is often a little bit unstable, so reading values from monitor over DDC/CI sometimes fails,
especially while transfering many data, like a long capability string,
so it is really important to try many times with a short delay, to get the data from monitor.
This simple thing is the main reason why some monitor controlling apps work better than others.