• State Not Answered
  • Replies 47 replies
  • Subscribers 74 subscribers
  • Views 4679 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 315571
Options

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

Parents
  • 0
    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

  • 0 in reply to Elfving

    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

  • 0 in reply to Elfving
    Elfving said:
    I am just wondering how you did the test earlier with the second endpoint earlier without these issues.

    I never tried before with TWO endpoint.
    In any case, at starting of this thread, you have said 

    Elfving said:
    If the end-node sends to the endpoint #255, it broadcasts to all end-points on the device. So you do not necessarily need to add another end-point for it to be picked up.

    Perhaps this means that for endpoint 255 it is not needed the macros declaration?
    Then, the only I have to do is to try the calling of function you suggested and on image here below the code I has to add to my application to have a callback for data received from endpoint #255?

    Let me know about ...
    Many many thanks for your patience and for your help

    Abele

  • 0 in reply to abe
    abe said:
    Perhaps this means that for endpoint 255 it is not needed the macros declaration?

    Exactly, I do not think that is required. When something is sent to endpoint 255, it should be recieved on endpoint 64, as well as all other end points on the device. 

    abe said:

    Then, the only I have to do is to try the calling of function you suggested and on image here below the code I has to add to my application to have a callback for data received from endpoint #255?

    I am not sure exactly what you mean here, but I do not think you need to add a handler for EP 255 either. It should be recieved at all EPs on the device. 

    I just got a coworker to try this in v3.2 as well (by simply adding an enpoint handler using ZB_AF_SET_ENDPOINT_HANDLER(HA_DIMMABLE_LIGHT_ENDPOINT, light_bulb_ep_handler);). That endpoint recieved a messages addressed to both EP 10 and EP 255.

    Interestingly, that test shows that in this situation init_multi_ep_fixers() wasn't necessary, might be that is the case for you as well. Which might mean that we are back where we started, since this is the situation you had issues with to begin with, right?

    Either way, try this. And then try adding init_multi_ep_fixers() somewhere. It might be that the placement of it makes a difference, but I guess it is worth a try to check if it works without worrying too much about where it is placed.

    abe said:

    Many many thanks for your patience and for your help

    No problem, and thanks for your patience as well. It isn't as easy to support older SDKs, so it might take a bit longer than usual.

    Regards,

    Elfving

  • 0 in reply to Elfving
    Elfving said:
    I just got a coworker to try this in v3.2 as well (by simply adding an enpoint handler using ZB_AF_SET_ENDPOINT_HANDLER(HA_DIMMABLE_LIGHT_ENDPOINT, light_bulb_ep_handler);). That endpoint recieved a messages addressed to both EP 10 and EP 255.

    This seems a configuration for end-node, but I'm using the Coordinator.
    On my coordinator the callback for endpoint #64 is never invoked if the end-node sends to endpoint #255


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

    I am aware that this situation could be hard to solve, but please have patience to me, my customer is worried and is hoping that we could solve the issue.

    Any further suggests?

    Thanks

    Abele

  • 0 in reply to abe

    Dear Elfving,

    to give more details ... this is the info sent to endpoint #255 by end-node to my coordinator

  • 0 in reply to abe

    Hi Elfving

    any news for me?
    Thanks!

    Abele

Reply Children
Related
Terms of service