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

[Elfving]

abe said:

and on _agent_ep_handler_255 I can process all data received on endpoint 255, that's right?

Yes, if my understanding is correct then, if the correct clusters are configured, you should receive it on that endpoint handler.

abe said:

ZB_AF_SET_ENDPOINT_HANDLER (ZIGBEE_ADRI_ENDPOINT_255, _agent_ep_handler_255);

Are you using 255 as the actual endpoint number here? Maybe that is the issue. You have to use between 1 and 240.

Regards,

Elfving

[abe]

I apologize for the long delay ... I was busy with other works ..
To sumarize ... I have a Sonoff Zigbee 3.0 end node that sends IAS Alarm info to coordinator using endpoint #255 It even sends all other infos (battery level and voltage, ...) to coordinator endpoint #64 (as configured by my code)
Here below the declaration to configure the two endpoints:

I also tried to add this to declare macro

But I have error!

How can I add this endpoint to my coordinator?
I need to make it able to receive from Sonoff end node!

Many thanks for help!

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

[abe]

Yes, I started from CLI Agent (the only coordinator example available on the SDK 3.2), and my endpoint handler is  based on cli_agent_ep_handler

Abele

[abe]

Hi Elvfing,
any more answers?

[abe]

... anything for me???