Smart home control by Oxy. Connects to a Home Assistant instance and gives you a fast, native-feeling view over your climate and light entities.
Built with Expo (React Native).
bun install
bun startWillo declares the Oxy signature permissions, so @oxy.so/services' withOxySharedPermissions
(applied by ['@oxy.so/app-preset', {}]) signs every release build with the Oxy ecosystem key
and fails the build without it. The key comes from Gradle properties, never the repo:
OXY_UPLOAD_STORE_FILE, OXY_UPLOAD_STORE_PASSWORD (or OXY_UPLOAD_STORE_PASSWORD_FILE) and
OXY_UPLOAD_KEY_ALIAS (oxy), in ~/.gradle/gradle.properties, with -P, or as
ORG_GRADLE_PROJECT_<name> environment variables.
A debug / dev-client build keeps Expo's debug key, so it cannot be installed next to Oxy,
Commons or Mention (INSTALL_FAILED_DUPLICATE_PERMISSION). To put a dev client on a phone that
has Oxy apps, opt debug into the same key with OXY_UPLOAD_SIGN_DEBUG=true (for example
ORG_GRADLE_PROJECT_OXY_UPLOAD_SIGN_DEBUG=true, or a line in ~/.gradle/gradle.properties).
bun run lint runs Biome (formatting and linting) plus the frontend's minimal Expo ESLint
config; bun run format formats with Biome.
Willo's Oxy account calls use the shared linked transport for home management,
commands and camera snapshots. The session epoch resets the current home on
account changes; the product's /homes socket reads the current shared session
through the linked client at each handshake, refreshing an expired token before
connecting. It disconnects and cancels pending handshakes when that context changes. Home membership is
still checked by the backend. Home Assistant OAuth and device pairing remain
separate protocols.
Camera views fetch private images through that same transport, then render local blob URLs on web or in-memory data URLs on native. They never pass Oxy bearers to an image loader. Closing a view revokes its blob URL, and changing account aborts or discards its previous snapshot. Responses are private and not HTTP-cacheable.
The backend's Oxy client and ecosystem activity use temporary workload identity, including a registered local AWS SSO/assume-role identity. Own-product calls need no customer API key, app scope or consent screen. The shared SDK resolves and refreshes those credentials; deployment still controls the workload binding, environment and recipient audience.