A Velop child that will not join may be on a different mesh type, too far from the parent or in the wrong setup state.
Before you change anything
This is a diagnostic entry point. The source supports the general check, not a confirmed root cause for your device.
What to check first
Do parent revision and firmware support this method?
Record the exact model, hardware revision, firmware and recent change before adjusting settings. If you cannot answer the question, keep the cause open.
Narrow the likely path
| Observation | Next check |
|---|---|
| Light or app says offline | Use the correct model and role chart; color alone is inconclusive. |
| Node will not join | Check the specific mesh family and parent/child setup sequence. |
| Feature menu differs | Compare the current firmware and hardware revision with the vendor guide. |
Decision after the first test
Use the vendor's child-add sequence near the parent, then move it after the app confirms a working link.
Use a documented next step
Verify before escalating
After each change, repeat the exact failed task. If the result is unchanged, restore the previous setting and use the official support link for your exact hardware revision. Don’t assume a menu or capability from a related model.
Official sources
- Linksys Plug-N-Play child-node addition (full_text; checked 2026-11-01)
- Linksys Cognitive Mesh setup and firmware-specific methods (full_text; checked 2026-11-01)
Check your exact US model, hardware revision, and firmware on the linked support page before changing settings.