I’ve just realised that you’re not using the latest version of the binding that has had the work to try and solve this. I think it will likely solve the issue here. The problem is that the device doesn’t report that it supports multiple channels in the NIF, so the binding doesn’t know about the other channels, and yet the device sends multi-channel data. The device then doesn’t decode this.
The new version should fix this issue as it adds a check to ensure that there are multiple channels before using the multi-channel-association class.
The manually installing the version here -:
You might need to exclude the device again to ensure it’s cleanly reset. If the problems still persist, then please provide a new log…