akloeckner

I just gave it a try on the dev branch... Great magic. But it has worked, I think. There should be a new pre-release with the latest changes.

From how I understand the current - but also the old - code, that should have happened before as well. The first point on the graph is the first data...

I think, your seeing a different issue with similar symptoms. Since there is no data before March 8, the code just uses the earliest (I believe) data point also for...

I think, the changing timestamp could just be because the binning is not fixed (e.g. start of minute until end of minute). This is only the case, when using `group_by`....

You're also asking a lot: 120 points per hour is less than a minute, which seems to be the resolution of the interval display. 😆 Still... Or should just show...

Just to have the info here: this is where the magic happens: https://github.com/kalkih/mini-graph-card/blob/af01df1e2a68cbdd367cf8e27ada26ea8f41d83b/src/main.js#L528 And there's some condition on points per hour and hours to show. So, this might have it's...

I have tried to put the Allure in a sync group with my Arylic master and failed. It seems to be incompatible, if the firmware is below 4.6. That version...

I believe it is here: https://github.com/kalkih/mini-graph-card/blob/8e70381e3d887e5803bc8fc4bc115ecc4dc587e0/src/graph.js#L80-L98 `coords` is pushed with a new data point for every group of data `history[i]`. But if there are no entries in the history group,...

Not sure. I guess, it depends on the aggregate function and the type of data. The current logic probably has some reason for its existence, even though I don't get...

I dug a bit deeper into it in the course of #961. The correct substitute for missing data indeed depends on the aggregation function used, e.g. `delta` should surely be...