INDIGOplotD -- a plot tool for indigo -- program download

[kw123]

https://www.dropbox.com/s/qucuoz411juob ... 5.zip?dl=1

v 3.14.5

fixed:
MATPLOT (only) when using very large plot sizes, the x-axis labels (eg day /n month) were overlapping in Y direction. That should be fixed now

Karl

[kw123]

https://www.dropbox.com/s/dtc029ywbo4em ... 6.zip?dl=0 - v-3-14-6

fixed:
MATPLOT only: if data did not cover full time range, density of time tables where wrong. EG: If only 20days of one year data was present in a 365 day plot, it used the settings for 20 days not 365.

Karl

[kw123]

new version3-14-7 posted

http://forums.indigodomo.com/viewtopic. ... 48#p113648

fixed:
"/menu/simple plot" had some issues with creating plots while waiting for SQL import to finish.

some smaller internal fixes e.g. data config files are now formatted ..

Karl

from now on the most recent and history will always be posted here:
http://forums.indigodomo.com/viewtopic. ... 48#p113648

[kw123]

https://www.dropbox.com/s/bhwutuu0675fr ... 1.zip?dl=1


V 4-15-1
added:
- compatible with Indigo 5,6, and above .
- added MIN/MAX feature: plot min, max for each day in month, or day or week or hour on top of regular minute/hour/day plots
eg if you have and Minute-bin plot for one whole week. This option will show the min/ max for each day of that week = 7 points on top of the 2012 points from the Minute plot
you can place a dot or a number at these points.
works with Matplot and GNUPLOT


the example shows the month plot with the maximin / minimum values in the 3 months
Karl

[kw123]

v4-15-2 posted

fixed
"out2 not defined " error

https://www.dropbox.com/s/ntahq5arcakac ... 2.zip?dl=1

[kw123]

Fixed:
if data not presentGNUPLOT issues a warning.
There is now an option to suppress these warningsin general (in config) and the PLUGIN will automatically suppress MIN/MAX points that do not have any data.


https://www.dropbox.com/s/lgke89ra28bo2 ... 9.zip?dl=1

[kw123]

V 4-16-2

added EVENT measurement (data type)

Screen Shot 2016-09-28 at 21.54.52.png (73.33 KiB) Viewed 19652 times

Currently the plugin does averages/ max/min/ accumulated values, differentiated values etc. Now we are adding "EVENT"

For this the plugin reads the SQL database and ONLY PLOTS THE DATA THAT IS IN THE SQL-logger: Indigo writes to the logger only when a state / variable changes.

The attached shows an example of my "YOU GOT MAIL" sensor. When the mailbox gets opened the sensors sends a signal and when it is closed, not other wise.
Shown are the regular "average" as line and the "EVENT" measurement as red dot. You can clearly see the events when the mailbox got opened. While the average is an average over time for each bin ( here 1 hour) of the current state value in indigo.

This is NOT useful if you have frequent events (like 1/minute) You will get too many dots. It will look like a solid line.

One issue: the regular way does binning (collect info for eg 5 minutes) and the dot of the line gets draw on the corner of the bin eg at 5/10/15 minutes. The events get drawn at the second of when the event occurs. That might create some situations where the 2 infos seem out of sync.

Here how to use it:
in select device/states for data source, elect the device/state as before, but instead of average use "EVENT", click confirm

Screen Shot 2016-09-29 at 10.55.22.png (144.16 KiB) Viewed 19652 times

then in edit PLOT select the new data source and elect color linotype etc. and click confirm

Screen Shot 2016-09-29 at 10.55.53.png (91.2 KiB) Viewed 19652 times

Things like smoothing etc will likely not be working, but that would defeat the purpose anyway: do don't want smooth events, but raw as they occur.

Karl

[kw123]

https://www.dropbox.com/s/qnl070y3bxjzg ... 3.zip?dl=1

v 4.16.3 fixes data not updated

Karl

[kw123]

https://www.dropbox.com/s/f4kkhdmplvrlv ... 4.zip?dl=1

fixed matplot only:
do not show dots when <ymin or >ymax for matplot

I introduced

Code: Select all

y=max(ymin,min(ymax,y))

for Y values to be plotted to make the lines smoother when data was missing.
Other wise the lines would just stop. That also moved all dots into the plot rage, even when pushed outside by eg offset =-0.001 and plot range =0:2 to suppress dots at y=0
now that "fix" will only apply for lines and histogram etc. not for single dots. If they are outside Y-RANGE they will not be plotted.


Karl

[kw123]

https://www.dropbox.com/s/6btrgdj1xsdgn ... 6.zip?dl=1

posted v 4-16-6

fixed/added:
timing of matplot vs sql imports
improve sql import when a device/state is used as eg average AND max AND min( eg average temp/ max temp/ min temp in a day).
The SQL export job just runs once for all three


the plugin now accepts besides number:
val = str(val).upper()
if ( val== "TRUE" or
val== "T" or
val =="ON" or
val== "YES" or
val== "UP" or
val== "ENABLED"or
val== "CLEAR" ): return 1.0 # true/on/.... --> 1
if ( val== "FALSE" or
val== "F" or
val== "OFF" or
val== "NO" or
val== "DOWN" or
val== "FAULTED"or
val== "FAULT" or
val== "EXPIRED"): return 0.0 # false/off/... --> 0

Karl

[kw123]

https://www.dropbox.com/s/27jbel7sw0t7w ... 9.zip?dl=1
Version 4-16-9:

fixed:
problems with SQL import, only 2 days were imported. That caused some missing data and also created issues where no data was present when plot were generated.

added
new event types, to plot eg "door was opened", "mail arrived", "you got home" etc= parse data, In other words EVENTS, not for eg temperature plots etc.
ANY: any entry into the SQL logger Database
UP: only entry when data = 1/on/true/up/ ...
DOWN: only entries when data = 0/off/false/down/ ...
Changed: only data when it is different from last entry. (works only with MATPLOT not with GNUPLOT). When a device has eg 20 states and only one is changed all states get written to the database by indigo and that would be looked at as an "event". This option will only show the device/state events where the device/state is changed.
This only works with SQL logger switched on.

Karl

[kw123]

https://www.dropbox.com/s/ujsdlyn9r47jo ... 2.zip?dl=1

posted v 4-16-12

fixes:
depending on sequences sometimes EVENT type data was not handled properly (trying to optimize things too much)

Karl

[kw123]

posted v 4-16-14
http://forums.indigodomo.com/viewtopic. ... 48#p113648

added/fixed:
it will now automatically change path to SQLite database when you upgrade from i6 to i7 = change the path in indigoplotD/menu/configuration to the indigo sql database.

the pseudo logic is "if database still points to i6 path while indigo is v7 then change SQLite path to i7 path"

Karl

[kw123]

http://forums.indigodomo.com/viewtopic. ... 48#p113648

posted v 4-16-16

fixed issue that true/ false was not recognized as a "number" .

Karl

somehow i deleted: a line: val = unicode(val).upper().. it was recognizing TRUE though, but not true

[kw123]

http://forums.indigodomo.com/viewtopic. ... 48#p113648

posted V 4-16-18

fixed:
- invisible line not working when using ONLY event data in GNUPLOT. This option is needed to create a plot when no event data is present. Otherwise gnuplot does not create a plot if no data present.
- added variable position for "filled curves" line key in matplot. Filled curve is not a basic matplot line type. It is an graphical object and does not come with a line key. Before the line key was "manually" added at a fixed position. Now the Y position varies with line number so that you can have multiple filled curves and the line keys do not overlap.

Karl