[audio.bill]

Have a 2024 Touring Hybrid and the system clock was automatically was set back an hour today, I'm in CST zone (Chicago) where it doesn't change until next week. Tried various settings in the clock section but couldn't get it corrected. Any ideas on how to get it back to the correct time? TIA

 

[Bimmer74]

That's bizarre... It's an American thing that nd we don't roll the clocks back until next weekend.

 

[joebxr]

Owners Manual page 142

 

[mywrx320]

Owners Manual page 142

What’s an owners manual?

 

[joebxr]

What’s an owners manual?

EXACTLY!

 

[Bimmer74]

Just back from church... My clock is still correct.

 

[audio.bill]

Appreciate direction to the manual and I realize I can manually set the time. I have it set to automatically detect time zone and adjust for DST yet the clock is off by an hour as of today.

 

[mywrx320]

So reset the clock and leave it on manual for a week. Then go back to auto.

 

[MartyV6]

SO FUNNY

I was literally coming on here to post this

HO

Appreciate direction to the manual and I realize I can manually set the time. I have it set to automatically detect time zone and adjust for DST yet the clock is off by an hour as of today.

I posted another thread. For those of us on Central Time, apparently the system is keyed to "Bahia Banderas" in Mexico. But I am in Chicago. United States, not Mexico.

Funny

 

[JeffJo]

I posted another thread. For those of us on Central Time, apparently the system is keyed to "Bahia Banderas" in Mexico. But I am in Chicago. United States, not Mexico.

Okay, time (no pun intended) to go full-blown nerd. Skip this if you are not interested, but I will comment on the situation in your clocks at the end. In my defense, part of my professional career was related to tracking the difference between the sun's position, and the time you see on the clock on the wall. So this struck close to home. But there is so much that is potentially wrong in this story, that it boggles the mind. And I think demands some background.

First, such systems are not "keyed to" specific locals, they are governed by rules. But often a specific locale is mentioned to place those rules in a context. This locale seems to be Bahia de Banderas, a bay of the Pacific Ocean in central Mexico. It is most famous for resort towns, most notably Puerta Vallarta. It is also shared by two Mexican states, Jalisco and Nayarit. Jalisco, on the south of the bay, uses Central Time (UTC-6). Most of Nayarit, on the north, uses what the US calls Mountain time (UTC-7) but Mexico calls the Pacific Zone. The exception is the parts of Nayarit on the bay, probably so the entire resort area stays consistent. Here is a map:

Second, an observation about the politics of time zones. Theoretically, time zones are centered on longitude 15°*H, where H is the modifier from Universal Coordinated Time (UTC; blame the French for the acronym), and are 15° wide. This means that the Central Time Zone should extend from (east of) Columbus Ohio, -82.5° longitude, to (just west of) Wichita, Kansas, -97.5°. But the preferences of urban communities (where there are lots of people) as opposed to rural ones (where are not) tend to make these borders drift westward. So the actual Central Time Zone can start as far west as the Indiana/Illinois border (-87.5°) and almost extend to the western tip of Texas (-105°). The point of this westward drift is to create a "partial" Daylight Saving Time (not "savings", although most people say it that way) of 4 minutes for each degree of longitude.

That last longitude is important here. It is very far fomr the theoretical Central Time Zone; in fact, it is the theoretical center of the Mountain Time Zone (Pacific in Mexico). And the same longitude as Bahia de Banderas. That means that the position of the sun, in Bahia de Banderas, corresponds exactly to what Mountain Standard Time represents. So using a one-hour shift for DST represents a 90 minute shift relative to the sun.

That is a lot of shift from what people expect. This is why you will see the western portions of a political time zone decline to use DST at all; the confusion about time in Arizona and Indiana is an example.

+++++

And finally, to my point. Look at the legend for that map. You will see that Bahia de Bandares, like Arizona, does not use DST. Your 2024 HAH's clock can't legitimately use Bahia de Bandares as an example, or a key, because you use DST and they don't. The only thing Bahia de Bandares should be used for, is an example of Central Time Zone without DST. Yet they apparently adjusted for DST, on Mexico's Schedule. I can't say where this error occurred. All I can say, is use manual setting for this one week.

+++++

But I have to end with an anecdote. Several years ago, almost to the day, my wife and I took a trip from Maryland to Cancun, then to south Florida, and back. And crossed too many Time Zone, and DST borders, along the way.

1. For MD-Cancun (light tan region on my map) we were told that they used the same time zone. But not that they don't use DST, so we when we landed we were off by an hour.
2. We took a day trip to Chichen Itza (dark tan). We were told that they were in a different time zone, so we changed our watches. But they use DST, so the times were the same.
3. While in Cancun (actually, Isla Mujeres near Punta Sur, the Easternmost point in Mexico; don't ask), DST changed in Mexico but not the US. If I recall correctly, we had learned by this time and got that one right.
4. Upon leaving Cancun for Florida, DST turned back on. Eggbeater missed that one.
5. While in Florida, DST turned off.

The only saving grace was that (A) we were on vacation, so time didn't matter except for keeping schedules. And we were lucky to not miss any, although there were close calls. (B) It was an all-exclusive resort at 1/3 capacity in the off-season. Edwin, the waiter who "adopted" us, met us each day with the same drink we had ordered the previous day. If that wasn;t what we wanted, he replaced it. What was wrong, was that he didn't follow is to Florida.

 

[MartyV6]

JeffJo thanks but I still don't understand how any of that is relevant to the situation at hand. I think the relevant statement is where you said that someone at Honda messed up. The car should be able to know at least that it is in the United States and so keying one of its 4 time zone options off of Bahia Banderas Mexico is just wrong. I would think the auto time zone would run off the Telematics unit which would know the car location (recall that HondaLink offers a location finding service for the car).

 

[JeffJo]

JeffJo thanks but I still don't understand how any of that is relevant to the situation at hand. I think the relevant statement is where you said that someone at Honda messed up. The car should be able to know at least that it is in the United States and so keying one of its 4 time zone options off of Bahia Banderas Mexico is just wrong. I would think the auto time zone would run off the Telematics unit which would know the car location (recall that HondaLink offers a location finding service for the car).

My main point was that the car doesn't think you are in Bahia Banderas. It thinks you are in a time zone that works like Bahia Banderas. Why, I don't know, but it has to be based on the descriptions I gave.

That means (1) It thinks your time zone is nominally based on UTC-6 (true), (2) you do NOT use DST (false), and (3) If you were in a country that didn't use DST, that country would be Mexico, and you would stop using it on Oct. 28, 2023 (true but inapplicable statement - you don't live in Mexico).

Not using DST is the big mistake. The wrong changeover date probably follows from that, since about the only UTC

• It could be that your settings say the car thinks you don't use DST. If your settings are correct, that isn't true.
• It could be that whoever formed the list didn't understand #2 when they used Bahia Banderas as an example. That doesn't make sense, because the only reason to use it, as opposd to Chicago or St. Louis, is for that reason.
• It could be that this same person misinterpreted #2. Same reason to dismiss it.
• It could be that MartyV6's settings are different than yours; that he has DST turned off. Doesn't seem likely.

There a many other possibilities, but they get more and more speculative.

 

[MartyV6]

My main point was that the car doesn't think you are in Bahia Banderas. It thinks you are in a time zone that works like Bahia Banderas. Why, I don't know, but it has to be based on the descriptions I gave.

That means (1) It thinks your time zone is nominally based on UTC-6 (true), (2) you do NOT use DST (false), and (3) If you were in a country that didn't use DST, that country would be Mexico, and you would stop using it on Oct. 28, 2023 (true but inapplicable statement - you don't live in Mexico).

Not using DST is the big mistake. The wrong changeover date probably follows from that, since about the only UTC

• It could be that your settings say the car thinks you don't use DST. If your settings are correct, that isn't true.
• It could be that whoever formed the list didn't understand #2 when they used Bahia Banderas as an example. That doesn't make sense, because the only reason to use it, as opposd to Chicago or St. Louis, is for that reason.
• It could be that this same person misinterpreted #2. Same reason to dismiss it.
• It could be that MartyV6's settings are different than yours; that he has DST turned off. Doesn't seem likely.

There a many other possibilities, but they get more and more speculative.

I think it is just a software bug where someone tagged the wrong "Central Time" in some list of all the worldwide Central Time options.

 

[baldbear]

Have a 2024 Touring Hybrid and the system clock was automatically was set back an hour today, I'm in CST zone (Chicago) where it doesn't change until next week. Tried various settings in the clock section but couldn't get it corrected. Any ideas on how to get it back to the correct time? TIA

It's a programming mistake, and a pretty big one. It's using the 2005 Savings Time rules instead of the current ones (it used to change in Oct, now it's Nov).

Of course, they didn't test it, because the car isn't that old, now it is.

 

[MartyV6]

It's a programming mistake, and a pretty big one. It's using the 2005 Savings Time rules instead of the current ones (it used to change in Oct, now it's Nov).

Of course, they didn't test it, because the car isn't that old, now it is.

No, it's this issue with choosing the wrong time zone (a Mexican one)

As noted above

 

[baldbear]

No, it's this issue with choosing the wrong time zone (a Mexican one)

As noted above

That is so incredibly wrong. That is DEFINITELY a bug. When was the last time you had to put the wrong address down to get anything? You simply are mistaken. (I am a software engineer, that would get you a big bug report).

 

[MartyV6]

That is so incredibly wrong. That is DEFINITELY a bug. When was the last time you had to put the wrong address down to get anything? You simply are mistaken. (I am a software engineer, that would get you a big bug report).

Hi Mr Software Engineer!

I agree it's a bug. I just don't think it is your bug. What I'm saying is that the system is keying off a Mexican Central Time Zone, where they follow different DST rules vs the US Central Time Zone. So I am of the belief that it's not that the car is using Pre-2005 United States DST rules, as you suggest, but rather that someone in programming checked the wrong box in terms of which world time zone's rules to follow. That is the only explanation for why it says "Central Time (Bahia Banderas)" as we discussed at length above and in another thread.

So actually we both agree it is a Bug, but I believe it is you who is "simply mistaken" as to the root cause of the bug. But in any case it doesn't matter, it's wrong.....and they should fix it with a firmware update.....

And, I just sat in our Pilot too, and its time zone selection is "correct" in that all of them are normal Eastern Time, Central Time, Mountain Time etc. They also include Atlantic and a few other choices that I don't recall seeing in the Accord. But none of them have a weird parenthetical on one of the time zones keying it to a very specific time zone in Mexico.....

 

[joebxr]

What's curious to me is that the DST when set to AUTO, it reads info via GPS. So what is really causing this to happen? Is GPS faulty?

 

[baldbear]

What's curious to me is that the DST when set to AUTO, it reads info via GPS. So what is really causing this to happen? Is GPS faulty?

They are probably using a time library that is older than 2005. It could be GPS, it could also be cell tower information.

 

[baldbear]

Hi Mr Software Engineer!

I agree it's a bug. I just don't think it is your bug. What I'm saying is that the system is keying off a Mexican Central Time Zone, where they follow different DST rules vs the US Central Time Zone. So I am of the belief that it's not that the car is using Pre-2005 United States DST rules, as you suggest, but rather that someone in programming checked the wrong box in terms of which world time zone's rules to follow. That is the only explanation for why it says "Central Time (Bahia Banderas)" as we discussed at length above and in another thread.

So actually we both agree it is a Bug, but I believe it is you who is "simply mistaken" as to the root cause of the bug. But in any case it doesn't matter, it's wrong.....and they should fix it with a firmware update.....

And, I just sat in our Pilot too, and its time zone selection is "correct" in that all of them are normal Eastern Time, Central Time, Mountain Time etc. They also include Atlantic and a few other choices that I don't recall seeing in the Accord. But none of them have a weird parenthetical on one of the time zones keying it to a very specific time zone in Mexico.....

They are using the wrong library, I've seen it before.