> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/asset-management/managing-bluetooth-and-peripheral-devices.md).

# Managing Bluetooth and Peripheral Devices

Harmony's asset management capabilities extend to Bluetooth and peripheral devices connected across your environment. This article explains how Harmony identifies and catalogs Bluetooth peripherals, with a focus on Logitech device recognition, and what that means for your inventory accuracy.

### How Harmony Identifies Bluetooth Peripherals

When Harmony discovers devices in your environment, it cross-references hardware identifiers against its device catalog to resolve manufacturer attribution and specific model information. For Bluetooth peripherals, this process relies on device-reported identifiers to match each device to a known model.

Accurate identification at the model level is important because it directly affects:

* **Asset inventory accuracy** - each device appears with the correct name, manufacturer, and model, rather than as an unresolved or generic entry
* **Manufacturer attribution** - devices are credited to the correct vendor, preventing incorrect third-party lookups
* **Asset cataloging** - your inventory reflects a precise picture of the peripherals deployed across your organization

### Logitech Bluetooth Device Recognition

Harmony includes enhanced identification for Logitech Bluetooth peripherals. Rather than relying on generic or third-party lookups, Harmony resolves Logitech devices to their specific models and correctly attributes them to Logitech as the manufacturer.

#### What Is Covered

This recognition covers **65 Logitech Bluetooth devices** across the following categories:

| Category  | Example Devices                           |
| --------- | ----------------------------------------- |
| Mice      | MX Master 3S, M720 Triathlon              |
| Keyboards | MX Keys S                                 |
| Headsets  | Various Logitech Bluetooth headset models |

#### What Changed

Previously, Logitech Bluetooth devices could appear as unresolved entries or be misattributed to an incorrect manufacturer due to third-party lookup fallbacks. Harmony now identifies these devices at the model level directly, which means:

* Logitech peripherals are no longer misattributed to third-party vendors
* Devices that previously showed as unresolved now resolve to a specific Logitech model
* Your asset catalog and inventory reports reflect accurate, model-level detail for Logitech Bluetooth hardware

### Impact on Your Asset Inventory

If your environment includes Logitech Bluetooth peripherals, you may notice the following changes in your asset inventory after this improvement takes effect:

* Devices that were previously unresolved or listed under an incorrect manufacturer now display the correct Logitech model name and manufacturer attribution
* Asset counts and groupings based on manufacturer or model will more accurately reflect your actual hardware
* Reports and dashboards that surface peripheral data will show cleaner, more reliable entries for Logitech devices

No action is required on your part. Harmony applies these identification improvements automatically as part of its asset discovery and cataloging process.

### Supported Device Categories

Harmony's Bluetooth peripheral identification is not limited to Logitech devices. The asset management engine resolves peripherals from a broad range of manufacturers. Logitech-specific improvements are part of ongoing investment in expanding and refining the device catalog to support more accurate inventory management across your environment.

If you have peripherals that appear unresolved or incorrectly attributed in your inventory, contact Harmony support for assistance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.harmony.io/asset-management/managing-bluetooth-and-peripheral-devices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.