I connect use https://mqttx.app/web-client, and the connection closes with "An mqtt session is ended. Reason: No packet has been received for 1.5 times the Keepalive time.",
According to the definition, "The Keep Alive mechanism in MQTT ensures the connection’s liveliness and provides a way for the broker to detect if a client becomes unresponsive or disconnected.", who do we expect to send the keep alive back to client? Shall our service take this responsibility, as the same as what we do for the WebSocket connections?
Describe the bug
I connect use https://mqttx.app/web-client, and the connection closes with "An mqtt session is ended. Reason: No packet has been received for 1.5 times the Keepalive time.", According to the definition, "The Keep Alive mechanism in MQTT ensures the connection’s liveliness and provides a way for the broker to detect if a client becomes unresponsive or disconnected.", who do we expect to send the keep alive back to client? Shall our service take this responsibility, as the same as what we do for the WebSocket connections?