Home Advisor / Setup & support

Local setup, clear support boundaries.

Home Advisor is in development. This page outlines the setup design; customer instructions will accompany a future release.

Before first setup

What the current design requires.

The validated, release-matched FAT32 microSD card is part of normal operation. A blank card or a firmware file by itself is not a substitute.

Power and network

The current configuration uses USB-C wall power and 2.4 GHz Wi-Fi for fresh forecasts. First setup can be completed from a phone, tablet, or computer with a normal browser.

Household information

Have a five-digit U.S. ZIP code and your preferred time, units, and pollen sensitivities ready. Utility rates and comfort assumptions can be entered for estimate-based guidance.

Optional pollen service

A user-supplied key from a billing-enabled Google project is optional for completing setup, but pollen forecasts are unavailable until a valid key is saved. Provider charges or quotas may apply.

Everyday settings

After setup, ordinary configuration is handled on the touchscreen. The authenticated same-network browser view is for read-only status and sanitized support information, not a full settings portal.

When information is unavailable

If the screen shows older or unavailable information, check the source and freshness label before acting. A temporary outage may leave valid saved data available for a limited time; expired or unsafe evidence cannot authorize a positive recommendation. Pollen can also be unavailable because a type is not covered or a provider key has not been configured.

The display’s first touch after idle wakes it and is consumed. A second touch operates the intended control. This avoids an accidental action while waking the screen.

Support and updates

The planned update path uses a signed package on the required microSD card, validated locally at startup. See the updates page for the current release boundary.

Keep sensitive details out of general inquiries.Do not send Wi-Fi passwords, provider API keys, setup codes, local access codes, private IP addresses, or unreviewed support files through the website contact form. Review even a sanitized support export before sharing it.

If you need to discuss the pre-release product, use the ZeroHour contact page with a high-level description rather than credentials or private diagnostics.