<?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>Two models in one device: combination of light / light_switch sample applications</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/67996/two-models-in-one-device-combination-of-light-light_switch-sample-applications</link><description>I have used two sample applications light / light_switch from bluetooth mesh to get a device with 2 elements: 
 - generic on/off clent 
 - generic on/off server 
 I want to be able to configure it to make the client element talk to the server element</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 05 Nov 2020 14:55:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/67996/two-models-in-one-device-combination-of-light-light_switch-sample-applications" /><item><title>RE: Two models in one device: combination of light / light_switch sample applications</title><link>https://devzone.nordicsemi.com/thread/278643?ContentTypeID=1</link><pubDate>Thu, 05 Nov 2020 14:55:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b4925659-de26-4c46-9222-e7bd077feca5</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The loopback should work out-of-the-box, as long as the models are implemented correctly.&lt;/p&gt;
&lt;p&gt;You need to configure the publication and/or subscription of the models, using either group addresses or the element addresses of the server and client models. Just as you would if the models were on two different nodes.&lt;/p&gt;
&lt;p&gt;I recommend that you use the nRF Mesh smartphone app for configuration, and not the provisioner example, as the provisioner example expects the client and server to be on different nodes and will probably not work (without changes) for configuring your device.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>