Daylight Savings Time in Belchertown Skin

[ian...@kinnon.org]

I am in the UK and we went from GMT+1 to GMT a few weeks ago and I now see a discrepancy between the time for last updated between the default Seasons skin and Belchertown

Belchertown is an hour fast.

Any ideas where to look?

Thanks

Ian

[Tom Keffer]

You're not giving us a lot to go on! Which one was correct? 

And, how about a log?

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/weewx-user/caa0c246-a9c1-41d0-af21-190b8d2afac6n%40googlegroups.com.

[Mark Fraser]

On 03/11/2024 00:01, Tom Keffer wrote:

You're not giving us a lot to go on! Which one was correct? 

And, how about a log?

On Sat, Nov 2, 2024 at 8:57 AM ian...@kinnon.org <ian...@kinnon.org> wrote:

I am in the UK and we went from GMT+1 to GMT a few weeks ago and I now see a discrepancy between the time for last updated between the default Seasons skin and Belchertown

Belchertown is an hour fast.

Any ideas where to look?

Thanks

Ian

I'm seeing this too on a device that's running in kiosk mode.

It should be showing

"Connected to weather station live. Data received 3 November 2024, 08:10:03",

but instead it shows

"Connected to weather station live. Data received 3 November 2024, 09:10:03".

I know that if I restart the browser that is running in kiosk mode it will work, but that means logging in killing Chrome and then restarting.

[Karen K]

The timestamps in the Seasons skin are created by WeeWX. The live timestamps in the Belchertown skin are created by JavaScript in the Browser. 

Did you try different browsers? Ist it the same with all of them?

[Mark Fraser]

It is running in Kiosk mode, if I stop and restart it I will get the correct update time. The only access I have to it is through SSH.

[Karen K]

Mark Fraser schrieb am Sonntag, 3. November 2024 um 10:20:12 UTC+1:

It is running in Kiosk mode, if I stop and restart it I will get the correct update time. The only access I have to it is through SSH.

I was aware of what you wrote. Nevertheless, I guess, this situation does not prevent you from trying another web browser.

 

[ian...@kinnon.org]

For me, I have tried my desktop running chrome, my android mobile using chrome, my iphone using safari and my desktop running edge.

All give the same +1 hour error in the Belchertown skin

[gary....@gmail.com]

Just a data point.

I have no time display issue with WeeWX 5.1 and Belchertown.

That is with Firefox desktop, Chrome on Chromebook, and an Android tablet using Fully Kiosk Browser.

Have you double checked the locale, date, good system time on the weewx machine and on the client?

For me, this would work to ensure the system has the correct time zone.

timedatectl set-timezone America/New_York

[vince]

Wild guess - is everybody with the problem outside of the US ?   Wondering if there's a timezone error under the hood in Belchertown or the Highcharts things therein.  Also what's the time look like on your MQTT server if it's on a different computer than the weewx system ?

[ian...@kinnon.org]

Not sure if Pat from Belchertown is here, will raise it via his web page

[ian...@kinnon.org]

:-)

Seasons is correct (showing GMT)

Belchertown is +1 hour

Log attached