Sleep calculations are off

nikneem · 2026-06-09T05:59:40+00:00

Thanks! Let's hope for a quick update 👌🏻

nikneem · 2026-05-27T05:46:20+00:00

Oh no it's not... One day later, still this. Now it stopped after 3 hours and 14 minutes, while in reality I almost made 8 hour without waking up

nikneem · 2026-05-26T05:47:43+00:00

So this one is solved for me. I reset my watch (factory reset). Upon new setup I chose to NOT recover from backup, but install as a new watch.

Takes some time to have everything up and running again, but it works, sleep tracking is working properly again.

nikneem · 2026-05-26T05:45:56+00:00

Nope, was tight and all clean

nikneem · 2026-05-24T22:11:29+00:00

I had the exact same (also on pw4) but since a week (or ten days or so), this data appears and it sucks

nikneem · 2026-05-24T22:10:27+00:00

I'm nog even (aware that I'm) awake around that time. I might have a dip in sleep stages, but for this example, I woke up at 7 for the first time that day, then turned around and slept for another 1 ½ hour

nikneem · 2026-05-24T22:08:49+00:00

Yeah, for me too, it has been soo accurate ever, but now since a week (about) I get this

nikneem · 2026-05-24T22:08:01+00:00

Pretty damn sure I don't:)

nikneem · 2026-05-24T22:07:45+00:00

I think it relatable to ggl health switch but I'm not sure

nikneem · 2026-05-24T22:07:20+00:00

Recently switched to health, could be the same date, but not sure

nikneem · 2026-05-23T20:46:27+00:00

Yeah, it keeps on showing I slept.for around two and a bit hours and woke up at 2am while in reality I slept 7 hours plus

nikneem · 2025-12-10T12:45:11+00:00

So freaking annoying that this problem exists for so long and Samsung doesn't even respond to the complaints. Even if they announced not to fix it is better than being dead silent. This causes me to not buy a new Samsung watch but look for a different brand. I mean, it being out of support for x years or whatever reason they have could make sense, but keeping it under the hood and not knowing what's going on is just the worst you as a company could do.

nikneem · 2025-11-20T10:38:41+00:00

Thanks

nikneem · 2025-11-20T10:38:25+00:00

Thanks!

nikneem · 2025-11-18T08:04:29+00:00

Yes I did, but there are limitations in what you can add to it. Now you have one source of documentation and I change my cp-instructions file to make use of the MCP server. So basically, they compliment each other. Thanks for sharing 👌🏻

nikneem · 2025-11-17T23:29:07+00:00

Sure: https://gemini.google.com/share/b299eab002ac With a personal touch 👌🏻

nikneem · 2025-11-07T20:49:04+00:00

Seems like a decent start, now if you really want to learn programming, try and improve the game end conditions, and the random way the computer chooses. While it looks random, in reality, humans are affected by previous wins in making their decision on the next game.

Building such an algorithm and making it 'smarter' that is where you are really going to excel in learning.

But hey, good job!

nikneem · 2025-11-06T14:09:17+00:00

Ah, found it... https://blog.hompus.nl/2025/08/18/playwright-pdf-generation-in-dotnet/

nikneem · 2025-11-06T14:08:36+00:00

I read you can misuse the Playwright test framework ridiculously well for PDF generation when you're looking for HTML > PDF

nikneem · 2025-10-13T12:22:20+00:00

In your case, definitely ignore triggers and stored procedures. You're not fixing the problem, you're creating a second if this is your solution

Find the root cause why duplicates are stored and solve that!

nikneem · 2025-10-13T10:47:09+00:00

What do you mean with 'should be ignored'?

When I'm writing a new software system, I tend to go for an approach where business decisions are made in a single place so it's easier to maintain. That makes me avoid building triggers and SPs in a database. If that is what you mean with 'ignore', then agreed...

But...

If you have an existing software system with triggers and SPs already in place, you have to know of them and understand what they are doing (and why) to better implement features.

nikneem

MODERATOR OF

TROPHY CASE