Note:
Looking at the original offset of time more, it appears my fix below is for a different issue. The 4 our offset is too great to be caused by a DayLight Savings change. The Database would be recording UTC, not the time-zone time for the USER.
---------
so lets strike the following that had only to do with My Odoo User Time not being reflected properly.. It did take some effort to get it "working" after the error was discovered.
Leaving it there.
----
I had this issue running just now for at least 2 days but likely since the last "Spring Forward" timechange.
Odoo should be self adjusting for this, but it did not in this situation.
My "fix" was in moving my User Timezone from America/Denver to America/Los_Angeles temporarily. The Odoo sensed problem went away in my Odoo Header Line, and my Time Clock entries started going in on the time they should have been going in in Denver. That was a "working tweak"...
My Debian Server did know the correct time so that was not the issue.
I did then, reset my User Timezone back to "America/Denver", and initially the error returned in the Odoo Header but I did a few Page Reloads and the Error was finally gone.
I could not get this to kick without toggling from Denver to Los Angeles, and then back to Denver. No understanding of why but there seems to be a difficulty with Odoo handling systematic Time Changes such as DayLight Savings Time is my only guess. Posting this here expecting someone else may end up looking for how to resolve a similar issue on their system.