-
Notifications
You must be signed in to change notification settings - Fork 66
IndexError: list index out of range #30
Comments
Another one, probably related:
|
bank1 and bank2 don't have the same format on my device as on yours. I could make the parsing dependant on the firmware version or such, but I need to know which firmware version you have ... Is it documented somewhere ? |
I think it's something like 2.13a? |
I've got:
Is that what you're talking about ? |
Made it dependant on my own (4, 14), see benallard@322fe7b |
At a closer look, what you called in the code the "firmware version" is called "deviceInfo.hardwareRev" in the fitbit web request. I do think this could be used to distinguish the Fitbit and the FitBit Ultra, beter than the app version or the BSL version ... What's your's ? |
I get the same error message about list index out of range. I have a fitbit ultra, rev 4.14 (displayed at boot up/reset). I tried your commit above, and it fixed the problem. Can it be integrated into main, or does it cause problems with fitbit classic? |
@alfs It just looks like the project maintainer has other priorities. Actually, about this particular problem, I switched the decision bit from the software version to the hardware revision in a later commit: benallard@6f0248a , as I guess the hardware revision indicates us better if we are talking to a classic or to an ultra tracker. |
Project maintainer has been moving, so yeah, other priorities is about right. (The mozilla-central commits are because I'm paid to do that :) ) I see this commit is in the #34 uber pull request. Unfortunately I wasn't paying attention and merged things backward (this is why I usually never use pull request merge buttons), so I'll need to fix up the patch to merge it. Might also take me a bit to code review 'cause there's kind of a lot going on there. I'll try to get to it soon though. |
Running fitbit.py:
The text was updated successfully, but these errors were encountered: