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

Handle accuracy zero correctly in enter/leave events. #2833

Merged
merged 3 commits into from
Aug 16, 2016

Conversation

pavoni
Copy link
Contributor

@pavoni pavoni commented Aug 15, 2016

Description:
Zero accuracy checks prevented beacon transitions working properly.

Related issue (if applicable): fixes #2830

Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#

Example entry for configuration.yaml (if applicable):

Checklist:

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

If code communicates with devices, web services, or a:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
  • New files were added to .coveragerc.

If the code does not interact with devices:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • Tests have been added to verify that the new code works.

if 'acc' in data:
if data['acc'] == 0.0:
valid_gps = False
_LOGGER.info("Zero GPS reported")
Copy link
Member

Choose a reason for hiding this comment

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

These should not be info but warning. I also think that it might be nice if we can say which device reported it? (using dev_id?)

@balloob
Copy link
Member

balloob commented Aug 16, 2016

Looks good 🐬 . Can merge when comments addressed

@pavoni pavoni closed this Aug 16, 2016
@pavoni pavoni reopened this Aug 16, 2016
@pavoni pavoni merged commit 91e24de into dev Aug 16, 2016
@pavoni pavoni deleted the fix_owntracks_beacon_accuracy_bug3 branch August 16, 2016 09:34
@home-assistant home-assistant locked and limited conversation to collaborators Mar 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Owntracks enter/leave beacon transitions not working
2 participants