HEOS error 1002 is the app's generic "couldn't connect to the HEOS system" — the controller app can't establish a control session with your Denon (or Marantz; same HEOS platform). It's rarely the receiver dying. In practice it's one of three things: the phone and the receiver aren't truly on the same network, your router is blocking the multicast discovery HEOS depends on, or the receiver's network stack is wedged by a known firmware bug. (Denon doesn't define 1002 by number, but its "trouble connecting to HEOS" guidance lists exactly these causes.)
Fix it
- Put the phone and the receiver on the same network — really. Turn off cellular data on the phone and join the same 2.4 GHz SSID the receiver uses. On mesh or multi-AP setups the phone quietly roams to a different node or band than the receiver, and that mismatch alone produces 1002.
- Hardwire the receiver with Ethernet. This is the most reliable fix by a distance. A wired link sidesteps Wi-Fi drops and band-steering entirely, and it's what clears receivers stuck on "Waiting…".
- Reboot in order. Power-cycle the router, then the HEOS device — unplug each, wait 30 seconds or more, bring the router fully up, then the receiver. Use 30s+, not 10s; the network stack needs time to reset.
- Disable band-steering; keep HEOS on 2.4 GHz. One SSID that auto-switches the phone or receiver between bands is a classic trigger. Give 2.4 GHz its own name and join both devices to it.
- Network-reset the receiver and re-add it in the HEOS app (Settings → My Devices → add device). This is the required step after you replace a router — the receiver keeps stale settings and won't auto-reconnect.
The advanced cause: blocked multicast
If you run a prosumer router, a managed switch, or VLANs, this is your likely culprit. HEOS discovers devices over multicast (SSDP to 239.255.255.250:1900, plus IGMP). If IGMP snooping is on without an active querier, multicast is filtered, or the phone and receiver sit on different subnets/VLANs, discovery silently fails and you get 1002. Allow that multicast through (enable a proper IGMP querier, or turn snooping off), and across VLANs you'll need an mDNS reflector — by default HEOS simply won't be found across subnets.
The firmware-bug variant
If the receiver shows IP 0.0.0.0 with Wi-Fi, Ethernet, and Bluetooth all dead, that's the known HEOS-update bug, not your router. Denon/Marantz's remedy is to check the network, do a user reset per the manual, and if needed re-flash the initial firmware; some owners only recovered by downgrading firmware and disabling auto-update so the app doesn't re-break it. Heads-up: a settings backup made before the bad update may fail to restore afterward, so don't count on it.
FAQ
Does 1002 mean my receiver is broken? Almost never. It's a discovery/connection failure — same-network mismatch, blocked multicast, or band-steering. Hardwiring usually proves that instantly.
Why does HEOS hate my mesh network? Because the phone and receiver land on different APs or bands, and HEOS needs them on the same network with multicast flowing. Force both onto one 2.4 GHz SSID, or wire the receiver.
I just changed routers and now it won't connect. Expected — the receiver kept old network settings. Reset its network and re-add it in the app.