Alex Martens

That's all there is to it. That is the same thing my monitor does with these codes, just returns zeros. Do the setters do anything?

Can you point me to the specification that defines this value? This isn't defined by the existing specifications and is vendor specific as far as I know; this value may...

`set_input_source` will allow an int to be used: https://github.com/newAM/monitorcontrol/blob/9a319610a963a92e8c7f93e06d88936e609b9c42/monitorcontrol/monitorcontrol.py#L403 `get_input_source` has an example of how to handle out-of-range values: https://github.com/newAM/monitorcontrol/blob/9a319610a963a92e8c7f93e06d88936e609b9c42/monitorcontrol/monitorcontrol.py#L378-L387 Does that cover your usecases?

USB type C is not part of the specification, if this doesn't work there's not much that can be done about it.

I have seen this behavior once before on a different monitor, what helped for that was increasing the timeout beyond the DDC-CI minimum values. Can you try increasing these constants...

Huh, interesting! This is the first monitor that I have heard of that violates the spec then. I _would_ like to keep the exceptions as the default behavior since they...

> As I have physical access to this monitor I can prototype and propose something. What do you think? That would be great! :+1: It is hard to develop for...

...huh, if two people have this issue then this likely is a bug. I'll add something this weekend to optionally disable the checksum. @jiri-one does you monitor also work aside...

I pushed a 2.2.0 release which disables the checksums by default. https://monitorcontrol.readthedocs.io/en/latest/api.html#checksum-behaviour This does not fully address this issue since there were also problems with the payload unpacking mentioned here....

Thanks for the offer @jiri-one , I may take you up on that pending the results of this next iteration. I made another release, 2.3.0 with debug logging in the...