This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

problem in end device binding in light-switch home automation

Hi,

    in Home automation light profile it is defined that

#define SAMPLELIGHT_ENDPOINT            8

 and     in Home automation Switch profile it is defined that

#define SAMPLESW_ENDPOINT                8

now when i changed endpoint to 7 in switch profile

#define SAMPLESW_ENDPOINT                7

still binding in light and switch is happening. correct me if i am wrong SAMPLESW_ENDPOINT this is used to give ID(1-240) to end device.

  • Don't understand what your problem is? Would you specify it?

  • Hi Navnath,

    endpoints are virtual application objects. They don't have to be uniquely associated to their functionality.

    What I mean is that a light on a device can be implemented on endpoint 8, while a switch in the same network can be implemented on another physical device (ie therefore will have a different network address) and choose the same endpoint number, 8.

    Application objects in the same network are uniquely identified by the couple: network address, endpoint number.

    Binding is the process of linking these application objects.

    Physical devices in the network, implementing different functionality, have different DeviceIDs. For instance, in ZigBee Home Automation Specification, an on/off switch has device ID 0x0000 and an on/off light has device id 0x0100. However, the virtual application object that implements the light or the switch functionality in the corresponding ZigBee endpoint can be chosen to be the same or different, ie the on/off light can be on any endpoint 1-240, as well as the on/off switch.

    Hope this clarifies.

    Thanks,

    TheDarkSide