Folks,

Previously, I had created an attachment script for the Venstar thermostats (see http://www.schollnick.net/wordpress/hom ... e-monitor/ ) that would track the usage of the furnace, fan, and AC...

Now the Indigo v5 plugin is being reborn...

I am planning within the next day or so, to make a public beta available that replaces and expands on the previous generation...

How?

Well, it expands on statistics... Now reporting the time for each service (AC / Heat / Fan) for Daily, Weekly, Monthly and Yearly statistics. In addition, you can set maximum & Minimum temperature values, and the plugin will email whoever you specify, if those values are exceeded.

The usage statistics is output to a CSV file, and there is no longer any need to set a time/date action to output to the file. It will automatically be written to when the next heat / ac / fan event occurs after midnight... And all of the statistics are output to this file (Daily / weekly / monthly / yearly)......

And this plugin is not exclusively for the Venstar. Any thermostat adapter should work with this plugin....

- Benjamin

I can't wait ! Will it support multiple thermostats ?

five337 wrote:I can't wait ! Will it support multiple thermostats ?

Well the first part is easy enough. v1.00 - http://dl.dropbox.com/u/241415/Thermost ... 0v1.00.zip

Sort of.

The current version doesn't track which thermostat it is processing, it's designed to capture all traffic...

Which could and probably would conflict & confuse the plugin, in a multiple thermostat house....

But it would be a reasonably easy enough to modify this to support multiple thermostats...

I'll add it to the things to enhancement list...

- Ben

I don't think its starting up.

Code: Select all

  Plugin "Thermostat Enhancement Add-On" connected
  Thermostat Enhancement Add-On Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
<type 'exceptions.SyntaxError'>: ('invalid syntax', ('plugin.py', 112, 90, '\t\t\t\t\t\tprev_daily_runtime = indigo.devices[self.thermo_addon_id].states ["acDailyRunTime"])\n'))

five337 wrote:I don't think its starting up.

Code: Select all

  Plugin "Thermostat Enhancement Add-On" connected
  Thermostat Enhancement Add-On Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
<type 'exceptions.SyntaxError'>: ('invalid syntax', ('plugin.py', 112, 90, '\t\t\t\t\t\tprev_daily_runtime = indigo.devices[self.thermo_addon_id].states ["acDailyRunTime"])\n'))

I can't duplicate this issue.... When placed into the plugin directory, with Indigo v5.02, it's working fine....

Can you elaborate on what steps you have taken, so that I can try to reproduce this?

Downloaded, copied to the plugin directory, rebooted the computer.

Enabled the plugin and got it as soon as it loaded.

I get the same thing if I disable / re-enable it.

5.02 here as well.

I'll redownload and install it tomorrow and report back.

I'm getting the same error message:

Thermostat Enhancement Add-On Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
<type 'exceptions.SyntaxError'>: ('invalid syntax', ('plugin.py', 112, 90, '\t\t\t\t\t\tprev_daily_runtime = indigo.devices[self.thermo_addon_id].states ["acDailyRunTime"])\n'))

Running 5.0.2 also in OSX 10.6.8 Snow Leopard

The download says it is v1.0, but it is actually v0.9 --- It is the Survey plugin that is v1.0

Cheers,

Bryant

batr3 wrote:I'm getting the same error message:

Thermostat Enhancement Add-On Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
<type 'exceptions.SyntaxError'>: ('invalid syntax', ('plugin.py', 112, 90, '\t\t\t\t\t\tprev_daily_runtime =
The download says it is v1.0, but it is actually v0.9 --- It is the Survey plugin that is v1.0

Actually, I just found out what's the problem....

The Thermostat plugin is at v1.00, I verified it before I bundled it up... Actually I had to rebundle it before release, because I made that very mistake...

Instead, it appears that I made a different stupid mistake.

Don't take the Thermostat.indigoplugin from the "Add to Plugin's folder", that's the old version marked v0.90. Use the Thermostat.indigoplugin file from the root of the directory.

(I'll repackage it later today... @#$@#$@)

- Benjamin

Thermostat Enhancement Add-On Error Error in plugin execution InitializeMain:

Traceback (most recent call last):
<type 'exceptions.SyntaxError'>: ('invalid syntax', ('plugin.py', 112, 90, '\t\t\t\t\t\tprev_daily_runtime =
The download says it is v1.0, but it is actually v0.9 --- It is the Survey plugin that is v1.0

I just rebundled the download, http://dl.dropbox.com/u/241415/thermost ... 0v1.00.zip

(This should be the same URL as the old download....)

That one installed and runs fine.

Is there any advantage to using the Max/Min Temp thresholds in the plugin over just using Indigo's built in triggers to watch the temps ?

five337 wrote:Is there any advantage to using the Max/Min Temp thresholds in the plugin over just using Indigo's built in triggers to watch the temps ?

Before I answer your question... I have a question... The way you've asked this implies that there is an automatic way that Indigo will warn you, if it's over / under a particular temperature?

The only way I can think of doing this, is to create a trigger:

ie. Trigger -> Device State Changed, <Thermostate>, Zone 1 Temperature becomes greater than XXX...
Action -> Send Email
ie. Trigger -> Device State Changed, <Thermostate>, Zone 1 Temperature becomes less than XXX...
Action -> Send Email

Am I unaware of another method for performing this...?

But now, to answer your question.

five337 wrote:Is there any advantage to using the Max/Min Temp thresholds in the plugin over just using Indigo's built in triggers to watch the temps ?

Functionally, there is very little difference from the triggers described above....

The Max / Min temperature warnings feature was an obvious feature to add, and simply a convenience feature that I added. The addition of this simply allows the user of the plugin to not have to create the triggers above... In addition, I feel it's easier to change the Thermostat Monitor's preferences, then remember to update the triggers, if you decide to change the threshold temperatures. Let's face it, using the feature in the plugin, is an "freebie". Your already using the plugin, and it prevents you from having to add the triggers....

Indigo's triggers are nice, and excellent. I currently have 64 of them defined... And to be honest, I have forgotten about the majority of them. The philosophy I am attempting to use with my newest plugins (e.g. Switchboard, and the Thermostat plugin) is to add the most common functionality, and to try anticipate the features that people will want to use... This way, hopefully the user won't have to make a trigger to add some feature that I didn't add to the plugin...

Did this answer your question? if this didn't answer your question, then I apologize... But I'm not fully understanding the though behind the question... I'm not sure why it matters if it's part of the plugin, versus being able to be duplicated as a trigger...

Is there some extra functionality to that you would like me to add? If so, please keep in mind, I'm happy to add additional features...

I would be happy to elaborate, if you wish... But if you do want me to elaborate, could you please clarify the question a bit more?

- Benjamin

I was just curious.

I agree with the ease of keeping them in the plugin. I am quickly reaching 50 triggers and they are a pain to keep track of sometimes. No matter how well I name them - I can never seem to find the one I'm looking for to edit.

Functionality... (since you asked)

Email Notification for Filter changes based on a user specified hour of usage (i.e. Send "Change Filter Email" when AC + HEAT + FAN RunTime > 720 hours) ? Would anyone else find that useful ?

One trigger with an "is not between" condition would work as well. Just saying...

jay wrote:One trigger with an "is not between" condition would work as well. Just saying...

If "Is not between" is available, I would agree...

* Becomes Equal to
* Becomes not Equal to
* Becomes Greater Than
* Becomes Less Than
* Has any change

Are the only options I see for a Trigger against a Venstar Insteon adapter....

This is with Indigo v5.02 GM.....

- Benjamin