@Heizelmann said in Device attributes of 'boolean' should not be avaraged in graph:
The first graph is from online watching. Two short pulses had happend
Well, this does not happen for switch state and presence attributes in my test setup!
- Which presence device type are you using?
- Did you change the database settings in your setup?
Normally, averaging should only happen for “continuous” attributes. These are "number " type attributes by default, if not specified otherwise in the device schema. Attribute types of type “boolean” and “string” are “discrete” attributes by default where no averaging takes place. The following setup is the shoing the default configuration pimatic is using:
"database": {
"deviceAttributeLogging": [
{
"deviceId": "*",
"attributeName": "*",
"type": "*",
"interval": "0",
"expire": "7d"
},
{
"deviceId": "*",
"attributeName": "*",
"type": "continuous",
"interval": "5min",
"expire": "7d"
},
...
EDIT: The following example from my test setup is showing history data from the 15th of March. You see nice how responseTime (number) is average to the 5min while the presence state (boolean ) is not averaged:
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law