Thorben T.

> If only copy are in the second stage no qemu is needed. even more efficient for your case, if no qemu needed at all. you want to copy the...

looking at the code, "duplicates" is implemented in the "volkszaehler" api (it would have no effect with other APIs, confusingly). being in the API, it only sees the data after...

@astrakid: can you test the fix in https://github.com/volkszaehler/vzlogger/pull/501/files ?

great! #501 is not to be merged, because it's a very naive fix. i think the tolerance for the comparison (`0.000...01`) needs to be chosen in relation to the input...

@J-A-U: it's a typical tradeoff, you can't have complex features with an "easy" configuration. this won't happen before we have [strong AI](https://de.wikipedia.org/wiki/K%C3%BCnstliche_Intelligenz#Starke_und_schwache_KI) than can actually understand what the user wants...

quoting @J-A-U from https://github.com/volkszaehler/vzlogger/issues/431#issuecomment-812687394 > This may be an option with different states: only positive values, only negatives and both. > But it would be necessary to config this in...

this is somewhat a duplicate of https://github.com/volkszaehler/vzlogger/issues/481 , where options leading in this direction are already being discussed in more detail.

note that if your meters send data at async/irregular intervals (specifically s0 meters) this can become a pretty hard problem.

@wrichter: add it here: https://github.com/volkszaehler/vzlogger/blob/master/.github/workflows/build%2Btest.yml#L8

i would suggest to NOT use the uuids for this (and actually restrict their use to the volkszaehler.org middleware api that uses them. i think the only use-case where the...