<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ESL in template in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471969#M292823</link>
    <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/6947"&gt;@mathiassvegreus&lt;/A&gt; ,&lt;/P&gt;&lt;P&gt;SES ESL integration is a per-AP feature. If you use a template, ESL needs to be enabled on a template level, and a V:Cloud URL needs to be set (assuming that you are using the &lt;A href="https://documentation.meraki.com/MR/Deployment_Guides/SES-imagotag_Electronic_Shelf_Labels_(ESL)_Integration_with_MRs#Meraki_Dashboard_Configuration_and_V:Cloud_Connection_Types" target="_self" rel="nofollow noopener noreferrer"&gt;direct &lt;/A&gt;connection to V:Cloud). Then,  ESL functionality must be activated on individual APs within each child network.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot at Sep 21 16-40-34.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/270737iF24751DB54015179/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There is no impact on BLE functionality for APs that don't have ESL enabled unless you explicitly turn off BLE on the template level.&lt;/P&gt;</description>
    <pubDate>Wed, 21 Sep 2022 23:43:12 GMT</pubDate>
    <dc:creator>aneduzhk</dc:creator>
    <dc:date>2022-09-21T23:43:12Z</dc:date>
    <item>
      <title>ESL in template</title>
      <link>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471967#M292821</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;you can read a alot in this document ragarding ESL:&lt;BR /&gt;&lt;A href="https://documentation.meraki.com/MR/Deployment_Guides/SES-imagotag_Electronic_Shelf_Labels_(ESL)_Integration_with_MRs" target="_blank" rel="nofollow noopener noreferrer"&gt;https://documentation.meraki.com/MR/Deployment_Guides/SES-imagotag_Electronic_Shelf_Labels_(ESL)_Integration_with_MRs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;If we want to activate ESL in an template with mixed AP supported(mr44) and no supported(mr42). Can you activate ESL anyway?&lt;/P&gt;&lt;P&gt;Will ble beacon function deactivate on all ap in that template or particular ap that you really activate ESL on? &lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 06:51:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471967#M292821</guid>
      <dc:creator>mathiassvegreus</dc:creator>
      <dc:date>2022-09-21T06:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: ESL in template</title>
      <link>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471968#M292822</link>
      <description>&lt;P&gt;&lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/6947"&gt;@mathiassvegreus&lt;/A&gt;.,&lt;/P&gt;&lt;P&gt;The documentation say that It will be deactivated just on access points that you are enabling ESL.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 10:14:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471968#M292822</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2022-09-21T10:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: ESL in template</title>
      <link>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471969#M292823</link>
      <description>&lt;P&gt;Hi &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/6947"&gt;@mathiassvegreus&lt;/A&gt; ,&lt;/P&gt;&lt;P&gt;SES ESL integration is a per-AP feature. If you use a template, ESL needs to be enabled on a template level, and a V:Cloud URL needs to be set (assuming that you are using the &lt;A href="https://documentation.meraki.com/MR/Deployment_Guides/SES-imagotag_Electronic_Shelf_Labels_(ESL)_Integration_with_MRs#Meraki_Dashboard_Configuration_and_V:Cloud_Connection_Types" target="_self" rel="nofollow noopener noreferrer"&gt;direct &lt;/A&gt;connection to V:Cloud). Then,  ESL functionality must be activated on individual APs within each child network.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot at Sep 21 16-40-34.png" style="width: 999px;"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/270737iF24751DB54015179/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;There is no impact on BLE functionality for APs that don't have ESL enabled unless you explicitly turn off BLE on the template level.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2022 23:43:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471969#M292823</guid>
      <dc:creator>aneduzhk</dc:creator>
      <dc:date>2022-09-21T23:43:12Z</dc:date>
    </item>
    <item>
      <title>Re: ESL in template</title>
      <link>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471970#M292824</link>
      <description>&lt;P&gt;Good to know &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/14171"&gt;@aneduzhk&lt;/A&gt; . Then a try to reach support again, to activate that on our templates.(last time the didnt know that)&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2022 05:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/esl-in-template/m-p/5471970#M292824</guid>
      <dc:creator>mathiassvegreus</dc:creator>
      <dc:date>2022-09-22T05:13:48Z</dc:date>
    </item>
  </channel>
</rss>

