Learn what an IR blaster does, check emitter placement, and choose device commands that keep an entertainment activity predictable.
Learn how Eddy Bridge connects local entertainment equipment, what its secure cloud connection protects, and how the V2 agent differs from the original Pi image.
Understand the legacy port mapping examples, the limits of source filters, and why an outbound Eddy agent is the preferred connection for new setups.
Follow the original Raspberry Pi image workflow while keeping legacy setup, V2 agent pairing and Matter commissioning clearly separate.
Start Eddy with one supported controller, choose the right local connection, and build an activity from commands you have tested.
Modern routers can restrict incoming traffic by source address and service, but Eddy Agent avoids exposing a home device control port in the first place.
Plan a Watch TV activity that handles an already-on television, a slow receiver, and changes made with the original remote.
Use connection status and command traces to find where control stopped, then choose a sensible next step.
Link the new Eddy agent to your account with a short code, then discover controllers on your home network.
Compare the controls, apps, and equipment behind each connection before choosing a smart home integration.
See how Eddy maps local on and off actions into Matter and what you need before testing a TV with Alexa or Google Home.
A preview of the new Eddy agent for Windows, Mac, Linux and Raspberry Pi and how it connects your entertainment devices without port forwarding.
Use a trial to test your own devices, daily commands, and account settings before choosing an Eddy subscription.
Use one entertainment setup to understand the controller, device, button and activity concepts, with clear checks for legacy scene behavior.
Compare an inbound router exception with the bridge and new agent approach, including availability, source filters and the limits of transport encryption.
Understand what port forwarding exposes, what source filters can and cannot do, and why Eddy’s outbound agent is the preferred new connection path.
Enable supported TiVo network remote control, add the correct box in the legacy Eddy interface, and test navigation before creating activities.
Connect a compatible Global Caché controller to the legacy Eddy Bridge, select the correct output port, and test IR commands before building activities.
Review the earlier Chromecast setup workflow, understand its command limits, and test playback control on your specific receiver and app.
Choose a Raspberry Pi by software compatibility, reliable power, storage, networking, and the control hardware your Eddy setup actually needs.
Use Wake on LAN with the correct interface address, supported power state and local Eddy host, then verify the device is ready for its next command.
Identify your legacy Eddy Bridge version and Raspberry Pi model before using the earlier browser-based firmware update method.
Understand network addresses, TCP, HTTP APIs, Wake on LAN and authorized ADB so you can choose the correct control path for your equipment.
Compare infrared, HDMI-CEC and direct network control using the commands, hardware and feedback your actual equipment supports.
Connect a compatible Broadlink RM controller, learn one IR command, and confirm it works before building Eddy activities.