RE: Mesh Element not avdertised over Mesh, but accessible over Proxy

Simsim — Tue, 13 Sep 2022 08:25:33 GMT

Hi Simon

Yes you are totaly right i use the Dimming example and the Provisioning example.

Thanks for the explaining of the function of the provisioning example.

I had only to adopt the dimming server script in the config_scenarios.h

/* Sequence of steps for the level servers */
#if SCENE_SETUP_SERVER_INSTANCES_MAX > 0
#define CONFIG_SCENARIO_DIMMING_SERVER_EXAMPLE     \
    CONFIG_SCENARIO_COMMON,                        \
    CONFIG_LEVEL_SERVER,                           \
    CONFIG_SCENE_SERVER,                           \
    CONFIG_LEVEL_CLIENT,                           \
    NODE_SETUP_DONE

Simon

RE: Mesh Element not avdertised over Mesh, but accessible over Proxy

Simonr — Thu, 08 Sep 2022 12:23:19 GMT

I'm assuming the example you're referring to is the Dimming example with the Generic level server model, correct? The way the Provisioning example works is that it looks for a Uniform Resource Identifier (URI) to identify what SDK example it has found, and then provision the listed elements there, so it doesn't actually "discover" the Generic Level Client element by default. For that you will need to edit the URI your project is using on the Provisioner side to recognize it with the Generic level Client in addition to the already defined Server. See the node_setup.c, provisioner_helper.c and example_common.h files in the Provisioning example project for more details.

Best regards,

Simon