Replies: 1 comment
-
|
I fixed the issue at the end. After round of HA restart, TV Restart, and I tried to open Browser app in TV to inspect what's the error - it was ERROR 403. So I tried to refresh few more time in Browser app + remove entry in ip_bans.yaml then... I could see the HA login page at Browser app => QuickBars could be login without issue. Thanks for your program again. :-) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Android TV Hardware
Sony A80J
QuickBars Version
v1.3.3
Home Assistant Core Version
2026.6.4
What is happening?
I knew it should be nothing with QuickBars, but I need some help. I was an happy user for around 10 days and I paid for the app to show support.
However issue started. My HA setup with cloudflared + letsencrypted + https only set.
While I found QuickBars did not work with SSL issue, I checked for all things and I confirmed it is my SSL certificate got expired. On other devices I confirmed there might be some issues on the cached but I fixed on my other devices
% curl -Iv https://hassio.abc.net 2>&1 | grep -i "expire date"
curl -Iv https://hassio.home.abc.net8123 2>&1 | grep -i "expire date"
However I am unable to make QuickBars work when I put the mentioned as url.
My wild guess - my TV cached that ssl so connection to mentioned url did not work. As I unable to locate the cert at TV, I tried my best to delete App cached data / re-install QuickBars / reboot and reboot and reboot TV..
When re-install app again, I got Network Error - is HA is running error instead of SSL issue.
As said I understand it should be something related to ssl cert cached in TV. Any suggestion for this case?
Screenshots or Video
No response
Upload Configuration or Logs
No response
Relevant Logs
No response
Final Checks
Beta Was this translation helpful? Give feedback.
All reactions