Skip to content

Why is the alarm year & month hardcoded to Jan 2017? #53

Description

@maholli

When reading an alarm set point, the tm_year attribute is hardcoded to return 2017 and tm_mon to return 1. Is this intentional? Caused by a limitation somewhere?

time.struct_time((2017, 1, mday, hour, minute, seconds, wday, mday, -1)),

In contrast, reading the datetime properly returns the year reported from the RTC:

_bcd2bin(self.buffer[7] & self.mask_datetime[7]) + 2000,

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions