You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to both MQTT specs, the Keep Alive value should be an integer from 0 to 65,535. A non-zero value indicates the number of seconds between messages before the client must send a pingreq; a value of 0 disables the keep-alive mechanism.
Current Behavior
Attempting to set a keep-alive value of less than 5 seconds fails with the output 'Keep alives should be >= 5 secs'. This makes it impossible to set a 0 value, or to use shorter intervals for testing/time-sensitive applications.
The text was updated successfully, but these errors were encountered:
This PR removes the requirement that the keep alive timeout be at
least 5 seconds. This is in keeping with the MQTT spec, which
states that the keep alive value should be between 0 and 65535.
A value of 0 indicates that no keep-alive pings are sent to the
broker.
Issue: bytebeamio#643 - Keep Alive has an arbitrary limit
This PR removes the requirement that the keep alive timeout be at
least 5 seconds. This is in keeping with the MQTT spec, which
states that the keep alive value should be between 0 and 65535.
A value of 0 indicates that no keep-alive pings are sent to the
broker.
Issue: #643 - Keep Alive has an arbitrary limit
Expected Behavior
According to both MQTT specs, the Keep Alive value should be an integer from 0 to 65,535. A non-zero value indicates the number of seconds between messages before the client must send a pingreq; a value of 0 disables the keep-alive mechanism.
Current Behavior
Attempting to set a keep-alive value of less than 5 seconds fails with the output 'Keep alives should be >= 5 secs'. This makes it impossible to set a 0 value, or to use shorter intervals for testing/time-sensitive applications.
The text was updated successfully, but these errors were encountered: