Unable to send NBIRTH Message explicitly.

[michael-benoit]

Need the ability to send a NBIRTH message similar to PublishDeviceBirthMessage.

When the Primary App returns to ONLINE, stored messages need to be sent after a new NBIRTH message is sent. Also required to support the NCMD message: Node Control/Rebirth

[Kvargefar]

I need this as well. I currently have to use Device Control/Rebirth.

[SeppPenner]

I need to check for Sparkplug 3.0 conformity first (Will be the next step, I hope to do it today or tomorrow) and the next thing is to check this request.

[Kvargefar]

@SeppPenner I believe this functionality is needed to comply with the 2.2 standard. I haven't checked the 3.0 standard. In the meantime, I believe this is solved by making the Node.PublishInternal() method public. The node should however be able to distinguish between the node metrics and device metrics - which I'm looking into now.

[buentead]

In Sparkplug v2.2 specification, the Edge Node should be able to respond to the command Node control/Rebirth (chapter 17.5, page 66). According to the Sparkplug v3.0.0 specifications the Edge Node is required to implement the Node control/Rebirth command (chapter 5.17, page 56, last paragraph on page). As of now, I could only implement this command if I Stop/Start the Edge Node connection - and this doesn't really make sense, does it.
As the command Node control/Rebirth is a MUST have in Sparkplug v3.0.0, would it make sense that the SparkplugNet library handles this command itself?
I would really appreciate a solution soon, as we need to be able to handle the Rebirth command within the Edge Node. Thanks.

[adityashahazilen]

@SeppPenner Do you have any update on this feature?

[SeppPenner]

So, the main idea here is to have a method to do a node rebirth that (in contrary to a Stop() and Start() of a node) does only send a NDEATH and a new NBIRTH (without doing anything MQTT specific like disconnecting, reconnecting and subscribing, etc.). Or do I understand this in a wrong way?