Question About Subscription List sharing between two models with extension relation.

[listenYes]

Hi 

In the Mesh model specification,   The Generic Power OnOff Server model extends the Generic OnOff Server mode. 

According to Mesh Profile  4.2.3 Subscription List,  Power OnOff model shall share its subscription list to OnOff model.

now i have the following doubt:

1. Is there still a subscription list  for OnOff Model?

2. if there is no subscription list for OnOff model. should it use the same subscription list as PowerOnOff model has?

based on the above 2 questions, i have some scenarios:

OnOff model subscribed 0XC001, PowerOnOff subscribed 0XC002.

1.when the element received message package. which include destination address  0XC001.

Do the both model can receive and handle this message successfully at that time?

2. when the element received message package. which include destination address  0XC002.

 PowerOnOff model can handle this message, but i am not sure the ONOFF model can receive and handle the same message.

In the Mesh 3.10,  PowerOnOff model will deallocate the OnOff model subscription list, then it will share its own list to the OnOff model.

does is means  they are using the same subscription list ?(  the scenario2)

[Bjørn Kvaale]

1) Yes, there is a subscription list for the Generic On Off model. Take a look at the generic_onoff_client_init function & the access_model_subscription_list_alloc() in generic_onoff_client.c in mesh sdk v3.1.0 for more info.

2) See answer to question 1 above.

For your scenario questions, do you want to Generic Power OnOff model to extend the Generic OnOff model in the same element or do you want the Generic Power OnOff model in a separate element to the Generic OnOff model? I am guessing you want the first scenario, correct?

[listenYes]

I want to Generic Power OnOff model to extend the Generic OnOff model in the same element.

[Bjørn Kvaale]

Very sorry for the delayed response. Since you are extending the Generic OnOff model with the Generic Power OnOff model, they will share the same subscription list. 

2) If the OnOff model does not subscribe to the published message (0xC002), it will not do anything with this incoming message. Only the Power OnOff model will handle this message.