fixed: save config write error, executed once at midnight

fixed: unicode error

fixed: sql produced file with bad data INDIGOplotD Error 'could not convert string to float:

fixed settings for indigo 2022.1

make /Library/Application Support/Perceptive Automation/Indigo x.y/Logs/ default path to indigo sql db

added " (psql) and [] (sqllite) around column names in sql queries to allow eg index as name

set psql command string to default (w warning) if command is too short or does not contain psql

added measurement "delta Max" as compared to delta average of value this - last time bin

changes in v7.20.69 @ 2019-10-12

1. fixed nickname functionality
2. fixed width of histogram bars
3. fixed some menu items referencing old paths now all pointing to the indigo directories

changes in v7.20.68 @ 2019-10-10

1. added try/ except around individual lines in matplot, in case one line does not work the others get plotted

changes in v7.20.67 @ 2019-08-12

1. added measurement first and last. the data shown will only use the first /last data in that time bin.

changes in v7.19.67 @ 2019-08-12

1. worked on plotting external files

changes in v7.19.66 @ 2019-08-12

1. added action to reload sql data for ONE device/state/variable
2. some spelling fixes

changes in v7.19.65 @ 2019-08-11

1. added option to show todays data yesterday in setup line chhose shift line = -1day

fixed error:'Plugin' object has no attribute 'pr'

• added time debugging. ie track where cpu is spend.
• logfile is now called plugin.log, not indigoplotd.log

adopted new indigo path 7.2

indigo 6

v4.18.48

indigo 7

fixed SQL import bug for menu import single device/state . Was not properly initialized fixed SQL import bug for LARGE files. Sometimes the file was not completely finished exporting while indigoplotd started read and only read the first part of the file was imported

indigo 6

has now the following x axis for options:
1. off = leave # of ticks and date format to GNUPLOT or MATPLOT
2. blanks, use indigoplotD suggestions
3 A) GNUPLOT: %forat + ticks every xx seconds eg %H:M+2*3600 will show Hour:Min every 2 hours
3 B) MATPLOT use multiplier eg 0.1 1(default) 2 3 4 5 12 to decrease / increase # of ticks shows compared to indigoplotD suggestions

indigo 6

currently only for GNUPLOT added filed to set 1. format of x ticks ( %m/%d-%H= month/day-hour) 2. frequency of x ticks in seconds eg 3*3600 puts month/day-hour every 3 hours on the x-axis

enter: >>%m/%d-%H+12*3600<< in Format scale

Karl

indigo 6+

the reset period for event counts was set to 0 during restart of plugin.

indigo 6

fixed bug that was introduces in the previous version (a "-" sign was missing)

indigo 6

sql import bug fix

indigo 6 +

added indigo store version check
added eventCOUNT measurement: ** this measurement type counts all events (any entry in sql logger that is not 0 and adds them up. then at selected reset point the count goes to zero. reset points can be day, week, month, year.

this is useful if you have short events that go up/down in 1 - 3 secs so that the normal average months do not necessarily catch them . The normal counts measurement checks the value of the device/.state once a minute. What ever the state is then is used. This events count measurement checks all sql entries and will not miss any. In comparison to event UP or DOWN orANY count adds the # of events up.
So if you have 20 events in 1 hour
"eventsCOUNT" would show ONE point at y = 20;
"eventsUP" would show 20 points at y=1 at the exact event times hour:mim:secs.
"eventsDOWN" would also show 20 but at the points where the signal goes from 1 to 0.
"events ANY" would show 40 entries.

indigo 7

plugin now offers "event count" type lines.

in menue define data sources select measurement type event count

then in plots select this selection for a line

it plots the following quality:
for each bin (5 minutes/1 hour/1 day) if counts the number of events in the data where the data was updated in indigo and was > 0.
eg assume
5min 10 secs data was 1
6 min15 secs data was 0
7 min 35 secs data was 1
8 min 12 sec data was 0
10 min 1 sec data was 1
then the count value would be 2 for the 5 minute bin

This can be used to show eg how often a door was opened each hour

This is different than the regular count measurement. That measurement only tests the data once per minute at 58 secs and uses what ever the value is at that point in time. So if you have SHORT event types where a values goes up just for eg 3 seconds the regular count measurement would likely miss that.

indie 6

besides numbers the plugin recognizes:
if ( val== u"TRUE" or
val== u"T" or
val== u"ON" or
val== u"HOME" or
val== u"YES" or
val== u"SI" or
val== u"JA" or
val== u"IGEN" or
val== u"OUI" or
val== u"UP" or
val== u"OPEN" or
val== u"CLEAR"
): return 1.0
elif ( val== u"FALSE" or
val== u"F" or
val== u"AWAY" or
val== u"OFF" or
val== u"NO" or
val== u"NEIN" or
val== u"NEM" or
val== u"NON" or
val== u"DOWN" or
val== u"CLOSED" or
val== u"FAULTED" or
val== u"FAULT" or
val== u"EXPIRED" ): return 0.0

as 0 /1

indigo 6

the plugin now recognizes added QUI / NON as 1/0 in data besides --0/1 --yes/no --/true/false == ..

indigo 6

1. fixed bug for ";" delimted input files, bug was introduced with "events" feature
2. fixed some typos and improved the help text in device edit, ie how to configure x-format for self defined xaxis
3. fixed bug for RGB selection in device edit

indigo v 6

base release

indigo 6