Mesh extended Models in different elements

[david_owtschinnikow]

Hi, 

When I add a model that extends others (i.e. not a root model) to an element, should the extended models (for example root models) be in the same element?  

Maybe the question is more clear with my situation: I'm adding a Generic PowerOnOff Server Model instance to an element. If, for example, the Generic OnOff server model instance is in a different element: when I send a "Generic OnOff" Message addressed to the unicast address of the element where the Generic PowerOnOff is, should this model instance change the Generic OnOff Model state, even when it is in a different element? In that case, should the application key of the Generic OnOff instance be the same as the Generic Power OnOff instance? 

Thank you very much for your help!

David 

[Hung Bui]

Hi David, 

In your case of using  Generic PowerOnOff Server Model I don't see why you need to split it to lie on 2 elements ?  There is no duplicated states that you need to split them into different element. 

In case of a model that requires multiple element, there is a state binding that the state of the model on one element can be controlled by a command to the model on another element. 

There is a relevant discussion here. 

[david_owtschinnikow]

Hi, I get the idea that the main reason for having more than one element is to handle multiple identical states; from that point of view, I really don't have the need to split the model into different elements. Thank you very much!

[Naralasetty Praneeth]

hey can i know how to run and load this generic on off example into nrf52

[Hung Bui]

@Naralasetty Praneeth : Please don't include your question into other people question, and also don't  create duplicated questions.

[david_owtschinnikow]

The duplicated questions were mine, sorry for that.