Start here
Three facts to collect before you call anyone
Open the Savant app, go to Settings → About, and photograph the screen. Savant documents exactly what lives there, and all three fields matter to whoever picks up the phone.
| Field | What Savant says it is | Why it matters to you |
|---|
| App Version | The currently installed version of the Savant app. | Tells you whether your phone is the problem. A phone that auto-updated past the system is a common mismatch. |
| System Version | The currently active software version on the host managing the Savant Home. | This is your system's real age. It also tells an integrator immediately how much of the modern feature set you can even run. |
| System UID | A unique identifier of the Savant Host, “unique to the physical Savant Host unit,” used by installers for configuration and troubleshooting. | This is the number that identifies your home inside Savant's cloud. Nobody can help you properly without it. |
One trap worth knowing. The same screen offers Upload Diagnostics to Savant, and many owners tap it believing they have opened a support ticket. Savant's own documentation is explicit that uploading diagnostic logs “does not notify or contact Savant Support, and by default will not receive any response.” It puts a log in the cloud for an agent who is not looking. If you need help, you still have to call someone.
Triage
Symptom to likely cause, in one table
Ordered roughly by how often these generate calls in Los Angeles. The right-hand column is the honest answer about who can actually resolve it — some are yours to fix in ten minutes.
| Symptom | Most likely cause | Who fixes it |
|---|
| App spins, then “cannot connect” — and the internet changed recently | New router, new ISP, or a renamed/re-passworded Wi-Fi network. The host and every Savant device are still looking for the old one. | Dealer. Savant states adjustments are needed whenever the router, ISP or Wi-Fi credentials change. |
| Works at home, fails away from home | Local control is fine; the host's path out to Savant's cloud is not. Usually a firewall, content filter, double-NAT after a gateway swap, or an expired subscription. | Dealer, unless the cause is simply that your phone is on a VPN — turn that off and retest first. |
| Whole system dead after a power cut | The host was not shut down cleanly, or it did not come back up in the right order with the network. | Often recoverable remotely. See the host section below before pulling any plugs. |
| Lights and shades work, TV/audio does not (or the reverse) | One service or one piece of gear failed, not the system. Very common after a receiver, TV or streaming-box swap. | Dealer — the replacement device has to be re-added to the configuration. |
| Pro Remote shows “Connecting…” forever | Savant documents this message as the remote being unable to communicate with the host — nearly always a network or Wi-Fi issue, not a broken remote. | Start with the remote's own Wi-Fi settings; dealer if the host is unreachable. |
| Remote is dark or will not charge in its base | Deep-discharged battery or a charging-contact problem. Savant publishes a recovery sequence for both. | You can try both procedures below before ordering anything. |
| One room's touch panel is offline, everything else is fine | That panel's network drop, its PoE port, or the switch it lands on. | Dealer or your network provider — it is a cabling and switch question. |
| Nothing has worked since the original installer stopped answering | Not a fault at all. The system needs a new dealer of record before anyone can make changes. | Dealer. See the takeover section. |
Most common cause
If it broke the week your internet changed, that is the cause
This is the single highest-yield question we ask on the phone, and in Los Angeles it lands constantly — people move between fiber providers, replace a landlord's gateway, or drop a consumer mesh kit on top of an integrated system. Savant's guidance is unusually direct about it: because of the integration between the system and the home's network, the dealer needs to make adjustments whenever you switch internet providers, change the router, or update Wi-Fi credentials, and changes made before involving the dealer may affect how the system works.
There is, however, a narrow case Savant addresses directly. If you have only changed the Wi-Fi password or the network name — no new provider, no new router — Savant says it still strongly recommends contacting your dealer to ensure the best system performance, but that it is possible to provision some devices to the new Wi-Fi yourself:
- The Savant app: nothing to do inside the app. Just connect the phone or tablet to the network using the new credentials.
- Savant X2 Remote: from the main Home screen, swipe right to Settings → Remote Settings → Wi-Fi Information, then choose Configure Wi-Fi to edit the network name and password.
- Savant Multistat thermostats (CLI-W200 / CLI-W210 / CLI-W220): on the thermostat, open the Network menu, select the first Change option, and follow the prompts.
Savant still recommends looping in your dealer even in that narrow case, and we would agree for one practical reason: those three are the only devices with a user-facing Wi-Fi screen. Anything hard-wired, and anything with no display — the host itself, lighting controllers, keypads, matrix switches — has no way for you to hand it new credentials.
The part nobody tells owners
Your Savant host is probably an Apple Mac — and its macOS version matters
Savant's Pro Host has been Mac hardware for a decade, and still is. Savant's deployment guide lists the older SVR-4500, SVR-4500S and SVR-5000S as Mac minis, and the current range spans Mac mini–based Pro Hosts (SVR-5100S through SVR-5400S), Mac Studio hosts (SVR-6300S, SVR-6400S, SVR-6800S, SVR-6900S) and a Mac Pro host (SVR-7300S) — alongside a separate line of Savant-manufactured Linux hosts. So the first thing to establish is which one you have. If yours is one of the Mac models, that anonymous silver box in the rack is a computer, and it inherits every problem a computer has — including the two below.
Do not let it update itself
Savant publishes a supported-macOS matrix per release. In the SavantOS 11.2 column (released April 2026), macOS Ventura and older, Sonoma and Tahoe are all listed Not Supported for Mac hosts, and Sequoia 15.3.x and higher Sequoia point releases is the supported band. A footnote is blunter still: non-SVR-5400S hosts must be updated to macOS Sequoia 15.3 or higher for compatibility with SavantOS 11.0.5 and higher.
Read that carefully, because it cuts both ways. Sonoma was supported on earlier 11.x releases, so a host that was perfectly fine last year can fall out of support with nothing on site having changed. And the Tahoe line is the one that matters most right now: Savant lists macOS Tahoe as not supported for Mac hosts in 11.2, with a note that only Savant-manufactured hosts support it, while Savant's dealer-side tools separately gained Tahoe support. So “my Mac is offering me macOS 26, is that fine?” has a different answer for your host than it does for your laptop.
The practical version: on a Mac host, automatic macOS updates should be off, and version changes get scheduled with whoever maintains the configuration — not fixed at 9pm by clicking “Update Now.”
Never pull the plug
Savant's guidance on power is one line and it is worth taping to the rack: never remove power from the Savant host before shutting it down. Savant recommends a pure sine wave UPS with the ability to shut the host down gracefully before the battery runs out. In a city with rolling outages and PSPS events, that UPS is not a luxury item — it is what stops an outage from corrupting the machine that runs your house.
Hardware
Pro Remote: stuck on “Connecting…”, dark, or refusing to charge
Savant's Pro Remote troubleshooting guide covers the REM-1100, REM-2000 and REM-4000 (Pro Remote X2); the legacy REM-1000 has its own archived document. Three things in it are worth knowing before you assume the remote is dead.
- “Connecting…” is a network message, not a hardware fault. Savant defines it as the remote being unable to communicate with the host, and the instruction is to check network settings and confirm the remote is on the same local network as the host. A remote that says this is usually healthy.
- Will not power on: Savant's sequence for the REM-4000/X2 is to first charge it on a known-good base for at least ten minutes, then press and hold power for 15 seconds, release for 5 seconds, and press and hold again for 3 seconds.
- Will not charge in the base: Savant documents charging the remote directly over USB-C — remove the two Phillips screws holding the charging plate, connect the base's USB-C cable to the port at the bottom of the remote, wait at least ten minutes, then, still connected, hold power for 10 seconds. Savant's last step is the one people skip: reaffix the charging plate and make sure both screws are properly seated before retesting on the base. If it wakes on USB-C but still will not charge in the cradle, you have a contact or base problem rather than a battery problem.
That last one is an integrator-facing procedure from Savant's dealer documentation, and it means opening the remote. If you would rather not, don't — it is a ten-minute job on a service call and it keeps your warranty conversation simple.
Firmware is not something you drive from the remote. Savant's process is host-led: when the da Vinci / SavantOS software on the host is updated, the host scans the network for Savant devices, compares each Pro Remote's firmware against the version packaged with that release, and starts the update automatically if a newer one exists. A remote that will not update is usually a remote that cannot see its host.
Root cause
The network settings that quietly break Savant
Most “intermittent Savant” complaints are a Wi-Fi design problem wearing a costume. Savant sets out its recommended wireless settings in the Pro Remote troubleshooting guide (dated June 2022), and consumer mesh systems ship with the opposite of almost every one of them:
| Setting | What Savant recommends | What consumer gear usually does |
|---|
| SSID naming | A unique SSID. Savant notes that current production Pro Remotes work on both bands but “function best when not provisioned to a network where both bands share the same SSID name.” | One merged SSID across 2.4 and 5 GHz. |
| Band steering | Disabled. | On by default, and not exposed to the user. |
| Fast roaming | Disabled. | On by default in most mesh kits. |
| SSID per access point | In some installations, a unique SSID per access point so devices do not roam between them. | One name everywhere, roaming actively encouraged. |
| Channel selection | Disable automatic channel assignment; set a static channel (often 1, 6 or 11). | Automatic, and it re-picks whenever it likes. |
| Channel width | 20 MHz. | 40 MHz or wider on 2.4 GHz. |
| QoS / traffic shaping | Disabled; topology as flat as possible, especially where there are connectivity problems. | Enabled as a “gaming” or “streaming” feature. |
One honest caveat on that document: it also recommends WPA2 with TKIP/AES set to Auto. That was reasonable in 2022 and it is not advice we will repeat in 2026 — TKIP is a security downgrade, and we would rather solve a Savant roaming problem with SSID and channel design than by weakening the encryption on your house. If an installer tells you the fix is to turn TKIP on, ask what else they tried first.
Two more from Savant's host documentation, and they explain a surprising number of dead systems. First, all Savant devices must be on the same LAN or subnet as the host, because discovery is self-directed — the moment somebody puts the host on one VLAN and the touch panels on another, or provisions a device onto a guest network, discovery stops. Second, the host needs a static IP address or a DHCP reservation so its address survives a power outage; Savant recommends the DHCP reservation approach so every address is managed from one place. After any network change, Savant's own reset step is to unplug the host's Ethernet cable, wait 15 seconds, and plug it back in.
If your network was installed by whoever delivered the internet, this section is usually where the money is — see home network and Wi-Fi design and structured cabling.
The honest constraint
When the missing part is the dealer, not the equipment
Savant is a dealer-programmed platform. The configuration lives in professional software, and Savant's support desk says so directly: it tells homeowners to contact their integrator, and notes that Savant Support's own ability to assist with equipment in the field “is very limited and generally requires a professional integrator or installer on site.” To be eligible for Savant's support channel at all, an integrator must be with a company whose Savant account is in good standing, have at least one person on that account who has completed Savant Core Training, and have completed the Savant Troubleshooting Certification Course.
That is why “my installer disappeared” is a real technical problem rather than an inconvenience. Savant's guidance for anyone who bought a home with a system already in it is to contact the original dealer if the previous owner can identify them, and if not, to ask Savant to connect you with a new dealer in your area.
Adopting someone else's Savant system is most of what we do on the brand. It means establishing what is actually installed, getting the system documented and back under your control, and giving you the credentials and as-built in writing rather than holding them. If that is your situation, the orphaned system takeover page describes how we scope it, and Savant service and repair covers ongoing support.
What to expect
What a Savant service call actually covers
We start on the phone, not in the truck. Tell us what changed and when, send the Settings → About screenshot, and in most cases we can name the layer before anyone is dispatched. On site, a first visit is typically: confirm the host is healthy and shutting down cleanly, verify the network against the requirements above, re-establish device discovery, bring the app and remotes back onto the system, and document what is installed so the next problem takes minutes rather than hours.
What we will not do: quote a system replacement sight unseen, tell you a working system is obsolete in order to sell you a new one, or hold your configuration hostage. If the honest answer is that your system needs a network fixed rather than a Savant fixed, we will say that — and we hold the C-10 electrical licence to do both.
Innov8av holds California C-10 Electrical Contractor licence CSLB #1043428 and BSIS Alarm Company Operator licence ACO 7755 — both publicly verifiable through the CSLB and the California DCA licence search.
