
Garmin watches and scales need a 2.4 GHz network of their own, WPA2 password, no sign-in page. The second path skips it: the kit's phone in the room.
The network is not needed by «the watch» in general but by four different streams. They travel different roads and break for different reasons.
| What travels | By which road | Where it lands |
|---|---|---|
| The night and the day off the watch — sleep, pulse, HRV, stress, Body Battery, respiration, blood oxygen, steps | the watch's own Wi-Fi or the kit's phone over Bluetooth | the Garmin cloud; the portal collects from there every half hour |
| A weighing — weight, fat, muscle, water, bone | the scales' own Wi-Fi: no phone needed for the upload | the same cloud, the same half-hourly round |
| A walk and the functional tests — track, pulse, elevation, test results | our app on the watch, through the kit's phone | straight into the portal, bypassing the Garmin cloud |
| The day's carousel on the watch face — servings, procedures, the pulse corridor | the face's background service, through the kit's phone | from the portal to the watch, asked for every half hour |
The bottom two rows are ours, and Wi-Fi does not help them: a Connect IQ app sends its web request through the phone, not through the watch's network module. Which is why the phone stays in the room even where the Wi-Fi is set up perfectly.
Four networks are involved, but only one is new. Keep them apart by name rather than by password: handing the devices the guest network is the single most common cause of «everything is configured and nothing arrives».
| Network | For whom | What it must have |
|---|---|---|
| The device network — the one you build | Forerunner 165 Music watches, Index S2 scales | 2.4 GHz under its own name, WPA2-PSK, a password of 8 characters or more, a visible name, no sign-in page |
| The staff network | the kits' Android phones, the desk, the doctor | any band, WPA2; no sign-in page — a phone that waits for a tap in a browser after a reboot stops being a bridge silently |
| The guest network | the guest's own phone with the portal open | the hotel's ordinary guest network; a sign-in page is fine here — the guest has a browser and fingers |
| The room network | the television, a tablet, everything else | no use to the devices and not needed: the scales and the watch live on the device network, not the room one |
These are not recommendations but the operating conditions of the Wi-Fi module. Garmin publishes them itself: as a list for the Index scales, as the manual and a support article for the watch (see «Sources»). A broken condition produces silence, not an error.
| Condition | Why it is so | How a hotel breaks it |
|---|---|---|
| 2.4 GHz only | the devices carry an 802.11 b/g/n module with no 5 GHz | a modern access point serves 5 GHz and hides 2.4 GHz behind a shared name, or switches it off |
| Channels 1–11 | the device is built for that channel plan | a European router on automatic settles on 12 or 13 — and the network vanishes from the list on the watch |
| A visible network name | the device does not look for hidden networks | security hides the network name «for good order» |
| WPA or WPA2, password from 8 characters | the module knows no other modes | the access point is set to WPA3; the mixed WPA2 with WPA3 mode fails where protected management frames are required |
| No 802.1X | the device cannot pass a login-based enterprise check | the network is built on domain authentication, the way it is for laptops |
| No sign-in page | the watch and the scales have no browser, and there is nobody to press «I agree» | the devices were handed the guest network with its welcome window |
The last one is the sneakiest. The watch honestly shows the network as connected, the icon is lit, the signal is there — and nothing leaves: the data never reaches the cloud, the sign-in page turns it back.
Two different devices are sold under the one name Forerunner 165. The difference in the name is a single word; the difference in how data travels is fundamental.
| Model | Wi-Fi | How it hands data over |
|---|---|---|
| Forerunner 165 | none | through a phone over Bluetooth only |
| Forerunner 165 Music | yes | over Wi-Fi by itself; next to a phone — over Bluetooth as usual |
Garmin lists what the watch carries over Wi-Fi on its own: recorded activities, software updates, workouts and training plans, music. About all-day monitoring — sleep, pulse, HRV — that list says nothing, so the hotel checks it itself: one night with the watch on the wrist and the phone carried off to the desk.
As of 23.08.2026 that night has not happened yet, so the phone goes to the room. The hotel buys the Music version regardless: without Wi-Fi the watch cannot be updated and cannot be given an app from the Connect IQ store without a phone held next to it.
The order for a Forerunner 165 Music. Done once per kit, while preparing it, not at every handover.
The network on the watch does not belong to the guest and is not wiped at the handover: it lives on the kit, the way the six digits of the pairing code do (what else stays on the watch for good).
The scales are the kit's third device, and they need Wi-Fi harder than the watch does: there may be no phone near them at all, and the guest steps on them before breakfast and walks away.
This path is not the fallback but the main one: as of 23.08.2026 the hotel moves its data exactly this way. It also works with the plain Forerunner 165, which has no Wi-Fi at all.
A kit is three devices under one Garmin account that belongs to the hotel: the watch, an Android phone and the Index S2 scales. The phone travels to the room with the watch, lies on its charger and carries the measurements to the cloud.


The most expensive misconception while preparing the network is «we will set up Wi-Fi and keep the phones at the desk». The watch's Wi-Fi carries data to the Garmin cloud; the portal picks it up from there on its half-hourly round. Everything of ours travels another road.

| What you see | Why | What to do |
|---|---|---|
| The network is missing from the list on the watch | the access point serves 5 GHz only, the name is hidden, or channel 12–13 is in use | switch 2.4 GHz on under its own name, unhide the name, pin the channel within 1–11 |
| The password is not accepted | the network is on WPA3 or on an 802.1X enterprise check; the password is shorter than 8 characters | move the device network to WPA2-PSK with a password from 8 characters |
| The watch connected, the cloud is empty | the network has a sign-in page | take it off the device network; the guest network will not do for them |
| It worked and stopped | the password changed, the access point moved to another channel, or the network asks for consent again once a day | test the network with a phone the same way, then walk round the devices |
| «The watch is online», but no night arrived | what is silent is not the portal but the chain watch, phone, cloud: the phone is flat, carried off, or its Garmin Connect has not run a sync | put the phone back in the room and on its charger |
| Nothing arrives from a new kit | the watch is not paired to the kit's account — before the pairing Wi-Fi does not switch on | pair it through Garmin Connect or Garmin Express, then enter the network |