UPDATE: The IndigoSqlClient has been replaced in Indigo 5.1.2 by the SQL Logger Plugin, which provides additional functionality and several improvements. This forum thread has been locked, so please post any questions about the SQL Logger Plugin in a new thread.
Note that the old IndigoSqlClient client will be removed by the installer, and the old database format (table names and rows defined in the tables) is not compatible with the new plugin. If you are using the old IndigoSqlClient then please read over the documentation on the new plugin so you can make adjustments to your scripts/SQL to be compatible with the new plugin.
PREVIOUS CONFIGURATION DETAILS ON DEPRECATED SQL CLIENT:
The IndigoSqlClient can be used to efficiently save Indigo Device state changes, Variable value changes, and Event Log messages to either a SQLite database or a PostgreSQL database. This allows Indigo to integrate with other applications or systems, and allows for historical data tracking.
Although configuring SQLite is easier than PostgreSQL, if you have a specific need for PostreSQL then you will want to read about how to use PostgreSQL and Indigo.
- Mac OS X 10.5 or greater
- Indigo Server 2.5 or greater
I. Installing SQLite. SQLite is included in OS X 10.5's python install, so no special installation is needed.
II. Open configuration file to set your SQLite connection settings:
- Code: Select all
/Library/Application Support/Perceptive Automation/Indigo 2/IndigoSqlClient/IndigoSqlClient.conf
Make sure the database_type specified in the file is sqlite. The database name specified (sqlite_db) is the name of the database file that will be used inside the IndigoSqlClient folder.
III. Turn on the Log Device state history to SQLite or PostgreSQL checkbox inside the Start Local Server... dialog (available via the Indigo 2->Start Local Server... menu item).
Usage and Testing
When Indigo Server starts, it will now launch the IndigoSqlClient and begin logging Device state changes, Variable value changes, and optionally Event log messages. Check the Event Log window for any error messages from the IndigoSqlClient process.
Note the client does not attempt to purge old data from the database at any point, so you'll want to manually delete old entries occasionally.