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

openhaystack: store battery status in FindMy packet #3566

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bobrippling
Copy link
Collaborator

This allows a user to know their device's battery, as well as its location

See also:
seemoo-lab/openhaystack#185
https://github.com/MatthewKuKanich/FindMyFlipper/blob/e5a678e33dd17af46bb63050be4c9d10e17f6252/FindMyFlipper/findmy_state.c#L126-L137

@olivierbarriere let me know what you think - I'll be testing this over the next week or so

See also:
  seemoo-lab/openhaystack#185
  https://github.com/MatthewKuKanich/FindMyFlipper/blob/e5a678e33dd17af46bb63050be4c9d10e17f6252/FindMyFlipper/findmy_state.c#L126-L137

From biemster/FindMy#53
  Advertising byte:
    ?xx1rrmrr
    r: reserved
    m: maintained
    x: can be set. x must be:
      00: full
      01: medium
      10: low
      11: critical

  this doesn't seem to correspond with the above links
@gfwilliams
Copy link
Member

This looks cool. I'd be fine with merging it anyway.

Interestingly it's nice to have a way to send some data back. For instance if you had a remote letterbox or something it could report battery level as full if there was something in it, or nearly empty if there wasn't.

@bobrippling
Copy link
Collaborator Author

Yes that would be very cool to repurpose the 4 values as another form of communication - or it'd be interesting to see if "invalid" battery values made it through the network too.

I've had this running but my watch hasn't appeared on the network in a while, so can't confirm yet

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

Successfully merging this pull request may close these issues.

2 participants