When people imagine the first remote control, they picture a plastic clicker pointed at a television. The real thing arrived decades earlier, ran on radio waves, and floated. In 1898, at an electrical exhibition in Madison Square Garden, Nikola Tesla steered a small boat across a pool of water using nothing but wireless signals. Spectators were so unprepared for what they were seeing that some assumed it was magic, trained animals hidden in the hull, or Tesla controlling the vessel with his mind. What they were actually watching was the birth of wireless remote control, and arguably the first ancestor of the Internet of Things.
A boat that listened to radio
Tesla's vessel carried a radio receiver, a bank of batteries, and a set of relays wired to its rudder and propeller. From a control box on the edge of the pool, Tesla transmitted radio pulses. The receiver on board interpreted those pulses and triggered the relays, turning the boat, starting and stopping the motor, and even blinking its running lights. There was no human inside and no wire connecting the two. For an audience in 1898, the idea that a machine could receive instructions through empty air and act on them was close to incomprehensible.
The engineering underneath was rigorous. Tesla filed for and received US Patent 613,809, titled "Method of and Apparatus for Controlling Mechanism of Moving Vessels or Vehicles," granted in November 1898. The patent describes a complete command-and-control system, not a stunt.
Teleautomatics: a machine that carries out commands
Tesla did not see this as a toy. He coined the term "teleautomatics" to describe a whole field: machines that carry out commands transmitted to them from a distance, without a physical link. In his own writing he imagined fleets of unmanned vessels and automated devices acting on remote instructions. He was describing, more than a century early, the basic loop that every connected device runs today: receive a signal, decode it, actuate something in the physical world, and report back.
That loop is the heartbeat of modern embedded systems. A smart thermostat receiving a setpoint over Wi-Fi, an agricultural sensor node toggling an irrigation valve over LoRa, a drone responding to a controller, an industrial actuator driven from a cloud dashboard, all of them are direct descendants of a boat in a pool in 1898.
The hard problems were the same then as now
What makes Tesla's demonstration genuinely instructive for engineers is that the problems he wrestled with are the same ones we design around in firmware today. How do you make sure a command actually arrives? How do you keep someone else's signal from hijacking your device? How do you do something useful at the edge when the link is unreliable? Tesla even built in a primitive form of secure channel selection so that stray signals could not commandeer his boat, an early answer to a problem we now call command integrity and authentication.
Every team building connected hardware re-encounters this list. Reliable signaling, safe defaults when a link drops, validating that a command came from the right place, and squeezing real behavior out of a small device far from any operator. The radios are faster and the chips are smaller, but the shape of the work has not changed.
Why it still matters for builders in the Philippines
For students, startups, and engineers building IoT products here, Tesla's boat is a useful reminder that the fundamentals are old and well understood. You do not need exotic technology to build something that feels like magic to the people using it. You need a clear command loop, a dependable link, and careful handling of the cases where things go wrong. A thesis prototype that reliably reads a sensor and actuates a relay over a wireless link is working in exactly the tradition Tesla started.
At Fluidwire we build connected products across that whole stack, from the silicon and firmware on the device up to the cloud services that command it. If you are turning an idea into real hardware, our embedded and IoT services cover the design, firmware, and connectivity work, and you can get in touch with our team to talk through your project.
The next time you tap a button and something across the room or across the country responds, remember the boat. The clicker is new. The idea is 1898.
