FWIW:
"802.1AB
F.2.1 port VLAN identifier (PVID) The port VLAN identifier field shall contain the VLAN ID for the bridge port as defined in 8.4.4 of IEEE 802.1Q-1998. A value of zero shall be used if the system either does not know the PVID or does not support port-based VLAN operation."
I'd agree and also say HP is probably treating this situation incorrectly as well, since a device that claims it doesn't do VLANs (even if it is faking it) should not be flagged in the logs. The standard also of course mentions that it is legitimate to connect different PVIDs if you know what you're doing, so really vendors should provide a way to disable to warnings, and what Aruba chose to do here makes a bit of sense to deal with those that do not, with the exception of those that also warn on 0.
No dice on that command, unfortunately.