Questions about the implementation of Generic Power OnOff model

RE: Questions about the implementation of Generic Power OnOff model

JonasJ — Mon, 18 Feb 2019 08:15:59 GMT

I do agree with you that it doesn't really make sense. But since it was implemented I thought I might have overlooked something.

Perhaps it gets removed in the next release.

Thanks.

RE: Questions about the implementation of Generic Power OnOff model

Jorge M — Mon, 18 Feb 2019 08:13:36 GMT

Hi again Jonas,

I don't have an answer to the question in point 1, but as far as I can see in the code the generic_ponoff_setup_server_status_publish() function is never called, which make sense because the Mesh model specification in section 3.3.5.2.1 says:

" If the received message is a Generic OnPowerUp Set message, the Generic Power OnOff Server
shall respond with a Generic OnPowerUp Status message (see Section 3.3.4.3.2). "

So, the message added by the power on off setup server (the Generic OnPowerUp Set message) is answered with a message from the power on off server (the Generic OnPowerUp Status mesage) which supports publishing.

I might be wrong but it seems to me that there is no need of a `generic_ponoff_setup_server_status_publish()` function.

Best regards

RE: Questions about the implementation of Generic Power OnOff model

JonasJ — Sat, 16 Feb 2019 19:16:52 GMT

Hi,

Indeed, you are right. I must have overlooked that part, thanks.

Any comments on point 1?

Thanks.

RE: Questions about the implementation of Generic Power OnOff model

Jorge M — Fri, 15 Feb 2019 07:50:54 GMT

Hi Jonas,

Reviewing the Mesh Profile Specification, section 4.2.3 says about the subscription list:

"Instances of models that extend other models (i.e., all models within an
extension relation tree) shall share a single instance of a Subscription List per element."

So, it seems that, even if the states are not bounded, they should share the subscription list.

Best regards