pergola.fabio
Great job, really like the NFC part, works very good
Great job, really like the NFC part, works very good
Really good job guys, the sensors you have added over the weeks is really useful to use. Glad its coming along.
Awesome, thanks! As a new HA user since a few months, I actually didn’t know that there were Android/iOS Home Assistant apps. I guess these apps could be promoted a bit more, e.g. add a link to them in the footer of the HA website and/or in the info section of every Home Assistant instance.
You guys rocks, thank you so much for your work 
I can’t wait to include a heap of these new sensors. Great work!
Looking a the sensors for my Android phone in HA I see some don’t update very often at all. ie: light sensor hasn’t updated for over 45mins despite me changing it from direct light to in darkness. I’m not concerned about that as I have very little use for it, however I see exciting an automation future for the ‘phone state’… problem is, that is laggy too. Is there any way to speed up the refresh of these?
1 reply
Ok thanks, I’ll have a play with it.
Through some quick testing I have found the Lux sensor only updates when the HA app is first opened. To get it to refresh I have to completely shutdown the app and open it again. Not sure if this can be resolved but it makes the sensor rather useless.
Thanks for all your great work on this app 
Perhaps you have some battery savings on the app.
My phone does that by default on all apps and limits them to be used when not in foreground, when the screen is off and in sleep.
So pretty useless, but it can be disabled.
Yea sometimes it does update on its own. Its an odd one because when we query it there is only a short window it waits for an update and if we don’t get one it does not come through. Not only that but the events are not guaranteed when the app is not in the foreground. I see something similar on my Pixel at times but sometimes it does update when I didn’t touch the app. On a wall mounted tablet that keeps HA open all the time its a different story, it updates all the time during the interval. Its a bit difficult when the system decides not to give us an update, it may be something that can improve if we decide to use a foreground service/notification for updates to be more reliable.
1 reply
That’s good to hear for the example of a wall mount tablet. I’m currently just looking at my phone for detecting ringing, but a tablet using the Lux sensor will be handy. Thanks
Since I almost always have my phone on vibrate only and leave it lying around the house (I hate the concept of being tied to my phone)…
automation:
- alias: Daves S20 Ringing announce at home
trigger:
- platform: state
entity_id: sensor.daves_s20_phone_state
to: ringing
condition:
- condition: state
entity_id: person.dave
state: home
- condition: time
after: '08:00:00'
- condition: time
before: '18:30:00'
action:
- service: rest_command.assistant_broadcast
data:
command: Daves phone is ringing
- delay: '00:00:10'
- service: rest_command.assistant_broadcast
data:
command: Daves phone is ringing
Thanks again @dshokouhi
The NFC and QR code support looks really interesting and fun. I can see how that now makes easy door-unlock use-cases easier to handle, since I can now trust the authenticated delivery of the tag_scanned event in Home Assistant.
For the QR code use-case – can I suggest that the application also register for a shorter, more compact URL to process scanned QR codes? The longer https://www.home-assistant.io/tag/tagid URLs make for some fairly large and involved QR codes…
Also, in the tag_scanned events - is there an obvious way to map the device_id back to the specific device? Or some clever way to map the user_id back to a person other than iterating over all of the person entities, matching against the user_id attribute?
Once I create a launcher widget on Android, is there a way to edit the template? It might also be nice to be able to specify an action when tapped? Finally, in this same vein, the most useful feature missing it to be able to create a shortcut to launch the Home Assistant companion app to a specific lovelace page. It’s often hard to navigate the titles on the narrow screen of the phone to select the correct one that I’m trying to reach.
Thanks for all the work on the Android application of late - this is really working nicely these days.
Is there a way to get the next alarm reliably while still using tasker? The next alarm time is now changing continuously to a few minutes in the future.
1 reply
you might be able to use: https://companion.home-assistant.io/docs/troubleshooting/faqs/#using-a-self-signed-certificate-leads-to-a-blank-page-in-android
1 reply
See if these steps are helpful: https://github.com/home-assistant/android/issues/748#issuecomment-683302649
Truly a great app. It would be very useful if we can have the battery and phone temperatues as sensor outputs. How easy will it be to implement this?
Okay… I will give it a shot when I have more time. Thank you for your responds, it’s appreciated!
Hi,
First, thank you for this great app.
While everything work great and all choosen sensors show up, I can’t find a way to get the sensor.call_number to show up. I’ve reinstalled the app with all permissions including the call log. I’ve found a web post at ZDNET saying that Google restricts which android apps can request the call log. If this is unavailable now, maybe it should be remove from the official Companion doc or is there a way around it.
I can see that it’s been removed from last beta due to policy changes at Google.
(https://github.com/home-assistant/android/pull/1072)
Thank, I will try
because nobody else thought it was important enough to submit a feature request on github?
