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

NDEATH trigger problem #75

Closed
petrosinoE80 opened this issue Feb 27, 2024 · 2 comments
Closed

NDEATH trigger problem #75

petrosinoE80 opened this issue Feb 27, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@petrosinoE80
Copy link

Hi, I have an issue with the trigger of the death message publication.

When I call the SparkplugBNode Stop() method, I don't receive any death certificate at the client side.

Is there a way to trigger it forcibly, e.g. in order to call it in a Dispose() method or similar?

[SparkplugNet ver. 1.3.2]

Thank you very much in advance.

@shouidar
Copy link
Contributor

shouidar commented Feb 28, 2024

When the stop method is called an MQTT Disconnect packet is sent to the broker. In this case the broker will not deliver the WILL message to subscribers. Normally the Edge Node should publish an NDEATH message before intentionally disconnecting. Unfortunately, it seems the library does not implement a method for sending DEATH message. (This is also true for the Host application). This is a requirement for version 3.0 .

@SeppPenner SeppPenner self-assigned this Feb 29, 2024
@SeppPenner
Copy link
Owner

When the stop method is called an MQTT Disconnect packet is sent to the broker. In this case the broker will not deliver the WILL message to subscribers. Normally the Edge Node should publish an NDEATH message before intentionally disconnecting. Unfortunately, it seems the library does not implement a method for sending DEATH message. (This is also true for the Host application). This is a requirement for version 3.0 .

You are right, currently only the will topics are sent if disconnected unintentionally. I will add this as soon as I have fixed the total data conversion mess :D

@SeppPenner SeppPenner added the bug Something isn't working label Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants