Your devices, at a glance.
See what each connection can control. The commands available to your exact device depend on its model, setup and bridge platform.
These are Eddy control capabilities. Alexa, Google Home and Apple Home each expose their own supported subset. “Mapped commands” means the commands you configure; it does not guarantee every button or two-way state feedback.
| Integration | Type | Supported controls |
|---|---|---|
Global Caché |
IR blaster | Mapped IR commandsPowerPlaybackVolumeInputsChannels Controls depend on the IR codes you add or learn. A sent IR command does not confirm the device’s power or state. Serial and relay models use their own mappings. |
Broadlink |
IR / RF controller | Mapped IR / RF commandsLearned codes Use a compatible hub and reviewed or learned codes. Features depend on the hub and available codes. |
Google Cast / Chromecast |
Media player / speaker | Play / pauseStopVolume + / −MuteSeek Requires a compatible receiver and media session. Power on/off is not a general Cast command; volume and seek depend on the receiver and active media. |
Apple TV |
Streaming player | NavigationSelect / back / homePlayback buttonsApp launch Requires Companion pairing. TV power and speaker volume are not implied; use an appropriate TV, audio or CEC controller for those commands. Platform availability is shown during setup. |
LG webOS |
Smart TV | NavigationPlaybackVolumeMuteInputsChannelsPower Pairing approval is required. Wake support depends on the TV’s network and standby settings; supported commands vary by model. |
Samsung Tizen |
Smart TV | Remote keysNavigationPlayback keysVolume keysApp launch Requires approval and a compatible Tizen TV. Remote key delivery does not guarantee observed state or wake from standby. Check the bridge platform in setup. |
Roku / TCL Roku |
Streaming player / Roku TV | NavigationPlayback keysApp launchText entryTV volume / inputs Volume, power and input keys are for models that provide those TV functions; a Roku streaming stick does not gain TV controls automatically. |
Fire TV |
Streaming player | NavigationPlayback keysRemote keysApp launch Requires the supported ADB setup and on-device approval. TV power and volume depend on the hardware and remote command support. Check the bridge platform in setup. |
Android TV Remote v2 |
TV / streaming player | NavigationRemote keysText entryApp launch Requires PIN pairing with a compatible Remote v2 service. Key support and text entry vary by device and active screen. |
Sony Bravia |
Smart TV | PowerVolumeMuteInputsChannelsPlaybackApp launch Requires supported IP control and authorization. A command is available only when the paired TV exposes it. |
Panasonic |
Smart TV | NavigationPlayback keysVolume keysInput / channel keys Uses the configured Panasonic remote commands. Supported keys and wake behavior depend on the TV model. |
TiVo |
DVR / set-top box | NavigationPlaybackChannel entryChannel + / − Requires network remote control on a compatible TiVo. TV power and audio commands may need a separate controller. |
DIRECTV |
Set-top box | Remote keysNavigationPlaybackChannels Requires a compatible receiver and network control. Available keys depend on the receiver. |
Kodi / LibreELEC / CoreELEC |
Media player | Play / pauseStopNext / previousNavigationVolume Enable the supported JSON-RPC interface. Controls require an available player and the relevant playback capabilities. |
Jellyfin / Emby |
Media server sessions | Play / pauseStopNext / previousSeekVolume / muteNavigationPlay library item Targets a reviewed, controllable client session. Server access alone does not mean every connected app accepts every remote command. |
Plex |
Companion player | Play / pauseStopNext / previousSeekNavigationVolume Requires a compatible Companion client. Commands depend on the selected player’s capabilities and current playback. |
Sonos |
Speaker / speaker group | Play / pauseStopNext / previousVolume / muteReviewed groupingTV input Grouping and playback require a reviewed control profile. TV input is available only on supported home theater products. |
MPD |
Music player | Play / pauseStopNext / previousVolumeSeekQueue selection Uses a compatible MPD server. Queue actions require a current review; volume depends on the server mixer. |
Mopidy |
Music player | Play / pauseStopNext / previousVolume Uses the supported Mopidy HTTP interface and its advertised playback and mixer capabilities. |
VLC |
Bridge-local media player | Play / pauseStopNext / previousVolume Uses an approved local VLC player on a supported bridge platform. It does not control an arbitrary VLC instance anywhere on your network. |
MPV |
Bridge-owned media player | Play / pauseStopNext / previousVolume / muteSeek Uses the player owned by the bridge with a reviewed local media profile. Commands do not accept arbitrary media paths or URLs. |
Snapcast |
Multiroom audio | Client volume / muteGroup muteStream selectionReviewed grouping Controls audio clients and groups. Play and pause belong to the source player, such as MPD or Mopidy. |
HDMI CEC |
Connected HDMI hardware | Mapped CEC commandsPower / standbyNavigationVolume keys Requires compatible CEC hardware and the necessary bridge tools. Commands depend on the HDMI devices and connection. |
REST / HTTP |
Custom network controller | Configured HTTP commands Use the endpoint and command mappings supported by the device. This does not automatically discover features or provide smart home traits. |
A little stuck? We’re here to help.
Email support Tell us about your device and the step you’re on.