akiroz

I'm experiencing the same issue with `async-mqtt: 2.6.1` which depends on `mqtt: 4.1.0`. I'm guessing this has something to do with the MQTTv5 implementation? =============================================== EDIT: I've done some further...

Okay I've finally got to the bottom of this, it seems to be a MQTT.js bug in the reconnect logic. Some context: MQTTv5 supports a feature called Topic Aliasing where...

So it seems like the `topicAliasMaximum` property is actually set when handling the first `CONNACK` packet provided by the server, is this expected behavior when users are expected to handle...

bump. @chrisfarms

Thanks for all your efforts, the ads has been a huge pain point in using the 1933 app! I have briefly tested hkbus.app but it seems like the same issue...