Core: History and logbook start with yesterday's data

[metbril]

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):

0.41.0

Python release (python3 --version):

3.4.2

Component/platform:

logbook, history

Description of problem:

History and logbook start with yesterday's data
Until recently this always was today.

Expected:

History and logbook start with today's data

Problem-relevant configuration.yaml entries and steps to reproduce:

1. 
   
   
   2.
   
3.

Traceback (if applicable):

Additional info:

https://community.home-assistant.io/t/history-since-0-39-also-in-0-40-0-41/13667/4

[jenkins101]

Same problem here. +1

[VDRainer]

Same in 0.42.2
History shows only yesterdays data. If you pick another date -> no update.

[jenkins101]

downgraded. The latest working release for me is 0.40.2 here everything seems ok. history and logbook dates and data is shown right.

[Hooch76]

The same ("start with yesterday's data") is happening here after having upgraded to 0.42.2.

[redstar2k1]

Same here. Changing the date or the period does not change the displayed data anymore.

[pbavinck]

+1 here. Running 0.42.2

[radinsky]

same on 0.42.4

[cyberjunky]

Same on 0.43

Op 17 apr. 2017 17:16 schreef "radinsky" [e-mail]:

same on 0.42.4

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/6902#issuecomment-294506863,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMd-Y1kXI_GeQDs3CrKpBCyL6fzi6ITks5rw4JfgaJpZM4Mw4n0
.

[SCUZNUTS]

Same on 0.42.3

[scrimpys]

+1 ... version 0.42.4

[localhoster]

The problem still persist:(

[Paul-Vdp]

Has been a daily frustration for me too, for quite some time now.

[jansink]

Same here on 0.42.4

[scrimpys]

Not sure if the 0.43 update did it or my changes but got my history working.

Anyone else able to see history before yesterdays history ?

If so then clearly a fix was made to 0.43. If not I will detail the changes I made.

[Hooch76]

@scrimpys Just upgraded to 0.43 and the issue is not solved!

[scrimpys]

OK - to be clear. I still see it starting the initial screen at previous day but I am able to select and display other dates now.

My thoughts on the issue was the initial upgrade to the database was corrupted. A couple of releases ago they modified the schema and added a couple of indexes to tables - recorder_runs and states. The upgrade script seems to be triggered on the version number in the schema table.
Firstly backed up my DB
Then I stopped HASS
Next I deleted the row that had version 2 in the schema_changes table
Dropped the index called ix_recorder_runs_start_end in recorder_runs table
and
the indexes ix_states_entity_id_created and ix_states_last_updated in the states table
restart HASS and just wait. It takes a little longer to come up because the status is doing the upgrade and index creation but not much longer - perhaps 1 mins or so longer.

Anyway - I have seen other people reporting that the history issue is fixed so I didn't think my changes made an impact.

Haven't check with anyone to see if what I did breaks something.

Oh - forgot to mention - am running MariaDB ( MySQL ) on a Synology box. Not sure how this applies to the standard sqllite DB.

[Paul-Vdp]

Version 0.43's Logbook still starts with yesterday's date. How hard can it be to fix that ... :-(

[Hooch76]

@scrimpys We're talking about different issues then. I am able to select older dates and get data.
It's just about that the logbook displays 'yesterday' initially by default. That can be changed to 'today' manually then.

[amelchio]

I think the problem is here:

https://github.com/home-assistant/home-assistant-polymer/blob/master/panels/logbook/ha-panel-logbook.html#L102

The method toISOString() converts to UTC so when the time is discarded we end up with "yesterday" if your local timezone is ahead of UTC.

I don't know how to work in home-assistant-polymer but it seems to have been introduced by @balloob in home-assistant/home-assistant-polymer#241 so maybe he can also fix it :)

[amelchio]

The original problem is fixed now so I will go ahead and close this issue.

If you still have problems selecting other dates, please open a separate issue with more complete information.

[Paul-Vdp]

No idea why this is closed, because the problem (of starting date) remains unsolved. No change for the better in 0.43, nor in 0.43.1 :-(
To which I might add that the decision to change the layout of the Logbook into one that strives to use as much as possible screen estate to present as little as possible information beats me ...

[cyberjunky]

I can confirm it's not fixed on 0.44.0.dev0 for me either, tested it just
now, and it still points to 25 april.

Also the logbook layout is messed up in chrome on windows 10, but I believe
there was another issue opened for that, will look for it.

On Wed, Apr 26, 2017 at 9:58 AM, Paul-Vdp [e-mail] wrote:

No idea why this is closed, because the problem (of starting date) remains
unsolved. No change for the better in 0.43, nor in 0.43.1 :-(
To which I might add that the decision to change the layout of the Logbook
into one that strives to use as much as possible screen estate to present
as little as possible information beats me ...

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/6902#issuecomment-297278416,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMd-alsf3TElWX8-wE5AMgZf0M5mCkyks5rzvkngaJpZM4Mw4n0
.

[amelchio]

It was closed because a fix has been merged to the frontend. This means that it will be in the next release. Maybe I was a bit premature as the updated frontend is not yet in 0.44.0.dev0 so you cannot really test it.

This issue bugs me as well and I will nominate the fix for 0.43.2 if one comes around.

Please keep observations unrelated to the original problem description in separate issues.

[balloob]

We can close the issue since the merge has been fixed. It will be in the next release.