2 Gig Thermostat log time of A/C

[fastbird1]

Hi,

I have a vacation home and am all setup with lights/ thermostats etc.  Each room has its own thermostat.  When doors are left open the a/c shuts off.  But I want to know how I might go about keeping track of how much time in a day a thermostat is in the ON or Auto mode of cooling.  Is it possible being that it may be it may change modes several times?

Thanks

[larryllix]

This may depend on the mechanism you have to turn off the A/C in each room if the doors are left open.

 

Real time is hard to access in the ISY, so far. I achieve it by a WC8 board injecting real time into an ISY variable via the Rest interface.

 

 

An Insteon SynchroLinc 2423 can tell ISY when a 120vac plug-in A/C is running or not. 

 

Relative minutes and/or seconds could be tallied in ISY based on a counter that accumulates when the A/C is on only.

 

 

Based on another thread, you appear to have access to thermostat information in your ISY so those signals may be able to be used in the same manner.

[larryllix]

Something similar to this could possibly work.

 

If

    control A/C thermostat cooling is 'On'

 OR

    control A/C thermostat cooling  is Not 'Off'

 

Then

    Repeat every 1 seconds

       time.on += 1

 

Else

    --

 

Monthly time frames will be harder to achieve until v5.x.x. Three consecutive weeks are kept track of here. This could be extended to four weeks with more variables for each A/C.

 

If

      time is 12:01 AM every Friday

 

Then

    time.week_before = time.last_week

    time.last_week = time.on

    notify you 'Running Time for Last Week'

    time.on = 0

 

Else

    ---

 

Edit: Added forgotten "OR"

[fastbird1]

Thanks will let you know how that works. Is there a way to store the thermostat setting in a variable - for instance if I want to setback the temperature and restore it later?

[larryllix]

Thanks will let you know how that works. Is there a way to store the thermostat setting in a variable - for instance if I want to setback the temperature and restore it later?

No. Not in versions less than v5.0.0

 

You can write a series of programs to set a variable at the lowest temperature expected and run programs daisy chain from each other to test and set the variable from a comparison until one become True.

 

eg:

Program temp initiate

-----------------------------

if

    temperature >=0       <------any change initiates another run

  OR

    time is 4:00   <------- or initiate every so often anyway, just in case

 OR

   time is 12:00

 OR

  time is 18:00

then

   run program (if) temp_68

else

   ----

 

 

Program temp_68

-----------------------

If

   temperature > 68

then

   run program (If) temp_69

else

  set $temp_variable 68

 

 

Program temp_69

------------------------

if

   temperature > 69

then

   run program (If) temp_70

else

   set $temp_variable to 69

 

 

Program temp_70

------------------------

if

....

[fastbird1]

Something similar to this could possibly work.

 

If

    control A/C thermostat cooling is 'On'

    control A/C thermostat cooling  is Not 'Off'

 

Then

    Repeat every 1 seconds

       time.on += 1

 

Else

    --

 

Monthly time frames will be harder to achieve until v5.x.x. Three consecutive weeks are kept track of here. This could be extended to four weeks with more variables for each A/C.

 

If

      time is 12:01 AM every Friday

 

Then

    time.week_before = time.last_week

    time.last_week = time.on

    notify you 'Running Time for Last Week'

    time.on = 0

 

Else

    ---

Why both statements?

If

    control A/C thermostat cooling is 'On'

    control A/C thermostat cooling  is Not 'Off'

[larryllix]

Why both statements?

If

    control A/C thermostat cooling is 'On'

    control A/C thermostat cooling  is Not 'Off'

Not really sure about the use of "status" condition instead of "control" and some devices do not seem to need it so don't quote me on this one. Perhaps somebody more familiar with this one can chime in here.

 

Sorry, I made an error. The conditions must have an "OR" between them like this.

 

If

    control A/C thermostat cooling is 'On'

 OR

    control A/C thermostat cooling  is Not 'Off'

Then

 ....

 

In the first condition, obviously when the thermostat calls for cool "Then" is run as the complete logic of both is "True"

 

In the second condition when the thermostat turns Cool off Not causes the "Else" to run, stopping any code running in the Then and thus stopping the seconds counter from advancing further.

The "Then" section has program lines that will never stop on their own. Running the "Else" is one way to stop the counting up.

 

Since "Control" is used in both conditions and this only happens exactly when the signal is issued both can never be true.

For "Then" to run only one has to be true (Or)

For "Else" to run both have to be false (Or).  When the second condition becomes false (Not cool off) the first condition will also be false at that instant.

 

This looks weird at first but it works really well for other On/Off programming too.