larryllix

Sounds like the MS only has a BattLow On signal and not and Off being a one sided signal only. Also ISY has compensated by resetting ISY's status to Off by query.

Factory reset those things several times and then operate them from the link buttons a few times before hanging them back on the wall. I have always had problems with the MSes. I have 10 units. I have come to not trust the MS battery low signals or the flashing LED while seeing motion. I have one with a four month old battery, that has been flashing for two months of it, and yet never reported a low battery. Most of them don't seem to ever report it. I keep a list of every MS low battery signal reported in and a few have been flashing for the last two months but never reported in. This sometimes just goes away for another six month period and then resumes, also. I am just waiting until they stop working now. The battery clips won't stand much more of that nonsense. I keep my eye out for AC adapters and white 2.1mm x 5.1mm plug extension cords for a decent price. Only short ones seems to be out there for under the MS price.

A question please?Does this stat have a feature whereby you can click the current setpoint up/down a few increments and it does a temporary hold at that temperature and then returns the regularly scheduled program in 2 hours or some settable time? This is without disabling the schedule mode or multiple taps and/or menu shopping.

Not on purpose for the colour. My T7900 takes custom pictures in full colour but I find it annoying. Stats should disparear into the woodwork and not have a nuclear glow in the room. I have coloured lights for that. It would be hard to even figure out what the photograph is anyway with all the huge numbers and modes on the screen. Just makes a visual jumble of confusion.

That one seems to be very common in positive comments. With Zwave you eliminate all the components you can between ISY and the stat. That would be my pick and may be my next pick but without Zwave, maybe. Honeywell made good stats years back with the needed features.

Heard back is good!

It seems you can have Insteon/ISY simplicity with a very basic thermostat or you can go fancy with a stat and get control via NodeLink and a RPi. I do not support ZWave but I suspect they have some fancier models with better features. This is all dependant and what you want it for. The ecobee3 is the one I was considering to replace my Venstar T7900 but I don't wnt to make another $350 mistake out 6 devices and the real features you wil discover they have or do not have are never listed anyweher I have found. You may not even know what you want until about 6 months of usage and a few different seasons. My needs are very complex with my HVAC system. Some have been made possible by use of ISY programming but that is dependent on about 6 different devices functioning to be even possible. ISY, Router, WiFi, Rpi, WiFi, switches. Other stats will add the cloud to that mix.

Posts #57, 59, & 64 I use 2441ZTHs directly to ISY, for minor functions. I use Venstar T7900 for my A/C and some heating via NodeLink/Rpi to ISY I use various TekMar stats for main hydronic heating but they do not communicate without an additional $1000.00 bridge gadget. I use CAO Tags for probes, experiemntations and probes. I use a WC8 Webcontrol board with 1-wire sensors for outside and out building temps and wind speed REST interfaced into ISY. Wind speed is used to compensate chills in the winter by adjusting temps up half a degree C.

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.