larryllix

It is designed to piggyback off the 2441TH but ISY can control and recieve their signals directly.Having no hard contact o/p they are really only probe sensors for control elsewhere. I use one 2441ZTH units for humidity control in my cold cellar (ISY logic), and one for freeze alert/backup heater in my utility room (ISY logic). The OnOffLinc also acts as an Insteon repeater being at the corner of the L in my home and also acts as a powerline signal injector into one Inverter created phase/leg.

Which thermostat and how does ISY control it?

I only have the 2441ZTH, wireless. Answer: It does none of the above mentioned features.

Do any of these stats have things like: - Warm/cold weather shut down? - Dual schedules for heating and cooling - Temperature control based on external sensors, especially ANDing or ORing with inside sensor - Intelligent predictive setback compensation - most offer Intelligent setback recovery - better than 1 degree F resolution or sttability? I have a Venstar T7900 right now but it is very amateurish and seems to be created by a programmer, not an HVAC person. @Stu: Can you voice that stat from heat to Cooling and vice versa?

It is usually frowned upon, here, when you attack the 1 year old toddler from next door, with your GDO while attempting to crawl under to get that ball. That is the usual argument from the legal crowd on auto garage door closers.as per post #4. Unfortunately the links are all about selling contracts and the attempt to sell them through fear mongering but the risk does exist. I don't have my contacts connected to my GDO but only because of the ISY All On problem and laziness to connect. OTOH: I don't have the need for this HA or remote control due to my schedule and friendly neighbours I could call. I would have to worry more about racoons getting into my garbage than human intruders. I built this house without a security system.

Here is my date extraction tool Note: calculations are done in Integer variables and then copied to State variables to avoid multiple triggers. ---------------------------------- Set MM.DD - [iD 00B8][Parent 0006] If . . Time is 12:00:01AM . Or Time is 3:00:01AM . Or Time is 6:00:01AM Then . $sISY.DayOfWeek Init To [Current Day of Week] . $sISY.DayOfWeek = [Current Day of Week] . $sISY.DayOfMonth Init To [Current Day of Month] . $sISY.DayOfMonth = [Current Day of Month] . $ISY_Date.scratchpad = [Current Day of Month] . $ISY_Date.scratchpad /= 100 . $ISY_Date.scratchpad += [Current Month (Jan=1, Feb=2, etc.)] . $sISY.MM.DD Init To $ISY_Date.scratchpad . $sISY.MM.DD = $ISY_Date.scratchpad Else . - No Actions - (To add one, press 'Action') ------------------------------------------------

The first VenStat Log.newFile is the name of the ISY program that creates and writes the headers of the columns in the database file. The variable is created by myself using a separate program to extract the date. This requires V5 to get the date from ISY. You could just use any filename to start out. Mine switches files every first of the month. The "$s" indicates it is a state variable and I use it all through my system. See Next post

As a learning Allexian I am finding more vocal commands to use for things. One of the hardest decisions is to decide whether to do it vocally or just get up and tap the switch. I am finding the difference and what works best, slowly. If I am watching TV the vocals are good but If I am already travelling across the room the switch is usually less thinking. Time and experience will change that, I am sure.

Just about the same thing as using a six-shooter to shut a garage door.

I thought it was creepy when my GPS responds anytime to it's name in the car. You get thinking about this thing listening, waiting, for the key words and then popping up. It does have an antenna on it to send out traffic reports, so who knows....?

Exactly. Maybe if we had western low humidity it might be different. Even 0.5 degree C difference in a house in our climate seems to be too coarse. At times I want to drop the whole thing with these toy thermostats and go back to my real ones where increment of 0.1 C are possible. My old Honeywell stats had 0.5F increments or 0.2C increments. Maybe this is an admission they can't make the smart stats accurate enough to bother with more resolution. Having a heater chip built into the same box with a sensor is probably not the best design. On some weather days I have to set my stat higher and some the usual day settings are OK. Of course this is dependant on your own metabolism and to some degree how much A/C is blowing out of the registers right now. I really haven't determined why a temperature setting, and verified, feels too cool at one time and later too warm. I am going to start sitting on a CAO Tags to determine a better environment. Wife always laughs when she sees the anemometer on my hat, behind the monitor, hooked into my ISY994.

We all think you have an ISY994i as well as some other gadgets that hook into it. Since we are not all that good at hacking we would have to break in and steal the only valuable thing there...your ISY994i. You have to watch your assets! Not in your mind, but in the mind of the thief.

The 2441ZTH make the cheapest temp/humidity probes for Insteon on the market though.

Did the extra bill for the $475 scare tactics come with a non-disclosure contract also? I wouldn't tell anybody either :) When your GDO chops some intruder in half you are better off not to admit your were ever advised against doing what was involved with the accident.. That is negligence then. The lawyers love this stuff. After they make their dreamed up possibility public, they now have negligence cases to defend, as you have no ignorance to plead. Before that announcement, it was an honest mistake/mishap in somebody's home whereas the homeowner used every safety device made available by common sales knowledge. It's definitely a dog eat dog world out there. The "Did you know somebody done you wrong and it's always somebody else' fault?" billboards are starting in Canada, as well, now.

I have never seen a GDO system that came with legal documents being sold.

It's just too bad the whole thing seems to be geared toward ForeignHeat temperatures, and yet defaults to Celsius. Increments of whole degrees are too coarse for Celsius stat tweaking, usually. When I use Alexa to adjust a temperature setpoint, it is usually to tweak it, because somebody feels cold or hot. This only takes half a degree adjustments usually to not result in the opposite problem alternating the temperature radically. This appear to be one of the main reasons Celsius users switch back to Foreignheat on stats.

I would break your solution down into individual programs for each light. That way you can use different time allowances and different conditions for each zone of lighting. Does the time of day really matter for all of them? Lights left on during the day should be the same a problem.

Was a bit hard to find and I wasn't very proud of the details and updates done and wasn't happy about the charting capabilities in the forum but.... I am finding you really need to own and use a thermostat for almost a year to actually try it out. Thermostat information is always very vague, they state nothing n the box, and the real information needed, that makes a stat different from the rest is not stated anywhere. It works on the dreamware advertising technique. You dream it has a feature and will never know until it isn't returnable. http://forum.universal-devices.com/topic/17816-thermostat-features/?hl=%20thermostat%20%20comparison

Here is a simple fan status logger. Again a variable is used to square off the graphic representation. VenStat Log.fanChange - [iD 0111][Parent 00F8] If 'Gathering Room / GathRm VenStat' Fan State >= Off Then Run Program 'VenStat Log.cycle' (Then Path) Wait 4 seconds $Log.webfile.VenFan = 17 $Log.webfile.VenFan += 'Gathering Room / GathRm VenStat' Fan State $Log.webfile.VenFan Init To $Log.webfile.VenFan Run Program 'VenStat Log.cycle' (Then Path) Else - No Actions - (To add one, press 'Action')

This is the simplest of triggered recording without any fancy tricks ---------------------------------------------- VenStat Log.tempChange - [iD 0050][Parent 00F8] If . 'Gathering Room / GathRm VenStat' Temperature >= -50.0° Then . Wait 1 second . Run Program 'VenStat Log.cycle' (Then Path) Else . - No Actions - (To add one, press 'Action') ---------------------------------------------------------- To record data from events on my HVAC system, most parameters use a variable that gets written to the CSV data file. This makes it easier to write your notifications just using variable numbers and not devices. The big reason is to square off the presentation of the lines on the charting by recording the previous value, changing it and recording it again eliminating the long sloped line between points. In this example I chose the values 25 and 25 for Off/On to put them on the graph close to the temperature charting line and let the If section decide which value to place. Note the double call to the data writer to recordthe previous value one more time before updating. --------------------------------------------------------- VenStat Log.HumidifierChange - [iD 00F4][Parent 00F8] If Status (Old) 'Foyer / Humidifier' is Off Then . Run Program 'VenStat Log.cycle' (Then Path) . Wait 4 seconds . $Log.webfile.HumFan = 25 . $Log.webfile.HumFan Init To $Log.webfile.HumFan . Run Program 'VenStat Log.cycle' (Then Path) Else . Run Program 'VenStat Log.cycle' (Then Path) . Wait 4 seconds . $Log.webfile.HumFan = 26 . $Log.webfile.HumFan Init To $Log.webfile.HumFan . Run Program 'VenStat Log.cycle' (Then Path) --------------------------------------------------------------------- Here is the Heat/Cool/Off/Waiting mode logger. Again I picked a value that would be in the way on the chart. I started with the value of 25 and added the value from the stat resulting in an addition of 0-5. Some interpretation of values needs to be done on the graph to understand what mode the stat switched to. I was surprised to find the thermostat throws a lot of Waiting time out. This program may need some cleanup s the trigger for the program is the same data s I am recording. IIRC I found some delays in updating and may have remnant of experimentation yet. ----------------------------------------------------------------------- VenStat Log.heatPointChange - [iD 010E][Parent 00F8] If . 'Gathering Room / GathRm VenStat' Heat Setpoint >= 15.0° Then . Run Program 'VenStat Log.cycle' (Then Path) . Wait 5 seconds . Run Program 'VenStat Log.cycle' (Then Path) Else . - No Actions - (To add one, press 'Action') ------------------------------------------------------

First program is one that creates a new file each month and all recordings are to that file until another file is started. This is done by a variable that holds the number of the month as a suffix to the file name. A starting entry data line is also injected to start the CSV file off. ---------------------------------------------------- VenStat Log.newFile - [iD 010F][Parent 00F8] If . Time is 12:10:00AM . And $sISY.DayOfMonth is 1 Then . $Log.webfile.Month = [Current Month (Jan=1, Feb=2, etc.)] . $Log.webfile.Month Init To $Log.webfile.Month . Wait 2 seconds . Send Notification to 'eMail Larry' content 'Logger - HVAC Header' . Wait 5 seconds . Run Program 'VenStat Log.cycle' (Then Path) Else . - No Actions - (To add one, press 'Action') ------------------------------------------------------------ All recordings of data lines are done through the same program (Then) call. The purpose of this is consistency and to restart the timer that records every 30 minutes if there is no event action to record. ------------------------------------------------------------ VenStat Log.cycle - [iD 011E][Parent 00F8] If . Time is 12:00:15AM Then . Repeat Every 30 minutes . Send Notification to 'eMail Larry' content 'Logger - HVAC Entry' Else . - No Actions - (To add one, press 'Action') -----------------------------------------------------------------------

If you want examples of programs to record events I have ones that square off the chart lines generated also. Makes the output look more realistic. I record every HVAC change as well as record every half hour without events. It has caught a lot of HVAC program logic errors for me.

The UDI website is almost impossible to find things but after half an hour of searching I found this.https://www.universal-devices.com/sales/

Yes through another computer that accesses their cloud service. AFAIK the Venstars are the only stats that can be accessed from ISY without cloud access/accounts. EDIT: Sorry, incorrect. The only WiFi thermostats that can be accessed without cloud service. Insteon and Zwave thermostats can do this directly to ISY/PLM.

Factory reset removes all links if the factory reset is completely properly. In some devices the link button has to be held until the buzzing stops and most let go too early.