The Android Intent Executor allows you to remotely execute Android Intents from Home Assistant: open apps/settings (launch), or send broadcast intents (Home Assistant Companion compatible).

Exposes the ESPHome service launch_intent with one required field, intent_uri. Keeping the service to one field avoids ESPHome exposing optional intent properties as required fields in Home Assistant.

1. Settings → Device Controls → Diagnostic Sensors
2. Enable Android Intent Executor
3. Enable Show in Home Assistant

After enabling the service or upgrading from an older multi-field version, restart the voice satellite or reload the ESPHome integration so Home Assistant refreshes the schema.

1. intent_uri starts with broadcast: → broadcast
2. Otherwise → activity/URI launch

Broadcast properties are encoded in the one URI field:

broadcast:ACTION sends an implicit broadcast. Add ?package=PACKAGE to target one application. Query parameter values must be URL-encoded when they contain &, = or #.

HA Companion aliases (0.6.4): the long-form Home Assistant Companion query keys intent_action, intent_package_name, intent_class_name, and intent_extras are also accepted as aliases for action/package/class/extras inside the same intent_uri query string — useful when copying examples straight from HA Companion docs. Values embedded directly in the URI always win; the aliased keys only fill in whatever the URI itself did not specify.

action: esphome.device_name_launch_intent
data:
 intent_uri: "spotify://"

# System settings
intent_uri: "intent:#Intent;action=android.settings.SETTINGS;end"

action: esphome.device_name_launch_intent
data:
 intent_uri: "broadcast:com.example.ava.ACTION_TOGGLE_MIC"

The short form sends an implicit broadcast:

intent_uri: "broadcast:com.sendspinlite.ACTION_DUCK"

Use the package form when the receiver requires an explicitly targeted broadcast:

intent_uri: "broadcast:com.sendspinlite.ACTION_DUCK?package=com.sendspinlite"

intent_uri: "broadcast:com.urbandroid.sleep.alarmclock.START_SLEEP_TRACK?package=com.urbandroid.sleep"

intent_uri: "broadcast:?action=com.urbandroid.sleep.alarmclock.ALARM_STATE_CHANGE&package=com.urbandroid.sleep&extras=alarm_label%3Awork%2Calarm_enabled%3Afalse"

intent_uri: "broadcast:?action=com.example.ava.ACTION_SET_MOD_ENABLED&package=com.example.ava&extras=mod_id%3Aecho_dot_led%2Cmod_enabled%3Atrue"

intent_uri: "broadcast:?action=com.example.ava.ACTION_APPLY_SETTINGS&package=com.example.ava&extras=setting_path%3Amicrophone.voicePrintEnabled%2Csetting_bool%3Atrue"

The decoded extras query value uses name:value pairs separated by ,. Arrays use ; between values. Append :type for explicit types.

Guessing without type: digits → int, true/false → boolean, else string.

Also accepted: :urlencoded and docs alias :ArrayList.urlencoded.

Open Spotify, then switch to the display settings page five seconds later:

automation:
 - alias: "Morning Device Setup"
 trigger:
 - platform: time
 at: "07:00:00"
 action:
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "spotify://"
 - delay: "00:00:05"
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "intent:#Intent;action=android.settings.DISPLAY_SETTINGS;end"

automation:
 - alias: "Launch Netflix by Voice"
 trigger:
 - platform: conversation
 command: "launch netflix"
 action:
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "netflix://"

No UI opens — the device just reacts:

# Toggle microphone
intent_uri: "broadcast:com.example.ava.ACTION_TOGGLE_MIC"
# Restart the voice satellite
intent_uri: "broadcast:com.example.ava.ACTION_RESTART_VOICE_SATELLITE"
# Check for updates
intent_uri: "broadcast:com.example.ava.ACTION_CHECK_UPDATE"

Full list of Ava control broadcasts: ADB Commands.

Trigger a Tasker task by name (extras are packed into the one URI):

intent_uri: "broadcast:net.dinglisch.android.tasker.ACTION_TASK?package=net.dinglisch.android.taskerm&extras=task_name%3ABedtime"

Refresh a KWGT widget:

intent_uri: "broadcast:org.kustom.action.REFRESH_WIDGET?package=org.kustom.widget"

automation:
 - alias: "Weather-Appropriate Entertainment"
 trigger:
 - platform: state
 entity_id: sensor.weather_condition
 action:
 - choose:
 - conditions:
 - condition: state
 entity_id: sensor.weather_condition
 state: "rainy"
 sequence:
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "netflix://"
 - conditions:
 - condition: state
 entity_id: sensor.weather_condition
 state: "sunny"
 sequence:
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "spotify://playlist/outdoor"

Because broadcasts don't open a window, you can fire several in a row without anything jumping on screen:

automation:
 - alias: "Movie Night on Ava Panel"
 trigger:
 - platform: state
 entity_id: input_select.house_mode
 to: "movie"
 action:
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "intent:#Intent;action=android.settings.DISPLAY_SETTINGS;end"
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "broadcast:com.spotify.music.playlist?package=com.spotify.music&extras=playlist%3Achill"
 - service: esphome.ava_launch_intent
 data:
 intent_uri: "broadcast:com.example.ava.ACTION_RESTART_VOICE_SATELLITE"

automation:
 - alias: "Motion Snapshot from Front Door"
 trigger:
 - platform: state
 entity_id: binary_sensor.front_door_motion
 to: "on"
 action:
 - service: esphome.hallway_launch_intent
 data:
 intent_uri: "broadcast:com.example.ava.ACTION_SCREENSHOT?extras=path%3A%2Fsdcard%2FAva%2Fsnapshots%2Ffront_door.jpg"

1. Check the app's own developer documentation
2. Monitor adb logcat while opening the app manually
3. Use a third-party inspector such as "Intent Interceptor"
4. Search the Home Assistant community forums
5. Trial and error: try appname:// or com.package.name

• Tasker — Intent Launcher is the bridge between HA state and Tasker's device-level automation. Example: an HA automation fires a Tasker task via broadcast when the battery drops below 20%, while HA adjusts lighting to indicate charging.
• Automate — inject smart-home context into an Automate flow, or have Automate trigger an app launch through HA.
• Android Shortcuts — turn a static shortcut into a context-aware one, e.g. a "Movie Time" shortcut that opens Disney+ instead of Netflix when the kids are home.

sensor.your_device_name_intent_launcher_status

ESPHome’s service schema has no optional-argument flag. Ava now exposes only intent_uri and parses all properties from it. If Home Assistant still shows the old fields, restart the voice satellite or reload the ESPHome integration.

1. Intent Launcher + Show in Home Assistant enabled
2. After schema change, reconnect device / reload ESPHome integration
3. Verify that HA shows only intent_uri
4. Add ?package=PACKAGE if an implicit third-party broadcast is not received
5. URL-encode query values containing reserved characters

• Launch opens a UI (startActivity)
• Broadcast notifies a receiver (sendBroadcast) — screen may not change

1. Test each intent_uri manually (e.g. via the HA Developer Tools service call) before wiring it into an automation
2. Add short delay: steps between chained launches so the target app has time to come to the foreground
3. Prefer broadcast: over launch when you don't want the screen to change
4. Add ?package=PACKAGE whenever a third-party broadcast isn't received — many OEM ROMs block implicit broadcasts
5. Keep a personal list of working intent_uri values; app updates occasionally change their URI scheme

Back to Home