Ok, a couple of things.
Not all events are unknown. The log shows that the "A On" event was recognized properly. What device are you using to fire the "A1 On"? Because it doesn't look like it fires an "A1 On", it almost seems like it fires an address first, and then a separate On command. The '66' buffer is something that the plugin does not recognize, but looks a lot like an A1 address by itself. Normally this should be sent as a 0166 (the first byte is supposed to be the buffer length)
Based on the protocol I used, a proper A1 On command should be the following sequence: 03026662. In your case, two events get fired: a 66 and a 020162, which is A On.
Again, it could have something to do with the device you use to fire the commands or it could be that the protocol does not support this sort of communication.
