Most STR owners don’t think about WiFi until a cleaner texts at 11am: “the WiFi is down and the next guest checks in at 3.” The reason it’s down is almost never the internet. It’s the consumer router that can’t keep up with the device turnover between stays.

The turnover-day failure pattern

A typical Vail or Avon two-bedroom condo sees something like this on changeover day:

  • Departing guests leave at 10am. They’d had four phones, two laptops, an iPad, a Chromecast, two Bluetooth speakers, and an Apple Watch all attached to your WiFi for three nights.
  • Cleaning crew arrives at 10:30. Two cleaners with phones, sometimes a third doing laundry. They’re on the WiFi running the cleaning app, the smart-lock app, and probably checking messages.
  • Maintenance shows up at noon to swap a battery in the doorbell. Another phone on the WiFi, plus the doorbell’s own connection.
  • Next guests check in at 3pm. Four more phones, two laptops, kids with iPads.

That’s 15 to 20 distinct devices touching the network in five hours. Consumer routers handle bursts like that badly. They start dropping connections, the smart lock loses its tether, the cleaner’s app times out submitting the turnover checklist, and someone has to text the owner. The router isn’t broken — it’s just designed for an apartment with five devices that stay attached, not a property with twenty that cycle.

“The router isn’t broken — it’s just designed for an apartment with five devices, not a property with twenty that cycle.”

What cleaning crews actually need

If you ask STR cleaners what they need from WiFi, the answer is usually short:

  • The cleaning app (Properly, TurnoverBnB, Breezeway) needs to upload photos at the end of the turn.
  • The smart-lock app needs to talk to the lock to verify the new code took.
  • The doorbell needs to stay online so the cleaner doesn’t set off a notification when they show up.
  • Group messages to the owner or the next-shift cleaner have to send reliably.

None of that is bandwidth-intensive. What it needs is a network that doesn’t drop devices when 15 of them attach in an hour. That’s a capacity-and-management problem, not a speed problem.

The two-network setup we install

For STR properties we always install at least two separate networks on the same hardware: an owner/host network and a guest network. They share the same internet connection but have separate SSIDs, separate passwords, and separate VLANs so they can’t see each other.

The owner network

Holds anything you want to keep stable across stays: the smart lock’s controller, the doorbell, the security cameras, the thermostat, the smart switches, and any Sonos or Apple TV that you don’t want guests reconfiguring. The cleaning crew gets the owner-network password so their tools can talk to the locks and the doorbell. Guests never see this network.

The guest network

What the SSID and password in the welcome book point at. Fully isolated from the owner network. We set bandwidth caps per device so one teenager streaming 4K on Xbox doesn’t starve the next guest’s Zoom call. We also configure it to forget devices automatically after the stay ends, so the next guest connecting doesn’t see a list of the last twenty visitors’ phones in the router log.

This setup costs more than a single-SSID consumer router (we use Ubiquiti UniFi for STR properties — same gear we install at private residences, see our post on why we install UniFi exclusively). But it solves the turnover failure pattern at the root.

Guest network reset between stays

One of the small things that matters: we set the guest network to clear its DHCP lease table on a schedule, so by the time a new guest arrives, all the previous guests’ devices have been forgotten. The previous guest’s phone won’t auto-connect if they happen to drive by next year. The new guest’s device gets a clean assignment.

This isn’t critical for performance, but it’s the kind of thing that quietly prevents weird edge cases — a long-stay guest’s old laptop confusing the router three months later when they come back.

Bandwidth limits per device

Mountain properties often have a single bonded uplink (Starlink, fixed wireless, or a fiber connection where available) that’s plenty for a normal household but can be saturated by a single user. We set per-device bandwidth caps on the guest network so no one device can consume more than (say) 60% of the upstream. The cap is invisible during normal use — you only feel it if you try to upload a 50 GB video file while four other people are streaming. In that case the upload slows down. Nobody else’s movie buffers.

Documentation we leave for cleaners

Every STR install ships with a laminated reference card that lives in a kitchen drawer or stuck to the network closet door. It has:

  • The owner network SSID and password (for cleaners and maintenance)
  • The guest network SSID and password (in case a guest can’t find the welcome book)
  • Where the modem, router, and main access point live in the house
  • What to do if the internet appears down (the standard restart sequence)
  • Our email address and a note saying “email us a photo of any blinking lights and we’ll diagnose remotely”

Most issues get resolved by email or remote configuration session before anyone needs to drive out. That’s what cleaners want — a path to resolution that doesn’t involve a 2pm panic text to the owner.

Cameras and WiFi together

Most STR owners we work with end up bundling WiFi with security cameras — the cameras live on the owner-network VLAN, record locally to an NVR in the network closet, and the same controller manages both. It’s a clean install pattern. We cover this in detail on our short-term rental services page.

If your STR’s WiFi is failing on changeover days — or if you’re launching a new property and want to skip the “learn this the hard way” phase — send us the property address and a quick note on how many bedrooms and what your current setup is. We’ll come back within one business day with a written quote for the install and a sense of what kind of property it is from our end.