Closed fschwarz86 closed 5 months ago
I doubt you posted a valid card's picture since it shows "extrema" data - which is not supposed to be displayed by default (https://github.com/kalkih/mini-graph-card#available-show-options).
Do not use default values for important options.
Set:
ponts_per_hour
same as a real update freq (or x2 bigger - just in case)
smoothing: false
aggregate_func: last
type: custom:mini-graph-card
entities:
- entity: sensor.speedtest_ping
show:
extrema: true
points_per_hour: 2
smoothing: false
aggregate_func: last
However the result is still the same:
You have not set hours_to_show
(which is obviously!!!!) and have not provided info about a real update freq.
How can you compare graphs based on different input data?
To be 100% sure - post a history-graph, not graphs from more-info (which may have a statistics instead of real graphs).
From reading the documentation, I was under the assumption that hours_to_show defaults to 24 if not set, but I've included it in the code. Output remains unchanged. Real update frequency is 1 per hour. Therefore, as per your recommendation, I've set points__per_hour to 2.
type: custom:mini-graph-card
entities:
- entity: sensor.speedtest_ping
show:
extrema: true
points_per_hour: 2
smoothing: false
aggregate_func: last
hours_to_show: 24
Here's the output from history graph:
Your History view shows that is about 17:30 and your mini-graph says that extrema is 9:50PM - why? Are these graphs made at the same time ore be you posted a mini-graph from another day?
Exactly this is my question! These screenshots are taken within 1 minute.
Hmmm, try clearing a browser cache...
Tried that, doesn't help...
What HA do you use? I am using 2023.3.0, just updated to 3.1
Also, have you rebooted HA and did it solve the issue? People experience a similar flatline issue - https://github.com/kalkih/mini-graph-card/issues/933 - which is gone after HA reboot.
experiencing the same issue with other entities, e.g. temperature, download/upload speed, and is not limited to maxima, but also minima, avg., and datapoints as well.
For instance, with temperature: temperature here reports a max of 99 Celsius (obviously incorrect). On hovering over one of the datapoints, the reported values are also incorrect. This can be seen by comparing it to the native history-graph in homeassistant, which shows the highest temp is only 8.9 Celsius: Card configuration:
type: custom:mini-graph-card
entities:
- sensor.vancouver_temperature
show:
extrema: true
minima: true
Currently using Home Assistant 2023.3.3 w/ the latest frontend (Frontend 20230309.0 - latest) in a docker container. Using v0.11.0 of the Lovelace Mini Graph Card.
@markgllin
Suggest you to EDIT your post to avoid scattering info in several posts. Also, at least read previous comments, like this - https://github.com/kalkih/mini-graph-card/issues/936#issuecomment-1458021640.
Hello, it looks like I have the same issue :
the code is so simple, I don't understand what's wrong ?!
type: custom:mini-graph-card entities:
- sensor.co2
@NiamoR42 read one post above
@NiamoR42 read one post above
Hello & thanks for your feedback : that looks better today, don't know why... I did not change anything...
@NiamoR42
Your code which you posted could be WRONG. It has default values which probably make your graph absolutely different from a real picture. Even looking at the History from more-info popup (which is also WRONG since this is not a real data but an approximate statistics) I see a difference between your mini-graph
& History.
I recommended what you should do. Not it looks that I am begging you to improve your setup.
Is this issue still observed?
No feedback within 3.5 months, closing
Hi there,
unfortunately, the maxima feature doesn't seem to display the right value. I have stripped down the code to the very minimum:
As you can see from the screenshot, the maxima is already showing the wrong value (Max is 5ms, while current value is already 12ms):
I'm using mini-graph-card v0.11.0 and HA 2023.3.1
Any idea what I'm doing wrong?
Thanks, Florian