[Solved] No Plot history after installing Indigo 7.3

v7.18.55
After installing Indigo 7.3 last Friday we have a problem with Indigo PlotD.
The plots for a new day are normal, but the plots after a new day (yesterday and before are not displayed anymore (until the update of last Friday).
See samples below.
We have reload the whole SQL database. (no faults). Stopped and Started IndigoPlotD again but no results.
Thanks for the help.

John I am out of town for 3 weeks

Have you loaded the latest version? It should work w 7.3

Karl



Sent from my iPhone using Tapatalk

Thanks for the quick response Karl.

Yep, v7.18.55 was working perfectly for months, until 7.3.
I do not doubt it works with 7.3. but what's going wrong here?
Do you have seen this kind of problem before?
We can wait for 3 weeks, relax and have fun.

I expect it's probably because of the file path change with 7.3. Check all the configs for your plot devices and make sure they're all using the new filesystem path for the 7.3 install.

Thanks for the feedback.
As said; the day plot is perfect and is working well, yesterday and days before are lost in the same picture.
Path is always the same with IndigoPlotD, it's outside the Perceptive folder:
/Documents/INDIGOplotD/PlotEnergyDay+-day-S1.png

It might be the sql dB
- check with indigo utilities if you can do an sql report

Also I recall you need to update the paths in config to the proper directories




Sent from my iPhone using Tapatalk

Thank you so much for the perfect hint!
It was the path of the SQL file…
We thought all the stuff was in the IndigoPlotD folder and that’s it.
But.. with the terrible changes every time of the version numbers of the Indigo folder names, the path to the SQL file was also changed.
Maybe for developers it’s a handy thing to change every time the path names, but for normal users it’s a lot of work (and annoyance) to puzzle every time after an Indigo update where and which paths has to be changed in which plugins or not…

Maybe it’s an idea to have a check into the IndigoPlotD plugin with a message in the log when the SQL file is too old and don’t has the data of today?

Thanks again for the quick response and all the best.

The path for the database was added to allow a user to put the dB at any place as some have = outside of indigo.
I could reverse that ( hide the path and set it in the program ) but that would break their install.

...

Karl


Sent from my iPhone using Tapatalk

Thanks for the explanation. A nice option but the SQL file is standard always into the (changed) Indigo folder.

Hi Karl,

I seem to have the same problem.
This is independant if I use mysql or Postgres.
INDIGOPloT only shows data since the last restart of the plugin.
Every day at 0:00 the plot begins again showing no older data.
This is a snippet from INDIGOPlotD starting:

Code: Select all

IGOplotD                     initializing  ... ;  debuglevel=[]
   INDIGOplotD                     indigo version found: 7
   INDIGOplotD                      number of days per bin category are: [8, 38, 390] for [days, hours, minutes] data
   INDIGOplotD                     using '/usr/bin/python2.7' for utily programs
   INDIGOplotD                     testing if variable enableTimeTracking_INDIGOplotD is == on/off/print-option to enable/end/print time tracking of all functions and methods (option:'',calls,cumtime,pcalls,time)
   INDIGOplotD                     SQLMode: batch;  GNUPLOT/MATPLOT: mat;  GNUplotVersion= ;  PLOT-Directory= /Users/wilhelm/indigo/INDIGOplotD/
   INDIGOplotD                     dataversion 2  dataOffsetInTimeDataNumbers:5
   INDIGOplotD                      read file /Users/wilhelm/indigo/INDIGOplotD/data/minute.dat lines: 2304  ok
   INDIGOplotD                      read file /Users/wilhelm/indigo/INDIGOplotD/data/hour.dat lines: 912  ok
   INDIGOplotD                      read file /Users/wilhelm/indigo/INDIGOplotD/data/day.dat lines: 390  ok
   INDIGOplotD                     command: reLoad SQL started
   INDIGOplotD                     sql logger used 12.05 secs CPU so far
   INDIGOplotD                     checking py-restore files
   INDIGOplotD                     initializing  ...2
 

Is it correct, that INDIGOPlotD is detecting Indigo 7 even when running from 7.4.1 ?

I tried to reinstall the same version, but the installer simply does nothing, because it states the same version is already installed.
Trying to reload the sql data results in this:

Code: Select all

   INDIGOplotD                     command: ReloadSQL
   INDIGOplotD                     pending indigoCommands: ['ReloadSQL']
   INDIGOplotD                     command: reLoad SQL started
   INDIGOplotD                      clearSqlData resetting sql import for Temperatur  Badezimmer-sensorValue- Col#=9 will retry, error message is:/Users/wilhelm/indigo/INDIGOplotD/sql/sqlcmd.sh: line 27: -t: command not found

   INDIGOplotD                      clearSqlData resetting sql import for 2. OG Temperatur-sensorValue- Col#=10 will retry, error message is:/Users/wilhelm/indigo/INDIGOplotD/sql/sqlcmd.sh: line 30: -t: command not found

   INDIGOplotD                     ------------------------------------------------------------------------------
   INDIGOplotD                     restarting SQL import,    it seems to hang. If this happens several times reload INDIGOplotD :
   INDIGOplotD                     ------------------------------------------------------------------------------


Any hint very welcome!
Cheers
Wilhelm

could you post your V numbers or better the complete log the std indigo log and the plugin.log file

looks light the paths are wrong
for Sql you need to put the proper path into config, with postgres mine is:
/Applications/Postgres.app/Contents/Versions/latest/bin/psql indigo_history -U postgres


also could you post your config menu?

Karl


the std indigo log should look like:

Code: Select all

Starting plugin "INDIGOplotD 7.20.69" (pid 48459)
   INDIGOplotD                     initializing    ...
   INDIGOplotD                     path To files:        =================
   INDIGOplotD                     indigo                /Library/Application Support/Perceptive Automation/
   INDIGOplotD                     installFolder         /Library/Application Support/Perceptive Automation/Indigo 7.4/
   INDIGOplotD                     plugin.py             /Library/Application Support/Perceptive Automation/Indigo 7.4/Plugins/INDIGOplotD.indigoPlugin/Contents/Server Plugin/
   INDIGOplotD                     Plugin params         /Library/Application Support/Perceptive Automation/Indigo 7.4/Preferences/Plugins/com.karlwachs.INDIGOplotD/
   INDIGOplotD                     (testing logger; see >/Library/Application Support/Perceptive Automation/Indigo 7.4/Logs/com.karlwachs.INDIGOplotD/plugin.log<   for detailed logging
   INDIGOplotD Error               !!!!INFO ONLY!!!!  logger  enabled for   ERROR         !!!!INFO ONLY!!!!
   INDIGOplotD Critical Error      !!!!INFO ONLY!!!!  logger  enabled for   CRITICAL      !!!!INFO ONLY!!!!
   INDIGOplotD                     check                   /Library/Application Support/Perceptive Automation/Indigo 7.4/Logs/com.karlwachs.INDIGOplotD/plugin.log  <<<<    for detailed logging
   INDIGOplotD                     Plugin short Name     INDIGOplotD
   INDIGOplotD                     my PID                48459
   INDIGOplotD                     set params 4 indigo V 7.4
   Started plugin "INDIGOplotD 7.20.69"
   INDIGOplotD                     initializing  ... ;  debuglevel=[]
   INDIGOplotD                      number of days per bin category are: [8, 38, 390] for [days, hours, minutes] data
   INDIGOplotD                     using '/usr/bin/python2.7' for utily programs
   INDIGOplotD                     testing if variable enableTimeTracking_INDIGOplotD is == on/off/print-option to enable/end/print time tracking of all functions and methods (option:'',calls,cumtime,pcalls,time)
   INDIGOplotD                     ======>>>>   loading cProfile & pstats libs for time tracking;  starting w cProfile
   INDIGOplotD                     SQLMode: batch2Days;  GNUPLOT/MATPLOT: mat;  GNUplotVersion= 5.2;  PLOT-Directory= /Users/karlwachs/Plots/
   INDIGOplotD                     command: reLoad data from SQL for last 2 days started
   INDIGOplotD                     checking py-restore files


and the plugin log:

Code: Select all

11 12:46:59 !!!!INFO ONLY!!!!  logger  enabled for   THREADDEBUG   !!!!INFO ONLY!!!!
11 12:46:59 !!!!INFO ONLY!!!!  logger  enabled for   DEBUG         !!!!INFO ONLY!!!!
!!!!INFO ONLY!!!!  logger  enabled for   INFO          !!!!INFO ONLY!!!!
12:46:59 !!!!INFO ONLY!!!!  logger  enabled for   WARNING       !!!!INFO ONLY!!!!
2020-02-11 12:46:59.771   ERROR          Plugin.__init__                  !!!!INFO ONLY!!!!  logger  enabled for   ERROR         !!!!INFO ONLY!!!!
2020-02-11 12:46:59.771   CRITICAL       Plugin.__init__                  !!!!INFO ONLY!!!!  logger  enabled for   CRITICAL      !!!!INFO ONLY!!!!
12:46:59 myLogSet setting parameters -- logFileActive= indigo; logFile= /Library/Application Support/Perceptive Automation/Indigo 7.4/Logs/com.karlwachs.INDIGOplotD/plugin.log;  debugLevel= []
12:46:59 initializing  ... ;  debuglevel=[]
12:46:59  number of days per bin category are: [8, 38, 390] for [days, hours, minutes] data
12:46:59 using '/usr/bin/python2.7' for utily programs
12:46:59 SQLMode: batch2Days;  GNUPLOT/MATPLOT: mat;  GNUplotVersion= 5.2;  PLOT-Directory= /Users/karlwachs/Plots/
indigoMPplot         INDIGO matplot started Version 6.8;  pid:48463;    at: 2020-02-11 12:47:00.291456
12:47:01                          -dataversion 2  dataOffsetInTimeDataNumbers:5
12:47:01 dataversion 2  dataOffsetInTimeDataNumbers:5
 read file /Library/Application Support/Perceptive Automation/Indigo 7.4/Preferences/Plugins/com.karlwachs.INDIGOplotD/data/minute.dat lines: 2304  ok
 read file /Library/Application Support/Perceptive Automation/Indigo 7.4/Preferences/Plugins/com.karlwachs.INDIGOplotD/data/hour.dat lines: 912  ok
 read file /Library/Application Support/Perceptive Automation/Indigo 7.4/Preferences/Plugins/com.karlwachs.INDIGOplotD/data/day.dat lines: 390  ok
12:47:02 command: reLoad data from SQL for last 2 days started
12:47:02 sql logger used 7257.46 secs CPU so far
12:47:08 checking py-restore files
12:47:08 initializing  ...2
12:47:11 Reading SQL files,filtering,converting
12:47:11 Elapsed time   Device----- State name-------------------------------   records read/imported/  LastID/  F size--Rej: ValueRng/  Number/ TimeSeq/timeWind/  Data/   col#
12:47:11 0:00:00.112800 EnergyDay_2-value-sum                                             29/       1/      47/     638-rejec:       0/       0/       0/      29/     0/    10
12:47:11 0:00:00.218785 alarm_front_door-value-event                                      29/       1/      47/     638-rejec:       0/       0/       0/      29/     0/    36
12:47:11 0:00:00.325828 EnergyDay_1-value-sum                                             29/       1/      47/     638-rejec:       0/       0/       0/      29/     0/    39
.....
12:47:19 0:00:08.617463 s-5-Leo-Lum-Window-illuminance-average                        185336/     787/  188398/ 5204138-rejec:       0/       0/       0/  184549/     0/     3
12:47:20 0:00:09.489794 wind sensor-directionDegrees-average                          295985/    6632/  422195/ 8105676-rejec:       0/       0/       0/  289353/     0/    13
12:47:20 SQL imp.  ... finished, total number of records read/imported:              1931684/   77254


hmm, this seems to be exceedingly difficult.
I_m close to giving up.

You are using a plugin 7.20.69
The pluginstore only has 7.18.55

could this be the problem?

Additionally the plugin doesn't use the password supplied in the SQLLogger settings and so it cannot log into the database.

Sorry, I thought, I published the latest releases.

Should be available now.

Karl

Hi Karl,

just an update:
I managed to get it working again with der new version of the plugin using Sqllite.
The Postgres installation yet doesn't work. The databse is populated by the sqllogger but IndigoPlotD is unable to read the data.

Nevermind. I'm ok with it as it is now,
Thanks for your help

Wilhelm

You have to set the proper psql string in config

Try to do a psql in a terminal
Whatever works there should go into config




Sent from my iPhone using Tapatalk