search

roflcoopter / viseron

Self-hosted, local only NVR and AI Computer Vision software. With features such as object detection, motion detection, face recognition and more, it gives you the power to keep an eye on your home, office or any other place you want to monitor.
MIT License
1.76k stars 179 forks source link

Suspected Timezone Issue... #781

Closed sgoldtho closed 1 week ago

sgoldtho commented 4 months ago

Recordings appear to have the correct time but are being save according to UTC rather than local timezone AEST.

For example a recording that happened today 12/07/2024 @ 9:29:09 is being displayed under 2024/07/11 in the web interface.

Using Viseron 3.0.0b8

roflcoopter commented 4 months ago

Yes that is a known issue! Will be fixed in the next beta

sgoldtho commented 4 months ago

Thanks

roflcoopter commented 2 weeks ago

Sorry for the delay on this one. This should be fixed in dev now.

Would you mind testing it? Unit tests are working fine but I am only one hour off UTC so it is hard for me to verify end to end

sgoldtho commented 2 weeks ago

First test was this morning just past midnight so might be a bit close to be useful..

Detected an event at 00:09:48 on the 02/11/2024 which showed in Viseron under 01/11/2024.

Noticed a couple of other things: 1) When selecting the ‘View Recordings’ icon on a day the error message ‘Error loading recordings Request failed with status code 500’ is returned. Not sure what that is about as the path exists but there are no files in the directory

2) When the GUI is in light mode it appears that the font is white with a white background, so when hovering over an icon the text box appears blank.

On 1 Nov 2024, at 9:21 am, Jesper @.***> wrote:

Sorry for the delay on this one. This should be fixed in dev now.

Would you mind testing it? Unit tests are working fine but I am only one hour off UTC so it is hard for me to verify end to end

— Reply to this email directly, view it on GitHub https://github.com/roflcoopter/viseron/issues/781#issuecomment-2450929608, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJPPFB6TBLFKK3TTSM2ERLZ6KUP5AVCNFSM6AAAAABKYBLMMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJQHEZDSNRQHA. You are receiving this because you authored the thread.

roflcoopter commented 2 weeks ago

Thanks for testing so quickly! Yes I found some more issues, can hopefully have them fixed later today.

Will take a look on the font color as well

roflcoopter commented 2 weeks ago

Now these issues should be solved, both the recordings and the tooltip font color.

Please run some tests when you get the chance. I would appreciate if you could have a look on the events/timeline page as well to see if you notice anything strange there regarding dates.

I have done by best to make sure all cases are covered but it gets very complex when you mix and match different timezones in the client vs the server!

sgoldtho commented 1 week ago

Test results:

Tooltip font colour: No issues detected (fixed). Recordings grouped into correct date: No issues detected (fixed). Recordings playback: No issues detected (fixed).

Nothing strange detected with dates using the Events/Timeline page.

Looks good...

On 5 Nov 2024, at 1:05 am, Jesper @.***> wrote:

Now these issues should be solved, both the recordings and the tooltip font color.

Please run some tests when you get the chance. I would appreciate if you could have a look on the events/timeline page as well to see if you notice anything strange there regarding dates.

I have done by best to make sure all cases are covered but it gets very complex when you mix and match different timezones in the client vs the server!

— Reply to this email directly, view it on GitHub https://github.com/roflcoopter/viseron/issues/781#issuecomment-2454805652, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALJPPFAKRNDLS5GA5IAA7YLZ655LTAVCNFSM6AAAAABKYBLMMGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUHAYDKNRVGI. You are receiving this because you authored the thread.

roflcoopter commented 1 week ago

Great to hear! Closing this issue then. Please open a new one if you experience any other issues