has been fixed
1 Like
Hi, in landscape orientation front camera snapshot is rotated 90 degrees , it is always in portrait mode. I didn’t tested rear camera snapshots.
Also face recognition seems work worse in landscape.
1 Like
I just came across this. Looks interesting
Does anyone have any videos or screenshots of it in use. Particularly the floating windows and the doorbell feature
Amazing app!!
Need help on muting the built-in browser.
I’m displaying live go2rtc camera stream to the browser from HA:
- action: text.set_value
data:
entity_id: "text.xxxxx_voice_assistant_remote_browser_url"
value: "https://xxx.xxx.x.x:xxxx/stream.html?&src=driveway"
and mute the browser with browser command:
- action: text.set_value
data:
entity_id: "text.xxxxx_voice_assistant_remote_browser_url"
value: '{"volume": 0}'
Browser pops up full screen and streams correctly, but the sound from camera still plays in the browser, am I missing something?
tankyou
- action: text.set_value
data:
entity_id: “text.xxxxx_voice_assistant_remote_browser_url”
value: ‘{“eval”: “!function(){document.querySelectorAll("video,audio").forEach(m=>{m.muted=!0;m.volume=0;m.setAttribute("muted","")})}()”}’
Appreciate for the quick reply.
Unfortunately, that did not work for the go2rtc streams.
The camera elements will turn muted or unmuted just by turning the browser display switch in HA on and off without changing the url, very strange.
Will research more.
Thank you for you help.
I just noticed that intents do not open on Ava when using action: url with an intent:// path in the tap_action. Instead of launching the app, the dashboard tries to open the intent string in the web browser, which fails
It seems that when using the url action, the browser (or the WebView inside the app) tries to handle the intent:// string as a standard web link rather than a system command, leading to it failing or opening a blank search page.
1 Like
1 Like
Hi everyone, I just updated both to v0.3.9, and I now get an error in home assistant saying the following, does anyone else see this?
Update DEVICE_NAME_voice_assistant with ESPHome 2025.11.0 or later
Warning · Reported by ESPHome
ESPHome 2025.11.0 introduces ultra-low latency event processing, reducing BLE event delays from 0-16 milliseconds to approximately 12 microseconds. This resolves stability issues when pairing, connecting, or handshaking with devices that require low latency, and makes Bluetooth proxy operations rival or exceed local adapters. We highly recommend updating DEVICE_NAME_voice_assistant to take advantage of these improvements.
Are you running an ESPHome version prior to 2025.11.0?
My home assistant has ESPHome 2026.3.0, so I really don’t understand what it’s asking for… It showed up after I updated AVA on the devices. I first updated one early this morning and noticed the message in HA after. I didn’t make the link until a few hours later when I updated the other device to ava 0.3.9, and seconds later the warning popped up in home assistant for this second device too.
Thanks for your feedback that this technical issue has been resolved, sorry Release 0.4.0 · knoop7/Ava · GitHub 
1 Like
Fixed indeed, thank you very much for the rapid resolution!!!
1 Like
Hi, I updated to version 0.4 and now Ava’s settings (the gear icon) are not working for me.
Also, when using action: url, the triggered intent does not come to the foreground. The target of the intent (in this case Spotify) opens as an app, but it does not open as the foreground application.
Thanks for the help!
1 Like
Thank you very much for all your efforts on this project. I’ve seen many new features expecially in store section. There will be an update in documentation to fully understand these updates?
1 Like
A large number of instructions have been added, and you can directly read the introduction of the avd-mods project in the future, pay attention to the reason, in order not to disturb everyone, and control the content as little as possible