Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
F
Flask Label Input Interface
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • KEIT Chience
  • Flask Label Input Interface
  • Issues
  • #7

Closed
Open
Created May 06, 2020 by AYM@AYMMaintainer

Decide QoS level of MQTT message

MQTT has three QoS levels of message delivery. I think we should decide the QoS that suits our situation.

https://www.hivemq.com/blog/mqtt-essentials-part-6-mqtt-quality-of-service-levels/

level Purpose Advantage Disadvantage
0 At most once (default) This service level guarantees a best-effort delivery. There is no guarantee of delivery.
1 At least once A message is delivered at least one time to the receiver. It is possible for a message to be delivered multiple times.
2 Exactly once Each message is received only once It is Slower than other QoS

What should we choose?

Edited May 06, 2020 by AYM
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None