Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

History Data Point Viewer messes up shown data #1860

Closed
lxffm opened this issue Jan 1, 2023 · 6 comments · Fixed by #2057
Closed

History Data Point Viewer messes up shown data #1860

lxffm opened this issue Jan 1, 2023 · 6 comments · Fixed by #2057
Assignees
Labels

Comments

@lxffm
Copy link

lxffm commented Jan 1, 2023

Describe the bug
Sometimes if you want to view the recorded data in a data point, the table is shown messed up. (see Screenshot)
Screenshot 2023-01-01 at 16 07 44

To Reproduce
Steps to reproduce the behavior:

  1. Go to a datapoint which has recorded history data
  2. Find a time setting which is reproducing the error (not clear pattern found yet)

Expected behavior
The table is intact showing the correct data

Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.

Versions:

  • Adapter version: 2.2.4
  • JS-Controller version:
  • Node version:
  • Operating system: linux (RasPi)

Additional context
Maybe it's related to my data so I exported you the data. The time setting "last 12 months" lead to the issue, whereas "this year" which only contains one day, shows the table correct.

power consumption last day.csv

@Apollon77
Copy link
Collaborator

The data look good in general. Did you used the admin page to export the data? Which Admin version do you use? Please check if also other datapoints have this issue.In general this is an admin topic

@Apollon77 Apollon77 transferred this issue from ioBroker/ioBroker.history Jan 1, 2023
@Apollon77 Apollon77 added the bug label Jan 1, 2023
@lxffm
Copy link
Author

lxffm commented Jan 1, 2023

@Apollon77 Admin Version is 6.3.5 but I can observe this behavior for a couple of versions already.
I exported the data from the screen being shown.

Also other datapoints are suffering from this issue.
First I thought it might be related to the long floats in my energy consumption datapoints. But I also found the issue in some sensor data from homematic were it only stores a couple of minutes.

screens attached
Screenshot 2023-01-01 at 18 03 36
Screenshot 2023-01-01 at 18 05 32

@lxffm
Copy link
Author

lxffm commented Jan 1, 2023

Seems like it's writing the first value into the table header somehow.

@Marc-Berg
Copy link

Marc-Berg commented Apr 3, 2023

I know a very similar behavior, which occurs whenever you use more than one history instance. If you start with an instance in the view that contains no data and then switch to an instance with data, the columns are shifted.
https://forum.iobroker.net/topic/61006/darstellung-influxdb-in-admin/5?_=1680442904786

Animation

@ScumbagSteve
Copy link

I know a very similar behavior, which occurs whenever you use more than one history instance. If you start with an instance in the view that contains no data and then switch to an instance with data, the columns are shifted.

I can confirm this bug and also the reproduction steps, @Marc-Berg has mentioned.
Would be good to get a fix for it, the bug is around for quite a while already.

@foxriver76 foxriver76 self-assigned this Aug 20, 2023
foxriver76 added a commit to ioBroker/adapter-react-v5 that referenced this issue Aug 20, 2023
foxriver76 added a commit to ioBroker/adapter-react-v5 that referenced this issue Aug 20, 2023
* (foxriver76) fixed css classes of TableResize, see ioBroker/ioBroker.admin#1860
foxriver76 added a commit that referenced this issue Aug 20, 2023
@foxriver76
Copy link
Collaborator

will be fixed in the next version of admin

foxriver76 added a commit that referenced this issue Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants