larryllix

I'll second the value of the Network Module. It allows me to control MiLight RGBWW LED strips as well as Hue bulbs in programs. I use the logging contructs to track my HVAC systems and have found many bugs in my HVAC control system algorithms with MWaremans charting patches. This is all kept inside ISY with no other PC required except for the viewing of the charting.

TRigger Reverse was SmartyPant's idea to reverse the status logic, so scenes, without smarts like ISY, could still function. Trouble is, when a query is issued it reports the true state instead of the reversed status.. When ISY boots up it knows nothing about device's states. The whole system is mainly a report by exception (event trigerred). Until something sends it's change in status, ISY is blind. A Query gets a status response from most devices and then ISY remembers the last known state of each device.

The big concern that us usually dreamed up is the child next door crawls under the door as it is closing and the door beam does not see him/her in time to stop, and the door jam sensor is not set sensitive enough to reverse the motor without physical damage to the child. Web cameras sending live action of your automatic GDO would usually be too far delayed and not only would you, not see the child in time, but would not be able to react and send a successful GDO stop signal through all the cloud proxies and bridges to stop the door in time. With al the delays of this idea you will not be able to respond with enough speed to prevent anything. Mechanisms have to be in place on site. If people are concerned about the lawyers getting rich with their "could" and "should" and "possibility" they could install a multitude of beams and/or a grid pattern beam detections system which are available from some of security type paranoia generator/dealers. Uncheck the "trigger reverse" option and re-write your program to handle the logic indicating your door is in the opposite position, as before. Changing the sensor accomplishes nothing except you may not have to relabel your sensing point name in ISY, as GDO.closed to GDO.open, or vice versa.

Either Samsung is a really popular TV or there is something being radiated from samsung TVs

Shouldn't be a problem but you will not be able to handle the new feature based program lines you will have instigated. It will take a while to get using some of the v5 features but I would never go back now. Get the absolute value in the middle of a program Repeat While $variable < 0 . . $variable *= -1

I just went through it all a few weeks ago OK. I did have trouble with my PayPal password and it locked me out though.

If nothing in ISY changes then no user programs or logic statements are processed. It's an event based processing engine.

The variable also needs to change to cause ISY to re-evaluate whether true or false but I don't know how ISY would slip by a variable change without triggering the re-evaluation in the case of a folder condition.

Nice! Sitting here in Haliburton with a net over my head getting eaten alive by mosquitos by the campfire.

Spectrum analyser? Ouch! I was just going to mention that an RMS voltmeter may not be showing the whole voltage glitch picture but spectrum analyser? I'll retract any thoughts I had there. I think many are finding these thermostat companies are getting computer companies to attempt to build these designs. If the high-tech is stable then the concept an user interface is a POS. They all seem to have problems and those problems rear their ugly heads in only certain applications while others have no perceived problems at all. I have a Venstar with lots of deficiencies and was going to go to the ecobee3 but now I read the A/C relay contact overheats the stats raising sensed temperature up 6-10 degrees. Factory solution? Install an interposing relay between the stat and contactor. We would be better with one unit with three bimetal contacts and a separate logic somewhere else to select between them. No heat in the stat to make the sensing wander and a stable CPU to interface to the rest of the world.

It sure would have been nice to know which one to install. I spent a fair bit of time wondering why the instructions didn't work after I installed "the app". With a label including the "Smart Home" name it really confused me. When did UDI become "Smart Home"?

You took the words right out of my mouth.The last order I attempted to purchase with x10.com, I was so frustrated with 100s of pop-ups I told them I would never deal with them again. And I didn't. The whole Insteon appears to be based on X10 for concepts, silly algorithms, spam techniques, poor QC, and not understanding what they are doing. This scares me a lot even though I like their products mostly.

Thanks for the update Fred! Due to the Rh and Rc terminals connected together I assumed you were supplying the stat with 24vac. I had a stat like that way back and if the 24vac wasn't on the batteries would go dead every few months. The next thing, I would try, is a factory reset on the ioLink and then do an ISY restore on it to recover all the links back into it. Something is wrong with that ioLink as it acts like the Reverse option is on and this is a classic problem as you describe. BTW: Was that llama at the end of the street (StoneHouse) named after you?

See his screen shot that the Reversed option was not on. There may have been confusion there and he may have turned it off before the screenshot or possibly the options box did not update as some of mine have done until I clicked query. The symptoms fit the "Trigger Reverse" option nonsense it causes.

Thanks for chiming in here Brian. I was hoping. My concern is that 24vac control systems are usually common referenced to earth, and the internal circuits of the ioLink may also be. This puts live 24vac into the ioLink and/or may be causing some sensitive sensing jitter or component stress or burn out components. This would be mostly dependant on the internal coupling inside the ioLink. That is where your knowledge is usually invaluable.

I have never used the Auto function on a thermostat yet. The Heating and cooling would be coming on alternating style several times, every day, except in winter and a few days of the summer heat. I like my environment tightly controlled for comfort and that means a heat/cool differential of 0.5 degrees or less. The only solution I have seen for a thermostat being in Auto, is a huge delay between changing modes. To me this is the only algorithm that duplicates the human manual logic used, as closely as possible. Huge setpoint differences are not the answer and I may as well go back to cutting wood and throw another log or some coal on the fire to regulate my home temperature if a wide of temperatures is necessary. The wood or coal method would probably regulate temperatures more accurately. It would be very common to find my thermostat on with all the windows open to conserve energy in an attempt to lower the temperature before the stat cooling kicks in again. Thermal lag and thermal mass can sometimes be our enemy costly us energy to compensate for the combination. I hate sleeping in the heat and have paid dearly for it many times.

Add HA into the mix and a renegade app could activate a voice, to Alexa, to download more apps, or even tell other Alexii within hearing distance, to load another virus app. Oh Gawd! The beginning of Skynet!

OMG! We have the beginning of the first vocal viruses! "Alexa, install the virus"

Voltage indicators usually will not usually detect low voltages like 24vac on stats.

AFAIC I did not suggest a cure, maybe a temporary fix but not a real fix. From the OP I suspect the stat 24vac being connected to the live input of the ioLink, and both being ground referenced, then it may be bothering the ioLink causing it to act suspiciously. The ioLink wouldn't like that most likely. The 3:00 am, or any query, may report silly things and/or cause the problem to rear it's ugly head. The query is not the main problem, and the output not being programmed correctly probably isn't making a difference and may just be the ay it came from the factory. I am going to suggest to johnstonf that he see if his stat can run with the 24vac only connected to the Rc and C terminals and the IOLink connected to the Rh and W. If you have an ohmmeter check to see if the Rh and Rc are connected internally while the wires are off. Another suggestion is to factory reset the IOLink and do a restore and see what happens. Then check the options again and do a query while watching the options. IIRC I have seen options that not in synce with the devices. The whole thing wreaks of the "trigger reverse" being on and maybe not showing properly.

Are your fans actually turning off or is your ISY just reporting them as Off? You can try disabling your 3:00 am query program tonight, although tonight may be too cool to make it work and you will have to wait until Wednesday night.

Read post #2

At three AM you probably have an ISY query going on. I am also guessing that you have the option "Reverse status" enabled in your IOLink input. The Reverse option should have never been created. When you query an IOLInk it sends back the real "unreversed" status from the contacts. Later when it reports in the reversed option changes it back again. Remove the "Reverse" option and rewrite your program logic to match.

It is all possible in v5. I have several programs that use the capability to save and restore levels after "borrowing" lights for other purposes. This is useful for flashing light alarms.

Scenes are like presets on your car radio. You set them and then use them. You don't press two and try to get a station between them. I have about 6 difference scene levels for my Gathering Room lights. I don't need every percentage of level, or to adjust 15 lights each time. I have FullOn, Bright, Reading, TV, Movie, and Off. For all Alexa controls I operate programs, that operate scenes. For the Off scene I control a program using the Else section to operate the scene. I named the program All Lights. Alexa....turn off All Lights!