Looking at the current way a graph is formed when a motion or occupancy sensor is tripped, the value are just a 1 or a 0 and a line is drawn between them .
To make the graph more suited to the task and to show the period the sensor is tripped for I was wondering if you could fill in the gap between the 1 and the 0 (occupied) and leave the gaps between 0 and 1 blank (unoccupied)?
To help explain what I mean (as a picture can save a thousand words) I’ve mocked up a desk for you
Also while I have you, is there a way I can save my chosen graph options, rather than having to reselect them every time
Yes - I can change the SW to do this. It’s nearly possible now if you change the graph type to 3, but that causes other issues. Give this a go anyway and let me know what you think (with the obvious caveat that it’s a bit of a screwy graph).
Can you clarify what you mean? Do you mean have the options in the “Graph Options” tab restored when you restart?
Making the configuration persistent is something on my list - this includes the screen sizing and config options - it’s just not possible at the moment
In the channel configuration (where you enable logging), there’s an option called “GraphType”. It will normally be either 0 or 1, but you can change this, and 3 will generate an area plot… Just change to 3 and hit Save, and got and refresh the graph to see the difference…
I’ve tried Graph Type 3 and can see what you mean, but as you know all this does is fill in the gradient between 0 to 1s, rather than blocking out the entire time between 1 and 0 as that’s the period of occupancy (if you know what I mean)
Ok, so I think I’m missing something… What does the graph that you put in your example look like without “filling”? I assumed that filling the space between 0 and 1 was what you were after?
I’ve attached an example of what this would look like - and in the meantime I’ll take another look at your picture to try and see if I’ve missed something…
Ah - ok. That’s what I meant when I said type 3 didn’t do what you wanted. The version I attached is what I will put in the next version - it’ll probably go down as graph type 4. Currently I just bodged the graph to combine both types…