You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
MG/5.0 without membership: has your strap ever stopped serving history? #2890
On my MG (fw 50.42.1.0) the console logs "Flash: certificate counter set to
3888000 sec." and "BLE: Lock status updated to UNLOCKED." whenever the official
app pushes a certificate (commands 155-158), about weekly. That is 45 days, so
the strap may lock itself if no new certificate arrives.
If your MG/5.0 has no active membership, could you share:
roughly when the membership ended, and the official app's last sync
firmware version
whether history offload still works today
whether your console mentions "Lock status" or "certificate counter"
I have not found anyone documenting what happens when this counter reaches zero.
Same symptom here: a WHOOP 5.0 / MG with no membership. History offload stopped working after the strap moved to firmware 50.43.2.0. History sync had been working before that update.
This repeats every reconnect, then: Backfill: WHOOP 5/MG offload empty 2× — … backing off the bounce loop.
Also logged on every connect: fw gate: no version decoded — len=109 at93=0 expected=50 … hex[88..<101]=00000000000000000000000000. The hello reply looks zeroed where the version would sit.
Already tried: removed and re-added the strap, reinstalled the app, cleared the legacy R22 flags from the Test Centre (all cleared). No change.
Has anyone on 50.43.x without a membership got history to offload again? Or is this the firmware refusing to serve history to a strap that has no membership certificate? I can share the full strap log if useful.
Thanks, that's a useful data point. Two details would help tell the 50.43 update apart from the 45-day certificate counter:
Roughly when did your membership end, and when did the strap install 50.43.2.0? Was history still offloading on the old firmware more than 45 days after the membership ended?
In the strap log you offered, are there any lines with "Lock status" or "certificate counter"?
The membership ended about 6 months ago. I don't know exactly when the strap installed 50.43.2.0.
History kept offloading normally for months after the membership ended, so well past 45 days.
It only stopped recently, which lines up with the firmware moving to 50.43.2.0.
No. I searched every strap log I have and none contain "Lock status" or "certificate counter".
The only firmware lines are DIS: firmware=50.43.2.0 (standard profile, no bond required).
Quick follow-up: nothing has changed on my side since 50.43.2.0. Every offload still ends with outcome=nothing-banked, and live HR and R-R still work fine.
#2736 looks like the same symptom on a WHOOP 4.0 (fw 41.17.6.0) with an expired membership. So the cause may be the membership or certificate state rather than the 50.43 firmware itself.
@ryanbr, do you have an idea what could make a strap refuse SEND_HISTORICAL_DATA like this? Is there anything I could capture to help? I can share a full strap log or run a Test Centre mode if that's useful. Thanks!
Activity
bogaczcyprien-svg commentedon Nov 3, 2026
Same symptom here: a WHOOP 5.0 / MG with no membership. History offload stopped working after the strap moved to firmware 50.43.2.0. History sync had been working before that update.
insertedHRRows/insertedRRRows> 0 on every flush).Backfill: WHOOP 5/MG offload empty 2× — … backing off the bounce loop.fw gate: no version decoded — len=109 at93=0 expected=50 … hex[88..<101]=00000000000000000000000000. The hello reply looks zeroed where the version would sit.Has anyone on 50.43.x without a membership got history to offload again? Or is this the firmware refusing to serve history to a strap that has no membership certificate? I can share the full strap log if useful.
rcorppublishing commentedon Nov 4, 2026
Thanks, that's a useful data point. Two details would help tell the 50.43 update apart from the 45-day certificate counter:
bogaczcyprien-svg commentedon Nov 4, 2026
Thanks! Answers:
History kept offloading normally for months after the membership ended, so well past 45 days.
It only stopped recently, which lines up with the firmware moving to 50.43.2.0.
The only firmware lines are
DIS: firmware=50.43.2.0 (standard profile, no bond required).bogaczcyprien-svg commentedon Nov 6, 2026
Quick follow-up: nothing has changed on my side since 50.43.2.0. Every offload still ends with
outcome=nothing-banked, and live HR and R-R still work fine.#2736 looks like the same symptom on a WHOOP 4.0 (fw 41.17.6.0) with an expired membership. So the cause may be the membership or certificate state rather than the 50.43 firmware itself.
@ryanbr, do you have an idea what could make a strap refuse
SEND_HISTORICAL_DATAlike this? Is there anything I could capture to help? I can share a full strap log or run a Test Centre mode if that's useful. Thanks!