Extra/new output from the capabilities command about ddcutil HOT 2 CLOSED

Neither. The capabilities string is malformed. See the segment "C0 C6C 8 C9". The capabilities command is reporting that instead of its usual output.

Keep in mind that the capabilities string is unreliable. ddcutil simply reports it as best it can and does not rely on it. (ddcui unfortunately does make use of it, but that is another discussion.) See page Command Capabilities on the website.

Unfortunately, there's no clear line between what belongs in stderr vs stdout. At least I couldn't define one. For every rule I came up with, there was a case for which the split felt wrong. For example, suppose the monitor correctly reports that it does not support a feature. Seems like that belongs in stderr, but what if the getvcp command specifies a feature group instead of a specific feature. It's unlikely that all the features in a group are implemented. Does the output belong in stdout or stderr, or should it be split up? ddcutil generally uses stderr only for serious errors. Dealing with user error reports is harder when the output is split up.

As a workaround, you could edit the capabilities string, and save the corrected string in $HOME/.cache/ddcutil/capabilities.

from ddcutil.

Everything works as is (with vdu_controls), so it's probably not an issue. I think perhaps I edited out of past config files (months ago) and was surprised to see it today when I was testing running from scratch.

from ddcutil.