Skip to content

Year Change Date Problem #36

Closed
Closed
@scootergarrett

Description

@scootergarrett

This new year, I think there was an issue with the logged year not updating correctly. At midnight on Dec 29 (not even the last day of the year), it updated from Dec 29 to Dec 30 (like it should) but also increased the year from 2024 to 2025. It basically jumped to one year in the future. At the beginning of the next log file the year was corrected.
Here is a little data log snip:

General.Time,RV8803 [x32].Get Epoch,MAX17048 [x36].State Of Charge ,BME68x [x76].Humidity,BME68x [x76].TemperatureC,BME68x [x76].Pressure,BME68x [x76].Gas Resistance,BME68x [x76].Sensor Status 
...
2024-12-29T23:59:28-05:00,1735534768,118.383,35.213,20.586,97920.055,319202.000,176 
2024-12-29T23:59:43-05:00,1735534783,118.383,35.179,20.591,97919.656,319500.781,176 
2024-12-29T23:59:58-05:00,1735534798,118.383,35.113,20.593,97922.805,320400.500,176 
2025-12-30T00:00:13-05:00,1735534813,118.383,35.063,20.578,97922.469,320400.500,176 
2025-12-30T00:00:28-05:00,1735534828,118.383,34.961,20.581,97921.312,319800.125,176 
2025-12-30T00:00:43-05:00,1735534843,118.383,34.967,20.578,97920.922,320400.500,176 
...

Any ideas on what could cause this? I last updated the firmware on April 19, 2024.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions