kroutal

Results 4 comments of kroutal

'setAutomaticReconnect' not reconnection, when broker is initially not available

Hello, I'm also facing the same issue. The "MqttAsyncClient.startReconnectCycle()" method should be called when first connection fails and automaticReconnect is set to true. Is there a way to handle this...

websocket is automatically disconnected on Chrome browser (89.0.4389.128)

It's possible to avoid the disconnecttion issue by rescheduling the ping on pingresp. [https://github.com/mqttjs/MQTT.js/issues/1257#issuecomment-977701499](https://github.com/mqttjs/MQTT.js/issues/1257#issuecomment-977701499) The [default ](https://chromeenterprise.google/policies/#IntensiveWakeUpThrottlingEnabled)5 minutes can be reduced to 10 seconds for test purpose by using these...

MQTT keepalive less than 60s and chrome 88 intensive timer throttling

Hi, Paho-mqtt js is not impacted by this issue. I noticed that paho-mqtt js library reschedules the ping on pingresp . [paho-mqtt.js](https://github.com/eclipse/paho.mqtt.javascript/blob/f5859463aba9a9b7c19f99ab7c4849a723f8d832/src/paho-mqtt.js#L1432 ) It seems that reshecheduling the pings on...

MQTT keepalive less than 60s and chrome 88 intensive timer throttling

@hoIIer This is the current workaround I'm using: ``` .... this.mqttClient.on('packetsend', this.onPacketSend()); ... private onPacketReceived(mqttClient: MqttClient): OnPacketCallback { return (packet: Packet) => { //Used to fix chrome issue if (packet.cmd...