Skip to content
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

Show entity command errors #48

Open
kennymc-c opened this issue Feb 4, 2025 · 8 comments
Open

Show entity command errors #48

kennymc-c opened this issue Feb 4, 2025 · 8 comments
Assignees
Labels
low priority Low priority

Comments

@kennymc-c
Copy link
Contributor

If an entity commands fails for some reason the app doesn't show this error. This should be supported as the user doesn't always know if a command has succeeded or not.

@albaintor
Copy link
Owner

Actually errors are shown while in a "sub-page" i.e activities, remote, media players views.
But indeed not in the profile pages.

@kennymc-c
Copy link
Contributor Author

I don't see any errors on sub pages either

@albaintor
Copy link
Owner

I added some errors on profile pages as well but not on sliders : it can be annoying to receive repeated error messages when moving slider and in my case it occurs oftently. The remote has weak network performances (wifi chip/antenna) and even if connected it doesn't handle all requests successfully.

@albaintor albaintor self-assigned this Feb 14, 2025
@albaintor
Copy link
Owner

Fixed in build 133. Please close the issue if all errors (except sliders) are raised

@kennymc-c
Copy link
Contributor Author

I still don't see any command errors with 1.2.0 (133). To be clear: I'm refering to the response status codes that e.g. integrations send to tell the core if a command succeded or failed and are are also shown on the remote as internal server error etc.
Maybe you even could also show the error and info messages from the integration right before the error if you somehow can get acces to these log messages.

@albaintor
Copy link
Owner

Ok no I don't analyze the errors status. Just the same error message (still contextualized with the concerned entity)

@albaintor albaintor added the low priority Low priority label Feb 17, 2025
@albaintor
Copy link
Owner

Switched to low priority. This would need a lot of refactoring

@kennymc-c
Copy link
Contributor Author

FYI: Your own Remote Toolkit can display these error messages. I would be fine if the same messages appear in the app as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority Low priority
Projects
None yet
Development

No branches or pull requests

2 participants