-
-
Notifications
You must be signed in to change notification settings - Fork 20
Quick Start
This guide helps you quickly install and configure Ava.
| Requirement | Description |
|---|---|
| Android Version | 5.0 (API 21) or higher |
| Architecture | arm64-v8a or armeabi-v7a |
| Home Assistant | Must be installed and running |
| ESPHome Integration | Must be installed in HA |
| Network | Device and HA must be on same LAN |
Download the latest version from GitHub Releases:
Ava has a built-in auto-update feature. Once installed, it checks for updates periodically.
Look for the icon: Since 0.6.1, Ava uses a warm-brown geometric A icon across standard, round, adaptive and Android 14 monochrome launchers. The unnecessary splash screen has been removed, and existing users keep their current theme choice.
- Transfer APK file to your Android device
- Tap APK file to start installation
- If prompted about "Unknown sources", allow installation
On first launch, Ava will request these permissions:
| Permission | Purpose | Required |
|---|---|---|
| Microphone | Voice input | Yes |
| Overlay | Display screensaver, notifications, floating windows | Yes |
| Foreground Service | Keep service running | Yes |
| Camera | Photos and video | Optional |
| Bluetooth | Presence detection and BLE proxy | Optional |
| Location | Required for Bluetooth scanning | Optional |
- Open Home Assistant
- Go to Settings -> Devices & Services -> Integrations
- Click + Add Integration in bottom right
- Search for ESPHome
- Click to install
- Launch Ava app
- Go to Settings -> Voice Config
- Tap Start Service
- Return to Home Assistant
- ESPHome integration will auto-discover Ava device
- Click Configure to complete setup
- In ESPHome integration, click Configure
- Enter Ava device's IP address
- Port defaults to 6053
- Click Submit
Custom HA port (0.6.3): Ava no longer assumes Home Assistant always uses port 8123. It learns the active port from addresses reported by Home Assistant, adding compatibility with randomized and custom ports introduced in recent HA betas. Legacy devices that do not provide updated port information continue to use 8123 as a fallback.
- Go to Settings -> Voice Assistants
- Ensure voice assistant pipeline is configured
- Recommended setup:
- Speech-to-Text: Whisper
- Text-to-Speech: Piper
- Conversation Agent: Home Assistant built-in
- Go to Settings -> Voice Config
- Confirm status shows "Connected"
- Select your preferred wake word
- Choose wake word engine (microWakeWord or OpenWakeWord)
To show Home Assistant dashboards on Ava:
- Go to Settings -> Browser
- Enable Browser Display
- Enter your HA URL in Remote Browser URL
- Choose render engine: System WebView or GeckoView
GeckoView is recommended for old devices. It provides a modern browser engine for devices with outdated system WebView. Requires downloading the engine pack separately.
For features like screen control, display resolution, and intent execution, set up Shizuku:
- Install Shizuku from GitHub
- Enable via wireless debugging or ADB
- Go to Settings -> Permissions -> Shizuku Authorization
- Tap Authorize
See Permissions for detailed guide.
The Start Core Service on App Open option is designed for panels where Ava may be opened manually, by a launcher, or by another automation while its voice service is not yet running. When enabled, Ava displays a full-screen circular countdown and starts the core service when it reaches zero.
- Delay adjustable from 3 to 30 seconds (default 7 seconds)
- Allows the Android system and device hardware time to settle before microphone, Bluetooth, and HA components start
- Off by default, separate from Auto Restart
Path: Ava Settings → Device Services → Auto Restart → Start Core Service on App Open
- Say wake word (default "Hey Jarvis")
- After hearing prompt sound, say "What time is it"
- Ava should reply with current time
- Say wake word
- Say "Turn on the living room light" (assuming you have this device)
- Light should turn on
- Ensure Ava and Home Assistant are on same network
- Check if firewall is blocking port 6053
- Try restarting Ava service
- Try manually adding device
- Check network stability
- Ensure Ava isn't being killed by system
- Disable battery optimization in settings
- See FAQ for brand-specific solutions
- Check Home Assistant voice assistant configuration
- Ensure Whisper and other components are running
- Check network latency
After setup is complete, you can:
- Configure Screensaver
- Set up Notification Scenes
- Enable Floating Windows
- Configure Camera
- Set up Bluetooth Proxy
- Configure Voice Messages & Calls
- Customize Quick Entity Panel
- Set up Sendspin / Music Assistant
Back to Home
- Quick-Start
- System-Requirements
- Voice-Control
- Chorus-Wake
- ESPHome-Encryption
- HA-Direct-Connection
- Browser
- Screensaver
- Floating-Windows
- Home-Launcher
- Home-Screen-Widgets
- Notification-Scenes
- Quick-Entity
- Sensors
- Backup
- Sendspin
- Bluetooth
- Voice-Messages-Calls
- Music-Playback
- Camera
- Screen-Control
- Intent-Launcher
- ADB-Commands
- Mod-Store
- Ava-Fleet