Support center

Support guidance that explains the problem before it tells you to reset everything

This section is designed for the broader support questions that often sit behind device failures: account state, onboarding flow, app permissions, privacy settings, compatibility assumptions, and escalation readiness.

It complements the troubleshooting center by helping visitors understand the context around a failure, not just the visible symptom.

FocusSetup, apps, compatibility, and escalationStyleHuman-readable guidanceUse casePrevention and diagnosis

Directory overview

Crawlable support-article hub for how-to content, app setup help, account flows, and general smart home support pages.

Articles6
Article types4
Tracked pagesFocused
Timed guidesPractical

Filter and sort

Server-side support directory controls for article type, text query, and ranking mode.

How to use this page

Review mode keeps this section intentionally simple. Start with the featured cards for the most common support themes, then continue into the section-based guidance below.

Support article results

The support center in review mode uses curated editorial sections instead of a large dynamic directory.

How to use the support directory

Setup basics

Start with one clean controller, one stable network path, and one correct account. Many smart home onboarding problems come from mixing old device state with new app state too early.

App control issues

If the app says the device is online but controls fail, compare local behavior, automation behavior, and direct app commands before assuming the hardware is broken.

Compatibility basics

Cross-ecosystem claims often hide real limitations around protocol support, firmware requirements, scenes, automations, sensor exposure, or hub dependencies.

Privacy and account expectations

Cloud-linked devices can fail in ways that look technical but are really caused by shared-home permissions, expired sessions, or account-level restrictions.

When to escalate to the vendor

Escalate only after collecting the exact model, firmware, app version, controller type, network context, and the shortest reproducible sequence of steps.