I'm seeing an issue where when an MQTT client timeout (onTimeout event) is triggered, it simply calls onError for the client, which this module then just punts to self.onError. The module is setup to reconnect on an explicit onDisconnect, but I'm not sure a timeout event triggers that.
What I'm seeing at a macro level, is the MQTT connection in the module either goes down and doesn't come back, or just in general doesn't respond to MQTT published events anymore.
I'm seeing an issue where when an MQTT client timeout (onTimeout event) is triggered, it simply calls onError for the client, which this module then just punts to self.onError. The module is setup to reconnect on an explicit onDisconnect, but I'm not sure a timeout event triggers that.
What I'm seeing at a macro level, is the MQTT connection in the module either goes down and doesn't come back, or just in general doesn't respond to MQTT published events anymore.