[implemented] Logging and graphing the state of devices

---

We need to be able to graph boolean devices

*I think the best solution for logging of states is the following:
We have to decide how the values are plotted and logged. So we would have two types:

• discrete values / states: don’t emit same values, draw horizontal lines from one data point to the next (states, enumerations, strings)

• continuous values: emit same values, draw interpolate line (linear / cubic) between data points (temperature, humidity, …)

In practice we can simply decide from the attribute type the plotting type:

• number => continusly (like we are doing now)
• boolean, enum, strings => discrete values (will be available later)

But that does not work for variables devices well at the moment because it does not emit changes, if the value does not change. I will try to change that (didn’t think about logging here).*

As stated before here in pimatic/pimatic#262

I can see why people would want that, but it should be configurable.

I for one really DETEST the dimmervalue popping up on my graph page. For me that is useless info.
I would like to log some of my variables, but most of my device states I give a rats a## about.

@DavidZH so just add your voice to the enhancement request the using the “upwards arrow” on my post

For me it makes sense too to store and graph boolean devices like ‘is heating on’ and also in combination with numeric values like ‘temperature of the heating system’.

You are right, but still: make it configurable.

What about this:

{
  "devices": [
     {
        "id....
        ...
        "prot...
           {
           }
        "graph": true
     }
  ]
}

• continuous devices will graph by default

• switch devices will NOT graph by default

add an option "graph": "boolean" with the defaults above.

I’ve added support for graphing of state attributes in the newest version of pimatic and pimatic-mobile-frontend. Let me know what you think of it and if there are any issues. I had to change the charting library because of licensing issues, but I think I found a very good replacement.

@sweetpi thanks, to me this is working absolutely fine (for example i can display my boiler switch state together with the temperature, i can also see when doors or windows were opened in the day (contact))

Sorry, after update I still can’t get it working. Would like to have graph for GPIOs, here my current config:

    {
      "id": "presence-sensor",
      "class": "GpioPresence",
      "name": "INPUT1",
      "gpio": 20,
      "inverted": true,
      "graph": true
    },
    {
      "id": "presence-sensor2",
      "class": "GpioPresence",
      "name": "INPUT2",
      "gpio": 26,
      "inverted": false,
      "graph": true
    },

What is wrong, or is it not possible for GPIO plug-in?

EDIT: after a complete reboot of the pi I have the graph of the GPIOs now => solved for me

Ok, I can see ALL of my devices on the graph page, but now I’d like to turn some off.

    {
      "id": "living-lamp-dining",
      "name": "sys_lamp_eettafel",
      "class": "HomeduinoRFDimmer",
      "protocols": [
        {
          "name": "dimmer1",
          "options": {
            "id": 7979378,
            "unit": 11
          }
        },
      ],
      "graph": false
    },

parsed fine, but didn’t work.

@sweetpi, i am monitoring my gas consumption (every 10 minutes i fill a variable with the number of m3 over those 10 minutes).
So i think that a “discrete” type should be more appropriate than a “continuous”, so i added “discrete”: true into this

{
  "variables": [
    {
      "name": "ConsoGaz10",
      "expression": "$gas_consumed",
      "type": "number",
      "discrete": true,
      "unit": "m³",
      "label": "Conso Gaz Inst."
    }
  ],
  "xLink": "",
  "id": "conso-gaz-24h",
  "name": "inst./24h",
  "class": "VariablesDevice"
},

but unfortunately pimatic is still seeing that as a continuous variable.

By the way with the new graph you can’t click on an item to disable/enable it in the legend of the graph.

@sweetpi hi, should i open a bug report on github for:

By the way with the new graph you can’t click on an item to disable/enable it in the legend of the graph.

and second question is it a bug or an additional feature for discrete type for number?

@Tomasz said:

Sorry, after update I still can’t get it working. Would like to have graph for GPIOs, here my current config:

{
  "id": "presence-sensor",
  "class": "GpioPresence",
  "name": "INPUT1",
  "gpio": 20,
  "inverted": true,
  "graph": true
},
{
  "id": "presence-sensor2",
  "class": "GpioPresence",
  "name": "INPUT2",
  "gpio": 26,
  "inverted": false,
  "graph": true
},

What is wrong, or is it not possible for GPIO plug-in?

EDIT: after a complete reboot of the pi I have the graph of the GPIOs now => solved for me

There’s currently no graph option for devices.

@sweetpi, i am monitoring my gas consumption (every 10 minutes i fill a variable with the number of m3 over those 10 minutes).
So i think that a “discrete” type should be more appropriate than a “continuous”, so i added “discrete”: true into this

This option doesn’t exist either. I’ve added it.

By the way with the new graph you can’t click on an item to disable/enable it in the legend of the graph.

Should be possible, did you click on the text in the legend (not the line)? If it’s not working => github issue with browser/device you are using.

@sweetpi discrete for number is working fine!!! Fantastic i will post a graph when i will have collected more data: it’s beautiful!
For the disable/enable nothing happen when i click on the text legend (FF 35.01 on Windows 7), i will check with my personal computer this evening and report in github…

@sweetpi Look how it’s great now

In blue : temperature of the room (continuous)
in green : boiler state on/off (discrete)
in black : gas consumption over the 5 last minutes (discrete)

@sweetpi General a possibility of “discrete” would be very useful, especially for “ShellSensor”/“shell-execute” plug-in I would prefer.

@Tomasz said:

@sweetpi General a possibility of “discrete” would be very useful, especially for “ShellSensor”/“shell-execute” plug-in I would prefer.

Me too.

I’ve added the option for ShellSensors, too.

@Yves911 Really nice graph

perfect! thanks!