SQL Logging and Custom Device Plugin

I'm working on a custom device plugin.

Is it somehow possible to log the states via SQL? I don't my states in the SQL database, even though it's updating in the GUI.

[jay (support)]

You can subscribe to all device changes with indigo.devices.subscribeToChanges(), described here and here, which will have the server forward all device changes to your plugin by calling the following methods in your plugin (if you define them): deviceCreated, deviceUpdated, deviceDeleted.

The same holds true for triggers and variables, and will work for schedules and action groups once we finish those (by GM).

Just call the appropriate indigo.*.subscribeToChanges() in the startup() method of your plugin and you'll begin receiving those messages.

You can subscribe to all device changes with indigo.devices.subscribeToChanges(), described here and here, which will have the server forward all device changes to your plugin by calling the following methods in your plugin (if you define them): deviceCreated, deviceUpdated, deviceDeleted.

The same holds true for triggers and variables, and will work for schedules and action groups once we finish those (by GM).

Just call the appropriate indigo.*.subscribeToChanges() in the startup() method of your plugin and you'll begin receiving those messages.

The second link says I don't have permissions, but it looks like that link is for 5.1 documentation?

In any case, I don't think I explained my issue clearly.

My custom device has a few states (volts, current kilowatts, etc). My plugin is updating the state in the GUI just fine, but I'd also like to update the SQL database with the new states.

Edit: Maybe I should also ask this: Is it the plugin's or Indigo's responsibility to log the data to the SQL database? If it's my responsibility, how do I go about doing it (use Indigo's API or use Python's sqlite3 API)

[jay (support)]

Sorry, fixed the link.

And yes, I did misread your post. Our SQL logger will eventually get plugin defined device state changes into the DB. Our intention all along has been to rewrite the logger as a plugin - if we don't get it done by GM it will be done very soon after.

You can subscribe to all device changes with indigo.devices.subscribeToChanges(), described here and here, which will have the server forward all device changes to your plugin by calling the following methods in your plugin (if you define them): deviceCreated, deviceUpdated, deviceDeleted.

The same holds true for triggers and variables, and will work for schedules and action groups once we finish those (by GM).

Just call the appropriate indigo.*.subscribeToChanges() in the startup() method of your plugin and you'll begin receiving those messages.

Jay,

Is there a way for the subscribeToChanges() function allow you to filter, or specifically choose a single (or class of) devices?

[jay (support)]

Not currently - you'll need to implement the filtering in your plugin code.