A Matter-over-Thread sensor does not need a direct radio path to the home’s Wi-Fi router. It joins a Thread mesh, usually as a low-power end device, and communicates through a parent. A Thread border router connects that IPv6 mesh to the rest of the home network. Placement work becomes easier once those roles are mapped separately.
Start with roles, not signal bars
Battery sensors are commonly sleepy end devices. They keep their radios off most of the time, wake to exchange data with a parent, and do not forward traffic for other nodes. Mains-powered Thread devices may be router-capable: they stay available and can relay packets. A parent is the router currently serving an end device; it is a relationship, not a separate product category.
A border router has another job. It forwards IP traffic between Thread and adjacent networks and can help with service discovery. It is not simply a stronger repeater. Multiple border routers can improve path options, but only if they are powered, commissioned into the same Thread network and placed where their network connections remain stable.
Make a baseline map room by room
Mark each sensor, powered Thread router and border router on a floor plan. Note walls, metal cabinets, utility spaces and floor changes. Then record whether each sensor reports reliably from its final mounted position over several normal cycles—not just while a door is open or a device is on a workbench.
RSSI can help identify a weak link, but one reading is not a pass/fail test. Thread links may use different parents or routes over time, and interference, orientation and people moving through a room can change measurements. Pair RSSI with repeated delivery, latency and parent/route observations where the platform exposes them.
Change one variable at a time
If a sensor is unreliable, first confirm power and firmware, then move or add a powered router-capable device between the sensor and the mesh. Recheck over time before changing another element. Moving a border router may help the mesh edge, but it will not automatically fix a poor end-device-to-parent link on the other side of metal or masonry.
The useful baseline is therefore a record of roles, locations and observed behavior. It gives future troubleshooting a comparison point without pretending that a single signal number describes the whole mesh.
Meeting this platform felt like finding a reliable travel buddy. The interface is so clear and the bonuses come with a warm welcome that makes newcomers feel right at ease. I appreciate how you keep things honest and straightforward. Already planning my next session. bdtk1971