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

[abe]

Hi Elfving
have any news for me?

Thanks

Abele

[abe]

Nobody can answer me?
Please let me know ...

Thanks

Abele

[Elfving]

Hello Abele and sorry about the wait,

First of all, I see I failed to mention earlier that the nRF5 Zigbee SDK is deprecated and you should preferably upgrade to NCS. Though if you are in the middle of development with nRF5 SDK I would understand if you do not do this now. But one thing I've overlooked and definitely should mention is that you are using 3.2 of the old Zigbee SDK, and not the newest one, v4.2. v3.2 conforms to Zigbee PRO R21, and not R22. You need to conform to R22 in order to get your Zigbee product certified.

Is there any particular reason why you are using v3.2?

I am not sure if this fixes your issue, but I see here that there are some issues that were solved in v4.2. I didn't use to think they were relevant for you, but now might be what you have been facing. Eg. KRKNWK-5826

Regards,

Elfving

[abe]

Hi Elfving
I used SDK 3.2 because I have developed this product for my customer in 2018. Then we are on production since 2019 ad we have several thousand of pieces on the field.
Now we need to add the sensor here above quoted, and we need to solve the issue and add at least a second endpoint to our Coordinator
We know about the new 4.2 solution, but unfortunatly there are no chanche tu update directly from 3.2 (we used IAR EWARM) to 4.2.
It needs probably to remake full project, and this is too much expensive and is not accettable.
In adition, there is the field that ask for this update.
Coould you help me for this solution?
Thanks
Abele