Is there something on the specifications regarding the structure of a node? We have a node currently with 3 Elements:
El0: Light controller: Config model, Health model, Gen On/Off server model, Gen Level server Model
El1: EnOcean A: Gen On/Off client model, Gen Level client Model
El2: EnOcean B: Gen On/Off client model, Gen Level client Model
Basic logic is that El0 is the light controller that turns on/off and dimm the light, El1 and El2 are the translators that receive the EnOcean commands and publish the messages on the Mesh, since EnOcean has 2 buttons, then we have 2 elements, anyways, the Question is: now we need to add a "configuration settings" models, for example, to adjust the low end of the dimming... my current idea is to add another element and move the light controller funtionality there and then keep El0 for configuration/settings so the new structure would be:
El0: Settings: Config model, Health model, Gen On/Off server model, Gen Level server Model
El1: Light controller: Gen On/Off server model, Gen Level server Model
El2: EnOcean A: Gen On/Off client model, Gen Level client Model
El3: EnOcean B: Gen On/Off client model, Gen Level client Model
Is there anything somewhere on the specifications on how to structure a node? or is this completely up to the developers?
