Hub Mesh Event Timestamp in 2041

[ritchierich]

@gopher.ny I noticed an event created by hub mesh has a year date of 2041! It is for my bed presence sensor so maybe I got into the DeLorean in my sleep and it logged it that way .

Original hub:

Meshed hub:

[tony.fleisher]

Is the clock right on settings -> hub details page (current hub time)?

[gopher.ny]

Which hub is this? First or last 2 characters of hub id is good enough or you can PM me.

[672southmain]

@ritchierich

has a year date of 2041!

Are people still wearing masks?

[JasonJoel]

Tracheal installed air purifiers. Now stop derailing threads.

[LosinIt]

@672southmain

Are people still wearing masks?

Good one!

[ritchierich]

@tony.fleisher

Is the clock right on settings -> hub details page (current hub time)?

Yep all good there.

@gopher.ny

Which hub is this? First or last 2 characters of hub id is good enough or you can PM me.

Hub with 2041 date:
First 3 Hub ID is 384
Device ID is 22

Thanks!

[ritchierich]

@gopher.ny @bobbyD this 2041 date issue is causing issues with my automated backup download as there is a backup dated 2041 thus that is always the "latest". If I click download new it gets this one too, how can I get this backup deleted? I cannot wait 21 years for this to fix itself Hub details are just above.

[bobbles]

Is the backup at the bottom of the list?
If it is, do a local backup, refresh the backups page and has it replaced it?
Something to try.

[ritchierich]

@bobbles

If it is, do a local backup, refresh the backups page and has it replaced it?

Thanks for the idea, I had tried that already. Because of the crazy future date, its stuck there and always considered the "latest" which is what that download local uses. I can download a specific backup though but as mentioned its borking my automated download.