# OH Drive - A new experimental openHAB app for Android Auto (APK + Sitemap Examples)

**URL:** <https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759>\
**Category:** Android App\
**Created:** [October 23, 2026, 9:58am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759 "2026-10-23T09:58:42Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 23, 2026, 9:58am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/1 "2026-10-23T09:58:42Z")

</div>

Hi everyone,

First of all, special thanks and greetings to @scooter_seh for his idea and the solution.  
As I cannot develop code, ChatGPT was helping me with Android Studio and the stuff around.

I would like to share a small personal project that I have been working on: **OH Drive** , an experimental Android Auto application for openHAB.

The idea was simple: I wanted to access selected openHAB devices and information directly from my car’s Android Auto display, using a clean interface with large buttons and minimal interaction.

After several development and testing sessions, OH Drive has reached **version 1.6**. I have tested it using the Android Auto Desktop Head Unit (DHU) and in my Mercedes with a Samsung Galaxy S23 Ultra.

I thought other openHAB enthusiasts might enjoy experimenting with it as well.

## What is OH Drive?

OH Drive is a standalone Android Auto application that connects to an existing openHAB installation through the REST API.

Its main feature is a **dynamically generated Android Auto interface based on a dedicated openHAB Sitemap**.

You decide which Items appear in your car by editing the Sitemap on your openHAB server.

There is no need to rebuild the APK whenever you add, remove, or rename an Item.

### Current features in version 1.6

- Dynamic loading of selected openHAB Sitemap entries

- Android Auto grid layout with large buttons and icons  
The icon are here listet with their names:  
[Icons | openHAB](https://www.openhab.org/docs/configuration/iconsets/classic/)

- Display of sensor values, temperatures, weather information and other Item states

- Switch controls with visual command feedback

- Special impulse handling for relay-based controls

- Roller shutter submenu with **Up, Stop and Down**

- Automatic roller shutter position updates approximately every two seconds while the submenu is open

- Live monitoring of configured relay events

- Visual command feedback: orange hourglass, green checkmark and red error symbol

- Automatic German/English interface language selection based on the Android system language

- Custom Sitemap labels are preserved exactly as configured by the user

The application uses openHAB’s existing REST API and does not require an additional openHAB binding.

## How is OH Drive different from OH Auto?

OH Drive is not intended to replace OH Auto or compete with its development.

My focus was specifically on a **Sitemap-driven approach**.

Instead of maintaining a separate, fixed selection of devices inside the Android application, OH Drive reads a dedicated Sitemap and builds its Android Auto interface dynamically.

For example, adding a temperature Item or another supported switch only requires changing the Sitemap on the openHAB server.

Other particular design choices include:

- A dedicated roller shutter control screen

- A simple dashboard with dynamically loaded icons

- Live relay feedback and command status indicators

- German and English interface localization

I have not performed a comprehensive feature-by-feature comparison with the latest OH Auto release. I would be interested to hear from users who have experience with both approaches.

## Example Sitemap

Create a file called `ohdrive.sitemap` in your openHAB Sitemap directory.

Here is a simplified example using fictional Item names:

```java
sitemap ohdrive label="OH Drive"
{
    Text item=Outdoor_Temperature
        label="Outside temperature [%.1f °C]"
        icon="temperature"

    Text item=Weather_Condition
        label="Weather [%s]"
        icon="sun"

    Switch item=Hall_Power
        label="Hall power"
        icon="poweroutlet"

    Slider item=Bedroom_Roller
        label="Bedroom roller shutter"
        icon="rollershutter"
}

```

Replace these Item names with your own existing openHAB Items.

The Sitemap controls the displayed Item selection and labels. OH Drive currently supports a selected subset of Sitemap widgets, not the complete openHAB Sitemap specification.

**Important:** Special impulse relay handling in this version uses predefined Item names in the application. It is not a generic, automatically configurable safety system for arbitrary garage doors or other actuators. Do not assume that simply adding a relay to the Sitemap enables the same safeguards.

## Installation

OH Drive is currently distributed as an experimental APK, not through the Google Play Store.

For my setup, installation requires **AA Enabler** to make the application available in Android Auto.

General procedure:

1. Download the OH Drive APK.

2. Install it using the AA Enabler procedure.

3. Configure the connection to your openHAB server.

4. Create the dedicated `ohdrive.sitemap`.

5. Start Android Auto and open OH Drive.

AA Enabler is a third-party tool, is not included with OH Drive, and may be restricted or blocked by Android or Google Play Protect. Compatibility is not guaranteed and depends on the Android and Android Auto versions.

Please use a trusted source for any installation tools and understand the risks of sideloading applications.

## Language support

OH Drive 1.6 includes **English and German** interface resources.

The application automatically uses the appropriate language based on the Android system settings.

However, labels coming from the openHAB Sitemap are deliberately **not translated**. Each user can define those labels in their preferred language.

## Testing and limitations

This is an early experimental version developed and tested primarily for my personal environment.

It has been tested with:

- openHAB 5.2.1

- Samsung Galaxy S23 Ultra

- Android 16

- Android Auto Desktop Head Unit

- Mercedes Android Auto display

- An active, working VPN Tunnel, that the you mobile have direct access to your OH Server

Other Android devices, head units, openHAB versions and network configurations have not been comprehensively tested.

A network connection to the openHAB server is required. Remote access, if used, must be configured and secured by the user.

The roller shutter position display reflects the state reported by openHAB. Depending on the openHAB Item configuration, optimistic state updates may temporarily display the requested end position rather than the actual physical position.

## Important disclaimer – experimental software, use entirely at your own risk

**OH Drive is an unofficial personal hobby project, provided for fun, experimentation and educational purposes only.**

It is not an official openHAB application and is not affiliated with or endorsed by the openHAB project, Google, Android Auto or any vehicle manufacturer.

The application and APK are provided **AS IS** , without any warranty or guarantee of functionality, reliability, availability, compatibility, safety or fitness for a particular purpose.

I accept no responsibility or liability, to the extent permitted by applicable law, for damage, loss, malfunction, unintended device activation, incorrect status information or other consequences arising from installation or use.

**Do not rely on OH Drive for safety-critical functions.**

Controlling physical equipment such as garage doors, gates, shutters or other actuators can be dangerous. Software feedback does not guarantee the actual physical state of a device.

Users are solely responsible for evaluating their own configuration, implementing appropriate independent safety measures and complying with applicable laws and road-safety requirements.

Never operate the application in a way that distracts you while driving.

If you decide to try OH Drive, please understand that it is experimental software and use it entirely at your own risk.

## Downloads and examples

I am attaching the following files to this post:

- `ohdrive.sitemap` – example Sitemap

- Screenshots showing the main dashboard and roller shutter controls

I would be happy to hear whether the application works in other Android Auto environments and what improvements might be useful.

This started as a fun personal experiment. Perhaps it will also be interesting for other openHAB users.

Have fun experimenting!

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/9/3/93dd29bbb08e0275d1657d64dd75ac732d1490f3.jpeg)

 ![image](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/3/2/3224a9833b07e9c7d4084af59aa4035fad379e75.png)

Tell me if you have interesst, you will get the apk it via PM

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 23, 2026, 4:30pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/2 "2026-10-23T16:30:10Z")

</div>

# OH Drive 1.9 – Experimental openHAB Client for Android Auto

Hi everyone,

I’d like to share a small experimental project I’ve been working on: **OH Drive** , an Android Auto client for openHAB.

The idea is simple: provide access to selected openHAB items directly from the Android Auto display, using a dedicated sitemap.

The application currently supports displaying item states, controlling switches, sending configured impulse commands, and operating rollershutters and awnings.

## New in version 1.9 – Rollershutters and awnings

OH Drive now supports different display and control descriptions for **rollershutters and awnings** , even though both use the standard openHAB `Rollershutter` item type.

The distinction is configured through an optional OH Drive-specific marker in the sitemap label.

For example:

**Rollershutter:**

```java
Slider item=LivingRoom_Shutter label="Living Room Shutter [%s]" icon="rollershutter"

```

**Awning (0% = open, 100% = closed):**

```java
Slider item=Terrace_Awning label="Terrace Awning [ohdrive:markise:0offen] [%s]" icon="rollershutter"

```

**Awning with reversed percentage interpretation:**

```java
Slider item=Terrace_Awning label="Terrace Awning [ohdrive:markise:100offen] [%s]" icon="rollershutter"

```

The optional markers are:

- `[ohdrive:markise:0offen]` – Awning, 0% open and 100% closed

- `[ohdrive:markise:100offen]` – Awning, 100% open and 0% closed

- `[ohdrive:rollo:0offen]` – Rollershutter, 0% open and 100% closed

- `[ohdrive:rollo:100offen]` – Rollershutter, 100% open and 0% closed

Without a marker, OH Drive uses its existing rollershutter behaviour.

These markers are interpreted by OH Drive and hidden from the displayed item title.

### Independent icon selection

**Icons are not used to identify the device type.**

Users can select any supported openHAB Classic icon for their items. An awning does not need a special icon, and a rollershutter does not need to use `rollershutter`.

This keeps the sitemap flexible and compatible with existing openHAB installations.

### Control interface

Both device types use the standard openHAB commands:

- `UP`

- `STOP`

- `DOWN`

For awnings, OH Drive provides descriptions such as **Extend awning** and **Retract awning**. For rollershutters, it uses the corresponding raise/lower descriptions.

The underlying commands are not modified by the device marker or percentage setting.

The dashboard also displays the position in a human-readable format, such as _Fully open_, _81% closed_, or _Fully closed_.

## Other features

OH Drive currently includes:

- A dashboard generated from a dedicated openHAB sitemap

- Display of temperatures, item states and other sensor values

- Switch and impulse-command support

- Rollershutter and awning controls

- Position updates for rollershutter items

- German and English interface texts

- Support for connecting to an openHAB server over an existing network or VPN connection

The application is intended to work with standard openHAB REST API functionality.

## Installation and testing

This is currently an **experimental APK** , not a Google Play release.

My testing setup includes Android 16, Android Auto, the Desktop Head Unit emulator, and openHAB 5.2.x.

Installation in my test environment uses AA Enabler. This is not an officially approved Android Auto distribution method, and compatibility with other phones, Android Auto versions, or vehicles is not guaranteed.

Version 1.9 has been tested in the Android Auto emulator for dashboard rendering, awning recognition, icon independence, and the displayed control descriptions.

The reversed percentage configuration and actual movement directions have not yet been fully validated across different devices.

## Safety and limitations

Please consider this project experimental.

It can send real commands to connected devices. Be particularly careful with garage doors, gates, shutters, awnings and other moving equipment.

Do not operate equipment unless you can safely observe it, and do not interact with the application while driving.

The project is shared for testing and discussion, without any guarantee of suitability, reliability, compatibility or safety, to the extent permitted by applicable law.

## Feedback welcome

I’m interested in feedback from other openHAB users, particularly regarding:

- Different rollershutter and awning configurations

- Sitemap compatibility

- Icon handling

- Android Auto behaviour across different devices

- Possible improvements for a future public release

This is a personal experimental project developed for fun and to explore how openHAB can be integrated into Android Auto.

Thanks, and I look forward to your feedback!

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 9:51am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/3 "2026-10-26T09:51:42Z")

</div>

First of all thanks for the development… I would love to test it, but, where can I found the Apk file? There is also an “official” place for AA Enabler?

Thanks in advance!

Ruben

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 11:48am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/4 "2026-10-26T11:48:47Z")

</div>

Hello please check the current latest version and the readme here:

> **[GitHub - scheuerer/alexa-audio](https://github.com/scheuerer/alexa-audio)**
>
> Contribute to scheuerer/alexa-audio development by creating an account on GitHub.

AAenabler could be found here:

> **[GitHub - malebuffy/AAEnabler: Install Android Auto apps](https://github.com/malebuffy/AAEnabler)**
>
> Install Android Auto apps

---

<div class="post-metadata">

**Author:** ![Baschtlwaschtl](https://community.openhab.org/user_avatar/community.openhab.org/baschtlwaschtl/32/70481_2.png) [@Baschtlwaschtl](https://community.openhab.org/u/Baschtlwaschtl)\
**Post date:** [October 26, 2026, 1:17pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/5 "2026-10-26T13:17:56Z")

</div>

Oh. Version 2.7..

Nice.

I’ll test…

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 2:14pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/6 "2026-10-26T14:14:56Z")

</div>

Same feature set as 2.5, was trying to do some development for a camera support with  
a image to be take and shown under AA, but the size is to small to be usefull under AA.

→ Newest version 2.7 🙂

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 4:36pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/7 "2026-10-26T16:36:29Z")

</div>

I have installed with no problem… but I don’t understand german… so… I don’t know what the app is saying to me ☹ 😅

On the other part, I have put the myopenhab cloud as server, but it doesn’t work and there aren’t any place for auth… so, I think that actually only works with local no auth or some VPN. Is that true?

Thanks in any case.

Ruben

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 5:09pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/8 "2026-10-26T17:09:12Z")

</div>

Hello,

The app speaks German and English, depending what language you are using on your phone.

But all the Icon name can be used in whatever language you would like.

All information comes from the ohdrive.sitemap file were you OH installation is stored.

e.g. /etc/openhab/sitemaps/ohdrive.sitemap

The definition of the items is done only in the file on you OH installation

Now the App only works when you have an active VPN connection to you OH installation.

A cloud connection is not implemented now. Perhaps coming later.

So, you need to a VPM establish to your local network, where you OH installation is running, e.g. with wire guard, etc.

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 7:32pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/9 "2026-10-26T19:32:27Z")

</div>

I will explain my test. My phone is a Xiaomi 14T Pro, I have installed version 2.7 of OH Drive using AA Enabler. All works correctly during installations.

My phone uses catalan as primary language, also spanish and english as prefered languages, but OH Drive appears on german language, so I don’t know what it says 😅. I have created a sample sitemap bassed on documentation sample but using my items.

I have put my local OH server on OH Auto configuration, it seems to work as “Verbindung prüfen” display a “green message” (Although I use OH cloud, also have Tailscale, so I think could use it outside local network).

In any case, the problem now is that the program doesn’t appear on Android Auto as allowed application. Firstly it doesn’t appear on car screen apps, and I have gone to Android Auto apps selection and OH Auto doesn’t appear.

Android Auto version is 17.9.664044 and Android 16 (HyperOS 3.0.303.0)

I hope that could be used to improve app.

Thanks

Ruben

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 7:51pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/10 "2026-10-26T19:51:23Z")

</div>

Use the new 2.8 of OH Drive.  
I made a new version, were you can select the language you want to use. at the moment, German and English is supported.  
To see the App under Android Auto, you need to copy the file to you phone.  
To install the ohdrive, that it will be visible in the AA launcher, you need to install it via the App called AAenabler. Only installation with this App the ohdrive will get visible under Android Auto.  
Tailscale is a classic VPN tunnel App, which brings you mobile into you homenetwork, as you would be at home and connected via WIFI to you local network. It is, than should work.  
You need to have access from your mobile via classic IP adresses.  
e.g. 192.168.0.10 is your OH server, use this IP in OHdrive as your server IP.

Overseen, that you have already installed via AAenabler…

Have you enabled your AA in developer mode, and have selected, allow unknown sources?

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 8:14pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/11 "2026-10-26T20:14:44Z")

</div>

I will try the new version later, thanks.

And yes, I have installed using AA Enabler with no problems (my phone has developer mode because I teach .NET MAUI and tests apps in my phone).

Can I check something more?

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 8:23pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/12 "2026-10-26T20:23:13Z")

</div>

I send you some snapshots.

Installed again with AAEnabler. The language selector didn’t work for me neither closing and reopening it. And continue without appearing on Android Auto allowed apps.

 ![Screenshot_2026-10-26-21-16-59-175_com.aaenabler.app](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/f/6/f6cb99e64658e49edb6d1870861e9e92ed1ff9e5.jpeg)

 ![Screenshot_2026-10-26-21-19-38-884_com.google.android.projection.gearhead](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/3/1/319a5b9dba665bd5a8e2b5f53c677899a27dc25c.jpeg)

 ![Screenshot_2026-10-26-21-18-57-327_de.ohdrive.app](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/5/8/58c45455f73ea7b62695761977dd308c4dd104eb.jpeg)

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 8:23pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/13 "2026-10-26T20:23:45Z")

</div>

Please try with 2.8, but this will solve your not visible problem in AA launcher.  
Perhaps ChatGPT could help here…  
For me it works with A16 on my older SG23U.

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 8:43pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/14 "2026-10-26T20:43:25Z")

</div>

As you can see on snapshots… last test was with 2.8 ☹  
Maybe is mandatory to bought AAEnabler licence to work it?

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 26, 2026, 8:58pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/15 "2026-10-26T20:58:35Z")

</div>

Hi,

First of all, thank you very much for testing OH Drive and for providing such detailed feedback and screenshots! I really appreciate your help.

I’ve investigated the Android Auto visibility issue and found something interesting in the **AAEnabler GitHub project**.

It appears that AAEnabler can successfully recognize and install an Android Auto-compatible APK without necessarily guaranteeing that Android Auto will display the application.

There are also reports of similar problems on **Xiaomi devices running HyperOS** , where applications installed through AAEnabler do not appear in the Android Auto app launcher.

This could explain what you’re experiencing with your Xiaomi 14T Pro running Android 16 and HyperOS 3.

**Could you please check one thing?**

In Android Auto’s developer settings, make sure **“Unknown sources”** is enabled. This is different from the regular Android setting that allows APK installation.

If it is already enabled, the issue might be related to Xiaomi’s installation process or HyperOS restrictions rather than OH Drive itself.

I’ve also identified the language issue you reported. OH Drive 2.8 introduces German and English language selection, but your screenshots suggest that the selected language isn’t being applied correctly to the settings screen. I’ll investigate this for the next update.

For unsupported system languages such as Catalan, OH Drive should automatically fall back to English rather than German.

For now, I don’t want to change the Android Auto integration without understanding the underlying issue.

Thanks again for your support and for helping improve OH Drive!

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 26, 2026, 9:59pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/16 "2026-10-26T21:59:36Z")

</div>

Last check: I have checked the option of “Allow unkown sources” in Android Auto. I don’t know that that option exists! I have to enable “Developer Mode” in Android Auto that is different from “Developer Mode” in the phone.

Reinstalled version 2.8, and now, surpringnsly, the app allows me to change language and save it, so now is in english.

But actlually the App still doesn’t appear on Android Auto “apps to show”. I have rebooted the phone, but still doesn’t show in that list (second snapshow before). Tomorrow test with the car itself.

Ruben  
PD: Edited: Tested on the car and also doesn’t appear ☹

Edit 2; very strange, now app appears at Android Auto version info that in theory displays all AA enabled apps… But still refuses to show it. Attach screenshot.

 ![Screenshot_2026-10-26-23-12-05-222_com.google.android.projection.gearhead](https://community-openhab-org.s3.dualstack.eu-central-1.amazonaws.com/original/3X/2/b/2b3ec43121a77c62193d1ee3f15f6cfda9edbf41.jpeg)

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 27, 2026, 7:13am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/17 "2026-10-27T07:13:51Z")

</div>

## Please check the OH Drive installation on your Xiaomi phone

We’re comparing your phone with mine because OH Drive 2.8 appears in Android Auto’s **Customize launcher** on my phone, but not on yours. On my phone, Android reports OH Drive as installed by Google Play, version 2.8, and as a debuggable build. The same checks on your Xiaomi will show whether your installation source or app build is different. If they match, we can investigate a Xiaomi or Android Auto-specific issue next.

This check only reads app information. It does not change or reinstall anything. You do **not** need Android Studio.

### 1. Download ADB for Windows

Download Google’s official **SDK Platform-Tools for Windows** from the [Android Developers website](https://developer.android.com/tools/releases/platform-tools?utm_source=chatgpt.com). The ZIP includes `adb.exe`. [developer.android.com](https://developer.android.com/tools/releases/platform-tools?utm_source=chatgpt.com)

Extract the ZIP. Open the extracted `platform-tools` folder in File Explorer, click the address bar, type `powershell`, and press **Enter**. PowerShell should open in that folder.

### 2. Enable USB debugging on your phone

On your Xiaomi:

1. Open **Settings** and search for **Developer options**. If you can’t find it, go to **About phone** and tap the **OS version/HyperOS version** repeatedly until Developer options are enabled. The exact menu names can vary.
2. Open **Developer options** and turn on **USB debugging**.
3. Connect the phone to your computer with a USB data cable and unlock the phone.
4. If prompted, allow USB debugging for this computer.

This is the phone’s Developer options, separate from Android Auto’s Developer Mode. Google’s ADB instructions describe enabling USB debugging and accepting the phone’s authorization prompt. [developer.android.com](https://developer.android.com/tools/adb?authuser=1&utm_source=chatgpt.com)

### 3. Confirm that ADB sees the phone

In the PowerShell window opened in the `platform-tools` folder, run:

```auto
.\adb.exe devices

```

The phone should appear with the status `device`. If the status is `unauthorized`, unlock the phone and accept the USB-debugging prompt, then run the command again. If no device appears, try a different USB data cable or USB port.

### 4. Collect the OH Drive information

Run these commands one at a time in the same PowerShell window:

```auto
.\adb.exe shell pm list packages -i | findstr /i "de.ohdrive.app"

```

```auto
.\adb.exe shell dumpsys package de.ohdrive.app | findstr /i "versionName versionCode pkgFlags"

```

```auto
.\adb.exe shell run-as de.ohdrive.app id

```

Please send me the output of these three commands. You can leave out the device serial number shown by `adb devices`.

We’re comparing the **installer** , **version** , and **build flags**. If they match my phone’s results, the way the app was installed is less likely to explain why it is missing from your launcher. If they differ, that gives us a specific lead.

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 27, 2026, 8:59am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/18 "2026-10-27T08:59:03Z")

</div>

I have sent that all information to you. I hope it can help.

Ruben

---

<div class="post-metadata">

**Author:** ![Ruben\_Perez](https://community.openhab.org/user_avatar/community.openhab.org/ruben_perez/32/36021_2.png) [@Ruben\_Perez](https://community.openhab.org/u/Ruben_Perez)\
**Post date:** [October 28, 2026, 3:57pm UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/19 "2026-10-28T15:57:07Z")

</div>

I have just updated to 3.0 version… much more things on app… but it still refuse to show on my Xiaomi phone… are there other people with same problem?

Thanks @scheuerer for the development!

Ruben

Edited: I have read the change log… and the problem is still present. If you need or if I could help you with more tests and logs, tell me. If you want, you can send me a “logging debug version” that can save extra informatión to resolve the issue.

---

<div class="post-metadata">

**Author:** ![scheuerer](https://community.openhab.org/user_avatar/community.openhab.org/scheuerer/32/47609_2.png) [@scheuerer](https://community.openhab.org/u/scheuerer)\
**Post date:** [October 29, 2026, 8:05am UTC](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759/20 "2026-10-29T08:05:52Z")

</div>

Hi Ruben,

Just a quick update!

I’ve opened a new issue in the AAEnabler GitHub project regarding the problem with OHDrive on your Xiaomi 14T Pro.

I’ve included all the technical information and diagnostic results from our previous tests, including the comparison between your Xiaomi and my Samsung Galaxy S23 Ultra.

I also explained that OHDrive works perfectly on my Samsung but is not recognized by Android Auto on your Xiaomi, despite being installed successfully.

I’ve asked the AAEnabler developer to investigate whether this could be related to HyperOS 3, Android Auto, or the installation process, and whether a new version of AAEnabler might solve the problem.

I also mentioned that you would probably be happy to support the developer with additional tests and logs if needed. I hope that’s okay with you!

Let’s see what the developer says. I’ll keep you informed, and hopefully we can solve this together.

Thanks again for all your help and testing!

> <https://github.com/malebuffy/AAEnabler/issues/11>
>
> \<html\>
> \<body\>
> \<p data-pm-slice="1 1 \[\]"\>\<span\>We are developing \</span\>\<strong\>\<…span\>OHDrive\</span\>\</strong\>\<span\>, an Android Auto application that allows users to monitor and control their openHAB smart home directly from their vehicle.\</span\>\</p\>\<p\>\<span\>During our testing, we discovered a compatibility issue between two Android 16 devices.\</span\>\</p\>\<p\>\<strong\>\<span\>OHDrive works successfully on a Samsung Galaxy S23 Ultra, but it does not appear in Android Auto on a Xiaomi 14T Pro, despite successful installation using AAEnabler.\</span\>\</strong\>\</p\>\<p\>\<span\>Together with our tester Ruben, we have already performed several ADB diagnostics and compared both devices.\</span\>\</p\>\<p\>\<span\>We would appreciate your help investigating whether AAEnabler could be updated to resolve this compatibility issue.\</span\>\</p\>\<h2\>\<span\>1. Device comparison\</span\>\</h2\>
> Component | Working device | Non-working device
> \-- | -- | --
> Smartphone | Samsung Galaxy S23 Ultra | Xiaomi 14T Pro
> Model | SM-S918B | Xiaomi 14T Pro
> Android | 16 | 16 (API 36)
> Manufacturer OS | Samsung One UI | HyperOS 3.0.303.0
> OS build | — | OS3.0.303.0.WNNEUXM
> Android Auto | 18.1.164344-release.daily | 17.9.664044-release
> Android Auto versionCode | 181164344 | 179664044
> OHDrive | 2.8 and later versions tested | 2.7 / 2.8
> Android Auto visibility | Working | Not visible
> openHAB connection | Working | Working in the phone app
> 
> \<p\>\<span\>Both devices run Android 16, but use different manufacturer software and Android Auto versions.\</span\>\</p\>\<h2\>\<span\>2. ADB installation diagnostics\</span\>\</h2\>\<p\>\<span\>We checked the installation information using the following commands:\</span\>\</p\>\<pre\>\<code class="language-powershell"\>\<span\>adb shell pm list packages -i | findstr /i "de.ohdrive.app"
> 
> adb shell dumpsys package de.ohdrive.app | findstr /i "installerPackageName initiatingPackageName originatingPackageName"
> 
> adb shell dumpsys package de.ohdrive.app | findstr /i "versionName versionCode"
> 
> adb shell settings get global development\_settings\_enabled\</span\>\</code\>\</pre\>\<h3\>\<span\>Samsung Galaxy S23 Ultra – Working\</span\>\</h3\>\<pre\>\<code class="language-text"\>\<span\>package:de.ohdrive.app
> installer=com.android.vending
> 
> versionCode=26 minSdk=29 targetSdk=35
> versionName=2.8\</span\>\</code\>\</pre\>\<p\>\<span\>OHDrive is recognized by Android Auto and can be launched successfully.\</span\>\</p\>\<p\>\<span\>The application connects to openHAB, displays live values and executes commands.\</span\>\</p\>\<h3\>\<span\>Xiaomi 14T Pro – Not working\</span\>\</h3\>\<pre\>\<code class="language-text"\>\<span\>installerPackageName=com.google.android.packageinstaller
> initiatingPackageName=com.google.android.packageinstaller
> originatingPackageName=com.aaenabler.app\</span\>\</code\>\</pre\>\<p\>\<span\>Android developer settings:\</span\>\</p\>\<pre\>\<code class="language-text"\>\<span\>development\_settings\_enabled=1\</span\>\</code\>\</pre\>\<p\>\<span\>OHDrive is installed, and its Android Auto CarAppService is registered, but the application does not appear in Android Auto.\</span\>\</p\>\<p\>\<span\>The local openHAB connection works, so the problem does not appear to be related to openHAB server connectivity.\</span\>\</p\>\<h2\>\<span\>3. Tests already performed\</span\>\</h2\>\<p\>\<strong\>\<span\>Samsung Galaxy S23 Ultra\</span\>\</strong\>\</p\>\<ul data-spread="false"\>\<li\>\<p\>\<span\>OHDrive installation verified with ADB.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Android Auto developer mode enabled.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Unknown sources enabled in Android Auto developer settings.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Android Auto recognizes OHDrive.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Successful tests with the Android Auto Headunit Emulator.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Successful operation with Wireless Android Auto.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>openHAB sensor values displayed correctly.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Smart home commands successfully executed.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Later OHDrive versions also tested successfully.\</span\>\</p\>\</li\>\</ul\>\<p\>\<strong\>\<span\>Xiaomi 14T Pro – Ruben\</span\>\</strong\>\</p\>\<ul data-spread="false"\>\<li\>\<p\>\<span\>OHDrive installed using AAEnabler.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Installation completed without reported errors.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Android developer settings enabled.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>openHAB connection tested successfully.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Android Auto application visibility investigated.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>ADB package installation information collected.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>CarAppService registration checked.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Device and Android Auto version information collected.\</span\>\</p\>\</li\>\</ul\>\<p\>\<span\>Despite these checks, OHDrive does not appear in Android Auto on the Xiaomi device.\</span\>\</p\>\<h2\>\<span\>4. Possible causes\</span\>\</h2\>\<p\>\<span\>We suspect that the issue could be related to one or more of the following:\</span\>\</p\>\<ol data-spread="false" start="1"\>\<li\>\<p\>\<span\>Differences in how Samsung One UI and Xiaomi HyperOS handle sideloaded Android Auto applications.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Installer package identification and installation-source handling.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Compatibility between AAEnabler and HyperOS 3.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Changes in recent Android Auto versions.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Additional application restrictions introduced by Xiaomi.\</span\>\</p\>\</li\>\</ol\>\<p\>\<span\>One interesting difference is the installer information.\</span\>\</p\>\<p\>\<span\>On the Samsung device, the installer is reported as:\</span\>\</p\>\<pre\>\<code class="language-text"\>\<span\>com.android.vending\</span\>\</code\>\</pre\>\<p\>\<span\>On Ruben's Xiaomi device, the installation originates from AAEnabler:\</span\>\</p\>\<pre\>\<code class="language-text"\>\<span\>com.aaenabler.app\</span\>\</code\>\</pre\>\<p\>\<span\>We do not know whether this difference is responsible for the issue, but it may be worth investigating.\</span\>\</p\>\<p\>\<span\>The Android Auto versions also differ, so we cannot yet isolate AAEnabler as the root cause.\</span\>\</p\>\<h2\>\<span\>5. Request to the AAEnabler developer\</span\>\</h2\>\<p\>\<span\>Could you please investigate whether AAEnabler requires an update for newer Xiaomi devices running HyperOS 3 and Android 16?\</span\>\</p\>\<p\>\<span\>In particular, we would appreciate your assessment of:\</span\>\</p\>\<ul data-spread="false"\>\<li\>\<p\>\<span\>Whether AAEnabler correctly enables Android Auto applications on HyperOS 3.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Whether the installation-source information affects Android Auto application recognition.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Whether Xiaomi-specific restrictions require additional handling.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Whether a modified or experimental AAEnabler version could resolve the problem.\</span\>\</p\>\</li\>\</ul\>\<p\>\<strong\>\<span\>If you are willing to investigate this, we would be happy to help test a new AAEnabler build.\</span\>\</strong\>\</p\>\<p\>\<span\>Ruben, the owner of the Xiaomi 14T Pro, has already provided valuable diagnostic information and would very likely be willing to assist with additional tests, ADB logs and verification.\</span\>\</p\>\<p\>\<span\>I can coordinate the tests on our Samsung Galaxy S23 Ultra and compare the results.\</span\>\</p\>\<h2\>\<span\>6. About OHDrive\</span\>\</h2\>\<p\>\<span\>OHDrive is an Android Auto application developed for the openHAB smart home platform.\</span\>\</p\>\<p\>\<span\>Its features include:\</span\>\</p\>\<ul data-spread="false"\>\<li\>\<p\>\<span\>Displaying openHAB sensor values, such as temperature and rain status.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Controlling switches, garage doors and gates.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Operating roller shutters and other smart home devices.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Displaying camera-related information.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Configurable openHAB sitemap integration.\</span\>\</p\>\</li\>\<li\>\<p\>\<span\>Local and remote openHAB connectivity, including myopenHAB Cloud.\</span\>\</p\>\</li\>\</ul\>\<p\>\<span\>OHDrive is intended to be made available to the wider openHAB community.\</span\>\</p\>\<p\>\<span\>Our objective is to make it usable on as many compatible Android Auto devices as possible.\</span\>\</p\>\<h2\>\<span\>7. Conclusion\</span\>\</h2\>\<p\>\<span\>We already have one fully working Android 16 device and one Xiaomi Android 16 device where the application cannot be launched through Android Auto.\</span\>\</p\>\<p\>\<span\>This provides a useful starting point for identifying possible differences in AAEnabler compatibility.\</span\>\</p\>\<p\>\<span\>We would greatly appreciate your technical assessment and would be happy to cooperate on a possible fix.\</span\>\</p\>\<p\>\<span\>Thank you for your work on AAEnabler and for supporting the Android Auto developer community!\</span\>\</p\>
> \</body\>
> \</html\>

[Next page](https://community.openhab.org/t/oh-drive-a-new-experimental-openhab-app-for-android-auto-apk-sitemap-examples/170759.md?page=2)