Door Station & Indoor Station Wi-Fi Faults
Purpose
Wi-Fi Hikvision door stations and indoor screens have cost us several wasted hours per site. Two sites still have open issues. The faults look random, but nearly all of them come from one of three network conditions:
- One SSID shared by 2.4GHz and 5GHz (merged / "Smart Connect" / band steering)
- A Wi-Fi extender, booster or mesh node between the units and the router
- The two units ending up on different networks or radios, so the door station and indoor screen cannot see each other even though both show "connected"
This page makes those three faults quick to spot and gives the fix for each. Check this page before spending time in the Hikvision menus.
Golden rule: the door station and its indoor screen(s) must be on the same network (same subnet), ideally the same access point, and ideally cabled (PoE). If you cannot guarantee that, do not leave the site until you have tested a call both ways.
Fault 1 — Merged 2.4GHz / 5GHz SSID
What happens
Most ISP routers broadcast one network name for both bands and use band steering to push devices to 5GHz. The Hikvision units are listed as 2.4GHz Wi-Fi devices (see the note on specifications below), so they can fail in several ways:
- Setup fails or says the password is wrong when it is correct
- The unit joins, then drops and never rejoins
- The unit joins but is unstable, with the screen intermittently losing the door station
- The unit connects on one visit and not the next
The setup path matters too. Hik-Connect and similar setup apps take the Wi-Fi details from the phone you are using. If your phone is on the 5GHz side of a merged SSID, the device can be handed 5GHz details it cannot use. This is a general IoT onboarding problem, not something specific to Hikvision, but it explains why "the password is right and it still won't join".
Fix (in order of preference)
- Cable it. Both units support PoE. Hardwiring removes the problem entirely.
- Split the SSIDs. Name them differently (for example
Home-2GandHome-5G). Put the phone and the units on the 2.4GHz name during setup. - Give the units their own 2.4GHz-only SSID (IoT or guest network) with band steering and fast roaming (802.11k/v/r) off, 20MHz channel width, and WPA2-PSK (AES) rather than WPA3 or WPA2/WPA3 mixed.
- If the router can't split bands (many EE, BT and Sky hubs): fit a dedicated 2.4GHz access point, or put the ISP router in modem mode behind our own router. Switching the 5GHz radio off during setup is a last resort. It is fragile and often undone when the router updates or reboots.
Specifications note
- The DS-KV6113-WPE1 is listed as 2.4GHz Wi-Fi by UK resellers, and the DS-KH6320-WTE1 as IEEE 802.11b/g/n.
- At one KV6114-WBE1 site, however, the door station's Wi-Fi status showed it connected on 5GHz. So do not assume every unit is 2.4GHz-only, and do not assume that a unit showing 5GHz is stable.
- Always check the Wi-Fi status screen on the unit itself and record which band and signal it is on. Do not rely on the datasheet.
Fault 2 — Extender, booster or mesh node in the path
What happened (Neptune Cottage)
The indoor screen could not see the door station. The cause turned out to be a Sky / BT Wi-Fi extender in the path. The screen and door station each looked "connected" to Wi-Fi, but the screen would not discover or register with the door station. Removing the extender from the path fixed it.
The exact extender mechanism at this site was not fully confirmed. Typical causes are:
- The extender creates its own network, so the units end up on different subnets (double NAT)
- The extender blocks or does not pass discovery traffic between devices on either side
- One unit has joined the extender and the other has joined the router
- The extender has merged or band-steered the two bands again
Whichever it is, the result is the same: both units show Wi-Fi connected, but they cannot find each other.
Fix
- Put both units on the same access point, preferably the router itself or a Wilsons-supplied AP.
- Remove consumer extenders from the units' path. Use a cabled AP instead.
- If a mesh system is unavoidable, test a call after every change. Mesh systems that hand clients between nodes can reproduce the intermittent drops.
- Re-register the indoor station in the door station after any network change (see below).
Fault 3 — Both on Wi-Fi, but the screen shows Offline
A typical case: the door station is at 192.168.0.155, the indoor station at 192.168.0.251 and both answer a ping, but in the door station's Device Management the indoor station is listed under its floor/room with a session status of Offline, and the screen intermittently loses the door station.
A ping working does not prove the intercom session works. Check:
- Same subnet for both units (check the IP, subnet mask and gateway on each).
- Both on the same access point and band (see Faults 1 and 2).
- Registration: on the indoor station, confirm the door station's IP and the registration details, then re-add it. Where an extension stops ringing but live view still works, resetting the indoor unit, re-entering the master's IP and password, and re-running registration is a reported fix on the IPCamTalk forum.
- Firmware: update both units, ideally on the current release. See the firmware section of Doorbell WiFi & Connectivity.
- Static IPs or DHCP reservations for both units, so a lease renewal doesn't move them.
- If it is still unstable after steps 1 to 5, cable the units. Do not keep chasing Wi-Fi.
Quick diagnosis table
| Symptom | Most likely cause | First action |
|---|---|---|
| Won't join Wi-Fi / "wrong password" | Merged SSID, band steering or WPA3 | Move to a 2.4GHz-only WPA2 SSID; phone on the same SSID |
| Joins then drops, intermittent offline | Band steering or poor signal | Cable it or add a dedicated 2.4GHz AP |
| Both "connected" but screen can't see door station | Extender / different subnet / different AP | Both units to the same AP, remove the extender |
| Ping works but session status Offline | Registration lost or network isolation | Check subnet, then re-register the indoor station |
| Works then breaks after ISP router change | New router defaults (merged SSID) | See Doorbell WiFi & Connectivity |
Prevention — make it obvious at survey and install
At survey / quote
- Record the customer's router make and model
- Ask: "Do you have any Wi-Fi extenders, boosters or mesh units?" Note where they are
- Check whether the router can split 2.4GHz and 5GHz
- Default to PoE cabling to the door station and the indoor screen. Quote it first
- If Wi-Fi is the only option: quote a dedicated 2.4GHz AP, and have the customer accept in writing that router or extender changes can break the system
At install
- Phone on the 2.4GHz network during setup
- Both units on the same AP, same subnet, with static IPs or DHCP reservations
- Note the band and signal strength on each unit's Wi-Fi status screen, and photograph it
- Indoor station registered in the door station (status Online)
Before leaving site
- Call from the door station, answer on the indoor screen, with two-way audio and video
- Call again with the phone on 4G and the Hik-Connect app
- Reboot the router, wait 5 minutes, and confirm both units return Online without help
- Walk the indoor screen to its final position and re-test
Sources
- Merged SSID and band steering behaviour: Why IoT Devices Fail To Connect to WiFi and How To Fix It (AarTech)
- DS-KV6113-WPE1 Wi-Fi band: Netview CCTV product page
- DS-KH6320-WTE1 Wi-Fi standards: Proshop product page
- Re-registering indoor extensions: DS-KH8520 master rings, KH6320 extensions do NOT ring (IPCamTalk)
- Site findings: Neptune Cottage (extender), KV6114 / KH6320 job (session Offline despite ping)
Hikvision does not publish a statement that explains the extender behaviour. The extender causes above are how these faults usually arise, confirmed by the fix on site rather than by a manufacturer document.