Time Change not reflected in card.time request

Notecard API
1

I’m issuing a card.time request and am getting the response:

{‘minutes’: -300, ‘lon’: -90.xxxx, ‘area’: ‘New Orleans Louisiana’, ‘zone’: ‘CDT,America/Chicago’, ‘lat’: 29.xxxx, ‘country’: ‘US’, ‘time’: 1762101832, ‘crc’: ‘000F:8CC5C874’}

I should be getting (I believe):

{‘minutes’: -360, ‘lon’: -90.xxxx, ‘area’: ‘New Orleans Louisiana’, ‘zone’: ‘CST,America/Chicago’, ‘lat’: 29.xxxx, ‘country’: ‘US’, ‘time’: 1762101832, ‘crc’: ?}

Today is the time change day to CST. Can someone give me some insight on when the time change would be reflected in the card.time request? I’m hoping I don’t have to disconnect from the cell tower and reconnect.

Thanks,

Joe

2

Unfortunately, the time zone is only updated at the beginning of a connection. So you would need to disconnect and reconnect. While it’s not currently on our roadmap, it is something we might be able to address in a future firmware update. We’ll keep it in mind.

2 Likes
3

Thanks. I’ve already implemented a workaround, I’m using the current zone (For example, CST or CDT, i.e., Central rime) and UTC, and calculating the current local time.

Let’s say I’m driving and the notecard switches towers, would that zone information be updated?

Thanks,

Joe

4

Hi @scavoj,

You’ll only see updated timezone data when your Notecard initiates a new session with Notehub. Just to be clear, new sessions are created when Notecard boots up or periodically connects. They can also be programmatically reset with the hub.set duration argument if your Notecard is in continuous mode.

Thanks,
Rob