I can’t really help you in detail - it was more than 4 years ago that I last looked at this stuff. From your error text, though · it seems like something is interpreting the additional data as an OID…? Perhaps, alternatively, you could build a reaction on that error text by {grep}ing for particular data/OID and then acting on that within the (event-handling) script. Can’t contribute much more than that (any more), sorry!
You need to find in particular the TRAP entries for your OIDs in those MIBs. Unfortunately most vendors don’t really take good care of their public MIBs.