Home Assistant Companion Android App Release 3.0.0

taikapanu · November 10, 2020, 6:23pm

Makes me want to upgrade the phone
This hobby is getting expensive.

sbmlat · November 11, 2020, 4:16am

I found the issue. In the previous update, I didn’t change the device name.

There are 7 sensors starting with sm_g981u1

battery_level, battery_state, bluetooth_connection, light_sensor, next_alarm, storage

In the next update, I changed the device name. Now, I noticed 11 sensors starting with myphone_

audio, battery_health, charger_type, detected_activity, do not disturb,
external storage, geocode location, last reboot, pressure, proximity, steps

How do I reset all these sensors?

dshokouhi · November 11, 2020, 4:44am

you have to start fresh and set the device name during onboarding, then enable the sensors you want and everything will have the name you expect: https://companion.home-assistant.io/docs/troubleshooting/faqs/#starting-fresh-with-the-android-app

davegravy · November 12, 2020, 2:09am

Love the update and the app in general.

Any chance of getting a volume slider on the new mediaplayer widget?

flyize · November 12, 2020, 9:33pm

Since the new app, I’ve been having an odd issue. My phone, which is on the same network as HA, is unable to connect. The error I get is ERR_CONNECTION_REFUSED. What am I doing wrong?

sender · November 13, 2020, 8:22am

Hi, is there any option in the android app to have it installed but not controlled by the owner. I have 2 tablets for my children and I want to automate (send voice reminders) some rules. I want to use the apps voice tts for it thus it has to be installed. But since RBAC is not there and custom header was killed I want to restrict any access to the interface of the app. How can I do that?

Hellis81 · November 13, 2020, 9:00am

Password protect the app.
It’s in the settings.

sender · November 13, 2020, 9:03am

Thats not an option if the overall password setting for the android device is not enabled (it’s a kids device)

Hellis81 · November 13, 2020, 9:07am

I didn’t know that. I have just seen the setting.
But now I just tested it and it’s a bit odd.

When I enable the lock I have to put my finger on the reader.
But when I toggle the password off I don’t have to put my finger on the reader.

Generally I would say that enabling a password is less of a threat than disabling it. So shouldn’t the verification be the other way around, or both?

sender · November 13, 2020, 9:16am

I would like to see some sort of “kids mode”/“client only” mode in which I can have the client installed but not controlled…

rct · November 13, 2020, 2:52pm

How difficult would it be to get this app into the Amazon App Store for installation on Kindle / Fire devices (Without Having to side load the Google store bits)?

Thanks

dshokouhi · November 13, 2020, 10:11pm

The full version of the app requires google play services, the minimal version does not so you can install that and use it. As far as the Amazon store there are no current plans to add it there.

There is not, you will have to try a custom card approach to this. I believe there is one where you can lock the card based on the user but not sure its all custom stuff.

You have to think of the app as a webview to the frontend because that is exactly what we are, you would need to get the frontend to support something like this for it to work in the app.

capstan1 · November 14, 2020, 12:59pm

What about just using a launcher where you can hide apps from the launcher? Depends on how old and how desperate to control the smart home your kids are, this could work.
You could still open the app by search OR by Opening it from the play store.

sender · November 14, 2020, 3:46pm

Nice workaround :-). But I would like to see an option to password protect the app… without having to have android lock.

dshokouhi · November 14, 2020, 5:00pm

you should consider opening a feature request and explaining what you want then

sender · November 14, 2020, 5:19pm

How and where?

TazUk · November 14, 2020, 7:52pm

I’ve just been setting up an additional unifi camera on HA 0.117.6 (Python 3.8 venv, via Nabu Casa).

I display these cameras using a picture entity card with a live view when selected - this usually requires me to enable “Preload stream” per card after a configuration change which it did today.

In the past this has never been an issue to enable in the mobile app, however running v3.0.2-full on a Pixel 5 I am unable to check the option when displayed in the app.

I should note that this is not the case in Chrome on the same phone using the externally accessible Nabu Casa address and it wasn’t an issue when setting this phone up with the HA app in October.
I’ve also tested with and without the “Automatically Close Connections” user configuration option on and off, which makes no apparent difference - it feels rather like the touch is not recognised within the app.

Have I missed something in the release notes that would explain this?

Any pointers would be appreciated.

dshokouhi · November 14, 2020, 8:06pm

github: Sign in to GitHub · GitHub

Make sure to fill out the issue template and be specific with the request.

this appears to be a front end bug, please open an issue in this repo: Sign in to GitHub · GitHub

TazUk · November 14, 2020, 9:23pm

Thanks - raised as Picture-Elements card with live camera view: "Preload stream" option cannot be changed in Android (browser or official app) · Issue #7691 · home-assistant/frontend · GitHub

sender · November 15, 2020, 7:59am

It has been done:

github.com/home-assistant/android

Prevent access to main application - android comanion app but leverage "externals"

opened 07:59AM - 15 Nov 20 UTC

sanderlv

enhancement settings

Since every update more and more sensors and functionality are being added to th…e android Companion app. I am at the point of using the app more and more as a "meter" (sensors). And the ability of very simply using the TTS element as a reporting tool and also the usage of widgets makes me wonder the following. Since I see the following elements as **"externals" from the main application**, thus being able to control and meter elements WITHOUT the need to open the mains app, e.g.: - widgets - TTS - Sensor data I would like to be able to LOCK/PREVENT the opening of the mains application. Currently this is not possible due to the fact it complains about not having android lock security enable and this is not what I am after at all (to password protect android). I would like to have a SEPARATE LOCK (password?) option on the app to circumvent it from being opened by the USER of the android device (e.g. kids). In my case my children who have an android device which I would like to be installed with the app but PREVENT them from CONTROLLING everything and thus the need to open the app. But I would like to leverage the use of the "externals": - widgets (some I can add myself) - TTS (to present messages e.g. get ready for school) - Sensor data (so much possible) I was also the "WTH" starter for RBAC in homeasssitant, but that's not there and custom header has been deprecated so that is not an option. Like other apps able to "password protect" access to the app, I would like the homeassitant companion app to be preventable from opening but be able to use the "externals" of the app: - widgets - TTS - Sensor data **Describe alternatives you've considered, if any** Enabling password protection on android. But this is not an option since that password would also enable opening of the app. And since this is a kids table I do not want any passwords enabled in android.