FindPetition doesn't handle cases when event has alternative opcodes

[monni]

When trying to find matching message, LocalDeviceHandler::FindPetition stops looking for correct message if event matches but opcode isn't correct. In some cases there is alternative opcodes for same event.

Experienced behaviour: Message is not found Expected behaviour: continue looking until opcode matches or runs out of subitems in fEventsWanted.

[monni]

Patch to change behaviour of FindPetition

[oruizdorantes]

The idea is that each opcodeExpected index inside the BMessage has to match its eventExpected index.

There are 2 different events that contains Opcode (CommandStatus and CommandComplete) they cannot be inside the request with a ramdom index. You can achieve this by Adding first those pairs in the request and last events the ones which do not require opcode.

So it is actually the expected/needed behaviour.