https://forums.garmin.com/de/sports-fitness/laufen-multisport/en-USTelligent Community 13https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2044788Sun, 12 Jul 2026 06:11:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:f5926d3b-4a95-4c82-a422-c0474af461779601729Bei mir (Forerunner 965) hatte ich nach den letzten Updates auch teilweise Sync-Probleme mit Garmin Coach, allerdings nicht ganz so extrem. Manchmal half es, den Coach-Plan in der App komplett zu löschen (nicht nur anhalten), die Uhr danach per Kabel mit Garmin Express zu synchronisieren und dann einen neuen Plan anzulegen.Leider scheint es aktuell bei vielen Nutzern so zu sein, dass die Wochen-Zählung und die Trainingshistorie zwischen Uhr und App immer mal wieder auseinanderdriften. Garmin scheint das noch nicht richtig im Griff zu haben . Hast du schon mal versucht, den Plan über die Web-Version von Garmin Connect (am PC) anzulegen und zu verwalten? Manchmal ist die App da etwas buggy.https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2044786Sun, 12 Jul 2026 06:05:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:6521046a-9231-4ef1-8450-4cb9295c77079601729[quote userid="718886" url="~/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein"] Hallo, nach einen Update meiner Forerunner 965 (Version bleibt aber 27.09) stimmt der Garmin Couch Plan zur Verbesserung meiner Fitness zwischen Forerunner 965 und Garmin Connect nicht mehr überein. Desweiteren wird der Couch Plan aus der Connect App nicht gelöscht, wenn ich diesen absolviert habe, dass war vor dem Uhr Update definitiv der Fall. Erst wenn ich den Couch Plan anhalte und wieder neu starte und Uhr und App synchronisiere stimmen sie wieder überein bis zum nächsten Tag, dann geht das Spielchen wieder von vorne los. Wie erwähnt war das vor dem Update der Uhr nicht der Fall. Neu verbinden, Cache leeren von der App, Uhr synchronisieren über Express usw. haben nichts gebracht. Kennt jemand diesen Fall oder hat jemand den gleichen Fall? Vielen Dank im Voraus Burghard [/quote]https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/brustgurte-und-sensoren/439724/erfahrungen-zur-haltbarkeit-und-zuverlassigkeit-des-hrm-600Sat, 11 Jul 2026 18:11:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:ca46b827-6dcd-4648-90fa-45b6749eebceFlotte MotteLiebe Forumsmitglieder, ich möchte gerne fragen, ob jemand Erfahrungen zur Haltbarkeit des HRM 600 hat. Ich laufe jährlich rund 3000 km, d. h. durchschnittlich und habe ein Exemplar des HRM 600 seit 7 Monaten in Gebrauch. Grundsätzlich bin ich mit dem Gurt gegenüber den Vorgängerversionen sehr zufrieden was den Leistungsumfang angeht. Gegenüber den Vorgängerversionen ist nach meiner Erfahrung auch die Pulserfassung nun deutlich zuverlässiger. Die ärgerlichen, plötzlich und unerklärbar aufgetretenen Pulssprünge mit extrem hohen oder extrem niedrigen Pulswerten, welche hierdurch auch die Trainingsbewertungen seitens des Laufcomputers (in meinem Fall einer Fenix 7 x) nachhaltig negativ beeinflußten (falsche Einschätzung der Trainingseffiziezen, schlechtere Vorhersagewerte für Wettkämpfe), gehören mit diesem Brustgurt nach meinen Erfahrungen der Vergangenheit an. Nach etwas mehr als 7 Monaten Gebrauch und ca. 1800 km Laufleistung waren nun die Pulswerte jedoch plötzlich regelmäßig deutlich zu niedrig (rund 15 - 20 Schläge), dies trotz aller Pflege nach Anleitung (7 x spülen unter fließendem Wasser, dann 1 x Waschmaschine) und bei äußerlich perfekt erscheinendem Pulsgurt.sodaß ich die hoch heroben und anaeroben kaum noch bzw. nicht mehr erreichen konnte und damit auch die Trainingsbeurteiungen mit Trainingsstatus etc. nicht mehr stimmten. Ich habe mir daher einen zweiten HRM 600 gekauft, mit dem die Pulswerte 15 - 20 Schläge höher sind und damit auch die Trainingsbeurteilung durch die Laufuhr wieder stimmig ist. Dies ist auch der Fall, wenn ich den Sender des alten Gurtes an den neuen anknipse, sodaß ein fehlerhafter Sender ausgeschlossen werden kann, die Ursache jedoch offensichtlich auf den Gurt selber zurückzuführen ist. Offensichtlich ist daher der Pultgurt nach (schon) 7 Monaten und 1800 km Laufleistung trotz Pflege nach Bedienungsanleitung defekt, was angesichts des vgl. hohen Preises nicht so erfreulich ist. Erwartet hätte ich mir eine Haltbarkeit von ca. 2 Jahren. Daher meine Frage: hat jemand von Euch weitere Erfahrungen zur Haltbarkeit und Zuverlässigkeit des HRM 600? Über ein kleines Feedback würde ich nicht freuen! Happy Running!https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-265/439683/dear-garmin-product-support-teamFri, 10 Jul 2026 22:16:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:2de7b3fd-415c-4055-9003-11d9992593e53667823I live in South Korea and have been using a Garmin Forerunner 55 since 2021. In June 2026, I purchased a Forerunner 265 and tested it while wearing it simultaneously with my Forerunner 55. The Forerunner 265 showed clear and repeatable distance measurement errors, so I sent it to Garmin Korea’s service center and received a replacement unit. However, the replacement Forerunner 265 showed the same problems. I therefore sent the replacement unit to the service center as well. Garmin Korea informed me that they could not find any defect in the device. However, they were unable to explain the recorded discrepancies and test results that I provided. Garmin Korea has now offered to issue a refund. Although I appreciate the refund offer, I would still like to understand the technical cause of these repeated errors. The same problems occurred on two separate Forerunner 265 units, while my older Forerunner 55 recorded the distances correctly during simultaneous tests. ## Device setup and troubleshooting I tested the replacement Forerunner 265 after completing the following steps: * Removed the previous device registration from Garmin Express, Garmin Connect, and the smartphone’s Bluetooth settings * Registered the device again and performed additional tests, but the errors continued * Removed the device again from Garmin Express, Garmin Connect, and Bluetooth * Performed a full data deletion and factory reset * Set up the watch without transferring settings from the previous device * Used the default settings except for the items listed below * Selected **All Systems + Multi-Band** for Running, Track Running, and Walking activities * Set sleep mode so that it did not change the watch face * Changed data recording frequency to **Every Second** * Confirmed that no software update was available Despite these steps, the distance errors continued. ## 1. Distance undercounting in Walking mode ### Test method I wore the Forerunner 265 and Forerunner 55 simultaneously and walked on open courses whose distances had been checked using satellite maps. ### Test results **** June 25 — 3 km course * Forerunner 265: 2.83 km * Forerunner 55: 3.00 km **** June 30 — 3 km course * Forerunner 265: 2.93 km * Forerunner 55: 3.01 km **** July 4 — 5 km course * Forerunner 265: 4.64 km * Forerunner 55: 5.05 km **** July 6 — 7 km course * Forerunner 265: 6.57 km * Forerunner 55: 7.00 km The Forerunner 265 consistently recorded a shorter distance, whereas the Forerunner 55 was close to the measured course distance. The errors were too large and too consistent to be explained by ordinary GPS variation. For example, on the 5 km course, the Forerunner 265 undercounted the distance by approximately 360 metres compared with the known course distance and by approximately 410 metres compared with the Forerunner 55. ## 2. Incorrect lap distances and lap positions in Track Running mode I also conducted two tests on a standard 400-metre running track. ### Test results **** June 26 — five laps * Forerunner 265: 2,070 metres in total * Four laps were not recorded as 400 metres * Forerunner 55: 2,000 metres in total, with no incorrect lap distances **** June 26 — another five-lap test * Forerunner 265: 2,030 metres in total * Three laps were not recorded as 400 metres * Forerunner 55: 2,000 metres in total, with no incorrect lap distances The lap trigger was set to a position-based setting. On the Forerunner 265, the lap was not triggered consistently at the same point. The trigger position moved by approximately 10 metres, and the recorded lap distances included values such as 420 metres, 410 metres, and 400 metres. Even if the first lap is triggered several metres away from the original starting point, I would expect the watch to use a consistent reference point for the following laps. I would also expect a correctly configured Track Running activity on a standard 400-metre track to record each completed lap as 400 metres. This consistency is one of the main reasons for using a dedicated Track Running mode rather than an ordinary GPS Running activity. ## Responses from Garmin Korea A Garmin Korea service representative suggested that the track might not be a standard track. However, it is a standard 400-metre track, and I have used my Forerunner 55 on the same track for approximately four to five years without this problem. The representative also suggested that a distance-based lap setting might be more accurate than a position-based lap setting in Track Running mode. I do not understand this explanation. If the watch simply waits until its GPS-calculated distance reaches 400 metres, there is little advantage in using a dedicated Track Running mode. A runner cannot follow the exact measurement line perfectly throughout every lap. My understanding is that Track Running mode should identify the track and lane, correct the GPS path to the known track geometry, and count each completed circuit as a 400-metre lap when the runner returns to the relevant lap position. Otherwise, the device would merely be measuring ordinary GPS distance while running on a track. ## Questions for Garmin I would appreciate a technical explanation addressing the following questions: 1. Why did two separate Forerunner 265 units repeatedly undercount distance in Walking mode while the Forerunner 55 recorded the same courses accurately? 2. Could this be caused by the Forerunner 265 firmware, activity profile, distance-calculation algorithm, speed filtering, arm-movement processing, or another software-related factor rather than a hardware defect? 3. Why did Track Running mode record laps of 410 or 420 metres and move the lap trigger position by approximately 10 metres on a standard 400-metre track? 4. In Track Running mode, is each lap distance supposed to be corrected to the known track and lane geometry, or is it still calculated mainly from raw GPS distance? 5. Is Garmin aware of similar reports involving distance undercounting during walking or inconsistent lap detection on the Forerunner 265? 6. Are the procedures used by the service center sufficient to detect this type of activity-specific or firmware-related error? A device may pass a basic hardware inspection but still produce incorrect distance measurements during actual use. I am not claiming that every Forerunner 265 has this problem. However, I experienced substantially the same errors with both the original device and the replacement unit, under repeated tests and after a complete factory reset. A refund resolves the purchase issue, but it does not explain why the problem occurred. I would therefore appreciate it if this case could be reviewed by Garmin’s technical or engineering team rather than treated only as a routine service-center inspection. I can provide the original Garmin activity files, screenshots, GPS tracks, lap data, serial numbers, service records, and comparison records from the Forerunner 55 if required. If it would assist your investigation, I am willing to provide my Garmin account ID and authorize Garmin to access the relevant activity data associated with my account. Thank you for reviewing this matter. I look forward to receiving a technical explanation. Sincerely, Suseok Kim South Koreahttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-570/439355/coached-planMon, 06 Jul 2026 04:17:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:7da60cca-95d9-43a8-b0a5-25f692240029BlondeBirdFlynnI started a coached plan for a race in October. The plan sets out the phases; base, build, peak etc. It firstly doesn't give you an option to say you only run 2-3 times a week so I don't often complete all the suggested run and my schedule changes so I might want to do my long run on a different day. All this means, I just can't move out of the base phase. Does anyone know a hack to be able to move up a phase and how to move training from the suggested day to a more suitable day?https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-265/411092/musikwiedergabe-hakt-beim-training/2041653Mon, 29 Jun 2026 18:29:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:6a0211f6-27e2-444e-ab63-49505c543abf3696786Ich glaub's nicht. Ich benutze die gleichen Kopfhörer. Ob das Zufall ist? Könnte also an dem Kopfhörern liegen....ich werde mal andere koppeln und gucken, ob das besser klappt. Mit manuell übertragenen MP3s hab ich es noch nicht getestet. Danke für die Rückmeldung.https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-265/411092/musikwiedergabe-hakt-beim-training/2041651Mon, 29 Jun 2026 18:21:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:3c26fd80-221c-4e4e-aa24-10d3c8c6dee34553803Hallo, ich benutze Anker Soundcore P20i. Die uhr ist nagelneu. Fehler ist reproduzierbar. Meistens nach dem ersten oder zweiten Lied. Getestet nur mit Spotify App. Hast du schon mit manuell übertragenen MP3 getestet?https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-265/411092/musikwiedergabe-hakt-beim-training/2041558Mon, 29 Jun 2026 13:34:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:1afcbbc7-e4e1-4f75-9413-e827a3aacabd3696786Bis jetzt leider nicht... Was verwendest du für Kopfhörer? Ich kann es mir nicht erklären. Habe nur noch die Bluetooth-Version in Verdacht. Sonst ist bei mir eigentlich alles auf dem neusten Stand.https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-265/411092/musikwiedergabe-hakt-beim-training/2041308Sun, 28 Jun 2026 10:30:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:0e60fef2-cb38-4fb2-b81d-163f2e3ebb7a4553803Ich habe das gleiche Problem. Gibt es eine Lösung?https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/438301/if-you-lift-and-run-your-965-thinks-your-strongest-weeks-are-your-worst-weeks/2040877Fri, 26 Jun 2026 10:52:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:2359a7ed-ce1e-42b1-8e6f-0c0bee9961159557070bluefish , thanks. Fair correction: Status isn't pure pace/HR. It weighs training load, and a hard lift session does add to load via HR and EPOC. So "strength is invisible" was too strong on the load side. But the verdict is a comparison: load vs fitness trend, and fitness = VO2 Max. Your own quote pins where that comes from: - "activities with VO2 max results from running or cycling" Lifting yields no VO2 Max, so it adds nothing to the fitness side. Net: a heavy block pushes load up while fitness stays flat. Load up, fitness flat, is the doc's own recipe for Unproductive/Strained. So the asymmetry is the whole story: lifting earns you the strain, never the fitness.https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-970/438478/garmin-970-gesture-sensitivity-to-sensitive-now-ever-since-the-update-17-33Mon, 22 Jun 2026 05:53:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:3668fc9c-6b2e-4de7-aa7f-0d7c0a237cae7677936ever since the 17.33 update, the wrist gesture sensitivity has become way too responsive just the slightest movement triggers the wake, even when I don’t want it to. Anyone else having this problem/ any fix yet ?970https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-970/438477/garmin-970-gesture-sensitivity-to-sensitive-now-ever-since-the-update-17-33Mon, 22 Jun 2026 05:53:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:7fee2b85-08e8-4398-95cb-27bee80caf607677936ever since the 17.33 update, the wrist gesture sensitivity has become way too responsive just the slightest movement triggers the wake, even when I don’t want it to. Anyone else having this problem/ any fix yet ?970https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2039599Mon, 22 Jun 2026 04:05:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:20ab1c35-e38c-44ae-a367-c7f700a95686Burghard Guten Morgen, letztes Update der Garmin Support hat sich gemeldet. Um es kurz zu machen nichts weiß man. Sie wissen nicht was ich meine, bzw. ich drücke mich schlecht aus und sie wünschen mir viel Spaß mit meiner Forerunner 965. Nochmals vielen Dank für eure Hilfe. VG Burghardhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/438301/if-you-lift-and-run-your-965-thinks-your-strongest-weeks-are-your-worst-weeks/2039112Thu, 18 Jun 2026 18:33:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:3d9e52f7-3638-4cd0-ab5f-2c6432d998b2bluefish[quote userid="2315305" url="~/de/sports-fitness/laufen-multisport/f/forerunner-965/438301/if-you-lift-and-run-your-965-thinks-your-strongest-weeks-are-your-worst-weeks"]I build a Garmin strength-logging app[/quote][quote userid="2315305" url="~/de/sports-fitness/laufen-multisport/f/forerunner-965/438301/if-you-lift-and-run-your-965-thinks-your-strongest-weeks-are-your-worst-weeks"]Training Status, and the Productive / Unproductive / Detraining label are built almost entirely from the relationship between your pace and your heart rate during running (and cycling).[/quote] ..“ What Are the Different Training Status States? Peaking: you are in ideal race condition. Your recently reduced training load is allowing your body to recover and fully compensate for earlier training. You should plan ahead, since this peak state can only be maintained for a short time. Productive: your current training load is moving your fitness level and performance in the right direction. You should plan recovery periods into your training to maintain your fitness level. Maintaining: your current training load is enough to maintain your fitness level. To see improvement, try adding more variety to your workouts or increasing your training volume. Recovery: your lighter training load is allowing your body to recover, which is essential during extended periods of hard training. You can return to a higher training load when you feel ready. Strained: Your performance ability is currently limited with inadequate recovery as a probable cause. This can occur, for example, during periods of unusually high training load. Alternatively, health and lifestyle factors may be interfering with your ability to bounce back from strenuous activities. Consider taking it easy until your body catches up. Unproductive: your training load is at a good level, but your fitness is decreasing. Your body may be struggling to recover, so you should pay attention to your overall health including stress, nutrition, and rest. Detraining: you are training much less than usual for a week or more, and it is affecting your fitness level. You can try increasing your training load to see improvement. Overreaching: your training load is very high and counterproductive. Your body needs a rest. You should give yourself time to recover by adding lighter training to your schedule. No Status: the device needs one or two weeks of training history, including activities with VO2 max. results from running or cycling, to determine your training status. NOTE: If the overall status (i.e. Peaking, Productive, Maintaining, etc.) has not changed from day to day or activity to activity, this does not mean the underlying metrics are not updating or changing. This just means that you are still within the specific range for that overall status state.“.. https://support.garmin.com/en-US/?faq=VxKazDQ2mkAmDoQbJriEBA#:~:text=Training%20status%20can%20be%20viewed%20on%20your%20Garmin,text.%20For%20details%2C%20refer%20to%20your%20owner%27s%20manual .https://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/438301/if-you-lift-and-run-your-965-thinks-your-strongest-weeks-are-your-worst-weeksThu, 18 Jun 2026 16:19:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:950a7ab5-87dc-4055-bd88-49790b973d339557070I build a Garmin strength-logging app, so I have skin in this, and I'll keep that to one paragraph at the very end. The reason I'm posting here is a structural problem that hits every hybrid athlete on this board no matter what they run, and I want to put numbers on it instead of vibes. Here's the claim, and I'll defend it with my own unflattering data: if you lift hard and run on a Garmin, the month you lift hardest can be the month your watch grades you worst. Start with how the headline verdicts are actually computed. VO2 Max, Training Status, and the Productive / Unproductive / Detraining label are built almost entirely from the relationship between your pace and your heart rate during running (and cycling). The engine watches how fast you move for a given HR, tracks how that's trending, and rolls it into a fitness number and a one-word verdict. That's a genuinely good model for endurance. It is also a model with no slot for strength. A heavy squat triple produces a wildly different HR-to-output relationship than a tempo run, and there's simply no field in the VO2 Max calculation where "moved 405 for a triple" can land. Strength isn't weighted lightly here. It's a null input. The math never sees it. Now watch what that does over a real block. Here's my n=1, and I'm posting the numbers that make me look bad on purpose. Roughly an eight-week stretch on my Forerunner 965 where I deliberately went lift-heavy: squat and pull volume climbing week over week, top squat sets moving from a grindy 365 lb to a clean 405, total tonnage up about 30% by the end. To isolate the effect, I kept my running roughly constant in character, same easy-pace routes, same rough weekly mileage, so my run-specific fitness trend (the pace-at-HR curve the watch actually measures) sat basically flat as a control. Nothing about my endurance got worse. The watch's verdict over that same window : - VO2 Max ticked down 2 points (51 to 49). - Training Status flipped to Unproductive in week 3, then sat at Unproductive/Strained for most of the block. - One deload week, after a particularly brutal leg session, it briefly showed Detraining. Read that back. Strength up across the board, endurance held flat by design, and the headline verdict said I was getting worse and possibly detraining. That's not a Garmin bug. That's the model doing correct arithmetic on the only signal it ingests. With running held flat and strength invisible, a stale-or-slightly-declining VO2 Max is exactly what the math should output. The verdict isn't wrong about running. It's just structurally blind to half of what I did, and then it renders a one-word judgment on my whole athletic life anyway. This is the part I think trips people up: the answer is not "learn to read your readiness scores better." Reading them more carefully doesn't help when the input set is incomplete by design. The fix is to stop letting a running-only model grade your entire training. Concretely, during a lifting block : 1. Track the run-specific fitness trend separately from the headline label. If your pace-at-HR on easy runs is steady or improving, your endurance fitness is fine no matter what the one-word verdict says. 2. Treat Unproductive/Detraining during a heavy lift block as missing-data noise. Backing off your lifting to please the algorithm is the actual training mistake here. 3. Judge the block by the block's own goal. If the goal was strength, the squat numbers are the scoreboard, not VO2 Max. To be fair, I'm not claiming heavy lifting can't touch the endurance picture at all: fatigue, sleep, and HR response during conditioning work can nudge things, and I'd genuinely like to hear that second-order discussion. But the first-order effect, the big one, is that strength is a null input and the verdict reflects that. So here's the replication ask, because I'd rather this be a data thread than a gripe thread. Pull up your own history and check one specific thing: did your Training Status flip to Unproductive or Detraining specifically on your heaviest lifting weeks, while your running stayed roughly the same? Post your VO2 Max delta and the label for that window. I'm especially interested in anyone whose numbers behave differently than mine. If your Status held Productive through a genuine strength block with flat running, I want to understand why, because that would sharpen the picture. One product note, since it's why I know this gap so intimately: I build a strength app that records lifting sessions to Garmin via the native FIT activity format. To be completely clear about what that does and doesn't do: no app fixes VO2 Max. Recording the session natively only stops your strength work from being totally invisible to load and history; VO2 Max stays a running number, full stop. I'm not here to sell you out of this problem, because the core of it can't be sold away. So, the open question for the board: has your watch's verdict ever talked you out of training you knew was working? Noahhybridstrengthtrainingvo2maxhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2038686Wed, 17 Jun 2026 04:44:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:c45b165f-45b6-4f8e-885e-e1d940762247Burghard Guten Morgen, ich möchte nochmal ein kurzes Feedback geben. Garmin hat sich bis jetzt noch nicht gemeldet. Es kann ja auch bis6zu 5 Tage dauern. Gestern früh wollte ich wieder mein Couchplan absolvieren und da lief wieder alles so wie es vor dem Problem war. Heute lief auch wieder alles so wie geplant. Allerdings zählt der Couch auf der Uhr immer noch die Woche falsch. Aber auch in Connect wird auch wieder alles richtig angezeigt und auch nur einmal. Bis jetzt.... Ich vermute das es mit Connect zusammen hängt. Gestern gab es auch wieder ein Update. Das zählen der Wochen in Couch natürlich nicht, dass wird mit der Uhr zusammen hängen. Ich möchte mich erstmal an dieser Stelle für eure Hilfe und Feedback bedanken. Ich werde mich nochmals melden, wenn sich Garmin irgendwie äußert.. VG Burghardhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2038174Mon, 15 Jun 2026 05:50:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:6b41080e-5d0a-4be8-9b28-88d068121758bluefish[quote userid="718886" url="~/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2038172"]Den Support habe ich gestern geschrieben, habe da aber wenig Hoffnung.[/quote] Guten Morgen ! Danke für Deine Updates. Hoffentlich meldet sich der Support und eröffnet ein Ticket. VGhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2038172Mon, 15 Jun 2026 05:23:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:c3323927-2277-4efc-ac5b-286d29670bd3Burghard Guten Morgen Update... erwartungsgemäß ist der Fehler nicht beseitigt. App zeigt heute Woche 2 an und auf der Uhr wird im Garmin Couch und beim Laufen jeweils Woche 0 angezeigt. Ich habe gestern die Uhr zurück gesetzt auf Werkseinstellung und dann das Backup wieder rauf gespielt. Mit einrichten usw. einen halben Tag verschlissen für nichts. Anfangs stimmenten die Couchpläne, Abends wieder nicht. In der Connect App stehen neuerdings auch beide Trainings drin, also das was ich machen soll und das was ich schon gemacht habe, also das gleiche Training 2x. Wenn ich den Couch anhalte, die Uhr synchronisiere und dann den Couchplan wieder fortsetze erkennt die Uhr und auch der Couch nicht mal das ich das Training schon absolviert habe. Also ist ein Training nach Garmin Couch praktisch nicht möglich. Ich bin 65 und wollte eine Fitness Verbesserung, die bis letzte Woche auch super funktioniert hat. So ist die Uhr für mich wertlos. Den Support habe ich gestern geschrieben, habe da aber wenig Hoffnung. VG Burghardhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2038030Sun, 14 Jun 2026 04:27:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:6abe12f0-5df0-4510-8c00-cc280d22554fBurghard Guten Morgen, vielen Dank für die schnelle Antwort. Ich habe gerade geschaut und meine Uhr hat jetzt das Update 28.05. Aber... Ich habe gestern festgestellt das der Couch in der App und der Couch auf der Uhr verschiedene Wochennummern anzeigt. Daraufhin habe ich den Couch in der App neu eingerichtet und Uhr und App zeigten das Gleiche, Woche 1. Heute Morgen zeigte die App immer noch Woche 1 an, die Uhr aber Woche 0. Auch synchronisieren brachte kein Erfolg. Dann habe ich den Couch angehalten, die Uhr synchronisiert, den Couch in der App wieder fortgesetzt und die Uhr synchronisiert. Es zeigten beide wieder Woche 1 an. Nun habe ich die Uhr entfernt, Bluetooth auf den Smartfon und App. Jetzt zeigt der Garmin Couch genau das an von heute Morgen, Woche 0 und ein ganz anderes Training. Mich wundert das die Uhr trotzdem einen Couch anzeigt, den ich auch nicht bearbeiten/löschen kann. Wo kommt dieser Couchplan her, die Uhr ist nicht mit der App verbunden? Ich vermute das der irgendwie auf der Uhr nicht mehr gelöscht werden kann. Es gibt auch bei der Aktivität Laufen keine "Tägliche Trainingsvorschläge" mehr. Das war jetzt nur erstmal zur Info. Der Fehler ist also in meinem Fall nicht behoben. VG Burghardhttps://forums.garmin.com/de/sports-fitness/laufen-multisport/f/forerunner-965/437988/garmin-couch-zwischen-forerunner-965-und-connect-stimmen-nicht-uberein/2037966Sat, 13 Jun 2026 11:55:00 GMTa9571b57-dd57-479e-8763-8f8a603e40aa:d3bde597-adbf-4c6c-86a0-f2398d7e81c0bluefishTeste das mal aus, und gib mal ein Update hier, ob es mit 28.05 funktioniert.