03-24-2019 04:39
03-24-2019 04:39
I wore 2 watches on the same account for years. My day starts at 630am& doesnt end until 11-1130pm. Battery dies quickly & Im not near power at all. I ordered a vesta just yesterday. After ordering I saw that you can’t have an ionic & vesta on the same acct. why?
I am not going to add what I do at night from 2 different accounts, that’s your job. And I will not go back to a lesser Fitbit like an alta. I love the big faces of the bigger watches. So why can’t I have 2 watches on the same account no matter what kind they are?
03-24-2019 07:35
03-24-2019 07:35
@aumannjoy These smartwatches by Fitbit have near identical operating systems. The app "sees" them as being the same device. You can only have one of each device on your account. This is a very frustrating situation for many users (include me in that).
Here is a link to a Feature Suggestion asking for multiple smartwatches at the same time. Please cast your vote and leave a comment.
A bigger concern to me -- why are your batteries dying so quickly? You should have days of life on each device. Are your devices still under warranty? I think you should contact Support about your battery life.
Laurie | Maryland
Sense 2, Luxe, Aria 2 | iOS | Mac OS
Take a look at the Fitbit help site for further assistance and information.
03-24-2019 11:43
03-24-2019 11:43
03-24-2019 12:01 - edited 03-24-2019 12:03
03-24-2019 12:01 - edited 03-24-2019 12:03
I don't buy the explanation that OS is almost the same and this is a reason. I think somebody was lazy and in the app used singleton or few innocent static vars when new OS was introduced ( probably hacking through the code and rushing to get the app out the door ) without thinking that this will make it very difficult to work simultaneously with other devices ( left as one of the "todo" things which will stay unfinished forever 😄 ). Refactoring usually means rewrite so I'm not surprised Fitbit's would rather tell everyone to post a feature suggestion than fix the issue. From my experience, I know how hard to fix "mistakes" like that are. I worked with lots of legacy code that had to be upgraded to the new requirements and statics, TLS, singletons used all over the shop because nobody thought that someday requirements may be changed. I see no reason why on-device OS would affect communication with the mobile app ( although, there's also an option of badly design communication protocol but didn't bother to trace that ). Knowing Fitbit software from the user perspective, I'd rather go with the first option - rush, laziness and as result spaghetti-code which now isn't easy to fix. I wouldn't bet my money that this issue will be addressed anytime soon if ever 😉 As much as the explanation is convenient for Fitbit, I don't buy it. It's just lousy, amateur coding. Rushing the untested product out the door and hacking the way through to get the milestone done - that's why we can't use two or more OS3.0 devices with the app simultaneously.
03-24-2019 12:19
03-24-2019 12:19