Problem statement
As with every product launched by our commercial partners, we aim to deliver a great user experience.
The upcoming Nabu Casa proxying device is inherently a more technical product as proxying devices by nature requires users to understand a bit more about how their setup works.
That said, we still want to make the onboarding experience feel approachable, consistent, and smooth for anyone setting it up within Home Assistant.
This opportunity focuses specifically on the discovery, setup, and user documentation side of the product experience - not the marketing and launch activities covered separately in #133 and #140.
Note that developer-facing documentation covering serial proxying and migration paths is already in place:
Community signals
As previously mentioned in #23
Scope & Boundaries
In scope
- Surfacing the product within Home Assistant in a way that clearly communicates what users can do with it, with direct links to relevant documentation
- A Welcome screen shown upon device discovery to orient users from the moment they plug it in
- Supporting user documentation for reference beyond the initial setup flow
- Continue evaluation of discovery and proxying existing Nabu Casa products, including ZBT-1/2 and ZWA-2
Not in scope
Foreseen solution
- Welcome Screen upon product discovery
- User documentation
Risks & open questions
Open questions
- Best way to identify and surface discovered Nabu Casa products
Appetite
Medium - 1 cycle
Execution issues
No response
Decision log
Problem statement
As with every product launched by our commercial partners, we aim to deliver a great user experience.
The upcoming Nabu Casa proxying device is inherently a more technical product as proxying devices by nature requires users to understand a bit more about how their setup works.
That said, we still want to make the onboarding experience feel approachable, consistent, and smooth for anyone setting it up within Home Assistant.
This opportunity focuses specifically on the discovery, setup, and user documentation side of the product experience - not the marketing and launch activities covered separately in #133 and #140.
Note that developer-facing documentation covering serial proxying and migration paths is already in place:
Community signals
As previously mentioned in #23
Scope & Boundaries
In scope
Not in scope
Foreseen solution
Risks & open questions
Open questions
Appetite
Medium - 1 cycle
Execution issues
No response
Decision log