Thread devices go offline when the border router is down

Matter-over-Thread sensors and lights stop responding but their battery and app status look normal.

Applies to

Matter over Thread devices
Thread sensors, locks and lights
Apple Home, Google Home and SmartThings Thread networks

Last verified2026-10-14

Quick answerTroubleshooting · last verified 2026-10-14

Matter-over-Thread sensors and lights stop responding but their battery and app status look normal. Most common cause to check first: Border router unplugged or rebooting

Applies toMatter over Thread devices, Thread sensors, locks and lights, Apple Home, Google Home and SmartThings Thread networks

CategoryThread

Escalate whenThread devices depend on a working border router and IPv6. If every Thread device fails at once, troubleshoot the border router and the network before touching individual devices.

Last verified2026-10-14

How to cite this page

IoT Atlas. "Thread devices go offline when the border router is down". https://hi-spark.net/troubleshooting/thread-device-offline-border-router.html Last verified 2026-10-14.

Likely causes

Border router unplugged or rebooting
IPv6 disabled on the router or ISP
Border router firmware out of date
Thread network credentials changed after a hub reset
Device dropped from the Thread network

Quick checks

Check that the border router is powered and online
Confirm the hub shows in the app as a Thread border router
Check whether other Thread devices respond
Look for a recent router or ISP change affecting IPv6

Step-by-step fix

Power-cycle the border router and wait for it to rejoin

Confirm Thread is enabled in the hub settings

Re-test one device near the border router

If only one device fails, remove and re-add that device

If all devices fail, reset the Thread network and re-add devices in order

Frequently asked questions

Why does this happen: Thread devices go offline when the border router is down?

Matter-over-Thread sensors and lights stop responding but their battery and app status look normal.

What is the most likely cause?

Border router unplugged or rebooting; IPv6 disabled on the router or ISP; Border router firmware out of date.

What should I check first?

Check that the border router is powered and online; Confirm the hub shows in the app as a Thread border router; Check whether other Thread devices respond; Look for a recent router or ISP change affecting IPv6.

How is it fixed?

Power-cycle the border router and wait for it to rejoin; Confirm Thread is enabled in the hub settings; Re-test one device near the border router; If only one device fails, remove and re-add that device; If all devices fail, reset the Thread network and re-add devices in order

When should the case be escalated?

Thread devices depend on a working border router and IPv6. If every Thread device fails at once, troubleshoot the border router and the network before touching individual devices.