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

Correct out of range detection #3

Open
kamaradclimber opened this issue Mar 31, 2017 · 2 comments
Open

Correct out of range detection #3

kamaradclimber opened this issue Mar 31, 2017 · 2 comments

Comments

@kamaradclimber
Copy link
Collaborator

At least with my nut tracker, out of range detection does not seem to work as expected.

Device might not be detected as disappeared even when out of range.

@kirichkov
Copy link
Owner

I've noticed myself that both my Mi Fit band and my nut tracker have been marked as 'home', when I expected at least once in a while to disappear. As it turns out, when restarting hass, the gem would crash, and never update the status, so they'd be persistently 'home'. Maybe something similar is happening to you?

#6 should resolve this.

@kirichkov
Copy link
Owner

Have you found a solution for this? I'm still observing this issue with my nut tracker. My fitness band (Xiaomi Mi Band 1S) does disappear and reappear (marked as home and away), but the nut is never submitted as missing, only as being at home. It is set as "hide if away", so I changed it to rule this out as a reason.

kb5zuy pushed a commit to kb5zuy/home_assistant-ble that referenced this issue Jan 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants