Cormacs

I got it working great. The only issue I have is the odd time the notification doesn’t come. When I rerun the program the notification comes through.

I have. Not only did I make a notification alert for when the stove fires up and shuts down. I also have a program to count the seconds the stove runs and emails me run times.

So I think I have it working fairly reliably with programs and variables now. I used a few variables to accomplish my goal... Stove On Temp = the desired high temp Stove Off Temp = the desired low temp I made this program to lower the setpoint when the stove reaches the desired temperature. Heat Off - [ID 0011][Parent 0012] If $Garage_Temperature >= $Stove_On_Temp And 'Garage / Garage Thermostat - Main' Heat Setpoint is '$Stove_On_Temp Degrees' Then Set 'Garage / Garage Thermostat - Main' Heat Setpoint '$Stove_Off_Temp Degrees' Else - No Actions - (To add one, press 'Action') Then I created this program to raise the setpoint when the desired low temperature is reached Heat On - [ID 0010][Parent 0012] If $Garage_Temperature <= $Stove_Off_Temp And 'Garage / Garage Thermostat - Main' Heat Setpoint is '$Stove_Off_Temp Degrees' Then Set 'Garage / Garage Thermostat - Main' Heat Setpoint '$Stove_On_Temp Degrees' Else - No Actions - (To add one, press 'Action') Now the issue with this is I have found that the thermostat isn't reliably receiving the isy commands. So I made these two programs to confirm the thermostat has received the command. For these two programs I use two variable. Before Query = The thermostat setpoint as the isy believes it After Query = The actual thermostat setpoint as retrieved from the thermostat after the query This first program sets the variables after a change in heating state. Query - [ID 0017][Parent 0012] If Program 'Heat Off' is True Or Program 'Heat On' is True Then $Before_Query = 'Garage / Garage Thermostat - Main' Heat Setpoint ° Set 'Garage / Garage Thermostat - Main' Query $After_Query = 'Garage / Garage Thermostat - Main' Heat Setpoint ° Else - No Actions - (To add one, press 'Action') Then this second program evaluates the two variables and if they are the same then nothing happens. But if they are not the same it re-triggers the first program and the cycle continues until the thermostat has received the command from either of the first two programs Compare Query - [ID 001C][Parent 0012] If $Before_Query is not $After_Query Then Run Program 'Query' (Then Path) Else - No Actions - (To add one, press 'Action') And then I made this last program to make setting the desired temperature easier. With one last variable. Keeping in mind I always want the low temperature to be 5 degrees lower than the high temperature. Stove Setpoint = the temperature that I actually desire the room to be at Stove Temperatures - [ID 0015][Parent 0012] If $Stove_On_Temp is not $Stove_Setpoint Then $Stove_On_Temp = $Stove_Setpoint $Stove_Off_Temp = $Stove_Setpoint $Stove_Off_Temp -= 5 Else - No Actions - (To add one, press 'Action') It seems like a lot of work but I am happy with it. The stove has been running all day today turning on at 15 degrees Celsius and turning off at 20 degrees Celsius. I am also open to suggestions if anyone thinks they can do it in a less complicated manor.

I have been noticing this.

Is there any way to change the hysteresis level in the Insteon thermostats? I have it controlling a pellet stove so it would be nice to have a little more temperature swing between calls for heat. Maybe someone has a program that would do the same thing?

Your if argument is using the ambient temperature as a trigger. Using the setpoint as the trigger may work better. "Thermostat setpoint is not 72". That way you wont have to wait for the furnace to heat up the house before it gets triggered. Maybe the setpoint will be a more reliable trigger.

There are three other devices in the garage. One is a plug in I/O device. I consider my Insteon network pretty strong since I only have a 1000 sq.ft and over 30 dual band devices. I haven’t had any issues with any other devices. But I guess the thermostat only being an RF device isn’t smart to be directly on top of the antenna wires for the dog fence. I’ll do some playing around, I may attempt to add the command twice in the program so it sends the command more than once.

Hi, I was just curious if there was anyway for the ISY to confirm it's commands. I have one program that puts my insteon thermostat Fan Mode to "On". The problem is my thermostat is right close to my invisible dog fence radio and I believe the odd time it overloads the radio in the thermostat and blocks the signal. Is there anyway to have the ISY confirm that it's command has been received? I thought by adding a Query device after the command in the same program would do the trick but it hasn't. Here is the program I have so far... Stove On - [ID 001E][Parent 0012] If 'Garage / Garage Thermostat - Main' Temperature <= '$Stove_Setpoint Degrees' And 'Garage / Garage Thermostat - Main' Mode is Heat And 'Garage / Garage Thermostat - Main' Fan Mode is Auto Then Set 'Garage / Garage Thermostat - Main' Fan Mode On Set 'Garage / Garage Thermostat - Main' Query Else - No Actions - (To add one, press 'Action') The times that the command isn't received I can look on the ISY admin console and it shows the fan mode as "ON" but when I query it manually it automatically goes back to "Auto". Then the program re-runs and usually that time the thermostat picks up the command. I know most people will say why don't you just separate the two devices but I'd rather not have to re-wire either device if I could just make a simple command to confirm the ISY's command is received.

Perfect I was getting confused because every time I was reading about it people were complaining about having to use another PLM to connect their computer for programming. But if I can do it all within the isy I will be happy. Sent from my iPhone using Tapatalk

Sorry for the newbie question. I'm looking for someone who has experience with the EZIO8SA. I have been researching like crazy before a pay for the expensive item. I'm just curious do you have to have a computer to configure this device or can you just link it to the ISY? When you link it does it just come up like an IO device but just with more inputs and outputs? I'm just trying to get the whole picture before I throw away $300 on a purchase that may not work for me. I have four dry contacts to monitor and four outputs that need controlling, that's why I'm looking into this item. Can I link the device and just start adding the inputs and outputs to programs and scenes or is there some programming that requires a computer and PLM? Thanks for any answers you can give me.

Who said he wants to open his garage with his phone in his car? SMH. All he said is he wants to open his garage with his phone. I find it very useful for when I want to let someone in to my garage when I'm not home without giving them the code. Sent from my iPhone using Tapatalk

I have it set for momentary b. It always required two presses until I made that program. Sent from my iPhone using Tapatalk

Before the program when I push the button the button would stay on so the next push would just be turning it off not doing anything. This is with having the io link set to momentary as well. If you do a query it would always jump back from on to off. Maybe it's because I don't have the position sensor? When I was having this problem there were tons of people on here having the problem and that's how I came across this program. Sent from my iPhone using Tapatalk

The program is a minor convenience. Without you would have to push the button twice instead of once to actuate the door again. Sent from my iPhone using Tapatalk

I run that same program. The purpose is there because the relay contact is intermittent. So when you actuate the door the relay goes closed then open to actuate the door. The problem is the isy sees the relay close command but since the io linc initiate the open conmand itself the isy doesn't always pick it up. That's why the query program works good so the isy always has the correct relay status. Before I had this program I would command the door open with mobilinc and mobilinc would report the status as always actuating and I would have to double tap the button. But with that program it automatically changes from actuating back to off. Sent from my iPhone using Tapatalk