ValueError: 33 is not a valid InputSource about monitorcontrol HOT 3 CLOSED

That is an unassigned value, only 0x01 to 0x12 are assigned. An unassigned value has happened before, but that was with a type-c monitor: #93

I'll double check those values are getting parsed correctly when I have time to refresh myself on the spec (probably this weekend).

from monitorcontrol.

I checked the spec, as far as I can tell 60(00 11 12 0F 21 22 2F 31) in the VCP capabilities string is invalid, 00 and 21 22 2F 31 are invalid.

The input sources for that monitor are

• 1x DP (1.2)
• 1x HDMI (2.0)
• 1x HDMI (1.4)

which corresponds to the 3 valid bytes (11 12 0F).

I am not sure what to do in this situation 🤔. The invalid bytes could be ignored, but invalid bytes are also used for inputs that are not (yet) defined by the MCCS specification, such as USB Type-C in #93. Also the specification is usually explicit when reserved values should be ignored, and it does not use that language for the input source.

from monitorcontrol.

Well I don't really know, especially since I don't know the spec at all.
Maybe an argument that tells if

• they should be ignored
• they should be returned as integers to be processed by people who know what they're doing
• they should raise an exception (default behaviour I guess)
  ?

This way, people like me who don't really care about these values can work with standard values instead of having an error and nothing initialized and nothing to work with, and people with USB-C ports can work with them too if they know which one of the non standard values it is?

This kinda sounds like a bad idea of "not deciding what to do" actually, but I don't have better ideas than you about what to do.

from monitorcontrol.