https://www.macrumors.com/2026/10/15/withings-plus-apple-health-syncing/

It’s not too late to just admit you fumbled this Withings.

Update: Verge has it too https://www.theverge.com/tech/1012350/withings-plus-subscription-new-users-october-13-2026

#SyncGate

So Withings just posted their official "clarification" on the support forum regarding the $99/year paywall for Apple Health sync, and it is a masterclass in corporate gaslighting.

Let’s break down the sheer amount of bullshit in their statement:

1. "Withings+ funds the services around your data" Absolute lie. Writing your weight to Apple Health via HealthKit or Google Health Connect is a local, on-device API call. It happens directly between the Withings app and the Apple Health app on your phone. It requires ZERO cloud computing, ZERO server maintenance, and ZERO of their new "AI Connector" processing. It costs Withings exactly $0.00. They are intentionally holding a free, local API call hostage to force you into paying for their AI medical features that nobody asked for.

2. "Existing accounts are grandfathered! Nothing changes for you!" This isn't a favor; it’s a calculated divide-and-conquer tactic. They know that if they retroactively paywalled existing users, they’d face massive backlash, European consumer protection probes, and tanked app ratings overnight. By grandfathering old accounts, they are hoping we just shut up and look the other way while they screw over every new customer. Bought a scale for your partner or kid? Congrats, their new account is paywalled on the hardware you already own.

3. "You can still export a CSV for free!" Ah yes, thank you Withings. Let me just open a spreadsheet and manually import rows of data on my iPhone every morning in 2026. We bought smart scales specifically for automation. Offering a manual CSV export as a "feature" is frankly insulting. A $15 no-name Chinese scale off Amazon manages to sync automatically to Apple Health for free, but a $200 Withings scale can't?

Don't let them spin this as "funding the ecosystem." It’s a blatant, predatory cash grab. If they get away with paywalling basic, local API syncs today, what are they going to lock behind Withings+ tomorrow?

Please continue to vote and write >>>>> HERE in the official support forum <<<<<

// DISCLAIMER: This code is for educational and illustrative purposes only.
// It is provided "as is" without any express or implied warranties.
// Use at your own risk. The author assumes no liability for errors or damages.

Here's how to get and keep your data.

I've tried to make these two scripts as cross-platform compatible as I can, but it's only been tested on Mac. It's python 3, so if you know what that is, you should know what you are doing.

Main script, copy and paste into a file named "backup_iphone.py":

#!/usr/bin/env python3
"""
Cross-platform (Windows / macOS / Linux) iPhone backup + extract.

Runs idevicebackup2 (libimobiledevice) to take a local backup, then calls the
extractor from extract_withings.py (keep both files in the same folder).

Requires libimobiledevice tools on PATH:
  macOS:    brew install libimobiledevice
  Linux:    sudo apt install libimobiledevice-utils usbmuxd
  Windows:  Apple's USB driver (iTunes or Apple Devices app) plus the
            libimobiledevice Windows binaries on PATH.
Encrypted backups also need:  pip install iphone_backup_decrypt

Usage:
  python backup_iphone.py [--backup-root DIR] [--out DIR] [--full] [--no-extract]
"""
import argparse
import shutil
import subprocess
import sys
from pathlib import Path

HERE = Path(__file__).resolve().parent
sys.path.insert(0, str(HERE))
def run(cmd, check=True, capture=False):
    return subprocess.run(cmd, check=check, text=True, capture_output=capture)

def main() -> None:
    ap = argparse.ArgumentParser(description=__doc__.split("\n")[1])
    ap.add_argument("--backup-root", type=Path, default=Path.home() / "iphone_backups")
    ap.add_argument("--out", type=Path, default=Path("withings_out"))
    ap.add_argument("--full", action="store_true", help="force a full (non-incremental) backup")
    ap.add_argument("--no-extract", action="store_true", help="only take the backup")
    args = ap.parse_args()

    for tool in ("idevice_id", "idevicepair", "idevicebackup2"):
        if not shutil.which(tool):
            sys.exit(f"Missing {tool} - install libimobiledevice and put it on PATH.")

    ids = run(["idevice_id", "-l"], capture=True).stdout.split()
    if not ids:
        sys.exit("No iPhone found. Plug it in, unlock it, and tap Trust if prompted.")
    udid = ids[0]
    print(f"Device: {udid}")

    # Pair (no-op if already paired). May require tapping Trust on the phone.
    run(["idevicepair", "-u", udid, "pair"], check=False)
    if run(["idevicepair", "-u", udid, "validate"], check=False).returncode != 0:
        sys.exit("Pairing validation failed.")

    args.backup_root.mkdir(parents=True, exist_ok=True)
    print("Starting backup (keep the phone unlocked; this can take a while)...")
    cmd = ["idevicebackup2", "-u", udid, "backup"]
    if args.full:
        cmd.append("--full")
    cmd.append(str(args.backup_root))
    # If the phone has backup encryption on, idevicebackup2 will need that password.
    if run(cmd, check=False).returncode != 0:
        sys.exit("Backup failed.")

    backup_dir = args.backup_root / udid
    print(f"Backup complete: {backup_dir}")
    if args.no_extract:
        return

    from extract_withings import extract_encrypted, extract_unencrypted, is_encrypted

    args.out.mkdir(parents=True, exist_ok=True)
    if is_encrypted(backup_dir):
        print("Backup is encrypted.")
        extract_encrypted(backup_dir, args.out)
    else:
        print("Backup is not encrypted.")
        print(f"Copied {extract_unencrypted(backup_dir, args.out)} files.")
    print(f"Done. Output in: {args.out.resolve()}")

if __name__ == "__main__":
    main()

Script #2, copy and paste into a file named "extract_withings.py", the filename must be this name, and in the same directory, as the first script calls this one:

#!/usr/bin/env python3
"""
Extract an app's files from a local iPhone backup (encrypted or unencrypted).

Usage:
    python extract_withings.py "<backup folder>" [output folder]

Example (Mac):
    python extract_withings.py \
      "$HOME/Library/Application Support/MobileSync/Backup/<device-id>" ./withings_out

Encrypted backups need:  pip install iphone_backup_decrypt
"""
import getpass
import plistlib
import shutil
import sqlite3
import sys
from pathlib import Path

BUNDLE_ID = "com.withings.wiScaleNG"
# Matches AppDomain-<id>, AppDomainGroup-group.<id>, AppDomainPlugin-<id>.*
DOMAIN_LIKE = f"%{BUNDLE_ID}%"
# Only SQLite files under a CoreData directory. The trailing % also catches the
# -wal and -shm sidecar files, which CoreData stores need to be complete.
PATH_LIKE = "%CoreData%.sqlite%"
def is_encrypted(backup: Path) -> bool:
    with open(backup / "Manifest.plist", "rb") as f:
        return bool(plistlib.load(f).get("IsEncrypted", False))
def extract_unencrypted(backup: Path, out: Path) -> int:
    db = sqlite3.connect(f"file:{backup / 'Manifest.db'}?mode=ro", uri=True)
    rows = db.execute(
        "SELECT fileID, domain, relativePath FROM Files "
        "WHERE domain LIKE ? AND relativePath LIKE ? AND flags = 1",
        (DOMAIN_LIKE, PATH_LIKE),
    ).fetchall()
    count = 0
    for file_id, domain, rel in rows:
        src = backup / file_id[:2] / file_id
        if not src.exists():
            continue  # listed in manifest but not stored in this backup
        dest = out / domain / rel
        dest.parent.mkdir(parents=True, exist_ok=True)
        shutil.copy2(src, dest)
        count += 1
    return count
def extract_encrypted(backup: Path, out: Path) -> None:
    try:
        from iphone_backup_decrypt import EncryptedBackup
    except ImportError:
        sys.exit("Encrypted backup: run  pip install iphone_backup_decrypt  first.")
    passphrase = getpass.getpass("Backup password: ")
    eb = EncryptedBackup(backup_directory=str(backup), passphrase=passphrase)
    eb.test_decryption()  # raises if the password is wrong
    kwargs = dict(
        relative_paths_like=PATH_LIKE,
        domain_like=DOMAIN_LIKE,
        output_folder=str(out),
        preserve_folders=True,
    )
    try:
        eb.extract_files(domain_subfolders=True, **kwargs)
    except TypeError:
        # Older library versions lack domain_subfolders
        eb.extract_files(**kwargs)
def main() -> None:
    if len(sys.argv) < 2:
        sys.exit(__doc__)
    backup = Path(sys.argv[1]).expanduser()
    out = Path(sys.argv[2] if len(sys.argv) > 2 else "./withings_out").expanduser()
    out.mkdir(parents=True, exist_ok=True)
    if not (backup / "Manifest.plist").exists():
        sys.exit(f"No Manifest.plist in {backup} - is this the device's backup folder?")
    if is_encrypted(backup):
        print("Backup is encrypted.")
        extract_encrypted(backup, out)
    else:
        print("Backup is not encrypted.")
        n = extract_unencrypted(backup, out)
        print(f"Copied {n} files.")
    print(f"Done. Output in: {out.resolve()}")
if __name__ == "__main__":
    main()

Now that you have all that, here's how you use it:

1. Read the comments in the top of the backup_iphone.py script to ensure you have the necessary utilities/modules installed. The two things it needs are: libimobiledevice and iphone_backup_decrypt.
2. Connect your iPhone to your computer via USB cable. Tell your iPhone to trust the computer (if prompted)
3. Run the file to perform a backup:

python3 backup_iphone.py --backup-root ./iphone_backups --out ./withings_out

1. Type your passcode to start the backup. This should be an encrypted backup, You do have your phone set to encrypt backups, don't you? and in the example above, it will place the backup in the folder "iphone_backups". Note that backups are incremental, and it does the entire phone on the first backup. So the first backup will take a while. Subsequent backups will take a lot less time as only changed files will be backed up.

2. After the backup is complete, the script will prompt you for your password - The password should be the one you set up on your phone when you told it to do encrypted backups.

3. Your files will be in the withings_out directory. Specifically:
   ./withings_out/AppDomain-com.withings.wiScaleNG/Library/Application Support/coredata

In there you will find a list of files:

The "XXXXXXXX" will be replaced with your Withings' account identifier. You will have additional sets of these files for each authorized user you share your devices with.

That's your data. All of it.

Write an app to read it all, or import data to Apple health, or Google's offering.

Got the BF last week and the first couple of days the bodyfat % seemed to be right (around 15%) but the last 2 days it dropped down to 12% with no real weight change. 12% seems too low for me so not sure what happened.

EDIT Update 2:

No need to be Mac-Specific anymore. I now have a script that will get the files from your iPhone no matter what platform you run - Mac Windows Linux.

EDIT: Update (new screenshots in the replies)

All data is now categorized into Sleep, Activity, Heart, Nutrition, Respiration.

All data from a single session that takes multiple readings are grouped by session, not individually.

StethO results are now available for review.

I have to finish up putting sleep info into HealthKit.

I am not going to pursue the nutrition and activity importations, I've done enough.

Devices I do not own (Scanwatch, Aura, U-Scan, CGM) may likely not appear, but every effort to allow Scanwatch readings to work has been done (it should work). The app will import any readings taken from a Withings device that have not been previously imported into Apple Health.

Removal of private information from the project files - then:

Upload to GitHub & documentation.

If you have an M-series Mac, read my instructions at the end of this top post. If you like tinkering and can use Xcode, you can have a lot of fun with this.

If you do not have an M-series Mac, this will still work - but you will need a 3rd party utility to get it to work.

ORIGINAL POST:

In response to the recent HealthKit developments, I'm nearing completion on an application that will fix the issue. An interesting side effect is the application reveals a hell of a lot more than just potential HealthKit data, it reveals - EVERYTHING. But the primary purpose is extraction of Withings data for HealthKit import.

Your data is placed in an iCloud directory and all processing on it is done on-device (iPhone).

Your Metrics Categories show up in a drill-down menu, shown below:

Select an item, say BMR, and you get a list of entries:

Tap on one and you get the details of every measurement:

Same with BP and other measurements:

Sleep data too:

And sleep details:

Aside from reviewing your data, you can then select to import any compatible data into HealthKit.

The app does duplicate detection, so it will not duplicate any Withings entry that already exists to any entry by the app that already exists.

The app also will delete all entries it makes into HealthKit, so its actions are fully reversible.

This is a proof of concept. I still have to bring in the workout sessions.

So the next question is:

Where do I get this data?

Pretty much it is already on your phone. There are several ways of making it accessible. I'm developing in a Mac environment, but I wanted to make sure the input to the utility is platform-agnostic as much as possible.

For Android users, there is probably a similar mechanism to get to the data.

I will not be releasing this as an application on the app store - for obvious reasons. But the source code will be made available for other's research purposes.

I'll answer questions as they pop up.

In the meantime, you can prepare to save your personal data:

If you have a Mac, go to the App Store and download the Withings' application. Log in and view your data on your Mac as you do on your phone. Then stand by.

If the app gets pulled, or you do not have a Mac, you can still get the data off of your iPhone jumping through an additional hoop. But it is available.

You do not need to jailbreak your device, you do not need to use Withings API - all data in already present locally on your device. Nothing is sent out over the internet, only to and from HealthKit and iCloud.

New to this sub. Just want to share the surprise I got from my wife's withings scale. Over the past 11 years, I have occasionally stepped on my wife's withings body+ scale, and it recorded my weight. Turns out all the weight had been stored in Withing's server. I was able to extra the weight via screen cap and reading it with AI:

The data has been highly useful in figuring out my "safe weight", when it's correlated with my liver enzyme values. I've recently been diagnosed with severe fatty liver and starting treatment with it.

I have to say, I've been happy with Withings as a company, especially how it supports its product and handles its data for the past decade. Hopefully it stays a similar company for the next decade, despite the pressures of investors. Fingers crossed.

I’m considering it. Aside from all this Apple Health malarkey:

- I can wear the Oura Ring in the sauna and in the ocean.

- I put all this food info into MyFitnessPal which syncs to Withings. Withings then give me no insights about my food whatsoever.

Another big one:

- IMO Withings work best if you go all in on their ecosystem. Makes it a bit hard to do so in Australia where their piss tracker is unavailable (the app relies on this for nutrition insights).

Preamble: for those considering the purchase of any Withings product I have to strongly discourage even looking at this company. They have been trying to pivot to a health portal company and are now locking local hardware features like Apple Health sync behind a subscription that offers absolutely nothing you can’t get with any other AI granted access to your health data. Every single one of these companies trying to lock-in your data and then resell Gemini or OpenAI is dead to me.

That said, I promised an update on the BodyFit and here it is.

After months and months they finally shipped an update that fixed the super low body fat readings. My first Dexa was 13.5% while Withings would always report half that; 6-9%. But my latest Dexa is very close to the point of being essentially 98% as good as Dexa. The scale nailed both muscle loss and fat gain over the 3 months between my scans. I was skeptical since I was clearly getting stronger and gaining muscle while the scale was telling me the opposite. I was sure the Dexa would show different results but it actually confirmed what the scale was saying. I had gained 1 lb of arm and shoulder muscle but LOST 3 lbs of leg muscle. My big complaint is this was not at all obvious from the scale. So much of the app is devoted to garbage now like Readiness, BodyPath, Sleep Score, Steps, Heart Rate, and on and on. All metrics that have nothing to do with Withings and are just scraped from Apple Health. I did know that muscle was trending down and fat up but despite the much touted segmented measurements, the fact I was losing in the legs while gaining in the arms was not presented anywhere in the app making the Dexa still needed for insights the app could give me if it was not wasting so much time trying to be everything except a scale. The hardware works. The app sucks and gets worse on every release. If Withings would just focus on matching not just accuracy but useful presentation of the data they capture and less time repackaging Apple Health data they would have a winning product but I have no faith left in this company.

The scale works, if a different product team would write a proper app this thing could be incredible but I am likely still going to be getting quarterly Dexa scans because the app is so useless.

The watch is new to me and today I did 1k steps on a walking pad/treadmill to see if it logged them and it didn’t. Not a single step but it is logging when walking otherwise. Additionally, it is saying I did five flights of stairs today when I have only done 1. Any ideas? 💃🏻Thanks :)

Hey r/withings,

As many of you have seen, Withings recently made a terrible, anti-consumer move: starting October 13th, new accounts are forced to pay $99/year for Withings+ just to sync their data to Apple Health.Writing to Apple Health via HealthKit is a local process on the phone. It requires zero cloud computing or server costs from Withings. This is nothing but a blatant cash grab, and it ruins the experience for families, partners, or anyone buying a new device.

Complaining here on Reddit is good, but we need to hit their official channels if we want them to backtrack.

I just created a thread on the official Withings Support Forum calling them out on this nonsense and their contradictory customer service replies (support literally told me it's a "standard free feature" and then in the next sentence said new accounts must pay for it).

Unacceptable: Apple Health Sync is now behind a $99/year paywall for new accounts – Withings | Support

Please take 60 seconds to click the link, upvote the post, and leave a quick comment. If enough of us make our voices heard directly on their platform, they’ll be forced to address it before this becomes the new standard.

Let’s not let them get away with paywalling basic features on hardware we already paid a premium for.

Given the recent change to lock metric syncing to Apple Health (for new accounts now but who knows what’s next) behind a pointless $99/year subscription, aside from not buying any more products, we should update our App Store reviews to reflect our dissatisfaction.

I’m now a fan for life

tldr: if you make a new withings account on or after oct 12 2026, the app won't send your weight to apple health unless you pay for withings+ ($9.99/mo or $99.99/yr). older accounts seem grandfathered for now.

set up a new withings body this week. bought it specifically because it's sold as apple health compatible. went to turn on apple health sync and got a paywall instead (screenshot).

"Syncing your measurements to Apple Health is part of Withings+ and needs an active membership. It starts the moment you join."

14 day trial then $99.99/year, or $9.99/month.

the funny part is importing FROM apple health into the withings app is still free. so they'll happily take all your apple health data, you just can't send your own weight back out without paying... you can still manually download a csv/pdf of your data.

as far as i know it's tied to your account, not the scale, so it should hit any withings device on a new account (body, body smart, body comp, body scan, watches etc). if you're an existing user don't delete your account and make a new one or you'll probably lose the grandfathering.

none of the "apple health compatible" listings on amazon mention any of this. returned mine.

if you set up a new account after oct 12 let me know if you got the same screen so people searching for this can see it confirmed.

also read:

https://www.reddit.com/r/withings/comments/1x3a30l/withings_is_locking_down_their_api_for_new/

https://developer.withings.com/developer-guide/v3/withings-solutions/withings-api-plans/

Hi everyone,

We’ve been closely following the active discussions regarding the recent updates, and we’d like to offer some clarity and reassurance about what is changing and who is affected. 

• 1.) If you already have a Withings account, nothing changes. If you created your account on or before October 12, 2026, automatic third-party sync stays free. This is tied to your account, not your device, so buying a new scale, watch or any other Withings device in the future won’t affect it. Your sync stays free.
  
• 2.) Every user, member or not, can export their full history as CSV or PDF at any time, keep importing data from other apps, and share data with their doctor through HealthLink and PDF reports. None of this is behind a paywall.
  

What’s changing for new members: for accounts created from October 13, 2026, automatic sync to third-party apps is part of Withings+.

Members also get:

• Exclusive scores (Heart Age, Readiness, Glucose Resilience)
  
• An improved Health Assistant that remembers your health profile and trends over time
  
• ECG reviews by qualified physicians through Cardio Check-Up
  
• Better-priced access to medical services with Sunrise, Fay and Dune (US)
  
• The new Withings AI Connector (MCP), to securely connect your data to the AI assistants you use
  

New members can try everything, sync included, with the free trial. If a membership ends, sync pauses, no data is lost, and sync resumes as soon as the membership is active again.

Our mission hasn’t changed. We exist to help people take care of their health at home, so they can spot changes early and act before small issues become big ones. Withings+ helps us do that over the long term: it funds the services around your data, while your data itself stays yours.

If you’re unsure about your account status, had sync issues before October 13, or think you should have free sync but don’t, please contact our support team, we will be happy to review your situation.

Thank you for your continued feedback and for being part of the community,

Team Withings

Does anyone know the sizing of a replacement sapphire crystal for a Scanwatch Nova 42mm.

I am in New Zealand, so unlikely to be able to return to an agent for replacement. So I thought I would try Ali Express.

Withings is locking down their API so that new accounts (signups after today) need a Withings+ subscription to export data. It looks like existing accounts will be grandfathered in (for now...)

Notice on the API page (& link):

Withings+ becomes required on the Start for Free API plan from October 12, 2026.Details

Withings accounts created after that date will need a membership to share health data with a free-plan app, including apps that are already live.

Accounts created before that date are unaffected, and Enterprise lifts the requirement for specific use cases.

https://developer.withings.com/developer-guide/v3/withings-solutions/withings-api-plans/

Hi everyone,

I’m looking for some feedback regarding the Withings ScanWatch 2.

My wife (23F, active, in perfect health) recently started wearing this watch. For the past week, it's been pretty stressful: she has received about 15 "Signs of AFib" alerts triggered by the automatic optical (PPG) scan. The weirdest part is that these alerts happen almost exclusively at night while she's sleeping, or in the evening when she's lounging on the couch on her phone.

I have the exact same watch and I've had absolutely zero alerts.

Instead of panicking, we cross-referenced all the app data (sleep graphs, continuous heart rate) and did some testing. Here is what we found:

The timing of the alerts: 100% of the nighttime alerts happen at the exact minute she changes sleep phases (e.g., going from deep to light sleep) or within 10 minutes of waking up.

Background heart rate: During these supposed "AFib" nights, her average resting heart rate is excellent and highly stable (around 55 bpm). The continuous graph shows no chaotic spikes or elevated rates.

Strap tightness: She was wearing the original silicone band very tightly so the watch wouldn't move. Result: in the morning, she had a deep, red circular indentation from the sensor on her skin. We suspect a "tourniquet" effect that restricts capillary micro-circulation, which, combined with nighttime movement, completely throws off the optical sensor.

Manual ECGs (the ultimate proof): Every time she took a manual ECG to check, the result was a perfect "Sinus Rhythm". The other night, right after an alert, she took 3 ECGs in 3 minutes: the 1st said "AFib", the 2nd was "Inconclusive" (she was adjusting her posture), and the 3rd was "Normal".

Our family doctor brushed it off, saying that at 23 years old, with no congenital conditions, it's virtually impossible and these are just sensor reading errors.

Question: is anyone else experiencing the same thing ? What is the rate of false signs that occur regularly ? How likely is it that those signs are not false given her good health condition and doctor's assessment ?

Morning 👋

Just an anecdote as n=1.

I’m 37 and have never had any known heart issues.

This morning I woke up feeling completely fine and was getting ready to head out for a 10-mile hike.

Stepped on my Body Scan 2 for my weekly longevity scan and it detected AFib. Thought that was odd, as I’d never seen that before, and my WHOOP w/ECG functionality (which I’ve had for about a year) has always shown normal sinus rhythm.

So I ran an ECG on my WHOOP, which also detected possible AFib.

Fast forward a couple of hours - went to urgent care, who referred me to the ER after seeing the same on their ECG.

Now in the hospital with confirmed AFib, and I’m currently lying here while they run more tests.

The strange thing is I still feel completely fine. 🤞🙏

If it wasn’t for the Body Scan 2, I’d probably be halfway through my hike right now, completely unaware.

So, just some n=1 anecdotal evidence that the BS2 earned its money today. 👍

From my regular activities this is what syncs/doesn’t sync:

Syncs perfectly:
Outdoor walks and runs

Syncs duration, no heart rate data, start time is off by 10 hours (hey Withings, did you know that time zones exist???)
Weights
Yoga

Doesn’t sync at all (really, this is just pathetic at this point)
Indoor walks and runs
Pilates

Indoor walks and runs is core and why does yoga sync but not Pilates? It’s madness.

Now I’m sure if the Teams Withings account chimes in here they’ll reply with I’ll pass your feedback onto the relevant development teams but this is pretty basic stuff that should’ve been picked up during QA testing. It should never have shipped in its current state and you’ve got no excuse for screwing it up this badly.

I started using my new Body Fit last week and was pleased as the weight was within 0.1 lbs of my previous Withings Body Comp and my trusty digital scale I have used for years.

I use my digital scale every day and do my Body Comp once a week (GLP1 journey) when it syncs with all my health apps.

Yesterday the Body Fit weighed in at 2 lbs higher than the other two scales. Then the second time it was 1.5 lbs higher. Basically I do not trust it now. Is this a common issue with the Body Fit? I was so excited to add the additional metrics.

I’m looking at the BPM Vision for example and notice a line “ECG (Europe only)”

If I buy this unit when I’m in the UK next month and use it with my US Withings account, will ECG be enabled or disabled?

I don’t particularly want the US FDA deciding what I can and can’t use from my own European designed and produced products.

Can’t read the word behind kcal remaining, burr something. Does this chart fluctuate depending on my daily activities?

I had a ScanWatch 1, and I was sooo happy with it. I had a few software issues that I reported to support, but I never got a proper answer. Still, it was so good that I didn't care.

When it broke due to normal wear and tear, I thought it was a good time to upgrade to the V2.

Biggest mistake ever...

The 2 is a freaking NIGHTMARE to charge. This is a known issue, but that’s not all.

How on earth is it possible that the developers aren’t doing anything about it? I mean, how hard is it to show “charging” in the app? How hard is it to show “charging” on the watch? No, better yet, make it a double tap on the watch that doesn’t work—especially since the only way to make it work is NOT to touch the watch when it starts charging.

Another issue: My family and I have had “simple” issues with the app, too, like WhatsApp calls not showing up on the watch. I’ve reported the issue 10 times and have always been told the developers know about it and are working on it. Five years later, it’s still not fixed...

Great product, AWFUL team!