Coordinator endpoint

[abe]

Hello, I developed for my customer, a ZigBee coordinator in last 2019, using nRF5 SDK for Thread and Zigbee v3.2.0.
I has installed many sistems on field, equipped witn several battery powered sensors (door, motion, occupancy ...) and mains powered actuators (bulbs and smart plug).
I have only one endpoint # 64 configured on my coordinator, and now I need to add a second endpoint to receive the info from some end-node that sends to fixed endpoint #255
How can I add it?
Thanks for help

Abele

[abe]

Hi Elfving

any news for me?
Thanks!

Abele

[Elfving]

abe said:

In any case, now I try the init_multi_ep_fixers(); as you sent me, but I have some build errors:

Once again I am not sure if that is necessary, try without it first. My coworker did manage to do it without that. 

abe said:

This seems a configuration for end-node, but I'm using the Coordinator.

Ah, right. I should've tried that immediately.

abe said:

On my coordinator the callback for endpoint #64 is never invoked if the end-node sends to endpoint #255

Maybe you need the right cluster implemented there. Though are you seeing the same issue when trying it on another end node?

Regards,

Elfving

[abe]

Hi

it is not a cluster issue, if I use an end-node that sends info of cluster 500 to endpoint #64 of my coordinator, it works well (we have some hundred of this type end-nodes on the field)
Now we tried with Sonoff, and it sends same info of cluster 500 but to endpoint 255 (image here below)

[Elfving]

abe said:

it is not a cluster issue, if I use an end-node that sends info of cluster 500 to endpoint #64 of my coordinator, it works well (we have some hundred of this type end-nodes on the field)

I see.

By the way, was your app based on the cli agent? Or are you just basing your endpoint handler on the cli_agent_ep_handler?

Regards,

Elfving

[Elfving]

My coworker has now tested this with a coordinator as well. The coordinator should be able to receive on an endpoint using ZB_AF_SET_ENDPOINT_HANDLER, as well as by using 255.

She sent an attr req for Basic cluster and ZCL version:

zcl attr read 0x0000 255 0x0000 0x0104 0x00

And can see that the endpoint handler is being called, both with endpoint set to 10, and to 255. But only for the clusters and attributes that are implemented on the device itself.

Regards,

Elfving