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

Don't blame on disconnected AndroidTV device #117723

Conversation

mib1185
Copy link
Contributor

@mib1185 mib1185 commented May 19, 2024

Proposed change

This will reduce the "not connected" log message from warning to debug.
btw this should already be the state, since the integration is rated as platinum

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Deprecation (breaking change to happen in the future)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • I have followed the perfect PR recommendations
  • The code has been formatted using Ruff (ruff format homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
  • Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

@home-assistant
Copy link

Hey there @tronikos, @Drafteed, mind taking a look at this pull request as it has been labeled with an integration (androidtv_remote) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of androidtv_remote can trigger bot actions by commenting:

  • @home-assistant close Closes the pull request.
  • @home-assistant rename Awesome new title Renames the pull request.
  • @home-assistant reopen Reopen the pull request.
  • @home-assistant unassign androidtv_remote Removes the current integration label and assignees on the pull request, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the pull request.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the pull request.

@@ -39,7 +39,7 @@ def is_available_updated(is_available: bool) -> None:
"Reconnected to %s at %s", entry.data[CONF_NAME], entry.data[CONF_HOST]
)
else:
_LOGGER.warning(
_LOGGER.debug(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to add this because the guideline says: Handles device/service unavailable. Log a warning once when unavailable, log once when reconnected.

Copy link
Member

@rytilahti rytilahti May 20, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The keyword here is once and it should probably be emphasized more :-) Without looking deeper into the code, this probably will probably log even when the device is already marked as unavailable in homeassistant?

Instead of changing the log level, I assume the proper fix would include marking the device as unavailable on disconnects, and only log if the device was previously available.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is supposed to be logged once after the device disconnects. If the device manages to connect and a few seconds later it disconnects again this will be logged again.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And if the device stays disconnected this won't be logged again per the guideline.

@mib1185
Copy link
Contributor Author

mib1185 commented May 20, 2024

not needed as per #117722 (comment)

@mib1185 mib1185 closed this May 20, 2024
@mib1185 mib1185 deleted the androidtv_remote/do-not-blame-on-disconnected-device branch May 20, 2024 13:58
@github-actions github-actions bot locked and limited conversation to collaborators May 21, 2024
@bdraco bdraco removed this from the 2024.5.5 milestone May 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Android TV Remote : disable the log when the device is turned off
4 participants