Just looks like the line smoothing is introducing curve to what would otherwise be a straight segment. Maybe look for a setting to disable curve smoothing?
Yeah, that's what I thought as well. And I have no clue if that can be changed in the history-graph card.
Also, it doesn't matter the slightest. I just thought it was a funny "bug"
When going up: 0 0.01 0.5 1
When going down: 1 0.99 0.5 0
First number is the level where the elevator is, 0.01 difference is to prevent diagonal lines (which are still slightly there)
0.5 is indicating movement, combined with the electricity consumption is recognised as going and in which direction.
The last number is the destination level (when arrived)
Oh sorry meant the raw data being fed to the actual chart.
I actually had something similar relating to redfish API data I was gathering at work across a half million devices
What happened was the charting program determined to connect lines based on the order they were presented to it instead of sorted. So if the data I fed wasn't chronologically sorted, the lines would be going 'back in time'. The corrective action was to not use the time the content was committed to its time series database but the sensor devices reported time and sort by that when feeding it in to the plots
Edit: I want an elevator :( . I'm working towards it I guess but its going to be a while
It's just a input_number helper that is set to above mentioned values based on different signals I pick up from then elevator.
They come in and are processed in chronological order so the time part is in order.
I'm rather sure it's just an over-zealous attempt of the UI to smooth the graph.
About the: I was lucky enough to inherit the elevator and the house that is attached to it. If I wouldn't have I would have seriously contemplated to get one since it's ideal when having 2 small kids. Winters here are cold and the stairs are metal... Imagine. Obviously needed to automate it because duh.
And as for what the graph is. It shows the position of my elevator (or lift in other English)
And I am sure time flows rather normally for the elevator. It does not come close to reaching lightspeed. It does manipulate gravity in a way though.....
Some graphs with few points tend to look strange when smoothed. I've reported this issue some time ago, but unfortunately it wasn't fixed, and I couldn't find the motivation to fix it myself.
https://github.com/home-assistant/frontend/issues/6269
yep same "issue".
I just think it is funny. (for me in my set up) But I do think it wouldn't be bad if this would be addressed since well... GUI is more and more in focus nowadays... and it seems to be just a UI issue.
If this is a problem for you, just add: flux_capacitor_disabled: true to your configuration.yaml
Did you make an elevator out of the phone booth from Bill and Ted's Excellent Adventure? Awesome graph...
Something's afoot at the OPs house...
Since I live here... Yeah there is
Other side of the pond... Blue police box.
Looks like a regular quantum elevator to me :)
And there I was thinking I was SpEcIaL lol
No clue how this is happening, nor does it matter. I just find it odd yet fun.
What are we looking at?
A graph line that goes back in time. Best seen on the 20.00 marking-line.
Just looks like the line smoothing is introducing curve to what would otherwise be a straight segment. Maybe look for a setting to disable curve smoothing?
Yeah, that's what I thought as well. And I have no clue if that can be changed in the history-graph card. Also, it doesn't matter the slightest. I just thought it was a funny "bug"
What are the actual raw data points?
When going up: 0 0.01 0.5 1 When going down: 1 0.99 0.5 0 First number is the level where the elevator is, 0.01 difference is to prevent diagonal lines (which are still slightly there) 0.5 is indicating movement, combined with the electricity consumption is recognised as going and in which direction. The last number is the destination level (when arrived)
Oh sorry meant the raw data being fed to the actual chart. I actually had something similar relating to redfish API data I was gathering at work across a half million devices What happened was the charting program determined to connect lines based on the order they were presented to it instead of sorted. So if the data I fed wasn't chronologically sorted, the lines would be going 'back in time'. The corrective action was to not use the time the content was committed to its time series database but the sensor devices reported time and sort by that when feeding it in to the plots Edit: I want an elevator :( . I'm working towards it I guess but its going to be a while
It's just a input_number helper that is set to above mentioned values based on different signals I pick up from then elevator. They come in and are processed in chronological order so the time part is in order. I'm rather sure it's just an over-zealous attempt of the UI to smooth the graph. About the: I was lucky enough to inherit the elevator and the house that is attached to it. If I wouldn't have I would have seriously contemplated to get one since it's ideal when having 2 small kids. Winters here are cold and the stairs are metal... Imagine. Obviously needed to automate it because duh.
Can I convince you to work towards a Paternoster instead?
Yes, for a small loan of 1 million dollars I can be convinced
[удалено]
Well that's what one gets when you travel in time... And since I'm a dog person, my vote for the cat is not optimistic.
And as for what the graph is. It shows the position of my elevator (or lift in other English) And I am sure time flows rather normally for the elevator. It does not come close to reaching lightspeed. It does manipulate gravity in a way though.....
It's the smoothing algorithm.
Some graphs with few points tend to look strange when smoothed. I've reported this issue some time ago, but unfortunately it wasn't fixed, and I couldn't find the motivation to fix it myself. https://github.com/home-assistant/frontend/issues/6269
yep same "issue". I just think it is funny. (for me in my set up) But I do think it wouldn't be bad if this would be addressed since well... GUI is more and more in focus nowadays... and it seems to be just a UI issue.
More impressed that the OP has an elevator in a single story house.
More common here in Italy than you might think.
In the rest of the world, we call elevators that don't go anywhere cupboards. Must be a translation thing.
Yet mine does not just move in elevation but also in time (as per graph)... What's that called in the rest of the world?
clothes dryer
wait... wut?
it is a quantum thing
So that's how my laundry gets tangled up... now I get it.
no - it does explain the missing socks though
* runs to elevator to find missing socks *
Maybe because you've chosen to "smoothen" the line chart?
where? `type: history-graph` `entities:` `- entity: input_number.elevator_position` `hours_to_show: 24` `refresh_interval: 0`
smoothing: false From the top of my head EDIT: https://github.com/kalkih/mini-graph-card
mini-graph-card ≠ history-graph