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

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

msalmankhan334 — Tue, 22 Feb 2022 08:22:17 GMT

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.

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

Amanda Hsieh — Tue, 22 Feb 2022 07:13:57 GMT

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

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

msalmankhan334 — Thu, 17 Feb 2022 10:07:16 GMT

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.

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

Amanda Hsieh — Wed, 16 Feb 2022 13:08:21 GMT

Hi,

It is hard to say anything from this one. Could be a configuration issue on the sensor client example.

Are you working with nRF52840DK? Do you see the same issue with the unmodified mesh sensor example? If not, please elaborate on how to reproduce the issue or share the paorject. Thanks.

Regards,
Amanda