app version 2024.10.3-full. Not sure which version introduced large delays however when using the Android Auto car view and opening a garage door under the Covers menu I am seeing up to 30 second delay in the action. Using same garage door entity directly on the companion app there is little to no delay on both wifi and carrier connection. I am not sure what changed. I have completely uninstalled and reinstalled the app and no changes. Others have reported success uninstall reinstall I have not. Are there any settings in the companion app that could help improve the Android Auto experience?
#Companion App Android Auto delay when opening garage doors
ember badge
dark dagger
If you look at the HA logs when you trigger it from Android auto, do you see the request immediately appear in the logbook for the garage doors?
fickle berry
there was nothing changed with respect to triggering an entity in the car...another suggestion to try is to restart the network or HA host if you are seeing calls being delayed. Could be API related as the dashboard does not use the API on the app
ember badge
If you look at the HA logs when you trigger it from Android auto, do you see the...
I did notice the state changed to closed immediately when the door closed on the Android Auto screen ... what specific HA logs do I need to view? I haven't dug this deep before... thx
slender spindleBOT
dark dagger
I did notice the state changed to closed immediately when the door closed on the...
If you open the logbook and select the garage door, then you should be able to see when it receives the request to close.
fickle berry
logbook is one, the app also has its own logs separate from the server. Settings > companion app > troubleshooting > show and share logs that will show if teh call has failed but if you are seeing a 30 second delay that souds like it can be on the server end. The states update via a websocket subscription but the actual action uses a REST API which could be seeing the delay
@ember badge on your android phone do you have device controls set up? see if you can actino on the same entity in that screen. The code there is the same with respect to performing a action. Same as widgets.
dark dagger
If it works immediately via the phone then I'd assume it's a networking issue from android auto personally. I see it time to time with CarPlay - because the phone is connecting to the car's network the cellular connection (back to home) slows down which is mostly seen when streaming music or trying to trigger things via HA.
fickle berry
Android Auto actually uses teh phones data connection....android automotive is teh one that has the cellular connection from the car....one is phone emulation which i thought is how car play works....the other is an actual OS in the cars infotainment system
dark dagger
Good to know. But narrowing down if HA receives the request when you tap it in the car is still a good start.
fickle berry
as far as the android app is concerned either the driving dashboard with those icons or the apps widgets/device controls (android specific features) the same API is used so id imagine the same issue is there
fickle berry
Good to know. But narrowing down if HA receives the request when you tap it in t...
yea im under the assumption its not reachng the server for those 30 seconds
dark dagger
Same here.
ember badge
I had to add logbook: to my configuration ... in the companion app I can control the entity.. each one with open stop or close... the AA widget only has a single icon which I am not sure is able to relay open stop or close ? in AA widget I get MAIN.cover or SMALL.cover widget... maybe this difference is why there is a delay for the action?
fickle berry
I had to add logbook: to my configuration ... in the companion app I can control...
in AA the cover.toggle action is used on teh entity whicih is either open or close i think
goign on the dashboard iin the app and clicking on items is not the same test here
if you go in device controls and add teh same cover entity you may see the same issue there
device controls being the feature on your android phone whch you may not have setup yet
you can also try another entity like a light to see if that works we use light.toggle action there
ember badge
I added the device control to tiles on the Android pull down for each door and those also work w/o any delay. they can be accessed w/o unlocking the phone so those won't stay..
I read somewhere the AA parts are loaded into a special partition .. could it be these files need updated to match the last updated HomeAssistant apk?
fickle berry
does it happen when your car is in the garage or some place where the connection may be slower?
fickle berry
I read somewhere the AA parts are loaded into a special partition .. could it be...
no thats not correct, its all loaded from teh app and handled by the app with what is displayed and the API calls
if you go in the car now and test does it also happen? and if so does the device controls on teh phone in the same location work?
ember badge
from the app itself no matter where I am wifi or carrier there is very little delay at all.. only when on AA screen widget the delay is 20 seconds or more ... up or down both entities.. I also tried direct wired via USB and Wireless using AAWireless and all same results App very little delay AA screen widget big delay. Device control very little delay
fickle berry
and same issue for other domains like light?
just checked teh code in android auto we do use cover.toggle but in device controls its open_cover or close_cover so that wasnt a good test my bad, if you create a widget with cover.toggle as the action that would be the closer test 🙂
ah looks like quick setting tiles we also use cover.toggle
ember badge
I don't have any lights I control to check... any way to add open_cover / close_cover in AA widgets?
fickle berry
I don't have any lights I control to check... any way to add open_cover / close_...
We don't even know if that is the issue
ember badge
ok was able to make a widget on HomeScreen with the cover.toggle action for cover.small entity and this is showing the same delays as the AA screen widget...both on wifi and carrier connections.
fickle berry
What integration provides that entity?
ember badge
MQTT
fickle berry
MQTT
do you see the same delay in developer tools > actions using teh same action? this will confirm if its from teh app or server causing the delay
ember badge
in the car w dev tools app perform action no delay on carrier, ...using AA widget same large delay
will the AA widget try to use the car built in cell data connection ever? I ask since mine is not active... and waiting for a try could introduce this delay.. just guessing here
fickle berry
AA always use phone emulation, so its all coming from the phone
are you using internal and external URLs in teh app?
if your usinig the internal URL did you by chance change teh setting to use the internal URL? settings > companion app > select the server > select configure home Wifi and look at the setting at the bottom of the page. What opton does it say?
ember badge
if your usinig the internal URL did you by chance change teh setting to use the ...
the url on the attached screen scrape was set to use the internal HA URL.... I changed to use HA URL ... delay is gone. I thank you for sticking with me here and I would have never known to look here nor do I remember changing this from the recommended setting.
