larryllix

This sound like the query gives glitches in the status. Why are you querying these devices on a regular basis? I only have 2441ZTH units so there is never a point in querying them. I don't know about the 2441TH units. Stu is more the expert on those.

That didn't happen in one night and not likely within a week either. My house took almost two weeks to drop to 10c in Ontario last February, when it was -15 to -20 every day. To get down to 0c inside may never happen, if the sun shines on the house during the day. The house has insulation between the studs as you can see the wooden studs leaked the heat outside faster than the pockets between the studs.

How are you getting these stat statuses into ISY? Are they Insteon thermostats? 2441TH units?

Right. I guess I only link in controlling devices that cannot produce an Off like MSes. The rest of my scenes are run by programs triggers by devices. If the KPL can only produce On commands this shouldn't be a problem. ISY could act as a toggle to use a program initiated ramp off scene. If KPL button is switched On AND Light is not Off Then set 'Ramp Off scene' On Else ---

Yeah, as per KeviNH, above, I would try a few second wait in each. Your power may be glitching and sending Heat off commands or you have a defective thermostat but your programs aren't generating false alarms.

Sorry. It takes three hours to raise the house one degree C. I have a 180,000 BTU/hr tamkless water heater that runs in floor hydronic in the basement and n air handler with coil but I only run 60c water and it isn't very high BTU output from the air handler. I lower my stats 2 degrees C at night and it takes 6 hours to get it back each day. My MBR runs cooler so that helps with not as much setback to sleep.

@MWareman Not a bad idea! I have begun to not worry about my home freezing. After setting my house temp back to 10 C last January I watched it take almost two weeks before the temp dropped that far in Feb 2015. Yeah it went to freezing in Orlando are at that time too and it was -20C here in Ontario. When building my home I had an open attic and my basement didn't freeze water on the ground inside despite -20 C for a week. After two weeks a thin film of ice formed and the melted the next day. The house was fully insulated in the walls at that time. We get very little sun in the winter and there was no heat available. I have no plumbing in outside wall, though. I now have an On/Off module running a small heater in the utility room set at 5C for an emergency long term failure of my heating. It also acts as a repeater for Insteon signals, being in the elbow of our L shaped house. With all this thermal mass and insulation my house take 3 hours to raise the temperature 3 degrees though. This is a PITA if I get home and the temp is really low. We have to sleep with an electric blanket for at least one night and wear heavy clothing for the next day. If you have an insulated home the freezing risk is minimal for less than a week of heating failure unless you have pipes in the outside walls.

I was thinking more of two buttons for On and Off. Even better, your idea, but in reverse. We usually want the speed of on so a scene would be in order but a program to enable a very slow ramp off would not expose any program delay incurred. A second scene could be used but I would just use a program to do the Off.

Nahhh... the doorbell is for the dryer finishing here. My piezo runs about 1-2 KHz and is intermittent, My ears are blind to over 8kHz and I have no problem hearing this anywhere in the house.

You an use a scene for the faster ramp rate going on and a separate scene for he ramp rate going off. Scene are economical and devices can hold more that 200 of 'em, each. Or ISY could, in parallel, beat the shared slow rate Off scene, going On, by issuing an On command with a faster local ramp rate that overrides the scene ramp rate. I think LeeG was discussing that above also. There are a few options with ISY/Insteon.

This the most basic Insteon device function and requires no variables or programs to accomplish. See Stu's description above.

V5.0.2 is absolutely stable as is all ISY firmware releases I have experienced or heard of. There are just some unfinished gui items and other minor things not completely working yet.

He uses a strange font though.

The From-To only serves to stop your loop by running the Else block, take it out. It only can confuse the ISY engine and does not run your code or serve any purpose. Query Thermostat - [iD 0011][Parent 0001] If At 12:00:00PM OR At 12:00:00AM <---second trigger in case of power failure and reboot, if desired Then Repeat Every 10 minutes Set 'Main Floor Thermostat - Main' Query Else - No Actions - (To add one, press 'Action')

The For 24 hours line only runs the Else block at the same time as it should retrigger. Take it out. It is not a condition with range of time, just a trigger Then at 12:00AM and a trigger for Else 24 hr. later.

No. It can never trigger false. I look at triggers at though they are instigating something not really being true or false as an attention getter for the PLC engine. If they are true or false it is only for their own purposes. Nothing else can test the trigger and find it true, ever. However, If SwitchLinc is NOT switched 'On' ...will run the Else block when an On command is received.

As Stu noted above a BuzzLinc is a much better idea. Blinking and Insteon device on and off every second for a long time will tie up your Insteon network badly and cripple ISY's seeing and controlling power. I bought a pulsing sonalert style beeper off eBay for a few bucks and hooked them to an I/O Link. It's loud enough I try to bury it behind some other junk in the room.. I created a series of programs from DefCon 1 to 5 that do various seriousness of beep and alerts, all based on one State variable. To make a few second beeping sound I use this line from any program. $sAlarm.level = 1 That's it. $sAlarm.level = 3 would also send me a text message explaining the problem. It would also send my wife a text message apologising.

I am using a portable humidifier as I screwed up and never left room on my furnace/air handler. People told me with ahome sealed this tightly the humidity would always be higher than wanted....BS! If I boiled noodles every day, and didn't have exhaust fans, maybe. Anyway this is my set of programs to cycle my humidifier at a constant humidity specified by an Integer variable constant, easily changed and denoted with '$c......'. Humidifier.start - [ID 003C][Parent 00BD] If $sHouse.humidity < $cHOUSE.HUMIDITY.SETPOINT And $sHouse.vacation is $cFALSE Then Run Program 'Humidifier.stop' (Else Path) Repeat Every 5 minutes Set 'Foyer / Humidifier' On Wait 25 minutes Set 'Foyer / Humidifier' Off Repeat 1 times Else Wait 5 minutes Set 'Foyer / Humidifier' Off Every 25 minutes, allow wick/filter to soak to top for 5 minutes. Humidifier.stop - [ID 0050][Parent 00BD] If $sHouse.humidity > $cHOUSE.HUMIDITY.SETPOINT Then Run Program 'Humidifier.start' (Else Path) Else - No Actions - (To add one, press 'Action') I have attempted to use centralised $sHouse.factors now, and use programs to clone device parameters into central variables. This offers the chance to use alternate parameter resources. eg: My humidity clone program checks to see if the Venstar T7900 thermostat is reporting OK and uses it's humidity report. If the T7900 is not reporting it uses an Insteon 2441ZTH in the basement that is slight off from the main floor sensing, but workable. If something fails ie: T7900, Router, NodeLink, RPi bridge, or other comm pathway device I can get parameters from the Insteon network devices.

As per Stu above and your follow up ideas. Main Humidifier - [iD 000B][Parent 0001] If Status 'Main Floor Thermostat - Main' is Mode Heat And Status 'Main Floor Thermostat - Main' is Fan On And ( ( Status 'Main Floor Thermostat - Main' <= 45% (Humidity) And Module 'Climate' Temperature <= 50 °F And Module 'Climate' Temperature > 40 °F ) Or ( Status 'Main Floor Thermostat - Main' <= 40% (Humidity) And Module 'Climate' Temperature <= 40 °F And Module 'Climate' Temperature > 30 °F ) Or ( Status 'Main Floor Thermostat - Main' <= 35% (Humidity) And Module 'Climate' Temperature <= 30 °F And Module 'Climate' Temperature > 20 °F ) Or ( Status 'Main Floor Thermostat - Main' <= 30% (Humidity) And Module 'Climate' Temperature <= 20 °F And Module 'Climate' Temperature > 10 °F ) Or ( Status 'Main Floor Thermostat - Main' <= 25% (Humidity) And Module 'Climate' Temperature <= 10 °F ) ) Then Set 'AprialAire 800 Humidifier' On Else Set 'AprialAire 800 Humidifier' Off With v5 you could extract the humidity and temperature into variables , do some math and u the humidifier on a sliding scale. I don't vary humidity but I never set it over 39%. I have to hand fill my supply bottles each day and don't want to have to cart 5 gal of water every day. Search for humidity sensor calibration. Damp salt with create an exact 75% humidity if you can get the sensor into a sealed vessel. Magnesium chloride with produce 33% humidity.

In this case (below)....none. Almost Sunset If Time Is Sunset - 30 minutes Then Run Program 'Fade Up Exterior' (Then Path) Fade Up Exterior If (NO CONDITION) Then Set 'ZwaveExteriorDimmer' 1% Repeat 50 times Set 'ZwaveExteriorDimmer' Brighten Wait 36 seconds, Else ----- However, -if there are conditions in the second program that are not wanted as triggers -if there are multiple conditions that result in more than two code path options. -if the first trigger could become false and it not be desirable to stop running the True block Almost Sunset If From Sunset - 30 minutes To Sunrise+30 minutes (next day) <------this will run else and stop Then Block Then Run Program 'Fade Up Exterior' (If) <---more decisions to be made Else Sunrise code here <---- sunrise+30 stops Then block, Fade Up Exterior insulated Fade Up Exterior [disabled] <----triggers can't happen If Door is closed <----door opening cannot stop code running, decision is made once Then Set 'ZwaveExteriorDimmer' 1% Repeat 50 times Set 'ZwaveExteriorDimmer' Brighten Wait 36 seconds, Else Door is open code lines

Not sure what "free-form" means but from my guess the answer is "No". ISY only accepts menu edited/written code. This is pretty standard for small controllers without debuggers or syntax checkers for interpreted code. If a syntax error was found who would it tell? Would you want your ISY to just stop/hang until you checked it next weekend? I don't believe 4.2.x supports setting to a variable based level. You will need v5.0.2. When v5.0.3 comes out it will be a drop in without much hassle. I have run v5.0.2 since it came out (a few months) and I doubt you will find a bug in it for the first 4-5 months of usage. If you can write free-form code then you can handle v5.0.2 with it's few GUI things not completed. Set your bulb ramp at 8 minutes and use the 3% jumps. You will never see it.

I have been through this before and spent a few nights on it. I need actual instructions not descriptions of some elements involved and acronyms. Most of this document is non-instructional for implementation on ISY and means nothing to me. Even the first link has an error built in I guess this is why I have never bothered with this nonsense to access my ISY.

Yup. Just as long as you have a Wait or Repeat line in there it hands the control back to the ISY engine to be productive while the time is being not-wasted.

You previously posted you could see the DON for the device in the Event Viewer. If that was true, the solution strength of the water would not make any difference to what the ISY does with the trigger inside Perhaps you were triggering a different unit than the program you were testing.

ISY v5.0.2 can use decimal multiplication for fine scaling and v4.+ can do offset (+/-) math, also. Linearisation will be more difficult.