-
Notifications
You must be signed in to change notification settings - Fork 590
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Widgets stuck loading when HA hasn't been opened recently. #4245
Comments
Logs
|
is this a duplicate of #4200 ? tough to tell but symptoms sound similar |
I can't tell, but if it is the same issue, I think the specific reproducibility in this method would make it easier to debug/fix. Is there anything else I can provide? I am using a WAN HA instance and I've only tested the WLED power widget |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This may be a duplicate issue but this has more details that do not match any other issues I have found.
Home Assistant Android app version(s):
2024.1.5-full
Android version(s):
14
Device model(s):
S21
Home Assistant version:
Core
2024.2.1
Frontend
20240207.1
Last working Home Assistant release (if known):
Unkown
Description of problem, include YAML if issue is related to notifications:
See attached video, but if a widget is pressed when HA has been closed (idk the android term) it will execute correctly once, but then buffer endlessly and prevent further presses. This also happens if HA just hasn't been opened recently, even if it still has an open window. Battery saver is off on my phone. reloading the widget fixes the issue and it behaves normally until you try again without the HA app running in the background.
Companion App Logs:
see comment (character limit)
Screenshot or video of problem:
50s demo on youtube (ofc youtube made it a short...)
Additional information:
I will post the log as a comment due to github character limits.
The log was saved directly after ending the recording on that video.
The text was updated successfully, but these errors were encountered: