<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>What happens if my mesh model has a lot of states?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24116/what-happens-if-my-mesh-model-has-a-lot-of-states</link><description>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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 08 Aug 2017 03:33:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24116/what-happens-if-my-mesh-model-has-a-lot-of-states" /><item><title>RE: What happens if my mesh model has a lot of states?</title><link>https://devzone.nordicsemi.com/thread/94954?ContentTypeID=1</link><pubDate>Tue, 08 Aug 2017 03:33:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2f74d4cd-c196-45a0-be74-aba836874760</guid><dc:creator>Mitch996</dc:creator><description>&lt;p&gt;I get it. For almost every application scenario, there is a server model specifically tailored for.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What happens if my mesh model has a lot of states?</title><link>https://devzone.nordicsemi.com/thread/94955?ContentTypeID=1</link><pubDate>Mon, 07 Aug 2017 09:07:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2dbf7cee-cc6a-4134-a687-32c1b4bd8e72</guid><dc:creator>Mitch996</dc:creator><description>&lt;p&gt;Hah, I thought the whole model thing was included in the profile specs,. Thanks anyway.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What happens if my mesh model has a lot of states?</title><link>https://devzone.nordicsemi.com/thread/94953?ContentTypeID=1</link><pubDate>Mon, 07 Aug 2017 08:34:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:997505c0-d36c-408d-87e7-11e4f32c96f0</guid><dc:creator>Thomas Stenersen</dc:creator><description>&lt;p&gt;Hi Mitch996,&lt;/p&gt;
&lt;p&gt;I&amp;#39;d recommend you&amp;#39;d take a look at the &lt;a href="https://www.bluetooth.com/specifications/mesh-specifications"&gt;Mesh model specification&lt;/a&gt;. There you can see how control of more complex components is envisioned and defined. One key lesson is that the &lt;em&gt;state&lt;/em&gt; is tied to the &lt;em&gt;element&lt;/em&gt; and the &lt;em&gt;model&lt;/em&gt; defines the operation(s) on the &lt;em&gt;state&lt;/em&gt;. 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 (&lt;code&gt;LIGHT1_OFF_LIGHT2_OFF&lt;/code&gt;, &lt;code&gt;LIGHT1_ON_LIGHT2_OFF&lt;/code&gt;, etc.).&lt;/p&gt;
&lt;p&gt;Best,&lt;br /&gt;
Thomas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>