<?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>Mesh Profile Specification -- Models and Elements</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46484/mesh-profile-specification----models-and-elements</link><description>Hi, 
 I am looking for ways to reduce the Element count on the nodes that have multiple instances of same model. 
 I was going through the Mesh specifications and I found this in the profile specs: 
 
 It says that an element can&amp;#39;t contain models using</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Apr 2019 12:42:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46484/mesh-profile-specification----models-and-elements" /><item><title>RE: Mesh Profile Specification -- Models and Elements</title><link>https://devzone.nordicsemi.com/thread/184076?ContentTypeID=1</link><pubDate>Fri, 26 Apr 2019 12:42:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3e009df2-3317-4664-971b-aaeecc1c7964</guid><dc:creator>Omkar Kulkarni</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;The requirement of `element can&amp;#39;t contain multiple models using the same messages` - arises from the more high-level design that, an element on the mesh node represents one actionable entity. This entity contains states that can be set or read by sending messages to that element address.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;With respect to nRF Mesh SDK, it is not only sufficient to have different opcodes, but you will also need to use a different model ID. Essentially, you will have a different model altogether even if it tries to do the same task as the original model.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;It is not a good idea to instantiate such overlapping models on the same element. If you need multiple instances of the same SIG models, you must instantiate them on separate elements.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>