Hi @Trooped, I came across this yesterday and it looks fantastic. I had a bit of trouble connecting to my HA insurance, but managed in the end by using this format: “mydomain.tld:443”.
It don’t seem to be able to pull any entities, though. At the initial import stage, the blue loading circle carries on for ages and never ends. If I click the Continue button, I get a message saying “No Entities Selected”. Clicking “Select Entities” takes me back to the infinite loading circle and “Continued to App” takes me into QuickBars but it is completely empty, as expected.
Is there anything I need to do in HA to allow QuickBars to see my entities?
If anyone faces the same issue, the problem was network connectivity. I had created a firewall rule to allow the access but forgot to mark it as active
Maybe a stupid question but does that automatically mean that the app will no longer be updated through the play store? I still see a 2025 version there. I don’t mind sideloading but am just curious.
@Amardeep
Hey, last time someone reported this problem - it ended up being he not entering the correct URL to his HA instace.
Try playing around more and figuring out what’s the correct domain, use this:
@AleXSR700
Hey, thank you!
Not a stupid question, and the app will only be released via the Play Store, are you able to download/update to v1.3.3 via the Play Store? It is the latest version.
I’m experiencing a critical crash that makes QuickBars completely unusable. The accessibility service unbinds immediately after being enabled, creating a permission loop.
Environment
Device: Android TV (Google)
Android Version: 14 (SDK 29)
QuickBars Version: 1.3.3
Installation: Official Play Store
The Problem
When I enable QuickBarService in accessibility settings, it successfully binds for ~2 seconds, then crashes with an IntentReceiver leak, immediately returning to the “Accessibility Permission Required” screen.
What I’ve Verified
Accessibility service properly enabled in Android settings
Service shows as “Bound” in dumpsys accessibility before crash
SYSTEM_ALERT_WINDOW granted via ADB
PACKAGE_USAGE_STATS granted via ADB
Battery optimization disabled
Correct service component path: dev.trooped.tvquickbars/.services.QuickBarService
Technical Details (from ADB logcat)
The service loads successfully:
QuickBarService: Successfully loaded bars and triggers.
Then shows the HA connection message:
llg: You must enable persistent background connection in settings to enable triggering QuickBars from Home Assistant
Then immediately crashes:
QuickBarService: Service unbound (onUnbind)
ActivityThread: Service dev.trooped.tvquickbars.services.QuickBarService has leaked IntentReceiver ac.x@dfc97df
ActivityThread: Are you missing a call to unregisterReceiver()?
Stack trace:
at dev.trooped.tvquickbars.services.QuickBarService.onServiceConnected(r8-map-id-f690d959cddd5083ecd7b46a1d5fe2641fe469630364fde574c2dabb071d1065:212)
at android.accessibilityservice.AccessibilityService.dispatchServiceConnected
Reproduction Steps
Fresh install from Play Store
Grant all required permissions (overlay, usage stats, battery)
Enable QuickBarService in Accessibility Settings
Observe: Service unbinds within 2 seconds
App returns to “Accessibility Permission Required” screen
Loop repeats indefinitely
Request
Is there a workaround to disable HA integration, or will this require a patch? I have full ADB logs available if needed.
Thanks for this excellent app - looking forward to getting it working!
@AldenDana
Hey man, thank you for providing all of this information!
Please open a bug issue in the QuickBars repo, so I could look at it further (and maybe even you could look at it yourself, you seem to know your stuff ).
Also mention there if it functions correctly with other apps that require accessibility permissions - since that is the first time I’m hearing about this bug.
I’ll reply there and try to assist how I can - and also hopefully fix it!
@Jamespigeon@VGrol
Can you open a discussion about it in the repo’s Q&A discussions?
I also own a shield and don’t experience it more. I want to get more information about it, and hear more experiences.
Hey, just seen it and replied to you that there’s already a discussion about it. It’s better to keep these centralized in one place - so other users can find it and report it as well, and we can come up with a solution for this.
emphasized text
Hi,
I am experiencing an issue where QuickBars constantly closes or crashes on my TCL Android TV device.
Device Details:
Manufacturer: TCL 65C7K 65" ]
OS: Android TV / Google TV
The Problem:
The app does not stay active in the background and seems to close automatically. Sometimes it crashes immediately when I try to trigger the overlay.
Troubleshooting already done:
I have disabled Battery Optimization for QuickBars (set to “Don’t optimize”).
I have granted the “Display over other apps” permission.
I have updated Android System WebView to the latest version.
I have verified my Home Assistant URL and Long-Lived Access Token.
Comparison:
Interestingly, the app “Notifications for Android TV” works perfectly on the same TV and stays active in the background without any issues.
Thank you for your hard work on this project!
For anyone trying to get streams working from Scrypted: Install the MJPEG Rebroadcast plugin for Scrypted. Add it to the camera(s). Add the camera(s) to HA as MJPEG Cameras - not Generic Camera, MJPEG. These work.
First of all, I’d like to congratulate the developer on their work. I find QuickBar incredibly useful.
Personally, I use it exclusively for cameras, to get live video alerts on my TV whenever something happens. Until now, I was relying on HomeKit Secure Video, but the notifications don’t work properly. Three quarters of the time, detections are either missed entirely or the video appears several seconds later. In short, it’s just not reliable enough for everyday use.
So I’m gradually trying to replace HSV with QuickBar. The only issue is that there are currently only two ways to stop displaying a video:
Call the same blueprint used to display the video in the first place, which then toggles it off.
Use a timeout.
The first option isn’t great because it’s the exact same action. Since it’s acting as a toggle, it can lead to errors quite often. For example, the video sometimes remains displayed on the screen indefinitely.
The second option isn’t ideal either. If you set a timeout of, say, 10 seconds, the video will disappear after 10 seconds even if a detection is still active and something is still happening in front of the camera.
It would be fantastic to have a dedicated action to stop a video display, completely separate from the action used to start it. Even better, the action that starts a camera stream should only be able to start it, not toggle it off as well. That would avoid a lot of edge cases and make automations much more reliable.
I’m not sure I’m explaining this very clearly, but being able to fully replace HSV with QuickBar would be amazing.
Love this - signed up for the pro version to support!
I am trying to get the camera integration working. Initial setup on TV works (TCL) but when creating the integration in my HA it is asking for host/port and I get tv_unreachable. I have confirmed the IP for my tv is correct and have set it to be reserved in my deco app.
Quick take: the TV app connects to HA fine (sidebar shows lights/lock)
Issue: port 9123 on the TV is not open — nc -zv from the HA host returns exit code 1 (connection refused), so the TV app isn’t listening
What I tried: enabled “persistent background connection to Home Assistant,” force-stopped/rebooted the app and TV, still no listener on 9123
My setup: Android TV (TCL) wired via Ethernet, same subnet as HA (reserved IP), HAOS on a Pi 5
Any help or suggestions would be greatly appreciated.
Hi I have upgraded to plug on Google TV I’m trying to add plus to firestick but unable too due to lack of playstore is there any way to upgrade to plus on firestick?
Accessibility service properly enabled in Android settings
).