Thank you very much for providing this!
During tests last night I noticed several packets available in the API we're not showing in mqtt as well as packets in mqtt not being available in the API. I haven't been able to establish if the two are mutually exclusive due to time constrains but it certainly looked that way.
Is the mqtt access designed to 'replace' the API once consumers register for a particular node? (I can't imagine it is as it would create a denial of service opportunity.) Or was it something random I'm just not interpreting the right way?