I’m confused by this one. Is Ava not passing through to the standard Home Assistant conversation agent/tooling?
1 Like
I really LOVE your app !
I think that it is getting less attention then deserved because of the title of the topic, you are mentioning only BLE.
For me the #1 feature this project bring is the ability to use any Android device into a Voice Assistant using Home Assistant with wake word. Exactly like Voice Assistant PE.
I have several Alexa that I’d like to dismiss and only one Voice Assistant PE, replacing all Alexa with Voice PE would be expensive and I was really dreaming to be able to use my phone / tablets for voice control and this project made my dream true finally !
I can use my phone (that is almost always next to me), I can use my wall screen tablet and I can eventually place some old unused phones around to act as voice assistants.
Thank you and keep working at the project to make it better and better 
2 Likes
Thank you! Still in the update, the oil monkey script will be added soon, so that more people will be convenient to use, need to optimize webiew, the current Bluetooth tends to be stable, the notification scene is basically not a big problem, welcome feedback to add new features, and patch bug bugs~
If you look closely, it may be difficult to understand
Has the source for this moved? The only update I see on the repo recently are version changes pointing to new compiled versions.
Hi knoop7, thank you for making this!
I gave it a try today but it crashes about within an hour of running, even without using but active and takes the HA companion app out too!
For me, what makes this really worth it, is that I can use an older (Android 10/4c) tablet with a simple dashboard and use as an Assist Satellite - which works really perfect.
Hello, I hope you update the test, I have added a number of debug logs, if the kill is likely to compete with the hass software, it is recommended to have a crash log to better solve the problem, I am very concerned about this matter, thank you～
https://github.com/knoop7/Ava/releases/download/0.2.7/Ava-0.2.7-release.apk
1 Like
Is it the source code? You can rest assured
Hi, thank you for your prompt response! 
I did install the latest version and this time I used the built-in browser to display the HA dashboard.
After about 1 hour AVA closed itself, no other apps were running/active.
Another thing that I’m trying to solve: I was putting the tablet into sleep after inactivity and by sending a webview command to the companion app, I could weke the screen.
Is there a similar way to achieve this with AVA?
1 Like
This is very strange, it would be much better if there was a log at the time of closing, I have tested on multiple old devices, including 1GB devices have not been automatically turned off, it is very likely that the quality comes from your system battery whitelist, since it has been flashed, you can use root to force it to live, install the xp module to prevent ava from being killed, or after killing our own application to live life
Have you looked at it on the hass side, there is a screen display switch, and the input URL can be opened quickly, maybe you haven’t looked at the software configuration options carefully?？
Hi,
I also test it on an older Android 8 tablet. Sometimes the bottom bar doesnt disappear when I switch browser on and off.
May I didn´t found it, but is it possible to switch on and off the display over an external motion sensor like on FullKiosk?
thanks for your work!
Hello~
You can realize your function, you can add a judgment through the built-in vibration sensor, the switch display can also be through the camera, you can use the face AI model built into the software, you can make automatic judgment
Ava has built-in face detection AI that works like Fully Kiosk Browser. When a face is detected through the camera, it creates binary_sensor.face_detected in Home Assistant.
Setup: Open Ava Settings, go to Camera section, enable camera and turn on Face Detection.
Entities: binary_sensor.face_detected shows “on” when face detected, “off” when no face. Optional sensor.male_count and sensor.female_count available with gender detection enabled.
Automation to turn on screen when face detected: trigger platform state, entity_id binary_sensor.face_detected, to “on”, action service switch.turn_on entity_id switch.screen_toggle.
Automation to turn off screen after 5 minutes no face: trigger platform state, entity_id binary_sensor.face_detected, to “off”, for “00:05:00”, action service switch.turn_off entity_id switch.screen_toggle.
Browser control automation with mode restart: trigger platform state entity_id binary_sensor.face_detected to “on”, actions service switch.turn_on entity_id switch.browser_display, delay “00:10:00”, condition state entity_id binary_sensor.face_detected state “off”, service switch.turn_off entity_id switch.browser_display…
Secondly, due to different device models, there may not be enough adaptation, you need to provide the model, or relevant screenshots or logs to better judge why the bottom bar will not disappear, and the others have been hidden globally
What do you mean by that?
There is this error in the HA log, exactly at the same time when the device became unavailable:
Logger: aioesphomeapi.reconnect_logic
Source: runner.py:289
First occurred: 12:32:37 AM (9 occurrences)
Last logged: 3:58:31 PM
Can’t connect to ESPHome API for tab1_voice_assistant @ 172.16.0.28: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address=‘172.16.0.28’, port=6851))]: [Errno 111] Connect call failed (‘172.16.0.28’, 6851) (SocketAPIError)
Can’t connect to ESPHome API for tab1_voice_assistant @ 172.16.0.28: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address=‘172.16.0.28’, port=6851))]: [Errno 111] Connect call failed (‘172.16.0.28’, 6851) (SocketAPIError)
Can’t connect to ESPHome API for tab1_voice_assistant @ 172.16.0.28: [Errno 104] Connection reset by peer (ReadFailedAPIError)
It runs Android 10, not a custom rom.
I’m also trying to find the battery sensor settings in AVA but cannot find it.
This ia really necessary since this device is automatically charged with a smart plug at 20/80 levels.
I can only turn on the diagnostic sensors, not the environment ones.
It has crashed again after 45mins.
I have no other apps running, even forcefully closed them completey, as much as possible.
Is there any solution for waking it up from sleep?
This is the log on the hass side, hello you need adb for the logs of the software, you can download Release v1.14.2 · liriliri/aya · GitHub this software for ADB log viewing
But I checked that Android 10 is an asop magic modified system, and there is a battery sensor in the advanced diagnosis.
1 Like
I’m testing 0.2.8 on an android 14 tcl smartphone. Everithing looks fine except I can’t login to homeassistant via built-in browser. I see login page but no keyboard pops out to write , neither bt keyboard input is working. Bt keyboard works fine outside browser ,I can change values in your app settings and outside AVA.
homeassistant:
customize: !include customize.yaml
auth_providers:
- type: trusted_networks
trusted_networks:
- 192.168.178.xxx
- type: homeassistant
On another note: this app is friggin amazing, absolutely love it so far !! thank you so much !
1 Like
Thanks mate, I’ll never found it.
1 Like