frigate: [Support]: Recordings timeline with wrong event times
Describe the problem you are having
For some reason, on the recordings view, the time on the current date always start at the top as 23:00. The event thumbnails show on the timeline on the right times, but the event recordings show on the wrong times starting from the top.
Example:
Current time: 17:00 There is an event at 16:49 The thumbnail shows on the timeline between 16:00 and 17:00
HOWEVER, if I click 16:00 it shows me the recording from 08:00. The actual recording for 16:00 is on 23:00. Clicking on 23:00 -> shows 16:00 Clicking on 22:00 -> shows 15:00 Clicking on 21:00 -> shows 14:00 Clicking on 20:00 -> shows 13:00 So on…
Again, current time is 17:00, so 20, 21, 22, 23 didn’t even have happened yet.
Version
0.11.0
Frigate config file
N/A
Relevant log output
N/A
FFprobe output from your camera
N/A
Frigate stats
{
"backyard":{
"camera_fps":5.1,
"capture_pid":238,
"detection_fps":5.2,
"pid":224,
"process_fps":5.1,
"skipped_fps":0
},
"detection_fps":10.6,
"detectors":{
"coral_pci":{
"detection_start":0,
"inference_speed":6.83,
"pid":215
}
},
"front_door":{
"camera_fps":5.1,
"capture_pid":236,
"detection_fps":5.4,
"pid":222,
"process_fps":5.1,
"skipped_fps":0
},
"service":{
"latest_version":"0.11.0",
"storage":{
"/dev/shm":{
"free":247.6,
"mount_type":"tmpfs",
"total":268.4,
"used":20.9
},
"/media/frigate/clips":{
"free":465493.2,
"mount_type":"zfs",
"total":536870.9,
"used":71377.7
},
"/media/frigate/recordings":{
"free":465493.2,
"mount_type":"zfs",
"total":536870.9,
"used":71377.7
},
"/tmp/cache":{
"free":991.6,
"mount_type":"tmpfs",
"total":1000,
"used":8.4
}
},
"temperatures":{
"apex_0":60.05
},
"uptime":677656,
"version":"0.11.0-3846a13"
}
}
Operating system
Proxmox
Install method
Docker Compose
Coral version
PCIe
Network connection
Wired
Camera make and model
N/A
Any other information that may be helpful
No response
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (1 by maintainers)
I plan to have the client pass the timezone to the api so the backend can calculate the recordings response based on that in the future. That will make the timezone on the server irrelevant.