Continue Discussion 113 replies
April 2019

jamesking

April fools?

April 2019

fernandex00

That’s awesome, thank you, I was afraid that this was somekind of April fools

April 2019

FiServedPi

Godspeed, my friend

April 2019

andriej

I hope it’s not april fools, as already HTML5 notifications on androidstart to suck… :slight_smile:
I hope one of the first features would be it and coords reporting. Rest can be (at 1st release) just lovelace-webview.

good luck!

April 2019

fillwe

Incredible news!

April 2019

areks

There’s a pretty good app under development at About HA Client - native Android client for Home Assistant

Which, IMO, is getting it right at being fast, lightweight and reliable. Perhaps a join effort could be done?

April 2019

mu3

I feel that I need to voice my position.

  1. Home Assistant Companion 2.0 for iOS is absolutely incredible.

  2. Ariela for Android is really great, and a $4 one-time payment for the ads-free version is totally normal. It’s rated 4.8⭐️ on Google Play with reason.

  3. Mobile App component that you’re working on is a great foundation.

  4. BUT I’m afraid spreading your focus on EVERYTHING will probably hurt quality and growth of the iOS app.

Competition is great when it comes to Android vs. iOS vision difference as every side can get inspiration (like cams, tre/hum sensors on Android and native integrations on iOS), but not inside one platform when the official status of the app kills innovation and already invested efforts.

I believe the better way is to overcome obscure frictions with Ariela developer @Ionut.

I will support your every decision, but that’s something to consider.

@balloob @robbiet480 Please join the discussion.

April 2019

teachingbirds

Paulus have opened up for the existing android apps to become official, but apparently that doesn’t seem to be something they want. On the latest podcast he explained what is needed of app devs to make an app official. There need to be an official app.

1 reply
April 2019 ▶ teachingbirds

Ionut

Hi there, actually even few days ago i made the proposal of making Ariela open source in order to became the official Android app for Home Assistant, proposal which was rejected for a couple of reasons. Still, the idea of having an official Android app is a very best one, and if i can and if i am allowed i will like to contribute to the new application and of course support and add new features to Ariela. Having multiple apps to choose from will allow users to have best Home Assistant experience based on their needs, users being what it matters for me and i suppose for the team behind Home Assistant.

April 2019

mu3

@teachingbirds I think you miss my point.

@Ionut I didn’t see it, what were the reasons for rejection?

There’s always a place for discussion.

2 replies
April 2019 ▶ mu3

Ionut

@mu3 the main reasons for rejection were:

  1. Ariela tend to have native implementation for the UI, and a web based UI is preferred
  2. The application do not use the new mobile_app component yet
  3. Ariela makes wrong assumption about the way users needs to use the authentication (they always need to use the web login)

Anyway, like i said before, there is no reason multiple apps couldn’t coexists for Android users. At the end users will choose the best app that suit their needs in order to have best Home Assistant experience. And of course if i can i will going to support the new official android app.

2 replies
April 2019

mu3

I personally only use the web UI (Lovelace) inside Ariela on all Android-based dashboards, and obviously use all these fancy custom components.

So these reasons sound ridiculous to me. Especially, when you compare fully functional, well-known and powerful app to something that don’t even exists.

April 2019 ▶ Ionut

DavidFW1960

Robbie will be THRILLED to have someone else assisting him with this app. His biggest problem with the iOS app was doing everything himself and not having any help. He would welcome your assistance with both arms…

April 2019 ▶ Ionut

aidbish

H @Ionut Love the Ariela app, so big thank you there.

In regards to the items mentioned of why it was rejected, would it not be possible to overcome them so that it could become the official app, that way yourself and robbie have a good base to start with?

1 reply
April 2019 ▶ aidbish

Ionut

Yes, from my end its possible to resolve those issues but at the end its not my decision if Ariela can be official Android app or not

April 2019

andriej

I’ve tested most of the current Android apps.
With every each of them I have issues either regarding visual side or vision for development.

I’ve just looked up HA App in Apple Store (as I don’t own apple device) - and it’s exactly what I would require from app! It supports GPS, notifications and pure webview.
I like my lovelace UI, why does all the devs try to do anything with that… :slight_smile:

I hope to see just an clone from iOS on Android and called ‘official’ so it’s always up to date with the API and growing with HA.

2 replies
April 2019 ▶ andriej

unf0rg0tt3n

Still no issues with this one: Ariela - Home Assistant Android Client
Really great app!

April 2019

toddw65

I’m using Ariela and very happy with it, but generally, I think having more options is a good thing so I welcome the news.

April 2019

CaptTom

I’d love to try an Android app with HA, but I’m sort of stuck on justifying it. I mean, I can already use the browser into Lovelace, and it works great.

I can certainly see the benefit of carrying around an HA client in your pocket, if you’re doing presence or location detection, but I haven’t gotten into that yet.

Is there some other killer feature an app offers which would bring me into the fold?

1 reply
April 2019

itzmrdavis2u

The features of Ariela I like most are

These are just the main features for me that make the app better than just using the webui

April 2019

123 Regular

If “official” Android app implies it must be open-source then that narrows the field of available options.

The inherent risk of elevating a closed-source app to “official” status is the app’s developer may ‘go dark’ (looking at you Zanzito). Without access to the developer or the source code, the community has no ability to update it and must find another “official” app.

An open-source app may be chosen as the official one but that doesn’t necessarily eliminate the market for a paid, closed-source app that offers superior functionality and performance. Competition breeds innovation and users will be drawn to whatever serves them best.

All in all, there’s room for more than one.

April 2019 ▶ mu3

teachingbirds

Well, my answer wasn’t directly aimed at you, but please do explain then :slight_smile:

1 reply
April 2019

mu3

I’ve highlighted my point in bold:

It is the same person who is developing iOS app, mobile component and now an Android app.

I really love and appreciate @robbiet480’s work but who was waiting for new releases for like literally years, knows what I mean when I’m talking about losing the focus.

2 replies
April 2019 ▶ mu3

teachingbirds

I don’t see how my post contradicts what you have said.

April 2019

dasbooter

I personally welcome a free, open source app that is secure. If the developer has other responsibilities but feels that they are doing good than that is her/his choice, and I thank them. I don’t use any Android app but have used Android since the original Google phone Nexus 1. It makes sense that there should be an Android app as there is an IOS app.I just wouldn’t demand one bc I don’t know how to contribute to making one myself. I somewhat depend on the kindness of people here to scrutinize and expose security issues and this is easier with open source apps. Monetized apps still have a place to get u that special support u need or a flashier UI. I’m not sure how having both an open source official app but also the same app with a cost associated in any different form would work out.

Anyways reading the initial post, I thought this person means business and who is this super hero lol. I’m still not sure I’ll use an app tho I’m currently ok with tracking with Google location tracking and html5 notifications… Till Google starts messing around

April 2019 ▶ mu3

aidbish

He is free to work on whatever he pleases, regardless if people are waiting for new releases/features etc.
Its his choice at the end of the day.

April 2019

awarecan

Sounds like a good reason to plug on my Moto X developer edition.

April 2019

balloob Founder of Home Assistant

Aaah, the irony. Years of “where is the official Android app?” and now here I am having to defend why there will be an official Android app :thinking:

I am not going to respond to the post about Robbie having to focus. It’s his life, his time, he can do as he pleases. And if he chooses to spend that time on building open source things that he will share with anyone, let’s not discourage him, but support him instead, please?

Most work for a mobile app that smoothly integrates with Home Assistant is actually done inside Home Assistant itself: secure token based authentication, webhooks to send data back, mobile app component to tightly integrate the data with other parts of Home Assistant. Robbie has recently put a lot of work in the mobile app part, and so in proxy, Robbie is making all other apps better, including Ariela.

About Ariela. We have talked to @Ionut and looked at Ariela and decided that it does things that we would not consider suitable for an official app.

I don’t expect Ariela to remove features, remove ads and become open source to become an official app. That doesn’t make sense. We have been putting a lot of effort in making Home Assistant simple and easy to use, and we will continue to do so. This is not a disconnect between developers and users, ease of use is the most frequent feedback.

Having multiple apps is not a bad thing, it’s the contrary. The great thing is that if people use one app, feel that it lacks features or disagree with choices that are made, they can switch! Yay for choice.

April 2019 ▶ andriej

fernandex00

Totally agree, Can’t wait for the Android app​:+1::+1::+1:

April 2019

anon34565116

And, I am sure. you can tactfully “borrow” any good mobile app ideas that can fit within the official framework too.

Thank you for this open, flexible ecosystem.

April 2019

mu3

I’ll summarise the issue to make it clear:

  1. There is an existing feature-rich, actively developed app which @ionut by himself proposed to open-source and make it the official Android companion. But was rejected because by default it uses native Android components. I believe most users immediately switch to Lovelace in the settings.
  2. There are plans to start developing a new app.

Do everyone understand how much resources are required to fully integrate into platform like iOS or Android and leverage all the sweet staff?
@robbiet480 went this hard way with Swift.
I mean, it’s in Beta now.

Is there a place for collaboration instead of reinventing the wheel?

2 replies
April 2019

anon34565116

This is @balloob 's sandbox. You are free to fork and collaborate to your heart’s content. :wink:

April 2019 ▶ mu3

balloob Founder of Home Assistant

There is a place for collaboration, hence why the mobile app component is built in a way that it’s able to support all mobile apps. We have written very detailed instructions on how to integrate with Home Assistant and the Android mobile app will be built according to that spec.

April 2019

mu3

@ionut Any thoughts?
(Replied to another post by mistake)

April 2019

Ionut

Seems that this escalated a bit and i am sorry for that. All i wanted was to explain the statement @teachingbirds said : “Paulus have opened up for the existing android apps to become official, but apparently that doesn’t seem to be something they want” which is not actually true and in fact i offered to make Ariela open source and fix the things mentioned by @balloob.

Now, regarding Ariela and the new official app which is in developing, there is no harm if both of them could coexist and i don’t see why we cannot discuss ideas or even help coding.
Indeed, Ariela tend to be more native in displaying entities, cards etc, meaning that custom lovelace cards will not be supported without extra work. But knowing this , a Web UI mode was also added for the users who do not want to use native. Same for MQTT, device tracker and most of Ariela functions, the functions exists in the app, but at the end users will have to choose if they will enable them or not.

At the end all i can say is that if anyone want my help or have any questions regarding Android & Home Assistant, please do not hesitate to ask, this being my way of helping this wonderful community.

1 reply
April 2019

mu3

Thank you all for participating in the discussion :heart:
Your time is greatly appreciated!

April 2019 ▶ Ionut

andriej

Thing is that I’ve even wanted to give your app second chance and it’s so not userfriendly at the beginning… I have to give WiFi name even if I have my own network configured to sort out either it’s local or remote connection… Also had issues with the token (why still bother with users with api_password as it’s deprecating)?
I didn’t even get thru first few steps to be able to try it out.

1 reply
April 2019

jjhuff

Did you consider ReactNative? You’d be able to share much/most of the code between iOS and Android.

1 reply
April 2019 ▶ andriej

Ionut

Indeed the setup process can be a little confusing but i believed that its explained enough in order to complete the connection. I know that api_password is deprecated, but unfortunately this doesn’t mean that its permanently removed so users will tend to use it. Please use the Ariela discussion thread if you want to give more details on what didn’t worked on your end to setup, in order to not spam this thread. Thank you.

April 2019 ▶ jjhuff

awarecan

The majority functionality planned to be provided by the “official app” involved some sort of Android native feature, it would not be an UI-rich apps, therefore I don’t think any cross-platform solution will help.

April 2019

TravelinMax

This just means that us iOS users need to donate more than Android users to keep @robbiet480’s focus in the right direction! :wink:

(jk, but seriously consider donating/contributing, software doesn’t write itself)

April 2019

robbiet480 Companion Dev

Okay, finally getting around to replying to this…

In no way, shape, or form was this announcement targeted directly at Ariela, let alone any other Home Assistant Android app. @balloob and I are in complete agreement that any and all apps are more than welcome to integrate Home Assistant in whatever way they see fit (excepting blatant ripoff of logos or the name and egregious security decisions, and no, that list is not exhaustive and could change at any time).

Paulus and @Ionut have already expanded on the reasons why we didn’t want to accept Ariela as the “official” Home Assistant Android app, but let me add two more:

  1. From my own technical perspective, it would take a lot of work to adapt Ariela to our vision. It would be unfair of us to ask @Ionut to do that, as well as unfair to users who may be using those features (such as the native UI or the MQTT integration). Here’s just some of the things that I believe would be necessary to align it with our standards:

    1. Migrate all MQTT sensors to new mobile_app sensors (To clarify our issues with MQTT, from what we have been told and seen ourselves, Ariela does not actually have a MQTT client embedded in it. Instead, it calls the mqtt.publish service in Home Assistant, effectively faking “MQTT”. We both don’t want an official app to use MQTT as its just another barrier to entry and don’t want them using workarounds such as this.)
    2. Figure out a replacement for the MQTT camera support, whether making a new camera platform for mobile_app or something else.
    3. Redo authentication to only use the browser as per Section 8.12 of RFC 8252 “OAuth 2.0 for Native Apps” for security reasons. Right now, using the native UI and asking users to enter a username/password directly into Ariela is a security risk as Ariela could take those credentials and use them for nefarious purposes. To be 100000% clear, We have exactly 0 information or reason to think Ariela is doing this at any time past or present or would in the future. It’s just something that we would require of a official app because they should be held to the absolute highest standards.
    4. Adapt to the new mobile_app notify platform that will be in 0.91 and uses Firebase Cloud Messaging as the backend, instead of HANotify.
    5. Removal of all native UI components that attempt to replicate the web UI/Lovelace inside of the app. Existing widgets and things external to the app are fine as is.
    6. Open source the app, relicense all code under the Apache 2.0 license, transfer the repository into the Home Assistant GitHub.
    7. Remove all ads from the app, as well as the paid version, from the Play Store. We don’t have any issue with @Ionut retaining his Patreon and adding a tip jar into the app, just like the iOS app. We would even be more than happy to promote the Patreon on social media, the blog, the forums, etc.
  2. I don’t think it would be right of “us” (speaking as Home Assistant, the entity) to co-opt someone else’s work and effectively remove their name from being publicly visible. For example, the repository would need to be under the Home Assistant organization and we would probably want to transfer the app onto a Play Store developer account that is at least partially controlled by someone other than @Ionut, just in case the worst happens and he is no longer available to us (or doesn’t want to be). Full disclosure, Paulus and another friend of mine have access to my Apple Developer account for similar reasons. Obviously it’s not like we would intentionally remove @Ionut’s name and would credit where possible but he would be recognized less just due to moving stuff around.

Overall, I personally made this decision from the stance of “what is most fair to everyone involved”. What is most fair to the developers, what is most fair to existing users of the apps and what is most fair to the community. I think if you read all of the above and think about it for a minute, few people here would want to be in the position that I and Paulus would’ve been in where we ask someone randomly to effectively upend their entire app that they’ve put a lot of time and a lot of effort into for a long time and in some respects make their apps drop features in favor of a simpler experience, let alone making a developer just outright delete code entirely.

If @Ionut or @estevez wanted to go to all of that trouble, then I think we would welcome it. To be clear to both of them, the list above is probably the majority of the changes necessary but there could be more as we work through the process. I have no problems with either of them. I’ve met and spoken to them both recently, know that they’ve done good work and have been very active members of the community for a long time, doing a sometimes very thankless job (trust me, I probably know this better than anyone other than them or our BDFL @balloob).

Now, speaking for a majority rarely heard from here: I’ve been friends for a while now with, what is effectively, the Paulus of China, in that he is one of if not the actual leader of Home Assistant in China. He runs a popular forum as well as the largest Home Assistant chat group on QQ and WeChat. He believes, and I agree with him, that there is a large market of Android users in China that would like to see an official app, as what they have now is limited in functionality. Here’s the problem though, China can’t use the Play Store, or more importantly, Google Play Services (including Firebase Cloud Messaging), so alternatives have to be sought. This wasn’t going to be something to do in version 1 of the official app, but it is on my short term road map (for perspectives sake, bbs.hassbian.com saw 40,000 unique users in roughly the last 30 days. I’ve had 8,000 installs of the iOS app from China. So just assuming that every user that has installed my iOS app also has visited the forum in the last 30 days leaves us with at least 32,000 Android users in China). The iOS app already works very well in China in terms of push notifications and localization. Android will be a bit of a tougher issue because Google Play Services provides push notifications via Firebase Cloud Messaging as well as a significantly better location system over the native Android APIs. Bonus of finding alternatives to Google Play Services: Some devices don’t have them installed, namely Amazon devices or those based on AOSP, and some people just don’t want to run them. Final point on this, do not read this and think that a non-Google Play Services version of the app is happening now or ever. It’s a personal goal of mine that is a nice to have, not a must have.

I also wanted to quickly throw out there just to get ahead of it (not that i’ve had any indication that people have been thinking this, but what can I say, I have anxiety), obviously I did not build mobile_app to be able to just turn around instantly and tell Android app developers they can’t be the official app. Everything just kind of naturally came together over the last few weeks, somewhat unexpectedly, as I was finishing development of the iOS app.

Finally, everyone has been asking and worried about @Ionut and Ariela. I also wanted to throw out that we reached out at the same time as we did to @Ionut to the author of HA Client, @estevez. He expressed very similar concerns and queries as @Ionut did. Both of them should be absolutely commended for their work.

That’s all I’ve got for now, I’ll be interested to hear your feedback. Thanks as always for your support.

2 replies
April 2019 ▶ robbiet480

nickrout Solution Institution

Thanks for the very detailed response @robbiet480

April 2019

estevez

Hi all. I want to thanks all of you who mentioned HA Client here, and @robbiet480 for his answer.
I decided to continue my work on HA Client as an third party app, not an official one. I will do my best to support highest security standards required by HA. OAuth is coming in next release by the way )

1 reply
April 2019

robbiet480 Companion Dev

Thanks for chiming in @estevez. Also just wanted to add that we are planning to update existing mobile_app developer docs with a best practices guide covering the standards we hope all apps will adopt.

1 reply
April 2019 ▶ estevez

balloob Founder of Home Assistant

If you get stuck and the docs don’t help, hit me up on discord.

1 reply
April 2019 ▶ balloob

robbiet480 Companion Dev

I am also more than happy to help of course!

April 2019 ▶ robbiet480

estevez

That’s what I really waiting for now. Thanks.

April 2019

pergola.fabio

Really interesting here… Would be good to have an official app… That’s what lots of users do when they look for new software… Is there an app…?? That’s also something what I do…

Well, one suggestion for me, please include to read NFC tags, like the app “Hass NFC”

April 2019

Gerben321

About time :wink:

April 2019

Steven_Rollason

Will the Android app have support for an internal URL, the same as the iOS app? It would be nice to be able to have it use the local address when I’m on my local WiFi and only use the remote URL when I’m away from home.
Built-in support for remote access via Home Assistant Cloud would also be good, so we could log in using the Nabu Casa login details and it automatically pick up the remote URL - I know we could always just enter the remote endpoint as the URL, but this would make it easier.

1 reply
April 2019 ▶ Steven_Rollason

pszafer

you can make some dnsmasq on your router so your HA installation would resolve as your internal IP in WIFI and as an public IP on different DNS’es.

2 replies
April 2019 ▶ pszafer

Steven_Rollason

I don’t think that’s possible with my router. I’m with Virgin Media and use the Hub 3.

1 reply
April 2019 ▶ Steven_Rollason

noodlemctwoodle

You can put your VM superhub in modem only mode and build yourself a hardware security appliance, like pfsense or opnsense. Or alternatively just buy another decent router. I personally opted for pfsense after 1 day of using the VM superhub, it’s a terrible router!!!

1 reply
April 2019 ▶ noodlemctwoodle

MarkR

I bought Orbis and they are fantastic

April 2019 ▶ pszafer

Anglac

Since we are talking about Android, Pie has a function called “private DNS” which forces the phone to use a external dns server and goofs up the whole plan of having your router resolve to the internal address… on my phone it was turned on by default.

April 2019

MrDuusDK

I am using homehabit app for android

April 2019

Klagio

HA Client is excellent, ready for prime time

April 2019

Skylord123

Adding the shortcut to your home screen pretty much treats it like an app (loading it in it’s own container instead of has a page under the chrome/other web browser).

I think it’s a little silly. The whole point of having a responsive website is so you wouldn’t have to create a whole separate app. That is why the whole “add shortcut to homescreen for websites in order to emulate an app” is a thing. A lot of people just forget this option even exists.

The only area I think an app is really necessary is when you have a fire tablet or other device that doesn’t let you place shortcuts on the home screen for websites. Then an app would be awesome.

EDIT: I guess if you want to do push notifications an app could be nice. With how many third party apps there are for this it is probably unnecessary though (I don’t see a benefit of using HA for push notifications over Matrix, Pushbullet, or any of the other services I use).

2 replies
April 2019 ▶ Skylord123

techwithjake

I agree that if the new Android App was just going to be view HA and Push it’d be pointless.
But it’s also going to allow for Location Tracking and hopefully sensor tracking as well.

That’d mean I could have one less App on my phone when all it’s for is HA anyways.

1 reply
April 2019 ▶ techwithjake

apop

Yeah, I think the differentiator here is definitely being able to push data from the device back to Home Assistant. Sure, there are other third-party apps that can do this already, or you can even roll your own setup with something like Tasker, which is the route I’ve taken. But for those who are less tech-savvy or don’t want to deal with the hassle of that, having an officially supported solution is a big plus.

That, and as I think someone mentioned upthread, for a lot of people, the first thing they do when looking at a piece of software is look for a mobile app. I agree that responsive websites with homescreen shortcuts are a great way to go when feasible, but a lot of people aren’t necessarily aware of this option or just have the idea of standalone apps ingrained.

April 2019

lhoracek

Great to hear that it’s coming officially to Android. Would love to contribute, PR review or whatever to help with that.

May 2019

acordill

Just trying to find out if this is being done or not? No activity on github since it was announced. :slightly_frowning_face:

1 reply
May 2019 ▶ acordill

robbiet480 Companion Dev

Meant to write a update to this post, still will, but short version is iOS 2.0 is slightly behind schedule because Apple broke the ability to test watchOS apps via TestFlight (their beta testing service) and nothing can ship until then. Furthermore, as I laid out in the post, the first beta of the Android app shouldn’t be expected until early to mid summer. Summer doesn’t start until June 21 :slight_smile:.

May 2019

Klagio

why not use HA Client for Android, its already there, open source, and works perfectly

2 replies
May 2019 ▶ Klagio

Emphyrio

Please read the topic, and you will find your answer :wink:

1 reply
May 2019 ▶ Emphyrio

Klagio

I did, probably they did not check HA Client app

1 reply
May 2019

flamingm0e

You should read the whole thread.

May 2019 ▶ Klagio

acordill

Maybe HA Client can work for me when it supports the custom layout card. Until then it is a no go for me.

June 2019

dasbooter

@robbiet480
How do we keep up on this?

Is there an official news source for the development on this. I mean not so I can bug but to see how things are going and maybe get in on a beta test

June 2019

robbiet480 Companion Dev

Soon. Beta. Soon.

1 reply
June 2019 ▶ robbiet480

nickrout Solution Institution

So are you saying that subscribing to this thread is the best way to keep up?

June 2019

robbiet480 Companion Dev

For now, sure. Will make a thread in the next few days in the Android forum which will be the place for updates.

2 replies
July 2019 ▶ robbiet480

tismondo

Hooray, I’m very excited for this! I always thought there was a good niche spot for an official app and am looking forward to using it!

July 2019 ▶ robbiet480

pepeEL

please give us link to this thread…

July 2019

BatiBato

Extremely interested since I use android…

July 2019

Snakuzzo

follow :slight_smile:

July 2019

nickrout Solution Institution

Keep an eye out here I think https://community.home-assistant.io/c/mobile-apps/android-companion

July 2019

shanem

Just saying you didn’t have to get a Pixel 3, a pixel 1 for $200 will officially run the latest Android.

August 2019

pepeEL

Any news about some beta…

1 reply
August 2019

nickrout Solution Institution

Someone should close this thread.

August 2019

pepeEL

Why should close?

1 reply
August 2019

nickrout Solution Institution

August 2019 ▶ pepeEL

aidbish

When its ready.
The developer Robbie has had a death of a family member recently so is probably taking time out to deal with that

September 2019 ▶ Skylord123

stainlessray

The mobile web does not integrate device information. Using the app for presence detection, accessing device sensor states, cameras etc. There are lots of reasons for an app.

1 reply
September 2019 ▶ stainlessray

Ionut

Ariela do already all these things, so until an official app is available you can use it :smiley:

September 2019

thundergreen

Try homehabit on Google store …

December 2019

WedHumpDay

Couple questions on the HA Mobile App for Android from Google Play store.

  1. Will “Push” notification pop up if an event/alert is triggered? (separate from HTML5).
    If yes, will this replace Pushover and other variant notification integrations?

  2. Geofencing capability? If so, how will this play with multiple devices?

  3. Real-time location ? (similar to Google tracking but would replace Google tracking)

1 reply
December 2019

flamingm0e

I don’t see them ever replacing the notification options, only adding to them.

location tracking is already implemented, albeit with some issues right now apparently with updating frequently enough.

1 reply
December 2019 ▶ flamingm0e

WedHumpDay

Thanks…

If yes, will this replace Pushover and other variant notification integrations?

I don’t see them ever replacing the notification options, only adding to them.

Apology for not being clear enough.

Can the HA App be used for Push notifications instead of Pushover or other variant notification integrations? Basically, if I wanted to disable Pushover, will HA App provide the same functionality?

1 reply
December 2019

flamingm0e

I think that is their plan, but I don’t know. I can’t imagine them NOT implementing that feature.

December 2019

WedHumpDay

This is great news the app now support Push Notification and tracking. No longer need Google tracking or Pushover app.

New feature request for the app:

  1. Include the ability for Tracking Update time intervals. i.e. 30 sec, 1 min, 2 min, 5 min, etc, etc. (Unless its already built in. If so, what is the default?)

  2. Include the ability for the app to know when the phone is on the home Wifi network.

1 reply
December 2019 ▶ WedHumpDay

WedHumpDay

Let us know when of if the feature for location update frequency can be implemented (30sec, 1min, 5min, etc).
The App currently doesnt seem to update as it should.

1 reply
December 2019 ▶ WedHumpDay

nickrout Solution Institution

I find that it only updates location when I actually open the app. Apparently I am at the office, despite it being holidays.

2 replies
December 2019 ▶ nickrout

finity

I’m seeing the same thing even tho I have “Background location tracking” enabled in the app.

1 reply
December 2019 ▶ finity

nickrout Solution Institution

Yes I meant to add that I have that set.

December 2019

WedHumpDay

Consolidation of requests for the App.

  1. Include the ability for Tracking Update time intervals. i.e. 30 sec, 1 min, 2 min, 5 min, etc, etc. (Unless its already built in. If so, what is the default?)

  2. Include the ability for the app to know when the phone is on the home Wifi network.
    (other than Geo-fencing)

  3. Include ability to have app ignore DND mode so notification come through.

1 reply
December 2019 ▶ WedHumpDay

WedHumpDay

Touching base to determine if any of the feature requests are being considered.

1 reply
December 2019 ▶ WedHumpDay

risk

Assuming you mean the official app, have you tried: https://github.com/home-assistant/home-assistant-android/issues

1 reply
December 2019 ▶ nickrout

Coedy

Check that Android isnt ‘optimising battery use’ for the App.
I had the exact same issue, so checked if this option was enabled and it was.

Since removing battery optimisation my status is updating as expected.
(it registered I had left the house within 1min of leaving and marked me as being at my Work zone within 2mins of arriving this morning)

go into app details in your settings (android settings), Home Assistant, Advanced,Battery,Battery Optimisation, Click the drop down that says ‘not optimised’ and change it to all Apps, find and click Home Assistant, Dont Optimise and then back right out of everything.
(Nice and simple…Thank’s Google…)
Worth mentioning I’m on the latest version of Android 10 so menu options may change on earlier versions of android. But in theory if you are on Android 9 or greater, this is the problem.