Home Assistant Companion Android App April 2021 Release

Hey Everyone! It’s time for the April 2021 Android release. Last month we wrote that we would be aligning our releases closer to Home Assistant core so here we are! Another month went by and the Android app has started to see more contributors coming along. Hopefully, you will join us next month as we can always use more contributors to move forward faster.

In-App Log Viewer

This release has a new feature that will make viewing and sharing the logs MUCH easier. Some of you may recall the large number of steps needed to get Android logs when you open issues. This usually involved installing Android Studio or another app and having to plug your device into a computer to grant some special ADB permissions. This was very difficult to get set up for the average user and just wasn’t user-friendly.

We’ve added a new option to the App Configuration called “Show and Share Logs”. It will show all the logs from our app, including debug logs to help troubleshoot issues such as when the location does not update or if the app is using the correct URL. You are not only able to view this log but also share and select from it so you can copy the logs to a GitHub issue for our team to look into.

![](upload://gzeHttxvuswNMsiqyjVQfppUWXv.png) Screenshot of In-App Log Viewer

Settings Improvements

We have had several improvements made to the overall design of the App Configuration pages to make better use of the space and add some neat features. First and foremost, every setting screen now has a new help icon taking you to the proper place in the documentation like location settings or even notifications. Just look for the new help icon at the top right-hand corner, if the page does not offer enough information.

As of this release the app now has a total of 71 sensors, given your device supports them all your number may be less. That is a lot of sensors and we don’t expect a lot of users to actually use them all. We have added 2 new features to make this page easier to navigate. You can now filter by showing only the enabled sensors to get rid of the sensors you don’t want to use, if you have all sensors enabled don’t expect to see this filter. You can also perform a search against the list of sensors to find one quickly and manage it.

Notification History now lets you search by the message that was sent to the device. Searching will bypass the filter options we have, which limits the view to the last 100 notifications. Filtering and delete options have been moved to the top right-hand corner to make better use of the space.

![](upload://6W8UkiMKZBafgFH8iV8MMyMiVqf.png) Screenshot of Sensor Search & Filter.


Sometimes when you open the app you may already know exactly where you want to go. You may find yourself on the same view often to see your cameras or give the nursery a quick look to make sure things are ok. You may even want to quickly see the history of an entity like when the door was last opened. In this release, we have introduced Android Shortcuts which will let you get to anywhere in the Home Assistant frontend quickly, directly from your home screen. Shortcuts will look like a separate app on the home screen allowing you to make them easily accessible and even place them into a folder for better organization. You can navigate to any Lovelace view or dashboard including other pages like the Shopping List. You can also navigate to any entity directly to get more information like the history or see the graph.

There are a few different shortcut types and in the nature of Home Assistant, we have opted not to add static shortcuts because they are static! We support dynamic shortcuts which will show up under the app long-press menu. Once you create a shortcut, you will be able to drag it onto your home screen. There is also support for pinned shortcuts that can be added automatically to your home screen without needing to drag the icon, given your device and launcher support pinned shortcuts. Check out the documentation for more details including known limitations.

![](upload://4kD8ts7vKZP0KnRB2ZtgpXYGWAw.png) Screenshot of Shortcuts

Other Changes

Here is a list of the other changes you may notice:

  • Battery Temperature Sensor
  • Notification command to turn on the screen
  • BLE Transmitter has a new setting to enable/disable the transmitter so the sensor can remain enabled. This new setting will correspond to the existing notification command.
  • High Accuracy mode has a new zone-based automation feature allowing you to trigger this mode faster. See the documentation for more details.

![](upload://t8cbaxzEcSfHw1pxAaUFBdVRxOx.png) Screenshot of High Accuracy Zoning.

  • Long-pressing an entity in Android’s Power Menu will now take you directly to the entity instead of the home page.
  • Covers that support setting the position are also supported in Android’s Power Menu.
  • Lots of fixes and improvements in all other areas of the app.

Big thank you to everyone involved. Please keep those bug reports and feature requests coming!


This is a companion discussion topic for the original entry at https://www.home-assistant.io/blog/2021/04/08/android-april-2021-release/

I cant get next alarm sensor to work. it has never worked for me

It seems like I don’t need to tap confirm button after unlocking the app with my face on Pixel 4. Thank you!

One important fix on this version is that now the app uses its own user-agent HomeAssistant/Android https://github.com/home-assistant/android/pull/1418 This was important because before it was using a generic one based on the framework the app uses (okhttp) and it was blocked in some deny-lists. Kudos to @dshokouhi for the fix!

1 Like

The high-accuracy zone can now be enabled if connected to BT devices and when entering a zone.

If I use both conditions, are they ORed or ANDed?

If, for example, I define that high-accuracy mode shall be enabled when connected to my car’s Bluetooth AND I define that high-accuracy mode shall be enabled when entering a 300 m zone around my home, must BOTH conditions be met for high-accuracy to be enabled, or will it be enabled also if I enter the home zone walking?

My preference would be AND (that I should both be driving AND entering the zone). I use this function to automatically open my garage cover when I arrive home in my car. I don’t want the garage cover to open if I’m coming home walking or biking. Others might want the OR function. Perhaps it should be selectable?

Thinking about it: Perhaps OR is better. I have a condition in my garage cover opening automation that ensures that the garage cover is only opened if my phone is connect to the car’s BT. So OR is preferred - for me :slight_smile:

EDIT: Typos… and additional thoughts…

EDIT2: Answering my own question:
Oh, RTFM! :nerd_face: It’s all there in the documentation: The two conditions are ORed.

Never mind, then, all is OK as far as I’m concerned. :smiley:

Is it just me or are groups (light groups for example) not supported in the power menu?

Actually just made a feature request on github but after clicking “submit issue” I get only:


might be a github issue, maybe try again and ensure you are logged into github?

What device? if its Samsung or Xiaomi you will need to avoid using their clock/calendar apps as they are known to abuse the android API that we use. Google Clock and Sleep as Android are good apps that don’t abuse the API. There is also an allow list setting for you to block unwanted updates.

Command screen off :grin:?

thats what the screen time out setting is for :sweat_smile: but it didnt seem like an easy way to do that given that for this we are acquiring a wake lock on the device and then letting go soon after. Its just to wake the device.

I am trying to get shortcuts going, and I’ve got ones for my main lovelace views and shopping list. I cannot, however, figure out how to do a shortcut to my other dashboard.

How do I determine the path to my additional dashboard? And do I still use /lovelace/ or just use the dashboard path?

It’s really the shortcut I would use the most and it’s killing me that I can’t figure this out.

use the entire path after the domain so if your url is like https://example.com/lovelace/test you will use /lovelace/test

But the idea is to use Homeassistant in background with a tablet with Touch portal a stream deck when the Pc on screen wake :+1: PC off i use tasker but Run every 2 min, with Homeassistant would be better :grin:

Anyone else getting extreme slowness/lag when editing Automations or Scripts with the android app?Can’t say whether it started happening before or after the latest update since I rarely edit this stuff via the app. Everything else seems to respond normally…it’s just editing these 2 are problematic.

Edit: seems like it’s not all automations or scripts…just my “longer” one and more specifically newer ones that include the new Target interface. Any automation or script with this part of the UI (pictured below) causes extreme lag on my Samasung Note 20.

1 Like

So teh app is only a webview to the HA frontend. Check if you can reproduce in Chrome for Android, also ensure android system webview is fully up to date.

Yup…doesn’t seem as bad but definitely laggy as heck in chrome too.
Webview appears to be up to date.

1 Like

I am also experiencing this and it is also happening in Chrome for Windows. But, as mentioned, only on the longer scripts.

1 Like

For me, Windows Chrome works fine…it’s just on my phone.

yea this all sounds like a frontend issue, may want to open an issue there

1 Like