Premiered date is showing up wrong

[heula 189]

For Windows I had this script running as a workaround for this issue and that worked because all premiered dates where correct again.

tzutil /s "Eastern Standard Time"

TASKKILL /F /PID EmbyServer.exe
TASKKILL /F /PID EmbyTray.exe

timeout 5

start C:\Users\username\AppData\Roaming\Emby-Server\System\EmbyServer.exe

timeout 20

tzutil /s "W. Europe Standard Time"

The same procedure works on my Synology NAS but I don't now how to get it working as the script does on Windows.

If anyone can help me out with a new script that I can use as a workaround for the Synology NAS, would be appreciated.

 

Thanks.

[chowbok 77]

I just noticed this and it was annoying me, so I tried to find a workaround. First, I changed the time zone on the (Linux) Emby server from CST6CDT to UTC and rebooted. This didn't fix it, so I tried launching Chromium (also on a Linux box) with my TZ set to UTC. This made it so when I went to a season page, no episodes were displayed(!). So maybe I've uncovered another bug?

 

Anyhow... has anyone figured a workaround to this on Linux (other than just entering the wrong dates on episodes to compensate)?

Edited November 7, 2018 by chowbok

[Happy2Play 8270]

The issue appears to be the datetime is written to the database in UTC  but written to the nfo in utc +/- timezone.  (At least from a edit point of view)

 

Example Edit metadata changing dateadded a few minutes ago.  I did this before 12:00am to this clearly isn't using a actual time.  From beta database.

 

 

 

Edited November 7, 2018 by Happy2Play

[Luke 37046]

Thanks happy2play, there is an issue in the metadata editor that I will look at.

[Happy2Play 8270]

The issue appears to be the datetime is written to the database in UTC  but written to the nfo in utc +/- timezone.  (At least from a edit point of view)

 

Example Edit metadata changing dateadded a few minutes ago.  I did this before 12:00am to this clearly isn't using a actual time.  From beta database.

 

 

 

 

This appears fixed in beta 3.6.x.x, not a issue to me but timestamp is set to 00:00:00 instead of actual time on manual edit in UI.

 

<dateadded>2018-11-30 00:00:00</dateadded>

 

[heula 189]

This is still an issue for me with emby server for synology 3.06.0.79.

Edited December 23, 2018 by heula

[Luke 37046]

This is still an issue for me with emby server for synology 3.06.0.79.

 

Why do you feel you're still having an issue? Can you please describe the problem in more detail? Thanks.

[Happy2Play 8270]

This is still an issue for me with emby server for synology 3.06.0.79.

 

For new items or existing items?

[heula 189]

I should be more clear.

I still have this issue in Kodi.

I have checked it in the Emby metadata manager and there it seems correct now. But when I open Kodi with the Emby addon activated and used to set up my Kodi library, I still see that the premiered date is one day earlier than it should be. 

How is that still possible when using Emby in Kodi?

 

This is for old and new episodes

 

 

 

 

 

Thanks.

kodi.log

Log.txt

Edited December 23, 2018 by heula

[heula 189]

Today I have reset my Kodi library once more to see what happens now with the premiered date in Kodi.

Unfortunatly it is still the same so I don't know why this is?

All good in the Emby metadata manager.

 

 

 

This shows Kodi after setting up a new library with the Emby addon for Kodi.

 

 

Kodi log

 

Thanks.

[Happy2Play 8270]

@@heula

Have you verified the datetime written to the database? 

 

@@Angelblue05

If the web client is showing correct, would it not be a Kodi datetime offset issue?

[heula 189]

I checked the Kodi myvideos.db and the date in there is wrong. No idea what is causing this.

I do remember that I did setup the Kodi library once without the Emby addon some time ago to see what happened to the premiered date and back than the premiered date was good.

 

So that makes me think it still is Emby related somewhere.

 

 

 

Thanks

Edited December 27, 2018 by heula

[Happy2Play 8270]

I know the Reports plugin does this improper datetime offset also.  So the plugins/addons themselves need looked at as the server (3.6) should be/is now reporting correct UTC.

Edited December 27, 2018 by Happy2Play

[Happy2Play 8270]

I checked the Kodi myvideos.db and the date in there is wrong. No idea what is causing this.

I do remember that I did setup the Kodi library once without the Emby addon some time ago to see what happened to the premiered date and back than the premiered date was good.

 

So that makes me think it still is Emby related somewhere.

 

 

 

Thanks

 

Looking at this shows that Kodi is pulling correct time from Emby database UTC (as I would expect Emby database to show "1545606000") since you are UTC/GMT +1.  But when Kodi displays it, it is not converted back to Local time (UTC/GMT +1).

[Happy2Play 8270]

@@Angelblue05, @@im85288, @, @@sualfred, @@xnappo

 

Not sure who to tag but how does Kodi addon present the above datetime that appear in database? It would appear the addon is displaying this datetime unchanged from its database entry.

[Luke 37046]

Can you install the EmbyCon add-on and compare with that? Thanks.

[heula 189]

With EmbyCon the same issue. Still one day off.

 

[Angelblue05 4130]

@@heula

 

Is the UTC time correct, it's just not converted to local time in Emby for Kodi? 

 

Edit: I went back a few posts and saw the webclient has the right time. Will correct this for the next version.

Edited December 30, 2018 by Angelblue05

[Angelblue05 4130]

@@heula

 

Try beta 3.1.39a

You'll have to update or repair your libraries. I do hope I got it right and the datetime will now be reflected correctly, please keep me posted.

Edited January 11, 2019 by Angelblue05

[heula 189]

@@heula

 

Try beta 3.1.39a

You'll have to update or repair your libraries. I do hope I got it right and the datetime will now be reflected correctly, please keep me posted.

It’s all good now!

 

Thank you all.

[schumi2004 9]

Wow, 3 years and 3 months that must be a record

[Angelblue05 4130]

Glad it is finally resolved.