-
Notifications
You must be signed in to change notification settings - Fork 45
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
Comments
Good question, I need to check this again. Still some time after my last changes here... |
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. |
Needs to be checked. Some messages must be sent with QoS 0 and retain = false (E.g. NBIRTH, NDATA). |
Is checked against Sparkplug version 3.0: NBIRTH --> QoS = 0 Only NDEATH allows to specify a QoS explicitely. |
Update: The request is completely invalid against the V3.0 spec:
Edge node will message = DDEATH |
How do I specify the QoS of a message to publish?
The text was updated successfully, but these errors were encountered: