You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an option to be set "PublishKnownDeviceMetricsOnReconnect" when we don't want to send the device metrics on startup but this is only for device metris and there is no such option for node metrics. As per the specification, when a primary host application is configured the node MUST wait until the STATE = True before sending the NBIRTH and DBIRTH.
[tck-id-message-flow-edge-node-birth-publish-phid-wait] If the Edge Node is configured to
wait for a Primary Host Application it MUST verify the Primary Host Application is online via
the STATE topic before publishing NBIRTH and DBIRTH messages.
The text was updated successfully, but these errors were encountered:
Hi @SeppPenner,
There is an option to be set "PublishKnownDeviceMetricsOnReconnect" when we don't want to send the device metrics on startup but this is only for device metris and there is no such option for node metrics. As per the specification, when a primary host application is configured the node MUST wait until the STATE = True before sending the NBIRTH and DBIRTH.
I've created a pull request: #111
Specification
[tck-id-message-flow-edge-node-birth-publish-phid-wait] If the Edge Node is configured to
wait for a Primary Host Application it MUST verify the Primary Host Application is online via
the STATE topic before publishing NBIRTH and DBIRTH messages.
The text was updated successfully, but these errors were encountered: