Comparing the legacy Eddy Alexa skills
Legacy skill comparison. This page describes the original Eddy Voice Remote custom skill and Eddy Smart Home skill. Skill availability, account requirements, subscription terms and supported commands must be checked in the current Alexa app and Eddy service before setting up a new installation.
The useful starting question is what you want to say and what the equipment can do. A shorter phrase does not automatically give an integration fewer capabilities, and a longer command list does not establish that every device supports those actions.
What the two interaction models mean
Alexa offers pre-built interaction models, including the smart home model, and custom interaction models whose phrases are designed by the skill developer. Smart home commands can refer directly to the configured device. Custom interactions can use a skill invocation and developer-defined requests. The Amazon voice interaction model documentation explains the distinction.
The original Eddy custom skill used Voice Remote as its invocation name. Treat that as a historical setting until it is confirmed in the currently available skill and locale.
Compare the legacy feature split
| Task | Legacy Eddy Voice Remote | Legacy Eddy Smart Home |
|---|---|---|
| Interaction design | Custom skill | Smart home skill |
| Activities and supported playback or volume commands | Listed in the original guide | Listed in the original guide |
| Named buttons and lists of activities channels or rooms | Listed in the original guide | Not listed in the original comparison |
| Voice-triggered IR learning | Listed for compatible learning hardware | Not listed in the original comparison |
The table describes legacy behavior. Current skill availability, supported phrases, controller allowances and subscription terms depend on the service and account you use.
Choose by one supported task
If your goal is routine power or playback control, first check which integration exposes those actions for your device. Test a simple request with the precise accessory name shown in Alexa. If the goal is a particular button or a learning action, confirm that the installed skill and controller explicitly support it.
For a custom skill, use the invocation and sample phrases shown by that skill. For a smart home integration, discover the configured accessory and test its advertised commands. Avoid giving two different integrations the same TV name while evaluating them; otherwise it can be difficult to tell which path answered.
A TV power command, a channel change and opening an app are separate capabilities. Support for one does not establish the others. A copied example phrase cannot add a missing device action.
Check account and local control separately
Where account linking is required, link the Alexa account to the intended Eddy account. That identifies the service account used for the request. It does not pair a new Eddy agent or confirm the TV is reachable. The Amazon account linking documentation describes the account relationship.
Before testing voice, verify one device command directly in Eddy. If that fails, correct the controller configuration or local connection first. If it succeeds but voice fails, review the enabled integration, account link, accessory discovery and phrase.
Keep Matter distinct from a cloud skill
The new Eddy Matter development path can expose configured on/off controls locally through a compatible Alexa Matter controller. It has separate commissioning and hardware-validation requirements and does not provide every custom-skill action. Amazon Matter documentation explains the local Matter route in Alexa.
The current Eddy companion targets on/off rather than complete television control. A Matter accessory named TV therefore does not gain volume, channels or input selection merely from its name. Confirm the supported release and physical behavior before switching a working setup.
Finish with an observable check
Choose one command you need every day, confirm the device responds once, and test it again from the starting state you actually use. After a timeout, inspect the equipment before repeating a toggle or activity. A success response and confirmed power or input state are different forms of evidence.
For the underlying command paths, read How Eddy works with Alexa, remembering that the original illustration shows a legacy route. Check current example phrases in the Alexa app rather than assuming the older list is complete.