Come sincronizzare il proprio Fitbit usando Linux

  36 Responses to “Come sincronizzare il proprio Fitbit usando Linux”

1. 

   Bob says:

   19 March 2014 at 15:26

   Galileo is great! One less reason to keep Windows around in a VM.

   After I downloaded galileo, it installed on Fedora 19 without a hitch. I used the following two commands

   yum -y install python-pip pyusb python-requests
   pip install galileo

   Looking forward to seeing the evolution of this product.

   Rispondi
2. 

   Richard says:

   28 March 2014 at 22:05

   Excellent, thank you for this guide.
   I only have one issue left now and thats running it as non sudo
   Followed your guide and created the udev rule, restarted udev etc and it works, but only once , after that it will only work using sudo.
   Seems to work if i pull dongle out and put it back in but will have to check that again in a bit.

   Again thank you for your superb guide

   Rispondi
3. 

   Chris says:

   28 April 2014 at 18:05

   I’ve made it easier for Ubuntu users and packaged galileo in a PPA, so now all you need to do is `sudo add-apt-repository ppa:cwayne18 && sudo apt-get update && sudo apt-get install galileo` and then reboot, and syncing will take place automatically

   Rispondi
   • 

     Dee says:

     5 October 2014 at 20:40

     Can this synch via the USB cable without the dongle on Ubuntu?

     Rispondi
     • 

       linuxari says:

       13 October 2014 at 20:14

       For what I know no, you need the dongle.
       The usb cable it’s just for re-charging

       Rispondi
   • 

     Jim in NH says:

     23 June 2015 at 03:44

     Great job Chris !!! Been trying get sync for a couple of weeks with no luck… Tried on daughter’s Mac and it synced yesterday….
     Tried your improved program tonight and saw this message:

     user@user-HP-Pavilion-g6-Notebook-PC:~$ galileo
     Tracker: BFEBF806E5E6: Skipped because recently synchronised

     Hope this means that the PC Dongle is talking with the fitbit charge HR. Am running Kubuntu 14.04 .

     Again, Thank you so much !!!

     Jim

     Rispondi
4. 

   Tim says:

   15 June 2014 at 18:57

   Followed Chris’s instructions for Ubuntu dated 04/26/2014 above on 14.04 amd64 and was advised “Unable to locate package galileo.”

   Rispondi
5. 

   Alan Jackson says:

   15 June 2014 at 20:34

   The install mostly worked for Ubuntu Precise, except for galileo itself.
   ]$ sudo apt-get install galileo
   Reading package lists… Done
   Building dependency tree
   Reading state information… Done
   E: Unable to locate package galileo

   ]$ sudo apt-get install fitbit-steps-indicator
   Reading package lists… Done
   Building dependency tree
   Reading state information… Done
   The following packages were automatically installed and are no longer required:
   libts-0.0-0:i386 twolame linux-headers-3.2.0-29
   linux-headers-3.2.0-29-generic libaften0 nvidia-settings-304 mjpegtools
   Use ‘apt-get autoremove’ to remove them.
   The following NEW packages will be installed:
   fitbit-steps-indicator
   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
   Need to get 8,070 B of archives.
   After this operation, 60.4 kB of additional disk space will be used.
   Get:1 http://ppa.launchpad.net/cwayne18/fitbit/ubuntu/ precise/main fitbit-steps-indicator amd64 0.2~precise1 [8,070 B]
   Fetched 8,070 B in 0s (25.4 kB/s)
   Selecting previously unselected package fitbit-steps-indicator.
   (Reading database … 839219 files and directories currently installed.)
   Unpacking fitbit-steps-indicator (from …/fitbit-steps-indicator_0.2~precise1_amd64.deb) …
   Setting up fitbit-steps-indicator (0.2~precise1) …

   Rispondi
6. 

   Noel Jackson says:

   4 August 2014 at 20:52

   This is fantastic. I was wanting to get this going on Raspberry Pi.
   Worked on it with both Raspbian and Pidora. Pidora required less work.

   Raspbian:
   be sure to apt-get update and apt-get dist-upgrade and apt-get install python-requests (as mentioned above)
   usbhid.quirks=0x2687:0xfb01:0x0004 added to /boot/cmdline.txt (to keep usbhid from taking over the dongle)
   manual upgrade of libusb (1.0.19 I think, http://sourceforge.net/projects/libusb/, download, unpack, ./configure, make and make install — configure required more packages but I don’t recall which) in order for 1.0.0b2 of pyusb and 0.5dev (maybe 0.4 too) of galileo to work.

   Pidora needed pyusb updated only.

   galileo needed adjustments to the write and read params in dongle.py similarly as mentioned above.

   Also had trouble running in daemon mode (my preference). Kept getting Resource busy on the second run. Finally figured out how to fix that (after many hours trying to understand the code). In dongle.py in class USBDevice change:

   def __del__(self):
   pass

   to:

   def __del__(self):
   self.dev.reset()
   pass

   This made it work nicely.

   Now just need to add wifi dongle and connect to local wireless, pick a nice central location and power it up and let it go.

   Rispondi
   • 

     Benoît Allard says:

     12 January 2015 at 19:01

     Your fix has been integrated into galileo. Thank you very much !

     Next time that you spend some time fixing an open-source project, consider proposing the change to the original project so that more people can benefit from it ! I would probably have never seen it on my own !

     Rispondi
     • 

       henry chan says:

       15 February 2017 at 09:15

       I agree. Thank you for your program. Is there a plan to use a 3rd party/native BLE instead of a fitbit dongle?
       I would like to see a version that uses the ANT dongle, for backward compatibility.

       Would like to get in touch with some development work. You can contact me at the email address below. Thanks.

       Rispondi
7. 

   Kelly Johnson says:

   1 October 2014 at 04:20

   I have the same unable to locate package issue:
   E: unable to locate package galileo

   Ubuntu version is 12.04

   Rispondi
   • 

     Nathan says:

     16 November 2014 at 05:14

     Same issue 12.04 (precise) 64bit E: unable to locate package galileo

     Rispondi
8. 

   Ashley says:

   19 November 2014 at 02:28

   Is this known to work with Fitbit Charge?

   Rispondi
   • 

     BrianA_MN says:

     24 June 2015 at 20:22

     Yes this will work with Charge model of FitBit.
     I have one and set this up on Slackware64 14.1.

     Rispondi
9. 

   Liz says:

   26 December 2014 at 04:05

   I had to register my FitBit Charge on a Windows 7 machine but it appears I am able to sync with Fitbit using galileo.

   Is there a way to register a FitBit using galileo?

   Rispondi
   • 

     Jim in NH says:

     8 August 2015 at 15:28

     Hi Liz,
     Did you ever get a reply on your question if Fitbit can be registered using Linux ?

     Thanks,
     Jim

     Rispondi
10. 

    susja says:

    10 January 2015 at 02:53

    Hello,
    Could someone help me? It looks that I successfuly install galileo but it failed to discover tracker. I have this error:
    **
    galileo -d
    2015-01-09 20:50:08,810:DEBUG: Configuration: {‘httpsOnly’: True, ‘logLevel’: 10, ‘doUpload’: True, ‘keepDumps’: True, ‘includeTrackers’: None, ‘forceSync’: False, ‘rcConfigName’: None, ‘dumpDir’: ‘~/.galileo’, ‘daemonPeriod’: 15000, ‘excludeTrackers’: set([]), ‘mode’: ‘sync’}
    2015-01-09 20:50:08,810:DEBUG: galileo initialising
    2015-01-09 20:50:08,829:INFO: Disconnecting from any connected trackers
    2015-01-09 20:50:08,830:DEBUG: –> 02 – 2
    2015-01-09 20:50:08,830:DEBUG: Switching to a newer pyusb compatibility mode
    2015-01-09 20:50:08,836:DEBUG: <– CancelDiscovery
    2015-01-09 20:50:08,840:DEBUG: <– TerminateLink
    2015-01-09 20:50:08,842:DEBUG: <– 02 ( 00 ) – 3
    # A serious error happened, which is probably due to a
    # programming error. Please open a new issue with the following
    # information on the galileo bug tracker:
    # https://bitbucket.org/benallard/galileo/issues/new
    # /usr/local/bin/galileo: 0.4.2
    # Python: 2.7.3 (default, Dec 18 2014, 19:03:52) [GCC 4.6.3]
    # Platform: Linux eliya-LifeBook-A6025 3.2.0-74-generic #109-Ubuntu SMP Tue Dec 9 16:47:54 UTC 2014 i686 i686
    # pyusb: 1.0.0rc1
    # requests: 0.8.2
    # yaml: 3.10 (with libyaml)
    Traceback (most recent call last):
    File "/usr/local/bin/galileo", line 9, in
    load_entry_point(‘galileo==0.4.2’, ‘console_scripts’, ‘galileo’)()
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 267, in main
    }[config.mode](config)
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 197, in sync
    for tracker in syncAllTrackers(config):
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 38, in syncAllTrackers
    fitbit.disconnect()
    File “/usr/local/lib/python2.7/dist-packages/galileo/tracker.py”, line 48, in disconnect
    self.dongle.ctrl_read()
    File “/usr/local/lib/python2.7/dist-packages/galileo/dongle.py”, line 212, in ctrl_read
    data = self.read(0x82, length, timeout)
    File “/usr/local/lib/python2.7/dist-packages/galileo/dongle.py”, line 191, in read
    return self.dev.read(*params)
    File “/usr/local/lib/python2.7/dist-packages/usb/core.py”, line 925, in read
    self.__get_timeout(timeout))
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 835, in intr_read
    timeout)
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 920, in __read
    _check(retval)
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 588, in _check
    raise USBError(_strerror(ret), ret, _libusb_errno[ret])
    usb.core.USBError: [Errno 19] No such device (it may have been disconnected)

    Rispondi
11. 

    susja says:

    10 January 2015 at 05:15

    Well … it looks that it works with Charge as well.
    Initially I reported that it does not work but after I restarted Charge Fitbit and ran command it discovered and synced.
    **
    $ galileo -v
    2015-01-09 23:14:42,744:INFO: Disconnecting from any connected trackers
    2015-01-09 23:14:44,758:INFO: Discovering trackers to synchronize
    2015-01-09 23:14:48,768:INFO: 1 trackers discovered
    2015-01-09 23:14:48,768:INFO: Tracker A2F88DECDDE5 was recently synchronized; skipping for now
    2015-01-09 23:14:48,769:INFO: Tracker A2F88DECDDE5 skipped due to configuration
    Tracker: A2F88DECDDE5: Skipped because recently synchronised

    Rispondi
12. 

    trevor says:

    22 January 2015 at 04:33

    On Linux Mint 17 and
    FitBit one
    I may be out of my depth here but….
    I used you tute using method 1 and got to “:-

    val-GA-78LMT-S2P pyusb-master # apt-get install galileo
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    galileo is already the newest version.
    0 to upgrade, 0 to newly install, 0 to remove and 33 not to upgrade.

    then i ran galileo :-

    val-GA-78LMT-S2P pyusb-master # galileo
    # A serious error happened, which is probably due to a
    # programming error. Please open a new issue with the following
    # information on the galileo bug tracker:
    # https://bitbucket.org/benallard/galileo/issues/new
    # /usr/bin/galileo: 0.5dev
    # Python: 2.7.6 (default, Mar 22 2014, 22:59:38) [GCC 4.8.2]
    # Platform: Linux val-GA-78LMT-S2P 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 athlon
    # pyusb: 1.0.0rc1
    # requests: 2.2.1
    # yaml: own version
    # Last communications:
    Traceback (most recent call last):
    File “/usr/bin/galileo”, line 9, in
    load_entry_point(‘galileo==0.5dev’, ‘console_scripts’, ‘galileo’)()
    File “/usr/lib/python2.7/dist-packages/galileo/main.py”, line 284, in main
    }[config.mode](config)
    File “/usr/lib/python2.7/dist-packages/galileo/main.py”, line 193, in sync
    for tracker in syncAllTrackers(config):
    File “/usr/lib/python2.7/dist-packages/galileo/main.py”, line 31, in syncAllTrackers
    if not dongle.setup():
    File “/usr/lib/python2.7/dist-packages/galileo/dongle.py”, line 225, in setup
    self.dev.set_configuration()
    File “/usr/local/lib/python2.7/dist-packages/usb/core.py”, line 811, in set_configuration
    self._ctx.managed_set_configuration(self, configuration)
    File “/usr/local/lib/python2.7/dist-packages/usb/core.py”, line 129, in managed_set_configuration
    self.backend.set_configuration(self.handle, cfg.bConfigurationValue)
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 781, in set_configuration
    _check(self.lib.libusb_set_configuration(dev_handle.handle, config_value))
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 588, in _check
    raise USBError(_strerror(ret), ret, _libusb_errno[ret])
    usb.core.USBError: [Errno 16] Resource busy

    Is there enough info here to make a comment on what’s wrong here ?

    Rispondi
    • 

      Jonathan Carter says:

      16 May 2015 at 17:07

      According to:

      https://bitbucket.org/benallard/galileo/issue/73/resource-busy

      You can downgrade python’s usb package (from b2 to b1) to get it to work. This worked for me:

      sudo pip uninstall pyusb
      sudo pip install -Iv pyusb==1.0.0b1

      Rispondi
13. 

    Tim Dawson says:

    12 March 2015 at 06:11

    For what it’s worth . . . Current distro (*NOT* package!) as of 3/8/2015, and Slackware 14.1 . . . Added the two python dependencies, placed the udev rule, typed “run” and watched it work . . .

    Not sure why they call that the “hard way” . . . to me, packages where you don’t get to see what is going on is the really hard way . . . But in any case, this worked flawlessly right out of the box!

    – Tim

    Rispondi
    • 

      BrianA_MN says:

      24 June 2015 at 21:01

      I’m running Slackware64 14.1. But ran into some issues.
      Using slackbuilds or sbopkg, python-requests. Checkout pyusb, but modify the slackbuild and info files to version 1.0.0b1 and the change lines 43 and 73 of slackbuild for .rst files. Don’t use pyusb-1.0.0b2 because it won’t let you access the dongle.
      Then downloaded and unpacked galileo to its own directory, setup the udev rule as described at the end of this article, NOT AS described in the galileo directory README. You might need to check the two id’s to verify proper idVendor and idProduct using lsusb from root. Mine matched both (with the first four (idVendor) and last four (idProduct) ) for the udev rule as listed above.
      Now type ./run from the Galileo folder as root. You might get a warning of SSL issue, but a second ./run doesn’t create the warning. Last thing is to setup a cron to run every 30 minutes as user.

      Rispondi
14. 

    alwinB says:

    18 April 2015 at 15:41

    Maybe I didn’t get the point, but the problem I’m faced with is that the fitbit bluetooth dongle is not recognized by the system (Kubuntu 14.04).
    When plugging it to the PC running a Windows XP with VM-ware player, the dongle is recognized.

    Any useful hint for a solution is appreciated.

    Alwin

    Rispondi
15. 

    Sean Gibson says:

    12 May 2015 at 22:38

    Excellent! Works a treat, thanks

    Rispondi
16. 

    Andrea says:

    19 May 2015 at 10:29

    Hello, thanks for the guide. I successfully installed galileo (and even changed the udev file), but the problem is that my tablet is a HUAWEI and doesn’t connect with my FitBit Flex, is not supported. Long story short, I managed to have an account on FitBit.com, a galileo on my laptop, but the two are not connected.
    I tried to do
    
galileo --force

    but it gave me this error
    
2015-05-19 11:22:27,854:ERROR: Fitbit server refused data from tracker AAD5CDB483D2, reason: Unpaired tracker contacted site. Tracker Wire Id: df955e2f1607
Tracker: AAD5CDB483D2: Synchronisation failed: Unpaired tracker contacted site. Tracker Wire Id: df955e2f1607

    On the website I don’t find any place where I can insert the tracker ID.
    So I’m stuck.
    Is there a way to match the device with the account with galileo?

    Thanks

    Rispondi
17. 

    Richard says:

    13 June 2015 at 02:35

    Andrea, did you ever get your “unpaired tracker” issue resolved? I’m having the same problem with my brand new FitBit Zip.

    Rispondi
18. 

    Julien says:

    15 November 2015 at 15:40

    Hi,
    I’m on linux mint and I also have the issue #a serious error happened …
    I downgraded python usb package as Jonathan Carter said and now I have another error :

    $ ~ sudo galileo -v
    2015-11-15 15:37:37,123:INFO: Disconnecting from any connected trackers
    2015-11-15 15:37:39,128:ERROR: Dirty state, not able to start synchronisation.
    $

    Rispondi
19. 

    Mike says:

    26 December 2015 at 13:17

    Hi. I’m trying to use a raspberry pi 2 to sync with a new fitbit flex. When I manually type galileo I just get a carriage return. When I type galileo I get the following.

    # A serious error happened, which is probably due to a
    # programming error. Please open a new issue with the following
    # information on the galileo bug tracker:
    # https://bitbucket.org/benallard/galileo/issues/new
    # /usr/local/bin/galileo: 0.4.4
    # Python: 2.7.9 (default, Mar 8 2015, 00:52:26) [GCC 4.9.2]
    # Platform: Linux raspberrypi 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l
    # pyusb: 1.0.0b2
    # requests: 2.4.3
    # yaml: own version
    Traceback (most recent call last):
    File “/usr/local/bin/galileo”, line 9, in
    load_entry_point(‘galileo==0.4.4’, ‘console_scripts’, ‘galileo’)()
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 276, in main
    }[config.mode](config)
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 206, in sync
    for tracker in syncAllTrackers(config):
    File “/usr/local/lib/python2.7/dist-packages/galileo/main.py”, line 37, in syncAllTrackers
    dongle.setup()
    File “/usr/local/lib/python2.7/dist-packages/galileo/dongle.py”, line 159, in setup
    self.dev.set_configuration()
    File “/usr/local/lib/python2.7/dist-packages/usb/core.py”, line 799, in set_configuration
    self._ctx.managed_set_configuration(self, configuration)
    File “/usr/local/lib/python2.7/dist-packages/usb/core.py”, line 128, in managed_set_configuration
    self.backend.set_configuration(self.handle, cfg.bConfigurationValue)
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 730, in set_configuration
    _check(self.lib.libusb_set_configuration(dev_handle.handle, config_value))
    File “/usr/local/lib/python2.7/dist-packages/usb/backend/libusb1.py”, line 552, in _check
    raise USBError(_strerror(ret), ret, _libusb_errno[ret])
    usb.core.USBError: [Errno 16] Resource busy

    Rispondi
    • 

      Mike says:

      26 December 2015 at 13:20

      These are the setup instructions I followed so far. Also note to get that debug output pasted above I used galileo –dump command.

      http://mbmccormick.com/2014/05/syncing-fitbit-on-raspberry-pi-with-galileo/

      Rispondi
20. 

    david allen says:

    27 December 2015 at 22:27

    I followed instructions successfully. There is hex data in ./galileo/#####. How does one interpret it?

    Rispondi
21. 

    Ben Downes says:

    30 December 2015 at 04:12

    I got an error:

    2015-12-29 22:04:10,036:ERROR: Insufficient permissions to access the Fitbit dongle

    To be able to run the fitbit utility as a non-privileged user, you first
    should install a ‘udev rule’ that lower the permissions needed to access the
    fitbit dongle. In order to do so, as root, create the file
    /etc/udev/rules.d/99-fitbit.rules with the following content (in one line):

    SUBSYSTEM==”usb”, ATTR{idVendor}==”2687″, ATTR{idProduct}==”fb01″, SYMLINK+=”fitbit”, MODE=”0666″

    The dongle must then be removed and reinserted to receive the new permissions.
    Exception usb.core.USBError: USBError(13, u’Access denied (insufficient permissions)’) in <bound method FitBitDongle.__del__ of > ignored

    I changed the rules to look like this entry:
    https://github.com/mbmccormick/fitbitpi/blob/master/99-fitbit.rules

    Now it works.

    Rispondi
22. 

    Ben Downes says:

    30 December 2015 at 04:14

    I forgot to mention that for Fedora 23 I needed to run:
    udevadm control –reload-rules

    then remove and reinsert the dongle

    Rispondi
23. 

    pozorvlak says:

    3 February 2016 at 16:25

    Thanks for this! I only had to make a couple of changes to get it to work on Fedora 22:

    sudo apt-get install python-usb python-requests becomes sudo dnf install pyusb python-requests

    and sudo service udev restart becomes sudo service systemd-udevd restart.

    Rispondi
24. 

    Shawn Q says:

    2 April 2016 at 04:47

    FYI the same instructions work fine for Lubuntu 15.10, even udev rules just make sure you restart udev and replug the dongle.
    Only caveat is that you need to install on Windows/Macintosh using their app first, at least one time.
    Afterwards, plug the same dongle into the Lubuntu system, run: galileo -v –force sync
    Should see a successful synchronization eventually, and bob’s your uncle!

    Rispondi
25. 

    Erik L. says:

    9 July 2017 at 15:47

    I had success installing on Linux Mint 18.2 and syncing my FitBit One. I suspect that means my phone is crapping out and not the much cheaper FitBit.

    Rispondi

 Leave a Reply Cancel reply

Your Comment

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

Name (required)

E-mail (required)

URI

Codice CAPTCHA *