When a Savant app or remote suddenly stops controlling the house, the fault almost always sits in one of three places: the host processor is offline, the network changed out from under the system, or the app/account layer lost its link to the host. A technician checks those in that order before touching anything else, because each one rules out the next. Many of these faults clear up with a remote session; a few genuinely need someone on site.
What does a technician check first when Savant stops responding?
The first question is whether the Savant host is actually online, since every app, remote, and keypad in the house depends on it. If the host lost power, dropped off the network, or is mid-reboot, nothing downstream will respond no matter how the app looks. After confirming host status, the technician looks at whether anything changed on the network recently — a new router, a new ISP, or updated Wi-Fi credentials are a common trigger, because Savant documentation is explicit that any network change made before the dealer is involved can affect how the system functions (Update My Router or Wi-Fi Credentials). Only after host status and network changes are ruled out does the technician move to the app and account layer — confirming the mobile device is actually connected to the current Wi-Fi network with the correct credentials, since Savant's own guidance notes that the app simply needs the phone or tablet on the right network to reach the system.
What can be fixed remotely versus what needs a visit?
Faults that trace back to the app/account layer or to a device that can be re-provisioned over Wi-Fi are often resolvable without a truck roll. Savant's support documentation walks through self-service steps for exactly this: reconnecting the app once the phone is on the new network, reconfiguring Wi-Fi credentials directly from a Savant X2 remote's Remote Settings menu under Wi-Fi Information, and updating network credentials from a Savant Multistat thermostat's Network menu. Those are real remote-fixable categories, not an exhaustive list — anything deeper, like a host that won't come back online, a processor that needs a firmware rollback, or wiring-level network changes (new router hardware, new ISP, changed subnet), typically needs a technician on site or at least a scheduled remote session with elevated access, because Savant explicitly recommends involving the dealer for any change beyond a simple Wi-Fi password update. Broader industry practice around remote monitoring for control systems reflects the same split: a dashboard can catch a device gone offline and sometimes reboot it automatically, but there is a hard line past which someone has to open the rack (Integration Guide to Remote Monitoring).
What should you have ready before you call?
Before calling for support, it helps to know: what changed recently on the network (new router, new ISP, password reset), whether the app is still connected to the current Wi-Fi, and — if you're not the original owner — whether you have any paperwork identifying who installed and serviced the system. Savant's own guidance for someone who inherits a home with an existing Savant system is to start with the prior dealer if that contact can be found, and only route through Savant's dealer-locator process if the original installer is unreachable (I Purchased a Home with Savant Installed). Having that history ready — or being honest that it doesn't exist — saves real time on the first call, since a support provider resuming service on an unfamiliar system has to reconstruct configuration details that a continuing dealer would already have on file.
How does ongoing support keep an existing Savant system running?
A support provider working an active Savant system without pushing a replacement typically layers two things: remote visibility into whether the host and key devices are online, and a defined escalation path for the faults that visibility alone can't fix. Ask any provider you're considering, including one you haven't worked with before, whether they will service and support an existing Savant platform rather than require a swap to a different control system — that answer should be settled before any truck rolls. Cave Group's Cave Watch program is built around that kind of layered support: managed remote monitoring of installed systems (Cave Watch 24/7), UL-listed central-station alarm monitoring (Cave Watch Central), and live guard video (Deep Sentinel) as separate, stackable services — see the full breakdown on the support page. None of that requires abandoning a working control platform; it means someone is watching for the host going offline, documenting the system as it exists, and resolving straightforward faults remotely before they turn into a dead app on a Saturday morning. If a system has reached a point where repeated faults point to aging hardware rather than configuration drift, that's a separate conversation worth having with whoever is supporting it — not something to assume from a single outage.
Frequently asked questions
Why did my Savant app stop working after I changed my Wi-Fi password?
Savant devices need to be reconnected or reprovisioned whenever Wi-Fi credentials change. The app side is simple — just get the phone back on the correct network — but Savant recommends involving a dealer for anything beyond a basic password update, since changes made without the dealer's involvement can affect how the system performs.
Can I fix a dead Savant remote myself?
Sometimes. A Savant X2 remote has a Wi-Fi Information setting under Remote Settings that lets you reconfigure the network name and password directly from the remote's screen, which resolves the most common cause of a remote that lost its connection after a router change.
What if I don't know who installed my Savant system?
If you can't identify the original dealer — common after a home purchase — Savant's guidance is to use its dealer-locator process to get connected with a new dealer in your area. A new support provider will typically need to survey the existing system before taking it over.
Does a Savant outage mean I need to replace the system?
Not necessarily. Many outages trace back to a host that dropped offline or a network change, both of which are diagnostic and configuration issues rather than hardware failures. Repeated, unexplained faults are worth raising with your support provider as a separate conversation about the hardware's condition.
Is remote monitoring enough to keep a Savant system running, or do I still need on-site visits?
Remote monitoring catches a meaningful share of faults — a device gone offline, a host that needs a restart — but some issues still require someone on site, particularly hardware-level faults or network changes involving new equipment. A support plan that combines both, like Cave Group's support program, covers more of the failure range than either alone.