Clock on the screen not updating

[bph...@gmail.com]

I'm running the latest Concerto 2 Debian VM updated to v. 2.3.4 using VirtualBox on a Windows 10 desktop, and my screen displays using a Raspberry Pi 3.  I've set the proper time on the screen that runs Raspbian to Central time, but the sign time display is UTC.  I went into the server to make sure it was set to Central time as well, but the screen time doesn't update to Central time.  Not sure what I'm missing here.  Can anyone help?  I've never encountered this problem before.

Brian

[Marvin Frederickson]

Is the timezone set on your Pi?  I'm not sure if that matters.

[Brian Hibdon]

Yes.  The timezone on the pi is set to central time, but it seems to have no effect on the screen time.

On Tue, Jun 27, 2017 at 11:13 AM, Marvin Frederickson <marvin.fr...@gmail.com> wrote:

Is the timezone set on your Pi?  I'm not sure if that matters.

--

Brian

Brian Hibdon

[Marvin Frederickson]

Brian, just to clarify-- is the time not updating, or is it updating but showing UTC instead of local?

[Brian Hibdon]

It seems to be showing UTC instead of local.

--

Brian

Brian Hibdon

[Marvin Frederickson]

It seems to be using momentjs to format the time, using the timezone if it is specified for the screen.

https://github.com/concerto/concerto-frontend/blob/master/contents/concerto-client-time.html#L48

Perhaps you could debug the frontend display via the developer console and put a breakpoint around here and inspect the values to help see what is going on?

[bph...@gmail.com]

I'm circling back to this time display problem.  I'm not sure about how to "debug the front end display via the developers console", but I could give it a shot with some direction.  No matter what display I use, the display is always 5 hours ahead of my actual central time.  Any thoughts?

Brian