<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:webfeeds="http://webfeeds.org/rss/1.0">
    <channel>
        <title><![CDATA[Logitech Hub]]></title>
        <description><![CDATA[Logitech Hub]]></description>
        <link>https://hub.sync.logitech.com</link>
        <image>
            <url>https://tribe-s3-production.imgix.net/AFd3eetg0bHgOHdiKNtO4?fit=max&amp;w=500&amp;auto=compress,format</url>
            <title>Logitech Hub</title>
            <link>https://hub.sync.logitech.com</link>
        </image>
        <generator>Bettermode RSS Generator</generator>
        <lastBuildDate>Wed, 24 Jun 2026 08:12:39 GMT</lastBuildDate>
        <atom:link href="https://hub.sync.logitech.com/rss/feed" rel="self" type="application/rss+xml"/>
        <pubDate>Wed, 24 Jun 2026 08:12:39 GMT</pubDate>
        <copyright><![CDATA[2026 Logitech Hub]]></copyright>
        <language><![CDATA[en-us]]></language>
        <ttl>60</ttl>
        <webfeeds:icon>https://tribe-s3-production.imgix.net/AFd3eetg0bHgOHdiKNtO4?fit=max&amp;w=500&amp;auto=compress,format</webfeeds:icon>
        <webfeeds:related layout="card" target="browser"/>
        <item>
            <title><![CDATA[Adding a Custom Logo to Logitech View]]></title>
            <description><![CDATA[This article explains how to add and manage custom logos that are displayed on maps through Logitech View. 


PREREQUISITES

To follow this guide, you'll need at least one room set up in Sync and be logged...]]></description>
            <link>https://hub.sync.logitech.com/sync-guides-e8y427my/post/adding-a-custom-logo-to-logitech-view-1kHrYPxKTrom4lk</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/sync-guides-e8y427my/post/adding-a-custom-logo-to-logitech-view-1kHrYPxKTrom4lk</guid>
            <category><![CDATA[Logitech Room Booking]]></category>
            <dc:creator><![CDATA[Reed A]]></dc:creator>
            <pubDate>Tue, 23 Jun 2026 16:42:23 GMT</pubDate>
            <content:encoded><![CDATA[<p>This article explains how to add and manage custom logos that are displayed on maps through Logitech View.&nbsp;</p><figure data-align="center" data-size="best-fit" data-id="8PcuBOtY7AHwAKGmz9gWu" data-version="v2" data-type="image"><img data-id="8PcuBOtY7AHwAKGmz9gWu" title="Screenshot 2025-07-07 at 6.02.53 PM.png" src="https://tribe-s3-production.imgix.net/8PcuBOtY7AHwAKGmz9gWu?auto=compress,format"></figure><h2 class="text-xl" data-toc-id="a12185f6-f74a-4e9b-8530-9ae917efff50" id="a12185f6-f74a-4e9b-8530-9ae917efff50">Prerequisites</h2><p>To follow this guide, you'll need at least one room set up in Sync and be logged in as an administrator with Admin privileges. For more information, see the<a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="https://hub.sync.logitech.com/sync"><u> Sync Admin Guide</u></a>.</p><p>You'll also need Logitech View enabled and set up on the RoomMate where you want to add a custom logo. For details on setting up Logitech View, see <a class="text-interactive hover:text-interactive-hovered" rel="noopener noreferrer nofollow" href="https://hub.sync.logitech.com/syncguides/post/getting-started-with-logitech-view-4S7YT8vEQx29A6m">Getting started with Logitech View.</a></p><h2 class="text-xl" data-toc-id="60d9c099-d322-40e3-ae24-ca16d35c07da" id="60d9c099-d322-40e3-ae24-ca16d35c07da">Adding a Custom Logo</h2><p>You can add custom logos to be displayed on maps through Logitech View from your Logitech Sync account at either the group level or for each map individually.</p><h3 class="text-lg" data-toc-id="53b44632-613e-4727-9a94-3097b12fb13c" id="53b44632-613e-4727-9a94-3097b12fb13c">Group Level</h3><ol><li><p>Log in to Sync with your admin account and navigate to Meeting rooms &gt; Settings from the left side menu.<br></p><figure data-align="center" data-size="best-fit" data-id="KlaYe677Avkn8NVDUBr1n" data-version="v2" data-type="image"><img data-id="KlaYe677Avkn8NVDUBr1n" src="https://tribe-s3-production.imgix.net/KlaYe677Avkn8NVDUBr1n?auto=compress,format"></figure></li><li><p>In Settings, select the group that has your RoomMates running Logitech View you wish to display a custom logo on from the left side hierarchy.<br></p><figure data-align="center" data-size="best-fit" data-id="LquzVBNnrR0STQ1avGOmf" data-version="v2" data-type="image"><img data-id="LquzVBNnrR0STQ1avGOmf" src="https://tribe-s3-production.imgix.net/LquzVBNnrR0STQ1avGOmf?auto=compress,format"></figure></li><li><p>With your group selected, click "Room Booking settings" at the top of the page.</p><figure data-align="center" data-size="best-fit" data-id="qmeH6PP2o6yHWjqEjw4Yr" data-version="v2" data-type="image"><img data-id="qmeH6PP2o6yHWjqEjw4Yr" src="https://tribe-s3-production.imgix.net/qmeH6PP2o6yHWjqEjw4Yr?auto=compress,format"></figure><p></p></li><li><p>In "Room Booking settings," scroll to the bottom to find the custom logo settings section. Click "Choose image."<br></p><figure data-align="center" data-size="best-fit" data-id="tzBcJzitXuF5QbRpjOGIB" data-version="v2" data-type="image"><img data-id="tzBcJzitXuF5QbRpjOGIB" src="https://tribe-s3-production.imgix.net/tzBcJzitXuF5QbRpjOGIB?auto=compress,format"></figure></li><li><p>A pop-up window will appear, allowing you to upload an image for a custom logo. Select an image from your computer that you would like to use as a Logo on your maps.</p><ol><li><p><strong>Note:</strong> If your organization has previously uploaded custom logos you will be able to choose one from this pop up.<br></p><figure data-align="center" data-size="best-fit" data-id="bfHoYKP7gxKiVe98oFzlR" data-version="v2" data-type="image"><img data-id="bfHoYKP7gxKiVe98oFzlR" src="https://tribe-s3-production.imgix.net/bfHoYKP7gxKiVe98oFzlR?auto=compress,format"></figure></li></ol></li><li><p>After uploading your custom logo you will see that you can now select between the default and custom options.<br><br></p><figure data-align="center" data-size="best-fit" data-id="c6SKiliWpfniwzMcBW2AC" data-version="v2" data-type="image"><img data-id="c6SKiliWpfniwzMcBW2AC" src="https://tribe-s3-production.imgix.net/c6SKiliWpfniwzMcBW2AC?auto=compress,format"></figure><p></p></li><li><p>&nbsp;Now the selected custom logo will be shown on all RoomMates displaying maps through Logitech View in this group.</p></li></ol><h3 class="text-lg" data-toc-id="35ac9b57-32d4-42e8-9165-8d7ffba3fdcd" id="35ac9b57-32d4-42e8-9165-8d7ffba3fdcd">Room Level</h3><ol><li><p>To apply a custom logo to individual maps, log into Sync as an admin and navigate to Meeting rooms &gt; Inventory.</p><figure data-align="center" data-size="best-fit" data-id="11S5rGbCy2F9WIKbyJzeX" data-version="v2" data-type="image"><img data-id="11S5rGbCy2F9WIKbyJzeX" src="https://tribe-s3-production.imgix.net/11S5rGbCy2F9WIKbyJzeX?auto=compress,format"></figure><p></p></li><li><p>Select the room that has the RoomMate running Logitech View where you want to add a custom logo to the map. In the room settings, click "System" under the RoomMate assigned to the room.<br></p><figure data-align="center" data-size="best-fit" data-id="KnpErBBpi13djuSMRodKJ" data-version="v2" data-type="image"><img data-id="KnpErBBpi13djuSMRodKJ" src="https://tribe-s3-production.imgix.net/KnpErBBpi13djuSMRodKJ?auto=compress,format"></figure></li><li><p>Expand the custom logo dropdown to the right.<br>Note: If you don't see this dropdown, ensure that your Tap Scheduler has Logitech Room Booking set as the provider.<br></p><figure data-align="center" data-size="best-fit" data-id="emHS4PSMvkMwNRWDG62Jl" data-version="v2" data-type="image"><img data-id="emHS4PSMvkMwNRWDG62Jl" src="https://tribe-s3-production.imgix.net/emHS4PSMvkMwNRWDG62Jl?auto=compress,format"></figure><p></p></li><li><p>From the "Custom Logo" dropdown, click "Choose image."<br></p><figure data-align="center" data-size="best-fit" data-id="9TrYeKudQw5M8RSXOxHln" data-version="v2" data-type="image"><img data-id="9TrYeKudQw5M8RSXOxHln" src="https://tribe-s3-production.imgix.net/9TrYeKudQw5M8RSXOxHln?auto=compress,format"></figure></li></ol><ol start="6"><li><p>A pop-up window will appear, allowing you to upload a custom log. If you've already uploaded images, you can select from those in the pop up too.<br><br></p><figure data-align="center" data-size="best-fit" data-id="SEBD7vwIWVfgrg5gVpj4v" data-version="v2" data-type="image"><img data-id="SEBD7vwIWVfgrg5gVpj4v" src="https://tribe-s3-production.imgix.net/SEBD7vwIWVfgrg5gVpj4v?auto=compress,format"></figure></li></ol><ol start="7"><li><p>After uploading your custom logo you will see that you can now select between the default and custom options.</p></li></ol><figure data-align="center" data-size="best-fit" data-id="KXPkdZarOd7aoiGqBNKjf" data-version="v2" data-type="image"><img data-id="KXPkdZarOd7aoiGqBNKjf" src="https://tribe-s3-production.imgix.net/KXPkdZarOd7aoiGqBNKjf?auto=compress,format"></figure><ol start="8"><li><p>Now the selected custom logo will be shown the RoomMates displaying maps through Logitech View in this room.</p></li></ol><p><br></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Prompt Builder: A Valuable Productivity Feature Worth Bringing Back]]></title>
            <description><![CDATA[Dear Logitech Product Team,

I would like to share my feedback regarding the removal of AI Prompt Builder from the latest version of Logitech Options+.

After recently restoring access to the feature ...]]></description>
            <link>https://hub.sync.logitech.com/discussions-nw2524il/post/ai-prompt-builder-a-valuable-productivity-feature-worth-bringing-back-fkplbOkOS9BfUdh</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/discussions-nw2524il/post/ai-prompt-builder-a-valuable-productivity-feature-worth-bringing-back-fkplbOkOS9BfUdh</guid>
            <category><![CDATA[Product Updates]]></category>
            <dc:creator><![CDATA[Geo B]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 14:43:40 GMT</pubDate>
            <content:encoded><![CDATA[<p>Dear Logitech Product Team,</p><p>I would like to share my feedback regarding the removal of AI Prompt Builder from the latest version of Logitech Options+.</p><p>After recently restoring access to the feature through an older version of the software, I immediately realized how much I had missed it and how important it had become in my daily workflow.</p><p>As someone who works in a sales role and spends a significant part of the day communicating with customers, writing emails, preparing proposals, and creating professional content, AI Prompt Builder has been an incredibly valuable productivity tool. It has helped me save time, improve the quality of my communication, and work more efficiently throughout the day.</p><p>What I particularly appreciated was the seamless integration within the Logitech ecosystem. Instead of constantly switching between applications, I could access AI assistance directly when needed, making the entire process faster and more intuitive. Over time, this became a natural part of my workflow and contributed significantly to my productivity.</p><p>Since AI is becoming increasingly important in professional environments, I believe features such as AI Prompt Builder are more relevant today than ever before. For me personally, it is not a feature that is occasionally used; it is a tool that genuinely helps me perform better in my job on a daily basis.</p><p>I was therefore disappointed to learn that it is no longer included in the latest version of Options+. While I understand that product decisions involve many considerations, I sincerely hope Logitech will reconsider this decision. AI Prompt Builder is one of the most practical and impactful features I have used within the Logitech software ecosystem, and its return would be greatly appreciated.</p><p>Thank you for taking the time to review my feedback and for considering the perspective of users who have integrated this feature into their daily professional lives.</p><p>Kind regards,</p><p>George</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to update a Windows driver]]></title>
            <description><![CDATA[If you are experiencing any of the following issues:

 * I can only hear audio output in call mode.

 * I can only hear audio output in music mode.

 * Bluetooth pairing and connection time takes too long.

 * Bluetooth ...]]></description>
            <link>https://hub.sync.logitech.com/zone-wireless-2-es-for-business-zjior0nv/post/how-to-update-a-windows-driver-yka2kmOOlmXGIwE</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/zone-wireless-2-es-for-business-zjior0nv/post/how-to-update-a-windows-driver-yka2kmOOlmXGIwE</guid>
            <dc:creator><![CDATA[Rebecca E]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 17:26:21 GMT</pubDate>
            <content:encoded><![CDATA[<p>If you are experiencing any of the following issues:</p><ul><li><p>I can only hear audio output in call mode.</p></li><li><p>I can only hear audio output in music mode.</p></li><li><p>Bluetooth pairing and connection time takes too long.</p></li><li><p>Bluetooth pairing fails every time.</p></li><li><p>Bluetooth connection randomly drops.</p><p></p></li></ul><p>Please follow all steps listed below to update your Windows driver:</p><div data-type="table-of-content"></div><h2 class="text-xl" data-toc-id="6fd0d22a-2281-4745-a695-2f958ffcd90f" id="6fd0d22a-2281-4745-a695-2f958ffcd90f">ISST Driver Installation</h2><ol><li><p>Press <strong>Win + X</strong> and open <strong>Device Manager</strong>.</p></li><li><p>Expand the System devices category.</p></li></ol><figure data-align="center" data-size="best-fit" data-id="5uO6Wt5AOrue8lWudbx7P" data-version="v2" data-type="image"><img data-id="5uO6Wt5AOrue8lWudbx7P" src="https://tribe-s3-production.imgix.net/5uO6Wt5AOrue8lWudbx7P?auto=compress,format"></figure><ol start="3"><li><p>Look for <strong>Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller</strong>.</p></li><li><p>Look for <strong>Intel(R) Smart Sound Technology (Intel(R) SST) OED</strong>” or <strong>BUS.</strong></p></li><li><p>Right-click each one, select <strong>Update driver</strong>.</p></li></ol><figure data-align="center" data-size="best-fit" data-id="2EzT9mG2wgjP0CIzPjR1e" data-version="v2" data-type="image"><img data-id="2EzT9mG2wgjP0CIzPjR1e" src="https://tribe-s3-production.imgix.net/2EzT9mG2wgjP0CIzPjR1e?auto=compress,format"></figure><ol start="6"><li><p>Select <strong>Browse my computer for drivers</strong>.</p></li></ol><figure data-align="left" data-size="best-fit" data-id="EwMskKzby9V8fso9DI1E8" data-version="v2" data-type="image"><img data-id="EwMskKzby9V8fso9DI1E8" src="https://tribe-s3-production.imgix.net/EwMskKzby9V8fso9DI1E8?auto=compress,format"></figure><ol start="7"><li><p>Select <strong>Let me pick from a list of available drivers on my computer</strong>.</p></li></ol><figure data-align="left" data-size="best-fit" data-id="mDLTeDYbXJyxyftvBLvHv" data-version="v2" data-type="image"><img data-id="mDLTeDYbXJyxyftvBLvHv" src="https://tribe-s3-production.imgix.net/mDLTeDYbXJyxyftvBLvHv?auto=compress,format"></figure><ol start="8"><li><p>Choose older one name contained:</p><figure data-align="left" data-size="best-fit" data-id="tYkGNjixkQRjUNnrxPLGD" data-version="v2" data-type="image"><img data-id="tYkGNjixkQRjUNnrxPLGD" src="https://tribe-s3-production.imgix.net/tYkGNjixkQRjUNnrxPLGD?auto=compress,format"></figure></li></ol><figure data-align="left" data-size="best-fit" data-id="LQoBXW03hfpBQ9sWWq3Zi" data-version="v2" data-type="image"><img data-id="LQoBXW03hfpBQ9sWWq3Zi" src="https://tribe-s3-production.imgix.net/LQoBXW03hfpBQ9sWWq3Zi?auto=compress,format"></figure><p></p><h2 class="text-xl" data-toc-id="c8037e60-af79-436d-91d6-c50a81af78ab" id="c8037e60-af79-436d-91d6-c50a81af78ab">Bluetooth Driver Reinstall</h2><ol><li><p>Press <strong>Win + X</strong> and open <strong>Device Manager</strong>.</p></li><li><p>Expand the Bluetooth category.</p></li><li><p>Selecting <strong>Intel(R) Wireless Bluetooth(R)</strong>.</p></li></ol><figure data-align="left" data-size="best-fit" data-id="Hhj8uPZSZiTNT25ajVbuy" data-version="v2" data-type="image"><img data-id="Hhj8uPZSZiTNT25ajVbuy" src="https://tribe-s3-production.imgix.net/Hhj8uPZSZiTNT25ajVbuy?auto=compress,format"></figure><figure data-align="center" data-size="best-fit" data-id="z8wWf7aaFnafREfoJMLkB" data-version="v2" data-type="image"><img data-id="z8wWf7aaFnafREfoJMLkB" src="https://tribe-s3-production.imgix.net/z8wWf7aaFnafREfoJMLkB?auto=compress,format"></figure><p></p><ol start="4"><li><p>Right-click each one, select <strong>Update driver</strong>.</p></li></ol><figure data-align="center" data-size="best-fit" data-id="B10KEsJtjGAQNZ51Qz7H9" data-version="v2" data-type="image"><img data-id="B10KEsJtjGAQNZ51Qz7H9" src="https://tribe-s3-production.imgix.net/B10KEsJtjGAQNZ51Qz7H9?auto=compress,format"></figure><p></p><ol start="5"><li><p>Select <strong>Browse my computer for drivers</strong>.</p></li><li><p>Select“<strong>Let me pick from a list of available drivers on my computer</strong>.</p></li><li><p>Choose older one name contained:</p></li></ol><figure data-align="left" data-size="best-fit" data-id="Sjb3ZaOPSNPC7Qk7LfQ6M" data-version="v2" data-type="image"><img data-id="Sjb3ZaOPSNPC7Qk7LfQ6M" src="https://tribe-s3-production.imgix.net/Sjb3ZaOPSNPC7Qk7LfQ6M?auto=compress,format"></figure><p></p><figure data-align="left" data-size="best-fit" data-id="PFhdRUQwnGK2sxgzoSgwy" data-version="v2" data-type="image"><img data-id="PFhdRUQwnGK2sxgzoSgwy" src="https://tribe-s3-production.imgix.net/PFhdRUQwnGK2sxgzoSgwy?auto=compress,format"></figure><h2 class="text-xl" data-toc-id="cde96e5c-ddc5-4cbf-98ce-ce48aa4dfc25" id="cde96e5c-ddc5-4cbf-98ce-ce48aa4dfc25">Audio Device Driver Uninstall</h2><ol><li><p>Go to the Bluetooth page.</p></li><li><p>Uninstall both <strong>Logi Zone Wireless 2 ES B2B</strong> and <strong>Logi Zone Wireless 2 ES B2B Avrcp Transport</strong>.</p></li></ol><figure data-align="left" data-size="best-fit" data-id="86zbkbx4AHujLNsp65wLV" data-version="v2" data-type="image"><img data-id="86zbkbx4AHujLNsp65wLV" src="https://tribe-s3-production.imgix.net/86zbkbx4AHujLNsp65wLV?auto=compress,format"></figure><figure data-align="center" data-size="best-fit" data-id="ADSGIEWVegiwmTp1L88DP" data-version="v2" data-type="image"><img data-id="ADSGIEWVegiwmTp1L88DP" src="https://tribe-s3-production.imgix.net/ADSGIEWVegiwmTp1L88DP?auto=compress,format"></figure><ol start="3"><li><p>Go to the<strong> System Devices</strong> page:</p></li></ol><figure data-align="left" data-size="best-fit" data-id="ODqVctm07KsNhqrCeVK4E" data-version="v2" data-type="image"><img data-id="ODqVctm07KsNhqrCeVK4E" src="https://tribe-s3-production.imgix.net/ODqVctm07KsNhqrCeVK4E?auto=compress,format"></figure><ol start="4"><li><p>Uninstall&nbsp; <strong>Logi Zone Wireless 2 ES B2B Hands-Free AG</strong>.</p></li></ol><figure data-align="center" data-size="best-fit" data-id="B3mQlHc1Dv8sPv8jqsrSt" data-version="v2" data-type="image"><img data-id="B3mQlHc1Dv8sPv8jqsrSt" src="https://tribe-s3-production.imgix.net/B3mQlHc1Dv8sPv8jqsrSt?auto=compress,format"></figure><h2 class="text-xl" data-toc-id="81fa39c9-6317-416b-947a-f7f6b77683a5" id="81fa39c9-6317-416b-947a-f7f6b77683a5">Final steps</h2><ol><li><p>Perform a factory reset on the headset by <strong>long-pressing the Volume Up button</strong> while <strong>sliding the Power button to the pairing position for 5 seconds</strong>. The reset is successful when the light indicator flashes red and white three times and then turns off.</p></li><li><p>Reboot the computer, pair and use again.<br><br></p></li></ol>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CollabOS devices running Google Meet on Android may experience intermittent freezes during meetings]]></title>
            <description><![CDATA[ * Products Affected: Rally Bar, Rally Bar Mini, Rally Bar Huddle

 * Conditions: Users may experience an audio/video freeze intermittently during a meeting.

 * Workaround: Reboot the device to recover from the ...]]></description>
            <link>https://hub.sync.logitech.com/known-issues-qv6ei1fr/post/collabos-devices-running-google-meet-on-android-may-experience-r03Dd4dZ2sfYD4L</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/known-issues-qv6ei1fr/post/collabos-devices-running-google-meet-on-android-may-experience-r03Dd4dZ2sfYD4L</guid>
            <category><![CDATA[Google Meet]]></category>
            <category><![CDATA[Google Meet on Android]]></category>
            <category><![CDATA[Rally Bar Huddle]]></category>
            <category><![CDATA[Rally Bar/Rally Bar Mini]]></category>
            <dc:creator><![CDATA[Vyomika L]]></dc:creator>
            <pubDate>Thu, 18 Jun 2026 16:46:51 GMT</pubDate>
            <content:encoded><![CDATA[<ul><li><p><strong>Products Affected</strong>: Rally Bar, Rally Bar Mini, Rally Bar Huddle</p></li><li><p><strong>Conditions</strong>: Users may experience an audio/video freeze intermittently during a meeting.</p></li><li><p><strong>Workaround</strong>: Reboot the device to recover from the frozen state.</p></li><li><p><strong>Resolution Progress</strong>: Google and Logitech are actively working to resolve this issue.</p></li><li><p><strong>Issue Number</strong>: 1938</p></li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spotlight 2 - Setup Guide]]></title>
            <description><![CDATA[Below is a quick setup guide to assist you with setting up and using your Spotlight 2.

]]></description>
            <link>https://hub.sync.logitech.com/blank-25t1yyt1/post/spotlight-2---setup-guide-c8eq9wVyfwDECgr</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/blank-25t1yyt1/post/spotlight-2---setup-guide-c8eq9wVyfwDECgr</guid>
            <dc:creator><![CDATA[Gunnar H]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 18:07:28 GMT</pubDate>
            <content:encoded><![CDATA[<p>Below is a quick setup guide to assist you with setting up and using your Spotlight 2.</p><attachment data-id="ltnc1xRZLKAR7UqWAU8Jg" data-type="attachment"></attachment><p> </p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mouse Cursor Movement Troubleshooting]]></title>
            <description><![CDATA[If the cursor isn't following the movements of your mouse, we suggest you:

 * Ensure you are using a mouse pad.

 * Avoid using your mouse on:
   
   * Glass and other see-through surfaces
   
   * Reflective surfaces, such as ...]]></description>
            <link>https://hub.sync.logitech.com/blank-jxeg2y8v/post/mouse-cursor-movement-troubleshooting-TQFI2QU06aTl3Mn</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/blank-jxeg2y8v/post/mouse-cursor-movement-troubleshooting-TQFI2QU06aTl3Mn</guid>
            <category><![CDATA[support-cp-generic-faq]]></category>
            <category><![CDATA[support-cp-generic-faq-mouse]]></category>
            <category><![CDATA[support-pws-troubleshooting-generic]]></category>
            <dc:creator><![CDATA[Gunnar H]]></dc:creator>
            <pubDate>Wed, 17 Jun 2026 17:59:49 GMT</pubDate>
            <content:encoded><![CDATA[<p>If the cursor isn't following the movements of your mouse, we suggest you:</p><ul><li><p>Ensure you are using a mouse pad.</p></li><li><p>Avoid using your mouse on:</p><ul><li><p>Glass and other see-through surfaces</p></li><li><p>Reflective surfaces, such as mirrors and metal desks</p></li><li><p>Wood grains and grooved surfaces</p></li></ul></li><li><p>Try the mouse on a piece of white paper to make sure it isn't a tracking issue on the particular surface you're using</p></li></ul>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MK880 Combo - Setup Guide]]></title>
            <description><![CDATA[Below is a quick setup guide to assist you with setting up and using your MK880 Combo.


MULTILINGUAL


JAPANESE

]]></description>
            <link>https://hub.sync.logitech.com/blank-55rff6kb/post/mk880-combo---setup-guide-nZADTPZegy3f4kj</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/blank-55rff6kb/post/mk880-combo---setup-guide-nZADTPZegy3f4kj</guid>
            <dc:creator><![CDATA[Gunnar H]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 17:55:00 GMT</pubDate>
            <content:encoded><![CDATA[<p>Below is a quick setup guide to assist you with setting up and using your MK880 Combo.</p><h2 class="text-xl" data-toc-id="9fa4d9b2-ebee-4dec-a321-a6bf87faed86" id="9fa4d9b2-ebee-4dec-a321-a6bf87faed86">Multilingual</h2><attachment data-id="2HDysmtzazN0OleaOgMSE" data-type="attachment"></attachment><h2 class="text-xl" data-toc-id="39ca433d-010c-404d-84da-214dfa0b949f" id="39ca433d-010c-404d-84da-214dfa0b949f"> Japanese</h2><attachment data-id="aGj1FVcWrpfv8zswIjkpj" data-type="attachment"></attachment><p> </p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Real-World Range test of LoRaWAN Gateway and Spot Sensors]]></title>
            <description><![CDATA[Logitech Spot can be deployed using BLE in spaces with Logitech CollabOS devices or through Logitech LoRaWAN Gateway. This gateway uses LoRaWan, which is an industry recognized standard for IoT ...]]></description>
            <link>https://hub.sync.logitech.com/logitech-spot-vlqrjobd/post/the-real-world-range-test-of-lorawan-gateway-and-spot-sensors-5A42Uq40RfbK3zz</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/logitech-spot-vlqrjobd/post/the-real-world-range-test-of-lorawan-gateway-and-spot-sensors-5A42Uq40RfbK3zz</guid>
            <category><![CDATA[Logitech Spot]]></category>
            <dc:creator><![CDATA[Reed A]]></dc:creator>
            <pubDate>Fri, 12 Jun 2026 19:40:17 GMT</pubDate>
            <content:encoded><![CDATA[<p>Logitech Spot can be deployed using BLE in spaces with Logitech CollabOS devices or through Logitech LoRaWAN Gateway. This gateway uses LoRaWan, which is an industry recognized standard for IoT devices to send data over long distances while using very little power. In practice, effective range depends heavily on building structure, floor separation, and obstructions.</p><p>This article summarizes measured range and performance across three test environments using one gateway and multiple Spots.</p><h3 class="text-lg" data-toc-id="f3780763-83cf-463e-b76c-f7e2b1f7551c" id="f3780763-83cf-463e-b76c-f7e2b1f7551c"><strong>Test environments (3 locations)</strong></h3><p><em>Range can vary by region due to LoRaWAN regulatory differences.</em></p><ul><li><p><strong>Taiwan (office, multi-floor): </strong>Indoor enterprise office testing for same-floor range and floor-to-floor attenuation.</p></li><li><p><strong>US (open space with obstructions): </strong>Open-space test with three large building blocks between gateway and test points.</p></li><li><p><strong>EU (open space):</strong> Open-space test focused the ability for Spot to connect over longer distances.</p></li></ul><h3 class="text-lg" data-toc-id="4fdc24fb-69f4-4c2e-abf6-c37d05fb7805" id="4fdc24fb-69f4-4c2e-abf6-c37d05fb7805"><strong>Summary of Key Results</strong></h3><table style="width: 793px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 226px"><col style="width: 307px"><col style="width: 260px"></colgroup><tbody><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Environment</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Scenario</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Performance</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Taiwan Office (Same floor)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Same floor, typical office walls: 65 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Stable connectivity; acceptable for production</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Taiwan Office (1 floor apart)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot installed on floor 4, Gateway floor 5. Estimated distance apart: 65 m</p><p></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Stable, but may see reduced signal strength.</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Taiwan Office (2 floors apart)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot installed on floor 4 and Gateway installed on floor 2. Estimated distance: 65 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Beyond 65 m we found degradation; Saw connection issues that limit the use.</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Poland (Open floor plan)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot installed on the same floor as the Gateway with a clear line of sight between them. Estimated distance: 200M</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Stable; beyond 400m found that the signal was not stable.</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>San Jose, CA (Open floor plan)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot installed in one building and the Gateway installed 2 buildings away. Estimated distance: 500m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Stable, but it took Spot a bit longer to show up in Sync.</p></td></tr></tbody></table><h2 class="text-xl" data-toc-id="73b037a6-cf38-4a2f-aed3-1a2338ed2c08" id="73b037a6-cf38-4a2f-aed3-1a2338ed2c08"><strong>Office Multi-Floor Test Setup (Taiwan)</strong></h2><p>A single LoRaWAN gateway was installed on the 1st floor of a modern office building. Spots were placed at varying distances and floor levels.</p><ul><li><p>Gateway and Spot set up on the same floor: ~10 m, 50 m, 55 m, and 65 m line-of-sight on the 1st floor.</p></li><li><p>Gateway and Spot set up on different floors: ~65 m distance to the 1st, 2nd, and 3rd floors.</p></li><li><p>Building structure: open-plan areas, meeting rooms, glass partitions, and mixed wall density.</p></li><li><p>Gateway was provisioned in Logitech Sync per the standard setup guide.</p></li><li><p>Spots were placed in designated locations, then set up and connected to the LoRaWAN gateway.<br></p><figure data-align="center" data-size="best-fit" data-id="PU1ljgryva1E7Y6zSDpfn" data-version="v2" data-type="image"><img data-id="PU1ljgryva1E7Y6zSDpfn" src="https://tribe-s3-production.imgix.net/PU1ljgryva1E7Y6zSDpfn?auto=compress,format"></figure></li></ul><h2 class="text-xl" data-toc-id="98f27a41-505a-44be-a764-1ece3ae475b5" id="98f27a41-505a-44be-a764-1ece3ae475b5"><strong>What We Observed (Office)</strong></h2><ul><li><p><strong>~65 m, Gateway and Spot on the same floor:</strong> Stable connectivity, reliable telemetry.</p></li><li><p><strong>~65 m, Gateway on 1st floor Spot on the 2nd floor:</strong> Still functional, but with lower signal margin and higher sensitivity to obstructions.</p></li><li><p><strong>~65 m, Gateway on 1st floor Spot on the 3rd floor:</strong> Major degradation; noticeable data loss and reliability not acceptable for production.</p></li></ul><p>These results support the expected behavior of LoRa in office buildings: dense materials and concrete floors significantly attenuate signal, and multi-story deployments typically need one gateway per floor for consistent coverage.</p><h3 class="text-lg" data-toc-id="f30328b9-c048-43c8-944a-50316269f1c4" id="f30328b9-c048-43c8-944a-50316269f1c4"><strong>Office Result Snapshot</strong></h3><table style="width: 660px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 182px"><col style="width: 173px"><col style="width: 305px"></colgroup><tbody><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Floor</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Distance</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Result</strong></p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway and Spot on the 1st floor</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>~65 m (same floor)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Stable</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway on the 1st floor and Spot on the 2nd floor</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>~65 m (1 floor up)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Functional with reduced signal strength</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway on the 1st floor and Spot on the 3rd floor</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>~65 m (2 floors up)</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Major loss in signal strength</p></td></tr></tbody></table><p><em>Range can vary by region due to LoRaWAN regulatory differences.</em></p><h2 class="text-xl" data-toc-id="60a4c980-f4c2-4c0f-9365-917b53077681" id="60a4c980-f4c2-4c0f-9365-917b53077681"><strong>Open-Space Results</strong></h2><h3 class="text-lg" data-toc-id="b900d16a-5efc-413c-97f5-316f40775737" id="b900d16a-5efc-413c-97f5-316f40775737"><strong>EU Open-Space Test</strong></h3><p>This test measured Spot’s ability to connect to a Gateway at longer distances in a low-obstruction environment.</p><figure data-align="center" data-size="best-fit" data-id="bZa0j1J4FDqpuOlKCpx5r" data-version="v2" data-type="image"><img data-id="bZa0j1J4FDqpuOlKCpx5r" src="https://tribe-s3-production.imgix.net/bZa0j1J4FDqpuOlKCpx5r?auto=compress,format"></figure><p></p><table style="width: 589px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 168px"><col style="width: 121px"><col style="width: 300px"></colgroup><tbody><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Distance between Gateway and Spot</strong></p><p></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Gateway Connection</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Observation</strong></p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>200 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Successful</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Connected quickly (~1 minute)</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>400 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Failed</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Unable to connect to LoRaWAN Gateway</p></td></tr></tbody></table><p><em>Range can vary by region due to LoRaWAN regulatory differences.</em></p><h3 class="text-lg" data-toc-id="128baf39-1e9a-4b4b-8809-a1f49bdee34f" id="128baf39-1e9a-4b4b-8809-a1f49bdee34f"><strong>US Open-Space Test (with Obstructions)</strong></h3><p>This test measured Spot’s ability to connect to a Gateway&nbsp; in the US region with three large building obstructions between gateway and device locations.</p><figure data-align="center" data-size="best-fit" data-id="HRssGA57gVfbQMYXJ2zOp" data-version="v2" data-type="image"><img data-id="HRssGA57gVfbQMYXJ2zOp" src="https://tribe-s3-production.imgix.net/HRssGA57gVfbQMYXJ2zOp?auto=compress,format"></figure><ul><li><p>Test distances: 200 m, 400 m, 500 m</p></li></ul><table style="width: 699px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 169px"><col style="width: 120px"><col style="width: 410px"></colgroup><tbody><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Distance between Gateway and Spot</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Gateway Connection</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Observation</strong></p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>200 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Successful</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Connected quickly (~1 minute)</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>400 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Successful</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Connection time increased (~2-3 minutes)</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>500 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Successful</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Connection took more than 5 minutes</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Beyond 500 m</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Failed</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Unable to connect to the LoRaWAN Gateway</p></td></tr></tbody></table><p><em>Range can vary by region due to LoRaWAN regulatory differences.</em></p><h2 class="text-xl" data-toc-id="ecca8c4c-3ec0-4a2d-b781-10ac284b7971" id="ecca8c4c-3ec0-4a2d-b781-10ac284b7971"><strong>Gateway Placement Guidance</strong></h2><p>To match or improve test outcomes:</p><ul><li><p>Place the gateway as centrally as possible on the target floor</p></li><li><p>Mount high (near ceiling), keep antenna vertical</p></li><li><p>Avoid placement near metal racks, HVAC ducts, or elevators</p></li><li><p>For multi-story buildings, plan <strong>one gateway per floor</strong> rather than relying on vertical penetration</p></li><li><p>In Sync (System &gt; Gateways &gt; Add Gateway), confirm status is <strong>Operational</strong> before placing Spots</p></li><li><p>Set up each Spot in the location where it will be used, since placement affects signal strength.</p></li></ul><p><strong>Example:</strong> In this test, a centrally located gateway on the 1st floor reliably served Spots up to ~65 m on the same floor. Devices two floors above at similar horizontal distance showed unacceptable degradation.</p><h2 class="text-xl" data-toc-id="cdf9c6bb-47f2-4bd4-b7a3-d4a527ab73a1" id="cdf9c6bb-47f2-4bd4-b7a3-d4a527ab73a1"><strong>Spot Placement Guidance</strong></h2><ul><li><p>Install Spots at <strong>1.2–1.8 m</strong> height for sensing accuracy and RF performance.</p></li><li><p>Set up each Spot in the location where it will be used, since placement affects signal strength.&nbsp;</p></li><li><p>Use LoRaWAN in areas where pairing to a CollabOS device is not feasible.</p></li><li><p>In large offices, plan by coverage cells: add gateways where Spots sit behind multiple dense walls</p></li><li><p>Treat two-floor separation as a design warning; place a gateway on that floor</p></li></ul><h2 class="text-xl" data-toc-id="e901ab84-af7c-4133-a203-73465b326b59" id="e901ab84-af7c-4133-a203-73465b326b59"><strong>Recommended Office Design Rules</strong></h2><table style="width: 912px" class="border-collapse m-0 table-fixed"><colgroup><col style="width: 254px"><col style="width: 344px"><col style="width: 314px"></colgroup><tbody><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Situation</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Planning Guideline</strong></p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p><strong>Recommendation</strong></p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway and Spot installed on the same office floor.</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Optimal distance is ~65m or less.</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot connects to the Gateway with good signal strength</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway on floor 1 and Spot on floor 2, single floor of separation.</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Optimal distance is ~65m or less</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Spot connects to the Gateway with lower signal strength</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway on floor 1 and Spot on floor 2, two floors of separation.</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Major loss in signal strength and would recommend installing a Gateway closer to Spot</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Major signal strength decrease, would recommend installing a Gateway closer to the Spot.</p></td></tr><tr class="isolation-auto"><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Gateway and Spot separated by more than 2 floors or concrete infrastructure.&nbsp;</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Major loss in signal strength</p></td><td class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0" rowspan="1" colspan="1"><p>Major loss in signal strength, recommend installing a Gateway closer to Spot centrally located on each floor.</p></td></tr></tbody></table><p>These findings are practical planning inputs, not absolute limits. Actual performance will vary based on materials, layout, and RF interference. <em>Range can vary by region due to LoRaWAN regulatory differences.</em></p><p><br></p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ability to "move" a Rally Bar between rooms in Sync]]></title>
            <description><![CDATA[It's kind of silly that you can move a Tap scheduler(which is usually bolted to the wall) between rooms in Logitech Sync, but you can't move a Rally bar. I've really enjoyed using Sync for device ...]]></description>
            <link>https://hub.sync.logitech.com/discussions-nw2524il/post/ability-to-move-a-rally-bar-between-rooms-in-sync-kOkTRn1GvHxKhlj</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/discussions-nw2524il/post/ability-to-move-a-rally-bar-between-rooms-in-sync-kOkTRn1GvHxKhlj</guid>
            <category><![CDATA[RallyBar]]></category>
            <category><![CDATA[Rally Bar Huddle]]></category>
            <category><![CDATA[Rally Bar Mini]]></category>
            <category><![CDATA[Sync]]></category>
            <dc:creator><![CDATA[Chris R]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 18:23:20 GMT</pubDate>
            <content:encoded><![CDATA[<p>It's kind of silly that you can move a Tap scheduler(which is usually bolted to the wall) between rooms in Logitech Sync, but you can't move a Rally bar. I've really enjoyed using Sync for device management because its functionality&nbsp;is generally very intuitive, however, this part feels broken, even if there is some intentionality behind it. </p><p>I've been given the guidance to "just rename the room" since I can't move the rally bar, but if I've entered the dimensions and all the other information for a physical room because I have it paired with a Spot, it requires a lot more effort to make sure everything is ported over than if the device could simply be moved between rooms in Sync.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logitech Rally Mic Pod 2 Manual]]></title>
            <description><![CDATA[INTRODUCTION

This manual provides important information about wiring, mounting, and using Logitech Rally Mic Pod 2.

Rally Mic Pod 2 provides studio-quality audio pickup for any meeting space with Rally ...]]></description>
            <link>https://hub.sync.logitech.com/blank-cpjcz10h/post/logitech-rally-mic-pod-2-manual-kOEgmTW9lGBIftJ</link>
            <guid isPermaLink="true">https://hub.sync.logitech.com/blank-cpjcz10h/post/logitech-rally-mic-pod-2-manual-kOEgmTW9lGBIftJ</guid>
            <dc:creator><![CDATA[Jeff D]]></dc:creator>
            <pubDate>Thu, 11 Jun 2026 17:15:53 GMT</pubDate>
            <content:encoded><![CDATA[<h2 id="3047c49c-43fb-47f6-91d5-9bc81af91052" data-toc-id="3047c49c-43fb-47f6-91d5-9bc81af91052" class="text-xl">Introduction</h2><p>This manual provides important information about wiring, mounting, and using Logitech Rally Mic Pod 2.</p><p>Rally Mic Pod 2 provides studio-quality audio pickup for any meeting space with Rally Board 65. Cutting-edge audio processing amplifies voices and minimizes background noise, so conversations sound natural and remote listeners feel like they’re in the room.</p><p>If you have additional questions after reviewing this manual, visit our support site at <a href="https://hub.sync.logitech.com/meeting-room-support" rel="noopener noreferrer nofollow" class="text-interactive hover:text-interactive-hovered"><u>https://hub.sync.logitech.com/meeting-room-support</u></a>&nbsp;</p><h2 id="e636fe7f-13a7-47a4-9913-9395d575972c" data-toc-id="e636fe7f-13a7-47a4-9913-9395d575972c" class="text-xl">Compatibility &amp; Number of Mic Pods Supported</h2><p>Rally Mic Pod 2 is compatible with Rally Board 65. It is not compatible with Rally Plus, Rally Bar, or Rally Bar Mini.</p><table class="border-collapse m-0 table-fixed" style="width: 423px"><colgroup><col style="width: 233px"><col style="width: 190px"></colgroup><tbody><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Device</strong></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Maximum Number of Mic Pods Supported</strong></p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Rally Board 65</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>2</p></td></tr></tbody></table><p></p><p>Connect Rally Mic Pod 2 to the “Link” or “EXT” RJ-45 port on Rally Board 65 via Cat cable. The Link port on Rally Board 65 can power two Rally Mic Pod 2s.</p><p><em>Note: Any Rally Board 65 with a serial number starting with 26xx and lower may have an “EXT” port. There is no functional difference based on the port label.</em></p><figure data-type="image" data-version="v2" data-id="GbF6zCJxeNzeFwgFiKzN0" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/GbF6zCJxeNzeFwgFiKzN0?auto=compress,format" data-id="GbF6zCJxeNzeFwgFiKzN0"></figure><p><em>Cable diagram showing the Rally Board 65 ports connected to two mic pods in a daisy-chain configuration.</em></p><h2 id="2c04cb84-7dbf-45a9-94f9-e627c3cbefd7" data-toc-id="2c04cb84-7dbf-45a9-94f9-e627c3cbefd7" class="text-xl">Wiring</h2><p>Rally Mic Pod 2 is compatible with Cat5e and Cat6 SF/UTP cables (or higher).</p><h3 id="9408818c-6ddc-48e0-a959-3c2cc22bb744" data-toc-id="9408818c-6ddc-48e0-a959-3c2cc22bb744" class="text-lg"><strong>Cat5e</strong></h3><p>With Cat5e cables, the maximum cable length between Rally Board 65 and the first Mic Pod 2 is 40 meters. The maximum cable length between two mic pods is 10 meters.</p><h3 id="df5aeca7-d410-4927-8c6d-5a39cb689662" data-toc-id="df5aeca7-d410-4927-8c6d-5a39cb689662" class="text-lg"><strong>Cat6&nbsp;</strong></h3><p>With Cat6 cables, the maximum cable length between Rally Board 65 and the first Mic Pod 2 is 70 meters. The maximum cable length between two mic pods is 10 meters.</p><p>Rally Mic Pod 2 offers a number of cable routing options to suit your installation. In all cases, the Cat cable connecting to Rally Board 65 must connect to the <strong>Link In</strong> jack on the first Rally Mic Pod 2. When daisy-chaining mic pods, connect the Cat cable to the <strong>Link Out </strong>jack on the first mic pod and to the <strong>Link In</strong> jack on the second.</p><p>This image below shows how a Cat cable is wired to a single Rally Mic Pod 2.</p><figure data-type="image" data-version="v2" data-id="8WdnIKrb4gFz90lx3io2I" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/8WdnIKrb4gFz90lx3io2I?auto=compress,format" data-id="8WdnIKrb4gFz90lx3io2I"></figure><p>The following images show 3 different options for wiring a Rally Mic Pod 2 that is daisy-chained to another Rally Mic Pod 2.</p><table class="border-collapse m-0 table-fixed" style="width: 690px"><colgroup><col style="width: 230px"><col style="width: 224px"><col style="width: 236px"></colgroup><tbody><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Option 1</strong></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Option 2</strong></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Option 3</strong></p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><figure data-type="image" data-version="v2" data-id="lgBegNzaU0ZSGCvVeEQ5Y" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/lgBegNzaU0ZSGCvVeEQ5Y?auto=compress,format" data-id="lgBegNzaU0ZSGCvVeEQ5Y"></figure><p></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><figure data-type="image" data-version="v2" data-id="JGcwrxzkdl7GMqlSAkk4W" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/JGcwrxzkdl7GMqlSAkk4W?auto=compress,format" data-id="JGcwrxzkdl7GMqlSAkk4W"></figure><p></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><figure data-type="image" data-version="v2" data-id="1EYaGEvDV7aSpN9xyuDdK" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/1EYaGEvDV7aSpN9xyuDdK?auto=compress,format" data-id="1EYaGEvDV7aSpN9xyuDdK"></figure><p></p></td></tr></tbody></table><p></p><p>In addition, cables can be routed through a grommet hole on the table and held in place using Rally Mic Pod 2 Grommet Mount (see below).</p><h2 id="ace78bc6-cb4e-4f2d-b64a-7a2eea5c15ba" data-toc-id="ace78bc6-cb4e-4f2d-b64a-7a2eea5c15ba" class="text-xl">Mounting&nbsp;</h2><p>Rally Mic Pod 2 can be placed on a table with one or both cables running out the sides. In addition, an optional Rally Mic Pod 2 Grommet Mount is available for more secure mounting. This is a convenient way to route cables through the table and keep Rally Mic Pod 2 in the proper position on the table. The Grommet Mount can also be used to attach Rally Mic Pod 2 to the ceiling.</p><h2 id="03cb3dbf-e30d-43a2-a24c-cce3a767347d" data-toc-id="03cb3dbf-e30d-43a2-a24c-cce3a767347d" class="text-xl">Grommet Mount on a Table</h2><p>Attach the threaded rod to the bottom of Rally Mic Pod 2 using the supplied screws. Pull the cable(s) through a 25 mm (1 in) grommet hole in the table and connect the cable(s) to the mic pod. Route the cable(s) in the slots on the threaded rod, place the mic pod mount through the grommet hole, and tighten it down with the included nut.</p><figure data-type="image" data-version="v2" data-id="WX3BE0NMPrecgroQzHKVE" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/WX3BE0NMPrecgroQzHKVE?auto=compress,format" data-id="WX3BE0NMPrecgroQzHKVE"></figure><p></p><h2 id="3b44c141-4c46-4705-aa23-c4e22bedb525" data-toc-id="3b44c141-4c46-4705-aa23-c4e22bedb525" class="text-xl">Grommet Mount on the Ceiling</h2><p>Attach the threaded rod to the bottom of Rally Mic Pod 2 using the supplied screws. Pull the cable(s) through a 25 mm (1 in) grommet hole in the ceiling and connect the cable(s) to the mic pod. Route the cable(s) in the slots on the threaded rod, place the mic pod mount through the grommet hole, and tighten it down with the included nut.</p><figure data-type="image" data-version="v2" data-id="NvuVXA90S2eMOBATbAeuY" data-size="best-fit" data-align="center"><img src="https://tribe-s3-production.imgix.net/NvuVXA90S2eMOBATbAeuY?auto=compress,format" data-id="NvuVXA90S2eMOBATbAeuY"></figure><p></p><h2 id="f97d2ce2-fb05-4116-bf4c-5bee13052502" data-toc-id="f97d2ce2-fb05-4116-bf4c-5bee13052502" class="text-xl">Using Rally Mic Pod 2</h2><h3 id="eabfde32-3b72-4121-82ce-a01234604180" data-toc-id="eabfde32-3b72-4121-82ce-a01234604180" class="text-lg">Muting the Mic Pod</h3><p>Muting the mic pod can be done by simply pressing the mute icon on the mic pod to toggle mute on and off. When the mic pod is muted, the LED is red.</p><p>Note: When any of the mic pods are muted, <em>all</em> microphones (including the built-in microphones in Rally Board 65) are also muted.</p><h3 id="e7240264-7bf0-4b85-8abd-e934215e9f2b" data-toc-id="e7240264-7bf0-4b85-8abd-e934215e9f2b" class="text-lg">Updating the Firmware for Rally Mic Pod 2</h3><p>When Rally Mic Pod 2 is connected to Rally Board 65, it automatically updates as needed when the host device’s CollabOS software is updated.</p><h3 id="2bdb2760-664f-46b5-a919-b130d26c83f3" data-toc-id="2bdb2760-664f-46b5-a919-b130d26c83f3" class="text-lg">LED Information</h3><p>When Rally Mic Pod 2 is powered on it will go through this LED sequence:</p><ul><li><p>For the first several seconds, the LEDs will be red.</p></li><li><p>Then the LEDs will cycle through several colors as the mic pod finishes powering on: blue, lilac, white, ciano. When the mic pod is powered up, the LEDs will reflect the current call state: no LEDs when not in an active call, white when in an active call, and red if the mics are muted.</p></li></ul><table class="border-collapse m-0 table-fixed" style="width: 416px"><colgroup><col style="width: 181px"><col style="width: 235px"></colgroup><tbody><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>LED Color</strong></p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p><strong>Indication</strong></p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>White</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>In active state</p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Red</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Muted</p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Lilac (pulsing)</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Firmware update in progress</p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Red (pulsing)</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Device error</p></td></tr><tr class="isolation-auto"><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>No color</p></td><td colspan="1" rowspan="1" class="relative border p-2 min-h-6 align-top [&amp;_p]:m-0"><p>Sleep mode</p></td></tr></tbody></table><p><br></p>]]></content:encoded>
        </item>
    </channel>
</rss>