I know this thread is very old, and hopefully things worked out for you Lukas. I just wanted to write for others who might stumble into this thread that the issue (causing errors related to the getPixelResolution method) might in some cases be a lot simpler than it seems. In my case, this was the problem:
device_number: 1
This actually means that you’re telling ioHub to your second monitor connected to the computer. The reason is that ioHub used 0-indexing/counting, where 0 is the first monitor, 1 is the second monitor, and so on. I only realized this after comparing my YAML file to the ones of the ioHub demo experiments. @sol Maybe the exception/error message could be updated, so that it suggests that device numbering might be the issue when getPixelResolution fails?