Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: QoS #38

Closed
michael-benoit opened this issue Feb 13, 2023 · 5 comments
Closed

Question: QoS #38

michael-benoit opened this issue Feb 13, 2023 · 5 comments
Assignees
Labels
documentation Improvements or additions to documentation invalid This doesn't seem right question Further information is requested wontfix This will not be worked on

Comments

@michael-benoit
Copy link

How do I specify the QoS of a message to publish?

@SeppPenner SeppPenner self-assigned this Feb 21, 2023
@SeppPenner SeppPenner added documentation Improvements or additions to documentation question Further information is requested labels Feb 21, 2023
@SeppPenner
Copy link
Owner

Good question, I need to check this again. Still some time after my last changes here...

@SeppPenner
Copy link
Owner

The short answer at the moment is: You can't :D Don't ask me why, but somehow I assumed that all Sparkplug messages should be sent with QoS=1 (Which in 2.2 was only the case for state messages as far as I researched it now). I will try to change this and provide full 3.0 compatibility with the TCK from Ecplise as requested under #39, so I guess you need to wait for that to be done.

@SeppPenner SeppPenner added the bug Something isn't working label Feb 23, 2023
@SeppPenner
Copy link
Owner

Needs to be checked. Some messages must be sent with QoS 0 and retain = false (E.g. NBIRTH, NDATA).

@SeppPenner SeppPenner added invalid This doesn't seem right wontfix This will not be worked on and removed bug Something isn't working labels Apr 7, 2023
@SeppPenner
Copy link
Owner

Is checked against Sparkplug version 3.0:

NBIRTH --> QoS = 0
NDEATH --> Not fix
DBIRTH --> QoS = 0
DDEATH --> QoS = 0
NDATA --> QoS = 0
DDATA --> QoS = 0
NCMD --> QoS = 0
DCMD --> QoS = 0
STATE --> QoS = 1

Only NDEATH allows to specify a QoS explicitely.

@SeppPenner
Copy link
Owner

SeppPenner commented Apr 8, 2023

Update: The request is completely invalid against the V3.0 spec:

  • Edge node will message QoS must be set to 1.
  • Edge node will message retain flag must be set to false.

Edge node will message = DDEATH

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation invalid This doesn't seem right question Further information is requested wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants