Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

RE: Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

Elfving — Mon, 23 Jan 2023 13:16:44 GMT

Ah sorry about that, my mistake. Disabling zb_disable_nwk_security just happened to what the customer ended up doing in that case, but I do not believe a solution like that would not be according to spec.

Try these suggestions. I see that you are using ZB_AF_SET_ENDPOINT_HANDLER.

Regards,

Elfving

RE: Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

Belalshinnawey — Fri, 20 Jan 2023 04:37:54 GMT

Could you please provide the docs for these two functions? I can't find them, and I am not sure what exactly they do.

zb_disable_nwk_security();
zb_nwk_set_ieee_policy(ZB_FALSE);

They are from the provided link

RE: Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

Elfving — Thu, 19 Jan 2023 13:44:09 GMT

Hello,

Could you try the solution posted here?

Regards,

Elfving

RE: Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

Belalshinnawey — Thu, 19 Jan 2023 04:04:34 GMT

Any updates on this? I really need your help since I am trying to reach devices with different profile IDs

RE: Changing Zigbee Profile ID to my Own Custom Profile makes the endpoint handler not trigger.

Belalshinnawey — Wed, 18 Jan 2023 04:28:50 GMT

Adding: Using other profile IDs inside the 0x0000 to 0x7fff range like the wireless sensor network profile 0x0106 works ok, it only breaks if I use the Manf range