CC2652R7: CC2652R7

any option to stop update of IP once acquired automatically and saved in NVM, because it updates some time in between and am not able to get data , as node IP is already updated / changed .

We usually use mDNS service to solve such issue. You can refer to openthread.io/.../mdns-discovery

am using launch CC2652 dev board.

Couldn't understand your reply.

Am using Development Board Launch pad CC2652 and manually sending command to GET data ,.

Then, you should manually check the IPv6 address every time before you send command.

Am using COAP for Data GET and POST with 3 Nodes and 3 different URI (Temperature , Doorlock and Pressure) .How can i know which URI for Which nodes , if IP changes every time.

That's why I suggest you to refer to mDNS service, but it seems that you don't accept my suggestion.

Will mDNS works on LaunchPad CC2652 ?

We usually setup mDNS service on more powerful platform. I don't think it's suitable/feasible to run mDNS discovery service on CC2652R

Yeah that is what my issue is, We have almost developed everything on CC2652 and don't have option to switch to any other platform now.
can you please suggest any way where I can make static IP without expense of changing everything? 

Please refer to these:

- https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/920754/cc2652rb-where-are-the-openthread-settings-located-in-flash-like-ipv6-how-to-prevent-getting-a-new-ipv6-address/3406054?tisearch=e2e-sitesearch&keymatch=%2525252525252520user%252525252525253A443300#3406054

- https://groups.google.com/g/openthread-users/c/R7wfk-Zqvf0

In summary, the IP address is meant to change as devices move or are removed, and it is up to the application layer to determine "logical pairing" (such as switch paired to light).

For example, you could potentially add a CoAP server on each device, which contains a property for "unique_id". Then you can read this CoAP element to determine mappings between "unique_id" and IP address.