Download Home Assistant (Android Automotive) APK 2024.8.3-full arm64-v8a, armeabi-v7a, x86, x86_64 · Android 29+

What's Changed
Bump softprops/action-gh-release from 2.0.6 to 2.0.7 by
@dependabot
in
#4521
Bump softprops/action-gh-release from 2.0.7 to 2.0.8 by
@dependabot
in
#4523
Bump horologist from 0.5.27 to 0.5.28 by
@dependabot
in
#4526
Fix Active Notification Count sensor showing 0 notifications when upd… by
@marazmarci
in
#4525
Use compat function for tiles launch API by
@jpelgrom
in
#4520
Bump lifecycle from 2.8.3 to 2.8.4 by
@dependabot
in
#4529
Bump activity-compose from 1.9.0 to 1.9.1 by
@dependabot
in
#4530
Bump androidx.fragment:fragment-ktx from 1.8.1 to 1.8.2 by
@dependabot
in
#4531
Bump paging from 3.3.0 to 3.3.1 by
@dependabot
in
#4532
Bump com.github.Dimezis:BlurView from version-2.0.4 to version-2.0.5 by
@dependabot
in
#4534
Bump io.sentry:sentry-android from 7.12.0 to 7.12.1 by
@dependabot
in
#4535
Bump com.google.devtools.ksp from 2.0.0-1.0.23 to 2.0.0-1.0.24 by
@dependabot
in
#4537
Update to Gradle 8.9, Reckon 0.18.3, optimized order by
@jpelgrom
in
#4540
Bump io.sentry:sentry-android from 7.12.1 to 7.13.0 by
@dependabot
in
#4542
Only update location sent variables when successful by
@dshokouhi
in
#4545
Bump rexml from 3.2.8 to 3.3.3 by
@dependabot
in
#4548
Bump media3 from 1.3.1 to 1.4.0 by
@dependabot
in
#4533
Rename services to actions by
@dshokouhi
in
#4541
Implement Health Connect Sensors by
@psbankar
in
#4452
Bump actions/setup-java from 4.2.1 to 4.2.2 by
@dependabot
in
#4558
Bump paging from 3.3.1 to 3.3.2 by
@dependabot
in
#4563
Bump hilt from 2.51.1 to 2.52 by
@dependabot
in
#4557
Bump gradle/actions from 3 to 4 by
@dependabot
in
#4554
Bump kotlin from 2.0.0 to 2.0.10 by
@dependabot
in
#4560
Bump AndroidX car dependencies to 1.4.0 stable by
@jpelgrom
in
#4566
Bump wear-protolayout from 1.1.0 to 1.2.0 by
@dependabot
in
#4564
Bump androidPlugin from 8.5.1 to 8.5.2 by
@dependabot
in
#4567
Bump androidx.wear.tiles:tiles from 1.3.0 to 1.4.0 by
@dependabot
in
#4568
Bump androidx.work:work-runtime-ktx from 2.9.0 to 2.9.1 by
@dependabot
in
#4569
Full Changelog
:
2024.7.3...2024.8.3

📱 Home Assistant Companion for Android

Documentation

If you are looking for documentation around the companion applications check out the

Home Assistant Companion Documentation

. This will provide you instructions on using the applications.

Setup App Development Environment

Download and install

Android Studio

Download / clone this repository to a folder on your computer

Create a Firebase project at

Firebase Console

Create four Android apps, with following package names

io.homeassistant.companion.android

io.homeassistant.companion.android.debug

io.homeassistant.companion.android.minimal

io.homeassistant.companion.android.minimal.debug

Now download the

google-services.json

file and put it in the project's

/app

,

/automotive

and

/wear

folders. This file contains the configuration of the whole project (all four applications). (

You can also use the mock services file instead of generating your own

. The file should contain client IDs for all packages listed above for debugging to work properly.

If you do not generate your own file FCM push notification will never work, only websocket notifications will

)

Start Android Studio, open your source code folder and check if the Gradle build will be successful using Build/Make Module "App". You might have to install the right Android SDK via Tools/SDK Manager first.

Run

gradlew assembleDebug

to build all debug versions, this might take a while.

If the build is successful, you can run the app by doing the following: click

Run

->

Run 'app'

.

Connect your phone or create a new virtual device following on screen instruction

🎉

If you get stuck while setting up your own environment, you can ask questions in the

#devs_mobile_apps

channel on

Discord

.

Push Notifications

If you want to work on push notifications or use a development build with push notifications, please go the server side code

HERE

and deploy it to your firebase project. Once you have your androidV1 URL to the deployed service, set it in to your

${GRADLE_USER_HOME}/gradle.properties

file, e.g.:

homeAssistantAndroidPushUrl

=

mydomain.cloudfunctions.net/androidV1

You can also define the rate limit function URL, e.g.:

homeAssistantAndroidRateLimitUrl

=

mydomain.cloudfunctions.net/checkRateLimits

App Flavors

The Android app has both a full flavor that uses Google Play Services to offer features like location tracking and notifications. There is also a minimal flavor that does not require Google Play Services and can be found in the releases section. The minimal flavor does not have location tracking or notifications.

Building for publishing

To build the app for publishing, you will need to sign the app. To do this, do the following:

Create keystore containing keypair for debug application signing. In Android Studio: Menu/Build/Generate signed APK, then use a button to create new keystore. Remember the passwords and key alias. Default, the keystore must be named

release_keystore.keystore

and should be placed in the

home-assistant-Android/app

and

home-assistant-Android/wear

folder.

Set environmental variables used in

app/build.gradle.kts

:

KEYSTORE_PASSWORD

KEYSTORE_ALIAS

KEYSTORE_ALIAS_PASSWORD

KEYSTORE_PATH

(if your keystore is located differently than stated above)

Run

gradlew build

The signed APK is located in your build folder

Testing Dev Releases

We are using

Github Actions

to perform continuous integration both by unit testing, deploying dev releases to

Play Store Beta

and final releases to the

Play Store

when we release. To help test out a specific feature/fixes users can find the APK on the Actions page for each pull request, this debug APK can be installed side-by-side the production or beta builds.

Quality

We are using

ktlint

as our linter. You can run a check locally on your machine with:

./gradlew ktlintCheck

This commands runs on our CI to check if your PR passes all tests. So we strongly recommend running it before committing.

To run a check with an auto-format:

./gradlew ktlintFormat

Translating

The project currently uses

lokalise

to translate the application. If you are interested in helping translate go to the link and click start translating!

Generating a release to production

Go to the latest Pre-release and edit it

Uncheck the Pre-release box, check the Latest release box, and click Update release

This should cause the

Play Publish Production

Workflow to execute and should handle the rest for Google Play

Some platforms, such as the Amazon App Store, need to be updated manually

F-Droid uses the

version_code.txt

file of the latest release to detect a new production release and build it themselves, this may take some time