Closed this issue 4 years ago · 1 comments
That is the way the specification of MQTT 3.1.1 handles such errors. Without moving to MQTT 5 this will not change.