The node advert via meshcore/command/send_advert may be ignored by other nodes if the clock is not set correctly in the sending node.
This means that in order to have the advert seen, one has to drop into meshcli and use the clock sync command to set the time. After doing that, the send_advert will work.
Setting the node clock should work similar to the App. It should be transparent.
Suggested behaviour:
When meshcore-mqtt starts or connects to the node, it will set the node clock. It should continue to set the clock on a reconnect or at a suitable minimum interval.
The node advert via meshcore/command/send_advert may be ignored by other nodes if the clock is not set correctly in the sending node.
This means that in order to have the advert seen, one has to drop into meshcli and use the clock sync command to set the time. After doing that, the send_advert will work.
Setting the node clock should work similar to the App. It should be transparent.
Suggested behaviour:
When meshcore-mqtt starts or connects to the node, it will set the node clock. It should continue to set the clock on a reconnect or at a suitable minimum interval.
<!-- github-sync-id:3877038140 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The node advert via meshcore/command/send_advert may be ignored by other nodes if the clock is not set correctly in the sending node.
This means that in order to have the advert seen, one has to drop into meshcli and use the clock sync command to set the time. After doing that, the send_advert will work.
Setting the node clock should work similar to the App. It should be transparent.
Suggested behaviour:
When meshcore-mqtt starts or connects to the node, it will set the node clock. It should continue to set the clock on a reconnect or at a suitable minimum interval.