It’s more reliable for when you use the service call.
That only worked with one device out of 3, one more to try
This is super interesting but the state of it at the moment is all over the place.
Very confusing to use, I do not understand the “floating” concept at all, cards just hang and dont go away. When does the clock appear? Who knows. it just does…sometimes…
The battery sensor dosnt report as a battery either which is minor but a bit annoying for automations and such. Could deffinitly do with a setting to set how long it listens to you after it responds when you have “Continuous Conversation” set on. Or at least let us know how long it listens.
Album display would be cool but I use Music Assistant for multi room so the media player on this isnt worth it to me and therefor I cant display any media info, would be nice if you can select a HA media entity instead.
Very promising, just very rough at the moment, nice work.
The ai crashed OFTEN and requires me to kill the app (or now since v18 restarting the service?)
Also now with the latest update the stop word has gone? and saying stop just causes them to ask what you want to stop which is really annoying behaviour.
As noted above, the updater is very suspect and wasteful, that needs looking at ASAP.
I love this app, simply LOVE it, thank you @knoop7. Yes it’s beta, but it has filled out a big gap I wanted to fill for a while: now the old phone I use to display HA dashboards actually not only serve as HA voice, but also bluetooth extensions. That’s 2 devices in each room I don’t need anymore. THANK YOU!
If we could amalgamate these
https://dashieapp.com/dashie-lite
And
VACA is the best one so far but struggling to get it yo worknon the TSV
Thanks for the feedback, fixing
1 Like
Thank you for the detailed and honest feedback. I really appreciate the time you took to write this. At the moment, the project is still in an early testing phase, and development is moving quickly, which does mean the experience can feel rough and somewhat inconsistent. That is on me.
To clarify the overall concept first: this is not intended to behave like a conventional app. The core design is built around voice interaction and a floating window model, which I outlined in the developer documentation. Voice wake-up and continuous conversation are still under active rework and are only partially implemented right now. The current behavior does not yet reflect the final “smart voice assistant” experience I am aiming for.
Regarding the stop word behavior: the stop mechanism was changed to support the new continuous conversation model, which is why saying “stop” can currently trigger an unintended follow-up instead of stopping cleanly. I agree this is frustrating, and the interaction logic here will be reworked.
On the floating concept: this is a direction I will continue to develop. Compared to embedded WebViews (wall / full modes), floating windows offer better performance, lower memory pressure, and more flexibility for long-running Home Assistant use cases. That said, the current lifecycle and state handling of floating cards is not mature yet, which explains why elements can appear to “hang” without clear dismissal behavior. This is a known issue and will be addressed.
The clock display is currently a very early implementation. There is no toggle yet because the current design is oversized and not suitable long-term. I plan to redesign this entirely rather than just adding a switch.
For the crash issues: this is a high priority. If possible, an adb log would be extremely helpful for diagnosing the root cause. The change in v18 to restarting the service instead of killing the app was meant as a temporary mitigation, not a final solution.
Regarding media and album display: I fully agree with your point. I personally use Music Assistant for multi-room audio as well, which makes the built-in media player less useful in those setups. As of v0.1.8, media player handling has been fixed, and I am planning to allow selecting an arbitrary Home Assistant media entity so media information can be displayed without relying on the internal player.
The battery sensor not reporting as a battery is noted. While minor, I understand it affects automations and consistency and will be corrected.
On the updater: your concerns are valid. The current implementation is inefficient and overly aggressive. This has been flagged for immediate review and rework.
One additional clarification I should have documented earlier:
Switching the remote browser source to an empty value will clear the remote browser display. This behavior was not documented properly, and that is my mistake. I will be updating the developer documentation to cover these implicit interactions more clearly.
This project is still rough, but the direction is intentional. Your feedback aligns closely with the areas I am actively working on, and it is genuinely helpful. Thank you for testing and sharing your experience.
2 Likes
Thank you very much for your evaluation, it is indeed still in the testing stage, there are still two versions before version 0.2, the current Bluetooth part is normal, and the interface adjustment is behind
It’s really great, but his software is too big 100MB, which is obviously against the minimum size that AVA pursues, I hope that low-end performance devices can also support it, and also support offline disconnection from HASS recognition, can communicate, but I want the small size, so that more devices, especially for touchscreen speakers and other better support, no one likes to hang a high-performance tablet plugged in and with a battery on the wall
I agree and thats why I am keeping a close eye on your progress.
I have a couple Lenovo TSVs and a Xiaomi Smart Clock all with LineageOS hacked onto them so a small footprint would be ideal
Unfortunately I cannot code to save myself but happy to test on the 6 different devices I currently use.
Also thanks for doing this!!
Thank you！I have seen your problems and have solved them. I hope you can test the experience. Thanks Release 0.1.9 · knoop7/Ava · GitHub
that works much better, i’ll try it on the other devices now 
1 Like
I tried upgrading my Samsung tablet with LineageOS to 0.1.9 and that went smooth, however the Floating display of HA is not working anymore.
–EDIT–
I just noticed the control that can be enabled in the Ava App, when enabling this switch in HA and then turning it on, shows me the browser again.
Hard to check the floating window permission problem (upper authority), and then the browser has a function switch, it is also your feedback, I am afraid you don’t understand, so I specially added a can control the display and open, it is recommended to kill the application and then give permissions, it will work very well on rooted devices, or use SKU (no root), including the update problem you said is also solved, battery problems, etc., why not solve the non-root device, because most machines generally support root before, Modern devices may support less
The switch made the browser float work, no worries.
Good afternoon. It is possible to change the application language to Russian
Is It just me or the app is only in Cinese?
It doesn’t work on the Xiaomi Smart Clock as “Display over other apps is not available as it slows down the phone”. It’s running LineageOS.
The Lenovo TSV seems to work well so far, I’ll keep testing over the next few days.
I had the same issue, almost pressed send in the message LOL