Skip to content

The broker quit operation - "Keep alive time overdue". #35

Description

@ingoogni

The broker quit operation after a client disconnects. It happened a few times, but it is not something I can reproduce. Below is all I could catch.

Using nmqtt-1.0.4, Nim 1.6.6, Windows 11

rx> Connect(00): 00 04 4D 51 54 54 04 06 00 3C 00 19 73 68 65 6C 6C 79 70 6C 75 67 2D 73 2D 42 43 46 46 34 44 35 41 32 36 30 37 00 29 73 68 65 6C 6C 69 65 73 2F 73 68 65 6C 6C 79 70 6C 75 67 2D 73 2D 42 43 46 46 34 44 35 41 32 36 30 37 2F 6F 6E 6C 69 6E 65 00 05 66 61 6C 73 65
tx> ConnAck(00): 00 02
Connections >> shellyplug-s-BCFF4D5A2607 was disconnected. Keep alive time overdue.
Client      >> shellyplug-s-BCFF4D5A2607
  host:
  sslOn: false
  sslCert:
  sslKey:
  verbosity: 0
  beenConnected: true
  username:
  password:
  clientId: shellyplug-s-BCFF4D5A2607
  s: ..disconnected..
  msgIdSeq: 3
  workQueue: 0
  pubCallbacks: 0
  inWork: false
  keepAlive: 60
  willFlag: false
  willQoS: 0
  willRetain: false
  willTopic: shellies/shellyplug-s-BCFF4D5A2607/online
  willMsg: false
  proto: MQTT
  version: 4
  connFlags: 00000110
  subscribed: 3

PS C:\Users\xxx>```

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions