Not sure if domopad or logging in sql causing the issue

Sent from my COL-L29 using Tapatalk

I haven't checked all my devices (would take very long time, hehe) but it seems all of them are getting the same invalid historical data error.

The errors are definitely with your Indigo Server / DomoPad plugin in some way. That first one should always come up - it doesn't do any real processing. What version of the plugin are you running?First I get internal error when launching (first screen shot) :
http://MYIP:8176/AndroidClientHelper/
Code: Select all
WebServer internal server error "http://MYLOCALIP:8176/AndroidClientHelper/" from MYLOCALIPFROM
WebServer
Request Headers:
AUTHORIZATION: Digest username="MYUSERNAME", realm="Indigo Control Server", nonce="3bb406141e0ce03e315a4ff64970f508", uri="/AndroidClientHelper/", algorithm=MD5, response="319e84fb1982cab2e9ae9f9826b71b97", qop=auth, nc=0000026b, cnonce="6c4a1b878c4e169f"
HOST: MYLOCALIP:8176
UPGRADE-INSECURE-REQUESTS: 1
ACCEPT: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
USER-AGENT: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.44 Safari/537.36
CONNECTION: keep-alive
Remote-Addr: MYLOCALIPFROM
ACCEPT-LANGUAGE: en-US,en;q=0.9,nb-NO;q=0.8,nb;q=0.7
ACCEPT-ENCODING: gzip, deflate
Traceback (most recent call last):
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cprequest.py", line 609, in respond
cherrypy.response.body = self.handler()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 157, in index
dbConn = self.getDatabaseConnection()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 380, in getDatabaseConnection
return indigosql.IndigoSqlite(dbConfig["dbName"], None, self.logMessage, None)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/dataAccess/indigosql.py", line 392, in __init__
self.sqlConn = self.sqlmod.connect(sql_lite_db_file, detect_types=self.sqlmod.PARSE_COLNAMES)
ValueError: database parameter must be string or APSW Connection object
WebServer undefined page requested "http://MYLOCALIP:8176/AndroidClientHelper/css/global4.css" from MYLOCALIPFROM
WebServer undefined page requested "http://MYLOCALIP:8176/AndroidClientHelper/css/indigo4.css" from MYLOCALIPFROM
WebServer undefined page requested "http://MYLOCALIP:8176/AndroidClientHelper/css/fonts.css" from MYLOCALIPFROM
This seems to be the issue - it is failing to read the database configuration. Do you have the SQL Logger configured and working?Traceback (most recent call last):
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cprequest.py", line 609, in respond
cherrypy.response.body = self.handler()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 157, in index
dbConn = self.getDatabaseConnection()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 380, in getDatabaseConnection
return indigosql.IndigoSqlite(dbConfig["dbName"], None, self.logMessage, None)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/dataAccess/indigosql.py", line 392, in __init__
self.sqlConn = self.sqlmod.connect(sql_lite_db_file, detect_types=self.sqlmod.PARSE_COLNAMES)
ValueError: database parameter must be string or APSW Connection object
SQL logger (in debug perspective) is running as normal and tables are updating and adding data ok. Also tried to rename sqlite dB in order to start fresh. No effect. Do you have any idea how to restart services further? Or should I post in another forum for this error?RogueProeliator wrote:This seems to be the issue - it is failing to read the database configuration. Do you have the SQL Logger configured and working?Traceback (most recent call last):
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cprequest.py", line 609, in respond
cherrypy.response.body = self.handler()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 157, in index
dbConn = self.getDatabaseConnection()
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/reqhandler.py", line 380, in getDatabaseConnection
return indigosql.IndigoSqlite(dbConfig["dbName"], None, self.logMessage, None)
File "/Library/Application Support/Perceptive Automation/Indigo 7.2/IndigoWebServer/plugins/AndroidClientHelper/dataAccess/indigosql.py", line 392, in __init__
self.sqlConn = self.sqlmod.connect(sql_lite_db_file, detect_types=self.sqlmod.PARSE_COLNAMES)
ValueError: database parameter must be string or APSW Connection object
Let me dig in there, might need to provide you a debug version to run to get us some more detailed error information.SQL logger (in debug perspective) is running as normal and tables are updating and adding data ok. Also tried to rename sqlite dB in order to start fresh. No effect. Do you have any idea how to restart services further? Or should I post in another forum for this error?
There will be a new version of the plugin coming out over the holidays which contains better error trapping and reporting to hopefully diagnose the issue...No news?