Hi,

I got a little surprise the other day when I updated to 5.1.2 and my scripts based on output from IndigoSqlClient stopped working. I don't anticipate fixing those scripts will be a problem. I just have to find time to reacquaint myself with them (wrote them so long ago) and do it.

I am curious, now that I can no longer see the options for IndigoSqlClient in the Indigo, what the differences between its capabilities were compared to those of the SQL Logger Plugin. What improvements, besides using the new plug-in architecture, does it bring to the table over the IndigoSqlClient?

Is it mainly the ability to auto-prune old data? I can't recall if that was or wasn't a feature of IndigoSqlClient.

In fact, I can't recall even setting options for IndigoSqlClient it was so long ago that I began using it.

Thanks - Mike

Hi Mike,

Take a look at the SQL Logger plugin page, if you haven't already.

The big difference is in how the data is stored. Previously, there were just 3 or 4 device tables: one for all the thermostats, one for all the sprinklers, one for all the dimmer/relays, etc. Now every device has its own table. And tables are created even for plugin devices that have their own states. For example, Oregon Scientific temperature sensors, rain sensors, and wind sensors now can have their state information all tracked in the database. With the old SQL client, all custom plugin devices were just skipped.

Other changes include the auto-pruning and the UI to configure the settings (the previous client had a config file that had to be manually edited). The newer plugin is also more efficient, and will hopefully handle errors more robustly.

Thanks, Matt, for the additional description/comparison details between the two mechanisms. That helps me a good deal.

I have been referring to the SQL Logger plugin page already and will use that to update my scripts.

Mike