Automation, Schedule, or Remote Control Is Offline

“Offline” describes a broken view or communication path; it does not describe the physical safety state of the pool. A pump may keep running from its own schedule when the app cannot connect. A controller may look online while a valve actuator is disconnected or a heater never receives the command.

Troubleshoot controls as a stack, from physical reality upward. Localize the smallest failed layer and avoid broad resets that erase the evidence and configuration needed to recover safely.

Fast decision

1. Physically unsafe or unknown equipment: remain local, keep people clear, use the appropriate emergency or equipment procedure, and do not send remote commands.
2. App only is offline: verify local controller and physical equipment; do not reboot the pool system just because a phone cannot connect.
3. Local panel works but a device is offline: preserve device address, communication and physical state; isolate controller-to-device communication from internet trouble.
4. Schedules run at the wrong time: check controller date, time, time zone, daylight-saving handling, schedule owner, overlaps, manual priority, egg timers, service mode, and the next event.
5. Display says on but equipment is off or wrong: treat it as physical-control, relay, actuator, device, wiring, interlock, or configuration trouble, not a network success.
6. Equipment runs but app says off: preserve the local schedule, manual override, pump keypad, time switch, freeze mode, and stale app state.
7. Recovery would require factory reset, firmware, wiring, load-center access, or account takeover: stop and refer with a configuration backup and exact failure layer.

The control stack

Inspect these layers in order:

Begin at the top of this table only after the physical layer is safe and known. Do not let a cloud icon substitute for field verification.

Preserve the as-found configuration

Before restarting, signing out, changing modes, editing schedules, or toggling circuits, record:

• exact controller, interfaces, app and property selected;
• controller date, time, time zone and displayed air or water temperatures;
• AUTO, SERVICE, TIMEOUT, manual, freeze, maintenance, or other mode;
• active circuits, color or badge meaning, current and next schedule events;
• pump internal schedule and automation command;
• pool and spa valve positions and actuator switches;
• heater source, setpoints, demand and delay;
• salt output, flow and automation relationship;
• cleaner, booster, lights, features, solar, cover and manual overrides;
• full alerts, offline messages, connection icons, firmware displayed, and timestamp;
• local physical state of every affected device;
• recent outage, router change, password change, service visit, firmware action, replacement, account change, or customer command.

Redact screenshots. Never store passwords, passcodes, pairing codes, QR secrets, Wi-Fi names, hardware or network addresses, tokens, personal email addresses, or customer identifiers in public Playbook feedback or notes.

Step 1: verify physical state and consequence

Before pressing any button, confirm what that circuit could do:

• start a dry or damaged pump;
• move pool and spa valves and change water level;
• call a heater without adequate flow;
• power a salt cell, feeder, cleaner or booster;
• open, close, or move a cover;
• energize lights or equipment with suspected electrical damage;
• activate a water feature that changes hydraulic pressure;
• interrupt freeze protection or heater cooldown.

If the circuit name is unverified, it is a hypothesis, not permission to activate it. Observe wiring labels only from outside closed safe enclosures and use prior records or a qualified person to map unknown outputs.

Step 2: identify the schedule owner

A property can contain several independent schedulers:

• mechanical or digital time switch;
• automation schedule;
• pump internal schedule;
• heater, heat pump, salt or cleaner program;
• smart-home integration;
• cloud automation;
• temporary egg timer or manual priority;
• freeze or protection logic.

Record which scheduler is intended to own each action and which can override it. Two valid-looking schedules can fight, duplicate runtime, or leave gaps.

Do not erase one schedule merely because another is newer. Establish the intended architecture, customer authorization, affected dependencies, and rollback first.

Step 3: check mode, time, and overrides

AUTO

AUTO generally permits configured schedules and automation logic, but exact behavior is model-specific. Confirm physical outcomes and the next event.

SERVICE

SERVICE may disable remote commands and schedules while allowing local manual operation. Equipment left on in service mode can remain on or behave differently than the customer expects. Document every manually active circuit.

TIMEOUT or timed service

TIMEOUT can temporarily act like service and then automatically return to AUTO. Record the remaining time, what will change at return, and whether anyone or any open equipment will be exposed when automation resumes.

Manual override and egg timer

A manual on state may last until turned off, until an egg timer expires, or until schedule priority resumes. A manual off may or may not cancel the current schedule. Use the exact controller rules and record the expiration or next transition.

Wrong clock

Check date, time, time zone, daylight-saving configuration, lost backup power, and whether schedules use local clock or cloud time. Do not shift every schedule to compensate for a wrong controller clock; correct the authoritative time through the approved procedure.

Step 4: localize the offline layer

App cannot connect; local panel is normal

Confirm the app is signed into the correct authorized property and that local physical operation is safe. Record app message, time, account role, whether other authorized users are affected, controller cloud indicator, and home internet status available without accessing private network credentials.

Possible categories include stale app session, phone connectivity, authorization, vendor cloud, home internet, router or access point, automation network connection, or account mismatch. Avoid power-cycling pool equipment as the first network test.

Local interface cannot reach the main controller

Record connection indicator, battery or power state, distance or obstruction, controller status, and whether another approved local interface works. Do not open the panel, move antennas or cables, or re-pair devices unless the exact user procedure and authorization permit it.

Controller is online; one equipment device is offline

Compare the automation state with the device's local display and physical behavior. Preserve device identity, address or assignment in the private service record, communication alarm, cable exterior, power state, and recent replacement or configuration.

Do not change addresses or factory-reset the device merely to make it appear. Address conflicts, wiring, communication bus, interface, configuration and device faults require exact-model diagnosis.

Controller itself is blank or unresponsive

Observe only safe external supply indicators and physical equipment. Do not open the load center, touch breakers inside an enclosure, remove a deadfront, probe voltage, or repeatedly cycle protection. Treat every affected circuit as potentially controlled by local schedules or manual states until verified.

Refer controller power, internal electronics, display, wiring and electrical supply to the qualified resource.

Cloud is available, but commands do not produce results

Separate command receipt from physical action. Record whether the circuit indicator changes, a delay appears, a relay or device state changes, an actuator moves, pump speed responds, flow changes, and dependent equipment acts.

The fault can lie in circuit configuration, relay or device communication, actuator, interlock, local override, service mode, physical equipment, or wiring. An accepted app command is not proof of completion.

Reversible user-level tests

Only perform a test when the exact manual describes it, the physical consequence is known, the equipment is safe, customer authorization exists, and rollback is documented.

A useful test changes one layer:

• refresh or reopen the app without changing equipment;
• compare another authorized user or local interface without sharing credentials;
• use a documented controller connection test;
• compare the local controller and physical device state;
• temporarily command one verified safe circuit while standing at the equipment;
• observe the next scheduled transition rather than editing it;
• enter a documented timed service mode for a defined task and allow or command the exact safe exit.

Do not factory-reset, delete the property, transfer account ownership, reconfigure circuits, update or downgrade firmware, remove devices, alter wiring, cancel safety delays, or cycle the entire system without an approved change plan.

Schedule diagnostic patterns

Did not start

Check correct date and day, start time, enabled state, priority, mode, manual-off behavior, egg timer, schedule overlap, pump or device availability, service state, interlock, and which scheduler owns the action. Verify whether the controller attempted the event.

Did not stop

Check manual on, egg timer, don't-stop setting, overlapping schedule, freeze protection, heater cooldown, feature group, pump internal schedule, local device mode, and remote user action. Do not simply cut power if a cooldown or safety function may be active.

Runs at the wrong time

Check clock and zone first, then schedule source, duplicate scheduler, day selection, duration, one-time event, daylight-saving behavior, and recent power or configuration event.

Correct circuit, wrong physical result

Verify circuit mapping, actuator direction and switch, relay assignment, equipment address, pump program, valve delay, and local device control. Stop if the wrong result can drain or overflow a pool or spa, run equipment dry, create heater or sanitizer trouble, or move a cover unsafely.

Works manually, not by schedule

The physical equipment can respond, but schedule ownership, enable state, priority, clock, mode, dependency, or automation logic remains suspect. Manual success does not close the diagnostic.

Account and privacy boundaries

The customer or property entity should remain the permanent owner of the automation account. Your company access should be authorized, revocable and no broader than required.

• Never make a technician's personal email the permanent property owner.
• Never ask a customer to send a password through ordinary service notes.
• Never reuse credentials between properties.
• Never publish screenshots containing property names, addresses, network details, access codes, or personal data.
• Remove temporary access when the task or relationship ends.
• Record access status and owner, not the secret itself.

Account recovery and ownership disputes require verified customer authorization and vendor procedure. Do not take over an account to make troubleshooting faster.

Restore and verify

After an authorized correction:

• restore the intended AUTO or other documented mode;
• remove temporary manual circuits, service states, countdowns and test setpoints;
• verify pump, valve, heater, salt, cleaner, feature, light and cover physical outcomes;
• confirm delays and interlocks remain enabled;
• check controller time and the next scheduled transition;
• observe that transition or establish a specific verification owner and time;
• verify local fallback behavior if remote access remains unavailable;
• remove temporary account access when required;
• document rollback and any unverified dependency.

Do not declare the system fixed from a successful login or one manual command. The intended schedule and dependent equipment must work together.