What happens if my mesh model has a lot of states?

[Mitch996]

Hi, I think the idea of limiting the behavior of a model to states is very wise, but due to my limited understanding in this matter, I find it puzzling as to what happens if my mesh model has a lot of states.

If my model serves only as a simple on and off server, then fine. What if there is a dimming function involved? Do I have to have 10 states? Seems a bit excessive, what if we are talking about factory settings where a motor has an rmp monitor? Isn't there going to be like 1500, 1600, 1700... 8000 a total of 66 states? I'm not saying it's undoable, I'm saying it's kind of wasteful?

Or I got something wrong again?

[Thomas Stenersen]

Hi Mitch996,

I'd recommend you'd take a look at the Mesh model specification. There you can see how control of more complex components is envisioned and defined. One key lesson is that the state is tied to the element and the model defines the operation(s) on the state. E.g., in the light control example, the client has four elements, one for each button/light. Of course, you can define a more complex state to only reside in one element (LIGHT1_OFF_LIGHT2_OFF, LIGHT1_ON_LIGHT2_OFF, etc.).

Best,
Thomas

[Mitch996]

Hah, I thought the whole model thing was included in the profile specs,. Thanks anyway.

[Mitch996]

I get it. For almost every application scenario, there is a server model specifically tailored for.