So just to close this off, there isn't really any reason for the plugin to try to retrieve the device information in that specific code path anyway, so I've just changed it to not do that. This way the error shouldn't happen regardless of how the driver internals behave in this situation.
|