Getting Your Head Around the Jandy Aqualink RS4 One-Touch System
The RS4 is one of those pool control panels that looks plenty simple until you actually need to make it do something complicated. It sits on your wall, has a color touchscreen, and runs everything from pumps to heaters to salt cells and lighting. The One-Touch feature is basically a shortcut system where you press one button and it toggles through whatever scenes you configured. Most people think that's all there is to it. It isn't. There isn't an official paper manual that Jandy hands out anymore for the One-Touch stuff specifically. The system documentation is mostly buried in the on-panel menus and the online resources that ProSERVE used to maintain before Jandy folded a bunch of support operations into Pentair. What I'd call the manual is really a combination of the built-in help screens and the configuration guide in the programming menu. If you're looking to download something concrete, the Pentair/Jandy support site has a general RS4 installation sheet, but nothing dedicated to One-Touch as a standalone document. You're working off what's on the panel and your own notes at that point. Here's how One-Touch actually works under the hood. When you program a scene, the RS4 saves a snapshot of every device state: pump speed, heater on or off, lights color and brightness, salt cell output percentage, and so on. When you assign that scene to a One-Touch button, pressing it cycles through a sequence of those snapshots. The "One Touch" part just means the panel handles the toggling logic automatically. You don't pick which scene runs next manually; the panel tracks your current state and jumps to the next one in the cycle. That's the basic mechanic. The frustrating part is figuring out why it sometimes ignores your cycle order entirely.
I spent a whole afternoon debugging a weird issue where the One-Touch sequence would reset back to scene one instead of continuing linearly. The pool was configured with a standard setup: variable speed pump, heat pump, LED lights, and a salt chlorinator. Everything programmed fine initially. Then after a power flicker, the sequence started behaving oddly. The problem turned out to be the auto-return feature being enabled in the system settings. When auto-return is on, the RS4 assumes you want to go back to a "home" scene after any manual override, and it breaks the cycling behavior. I had to go into the System Setup menu, find the Auto Return option, and set it to Off. After that, the One-Touch cycle worked exactly as programmed without jumping around. That setting isn't obvious at all. It's nested three menus deep and labeled pretty generically. Another thing nobody really warns you about is how the RS4 handles conflicts between One-Touch and scheduled automations. If you have a schedule running the pump at 10 RPM and you press a One-Touch button that calls for 2200 RPM, the One-Touch command takes priority immediately. But once that scheduled cycle completes, the pump drops right back to whatever the schedule says. The One-Touch change doesn't lock in permanently unless you also adjust the schedule itself. This bit me more than once when a homeowner would say the One-Touch feature "stopped working" because the pump reverted to low speed the next morning. It wasn't broken. It was just doing exactly what it was programmed to do, and nobody had realized the schedule was overriding the manual input. If you're trying to figure out the programming sequence from scratch, here's the path. Go into the main menu and select Device Programming. From there you'll set up each piece of equipment: assign it to a station, configure runtime defaults, and define speed ranges for variable speed pumps. Once devices are mapped, go to Scene Programming. Create your scenes here, naming each one something descriptive because the panel doesn't enforce any naming convention and you will forget what "Scene 3" actually does within a week. Assign speeds, on/off states, and percentages to each device per scene. Then move to One-Touch Programming, where you assign a scene sequence to each button and set whether it cycles automatically or requires a manual press per transition.
The RS4 interface itself is a strength and a weakness. The touchscreen is responsive enough, but the menu hierarchy isn't intuitive. Things like the auto-return setting I mentioned, the ability to lock the panel from accidental changes, and the way the system handles communication errors between the main board and the IO module are all buried in layers you have to dig through. There's no search function. You either know the path or you spend twenty minutes clicking around. One nuanced detail that's worth knowing: the RS4 uses a polling-based communication protocol to talk to its IO modules. That means the panel periodically checks in with each module rather than the modules pushing updates proactively. Under normal conditions this is fine. But if you've got a long cable run to a remote IO module and you're running it near high-voltage equipment or poorly shielded wiring, you can get comm errors that show up as delayed or missed One-Touch responses. The panel might register the button press but the scene won't execute because the module didn't respond in time. If you're seeing intermittent issues like that, check your communication error log in the diagnostics menu and consider shortening cable runs or adding shielding. It's a common source of "phantom" malfunctions that people blame on the panel itself when the real problem is electrical noise on the data line. For anyone who wants a reference document beyond the on-panel menus, I'd recommend taking screenshots of your own configuration as you set things up. The RS4 doesn't have a built-in export function for your scenes and schedules. There's no way to backup your configuration to a USB drive or cloud account. If the panel ever needs to be replaced or restored to factory settings, you're starting from zero unless you wrote it down somewhere. I keep a notebook next to my work truck with the exact menu paths and values for every RS4 I've installed. It sounds excessive until you're standing in a homeowner's garage at 7 PM trying to remember whether you set the heater to differential mode or fixed setpoint, and you can't access the panel because it's locked behind a security code they don't remember.
The One-Touch feature itself is genuinely useful once it's configured right. It's the kind of thing that makes a pool operation feel smooth for the end user. Press one button and the pump slows down, the heater turns on, and the lights shift to warm white. But the gap between the concept and the actual implementation is wide enough that most installers and homeowners never quite get it dialed in. The programming model assumes you understand device priorities, schedule interactions, and communication topology before you start. The panel doesn't teach you that as you go. It just lets you build whatever you build and then complains when it doesn't work the way you expected. If you need the actual download for anything related to the RS4, your best bet is the Pentair Support website. Search for the RS4 product page and look for the installation and programming guide PDF. It covers the basic setup and menu structure but skips a lot of the operational details like the auto-return behavior and comm error troubleshooting I mentioned. Those details aren't in any official document I've found. They come from experience and the occasional forum post from people who've already gone through the same headaches.
Practical Takeaways
The system works well when you respect its limitations. Don't expect it to be self-documenting. Don't assume One-Touch sequences are permanent unless you verify the schedules aren't overriding them. Don't ignore comm errors even when the panel seems to be responding, because the delays add up and make the whole thing feel sluggish. And definitely take your own notes during configuration. The RS4 won't do it for you.
