-
Notifications
You must be signed in to change notification settings - Fork 79
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
Comments
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 Admin Version is 6.3.5 but I can observe this behavior for a couple of versions already. Also other datapoints are suffering from this issue. |
Seems like it's writing the first value into the table header somehow. |
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. |
* (foxriver76) fixed css classes of TableResize, see ioBroker/ioBroker.admin#1860
- by incorporating fix of adapter-react-v5 - ioBroker/adapter-react-v5@75be27f - closes #1860
will be fixed in the next version of admin |
- by incorporating fix of adapter-react-v5 - ioBroker/adapter-react-v5@75be27f - closes #1860
Describe the bug
![Screenshot 2023-01-01 at 16 07 44](https://user-images.githubusercontent.com/3496522/210175646-d0f0891a-97e7-4d8c-a9cc-592a7c212b03.png)
Sometimes if you want to view the recorded data in a data point, the table is shown messed up. (see Screenshot)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The table is intact showing the correct data
Screenshots & Logfiles
If applicable, add screenshots and logfiles to help explain your problem.
Versions:
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
The text was updated successfully, but these errors were encountered: