Closed Kiogora closed 4 years ago
Thanks @Kiogora for sharing this. I don't think we can do anything about it in esp-mqtt
, not even "tolerate" these reserved bits, as the spec says the receiver (not only server) MUST close the connection.
Thank you @david-cermak . This is understood. I can close this, to archive it in case anybody finds the same problem.
For those using thingsboard, the implementation of the broker does not follow the 3.1.1 spec with regard to acknowledgement flags thus:
subAck is 0x92 instead of 0x90
pubAck is 0x42 instead of 0x40
Though wireshark does identify the header - Maybe it doesnt check flags on some commands for proper identification?
You may edit the mqtt_message.c to edit the expected flags check in mqtt_has_valid_msg_hdr() function as below: