docker icon indicating copy to clipboard operation
docker copied to clipboard

Weight log entries all end up saved as "2:00am" no matter which time is entered in the UI.

Open Bracket-I-I opened this issue 2 months ago • 4 comments

Referenced in #141

It seems to happen when the current time the program suggests, while making a new weight entry, is used. Manually changing the time of day sets it correctly.

Hmm.

Bracket-I-I avatar Oct 22 '25 09:10 Bracket-I-I

I noticed that when I click the calendar (just like right now) if the real time is not mappable to the calendar time selection, which is in like steps of 5s for minutes, then I can't click ok until I choose one of 'neat steps'.

Could that be what is happening when one just accepts the time the app suggests when adding a new weight entry via the gui? like let's say it's 9:16 in the morning, and that is displayed in the UI when one hits the (+) button on the weight entries. But if one opened the calendar view to pick a time at that point, the OK gets greyed out cause it's not 9:15, the nearest 'neat step'.

So perhaps in the guts of the app, the suggested time gets rejected when one clicks okay without picking a time, because underneath it expects a 'neat step'?

Bracket-I-I avatar Oct 24 '25 08:10 Bracket-I-I

No, that's probably just the picker (you can also edit the number with the keyboard, even if it's a bit awkward). However, this seems to be working fine here?

Image

rolandgeider avatar Oct 24 '25 23:10 rolandgeider

Strange, does not work for me, not on the dashboard, not on the detail view your screenshot is from. I have to edit the time in some way, I cannot just accept the current date and time of day the program autofills the dialog with.

If I accept it as is, it sets it to 2:00 am. (Its noon right now).

That said, I still cannot get the bodyweight change thing to work. Despite clearing cookies, cache, both through the developer tools and about:preferences (firefore) and co. and being on

2.4.0a2+gitfb43745
Date 2025-10-24

So maybe I bricked something in my newbness.

That said... the test routine I created on the 21st, logged data for on the 22nd with 'require logs to advance' finally advanced today 25th...

Hmm.

Edit: I'm on the default admin account btw. That once made difference for the 'ampache' streaming suite software I tried some time ago.

Edit2: Creating and changing to a test user did not do anything.

Just did another pull, am now on

2.4.0a2+gita63f25c
Date 2025-10-24

No change on firefox.

Tested it on chromium, also not working. (Did a delete site data and all that there too) So maybe I messed up the installation?

Bracket-I-I avatar Oct 25 '25 10:10 Bracket-I-I

My current workaround, even after a complete nuking of everything including (a backed up) database is to just use the keyboard to move to the time of day field and hit the up arrow once, then the down arrow once to 'wiggle' the time a bit, and then accepting.

This way the suggested time by the UI gets accepted in the actual log. Cause otherwise, it's still not working.

1.) Dashboard 2.) click + on weight entry 3.) enter weight in field 4.) do not edit the date and time the program autofills in 5.)click okay 6.) get wrong date (2am for me, Berlin timezone, aka +2 apparently)

Step 4.) has to be replaced by editing the time the program suggests in any way to actually make the underlying database use the time displayed to the user in the time/date field. Without editing it, only the date is correct, not the time, the time will be 0am, Null Uhr, mitternacht. +2 for the timezone (Berlin) for me.

Bracket-I-I avatar Oct 29 '25 16:10 Bracket-I-I