Base station eventually cannot see tracker

[marcushall42]

If I leave the base station running for a long time (several hours, it seems) I seem to be getting into a state where it cannot hear the beacon from the tracker. The fitbit_client.py code initializes the base station just fine, but then it seems to go endlessly waiting to hear the beacon. If I unplug and re-plug the base station, I can successfully sync again.

I did see reports of a failure to sync for other platforms, and it seems that a software update fixed things, but at a first glance at the logs from their newest software, it seems to be programming the base station just the same (I have not done a detailed comparison yet, though).

Has anybody else seen this problem before? I have a little script that runs fitbit_client.py with a timeout that kills it after 10 minutes, then restarts it again. I'd like to leave it running "forever" and have things just sync, but I keep running into this issue and have to unplug and re-plug the base station to get a successful sync.

BTW, is there any reason to supply "Commodore 64" instead of "linux" for the os? Just to dig at somebody at fitbit if they actually read their logs?

[adamcrown]

+1

I seem to be having the same issue.

• Ubuntu 11.10
• 3.0.0-17-generic-pae IndexError: list index out of range #30-Ubuntu SMP Thu Mar 8 17:53:35 UTC 2012 i686 i686 i386 GNU/Linux
• Python 2.7.2+

[thefotios]

+1

I have the same problem

• Fedora 16
• 3.3.2-6.fc16.x86_64
• Python 2.7.2

I also noticed that re-plugging the basestation seems to fix the problem.

[alexg0]

+1

[dinyar]

Any progress on this? Anyone found a solution other than plugging in and out? I'm running it in a script that kills it after 5 minutes and call that script every 15 minutes via cron, but that doesn't seem to help..