Before resetting or reprogramming a Harmony remote, identify its exact model and software family. Some remotes can still be configured through supported tools; affected legacy models can continue sending their existing commands but have lost the service used to change them. Preserving a working setup is the first step.
Check the exact model, not just the Harmony name
Logitech states that its legacy Logitech Harmony Remote Software shut down on May 28, 2025. The affected list includes the Harmony 676 originally associated with this page. Existing settings can still operate, but the listed remotes can no longer be programmed, updated or given new devices through that service. See the explicit retirement notice on Logitech's current Harmony software page.
Swipe the table sideways, or focus it and use the arrow keys.
| Family | Examples | Practical consequence |
|---|---|---|
| Affected legacy software models | 676, 880, 900, 1000 and 1100. | Preserve the current working configuration; the retired service cannot reconfigure them. |
| MyHarmony remotes without a hub | 600, 650, 665 and 700. | Use the exact model's supported desktop-software path and check operating-system compatibility. |
| Hub-based products | Companion, Elite and Smart Control configurations using a Harmony Hub. | Check the hub, app, firmware and paired remote as a system. |
The software page also contains older instructions. Its newer retirement and recovery notices take precedence over a generic paragraph suggesting that any old account can still sync. Do not infer support for a near-matching model number. If the label is unclear, identify it through Logitech support before making configuration changes.
Computer compatibility is a separate question from service availability. Logitech's Harmony and macOS guidance distinguishes hub-based and non-hub products and explains operating-system restrictions. Installing an older application on another computer does not restore a retired online service.
Document the working system before changing it
Download the Harmony system and activity record (TXT). Record the remote and hub models, each controlled device's complete model number, physical input connections and the activities people actually use. Keep account credentials out of the worksheet.
For each activity, write down which devices should be on, which input each should select and which device should receive volume commands. Photograph relevant settings or save screenshots where the supported software permits. This is a readable reconstruction record, not a claim that every remote supports an export that can later be restored.
Avoid changing the TV's input wiring and the remote's activity at the same time. If something fails, you want to know which change caused it. Retain the original device remotes: they help distinguish a device problem from a Harmony command problem and provide a fallback for occasional settings.
An activity can be wrong even when every button works
An activity sends a sequence of power and input commands. In many IR arrangements the remote tracks an expected state rather than receiving confirmation that every command succeeded. A blocked command, a manual input change or a second controller can leave that expectation out of step with reality.
Logitech's Harmony 650 manual (PDF) explains activities and its Help function. Use that model's relevant recovery controls when applicable, but consult current support notices for configuration access; the manual's original web-setup instructions are historical.
- Note the actual power and input state of each device after the failed activity.
- Try the required command individually, using the correct remote or supported device-control screen.
- Check whether a power toggle reverses an already-correct state. A discrete Power On command and a toggle are not equivalent.
- On a reconfigurable model, change only the documented setting implicated by the test, then repeat from a known starting state.
- On an affected legacy model, preserve its settings and consider a documented manual workaround or replacement plan.
If a device misses an input command only during startup, its readiness delay may matter. If a button advances twice, repeats may matter. Diagnose the observed pattern before changing several delays and repeat counts at once.
Distinguish IR, hub connections and HDMI-CEC
Infrared needs an effective path from the transmitting remote, hub or blaster to the device's receiver. A hub can be operating normally while its IR output is blocked inside a cabinet. Confirm which component actually sends the command in your configuration before moving hardware.
A hub does not make every device controllable by Bluetooth or over the network. Supported control methods depend on the target and integration. Test the exact power, input and navigation functions you need; discovering a device is not proof that every command exists.
HDMI-CEC can send power and input changes independently of Harmony. Logitech's HDMI and CEC explanation describes these interactions. To investigate unexpected switching, record the current CEC settings and change one relevant setting for a controlled test. Be aware that some devices couple CEC and audio-return behavior; check sound after a change rather than indiscriminately disabling everything.
Treat syncing and hub recovery as separate faults
A supported USB-configured remote that is not detected may need a working data cable, a different direct USB port or the correct software. A cable that supplies power is not necessarily carrying data. A hub connectivity issue instead involves its power, network connection, firmware and app.
Logitech's sync troubleshooting page contains model-dependent steps. Apply them only after the support-family check above. For hubs, also read the current recovery notice on the software page; older firmware can require a documented recovery route rather than an ordinary automatic update.
Do not use factory reset as a universal first response. Establish the supported recovery path and access to the needed account and tools before discarding a configuration. A new battery or repaired button may restore physical operation without solving a retired configuration service.
Replace the functions you need, not the brand name
Make a short requirements list: controlled device count, IR/Bluetooth/network needs, activity sequences, input selection, volume routing, tactile usability and software or account dependencies. Check whether a television's own remote and CEC can cover a simple setup before adding another control system.
For a more complex system, verify replacement support against exact device models and retain a return option for testing. Cloud-dependent configuration is a lifecycle consideration, even when daily commands work locally. Use the receiver planning guide to document the equipment path and the picture-quality checklist when control works but the expected video format does not.