larryllix

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.

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!