Publication is not configured for the Client "0",even after successfully set the publish address using nrf Mesh App

Hello I am working on a nrf mesh project, in which I am using a mesh sensor example as a reference for my project. The provision is successful and configured the publish group that the client could publish messages , when I press the button. And it worked as expected the status is sent to the server, but after some time later like 1 hour, when try to publish the message by pressing the button , the client say in debug output that the "Publication is not configured for the client 0 " why is that?

When I reset the client "like turn off and on" then the client can again send the message to server like before.

I am Using SDK Version 5

let me know if you need further information ....

Thanks in Advance

Parents Reply Children
  • I have modified the example, also in the example I have used UART in which ASCCI commands like "time Set" is received via serial port,  then client will publish this message "time Set" to the configured address/group. Those servers that have  subscribed to this address/group will set their respective time, Initially it worked but some time later

            case NRF_ERROR_INVALID_PARAM:
                /* Publication not enabled for this client.
                 * One (or more) of the following is wrong:
                 *
                 * - An application key is missing,
                 *
                 * - or there is no application key bound to the model
                 *
                 * - or the client does not have its publication state set
                 *
                 * It is the provisioner that adds an application key, binds it to the model and sets the
                 * model's publication state.
                 */
                __LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "Publication not configured for client %u\n", client);
                break;

    This case is executed when I try to send time packet to the servers.
    Also when reset the client, or run again in debug mode then it start working normally.

  • Hi, 

    I don't know what could be going wrong here, it seems like a combination of a configuration issue and a project-specific application issue. I would suggest you to use NCSDK for this purpose, as it has much better shell interface for experimenting with such a project. It will be easier to support that.

    -Amanda

  • Another thing I have notice when this case is executed "INVALID PARAMS", I noticed that when I scan for provisioned node using nRF Android Application I am not able to see the Client node.

    Its strange if this could be a configuration issue , then it should not work for the first time as well, but after some time like 1 hour , then the client is not able to publish the time sync packet.


Related