larryllix

As an afterthought v5 can assign variables the value of a thermostat mode and restore them after by assigning the mode the variable value. This could be used to memorise the stat mode, regardless of what mode is currently set, and restore it after the open door policy enforcement.

oooops...Not gonna' be that easy. If Status 'Doors and Windows / Door-Sliding' is On and Status "Air Conditioner' is Mode Cool <----the Mode was set = Off when the door opened. Then Set 'Air Conditioner' Mode - Off Else Set 'Air Conditioner' Mode - Cool The plot thickens with variables. It gets a little thicker, yet, once the compressor delay shows up. When will UDI inclement the "You know what I mean" program line? Probably not good to play with the Mode on the stat but rather just raise the temperature. Changing the mode raises all kinds of conditions like Home/Away, A/C was off in the first place due to spring or fall weather, and possibly a few more unseen conditions.

My wife says the same thing when I continuously clink the fork against the side of my plate or glass. I used the exact pattern sequence I taught her too. Somebody once told me, when a woman finds out they are not the only pebble on the beach they usually become a little bolder. Who wants a pet rock? ....."I don't understand what you just asked me" We are now entering dangerous ground. Please watch your step!

What was her head doing in the cloud anyway? Price of Dom Perignon predicted to increase by 300% this week.

OMG! You mean Alexa is a GMO product? It must be bad for us. Wait.....? !G.M.O.... O.M.G! Signal echo? Anybody succeed in changing their response phrase from Alexa? "Roxanne! Turn on your love lights tonight......". ... head in the cloud....

You are going to want to add some conditions to your program to stop the A/C from turning on in the winter when somebody closes the door. If you can control your stat you can likely read the stats of the heat/cool mode also. This will take two programs and no use of the Else clause though.

OK. What is "blah...blah...blah...", programmed to do though?

With an ISY I have never needed to press any link buttons, except for battery devices, to link them to ISY. Those instructions are for linking without an ISY as provided by SmartHome. Just supply the Insteon three byte address.

Does the camera app not use a common IP address/URL for the lot of the cameras? Should have been a change one IP Address:Port and done? Does each cam have a custom IP:Port that needed to be individually setup?

Same with the girls sometimes. Sometimes the dimbulbs are cheaper. Some of the brighter ones do cost more. Some are high maintenance. I picked up one with the rounder bottoms back in the early 70s and she still lights up well when I throw the stitch. Teken. Not nice to spit coffee on your keyboard.

Looks like you have it. We will be expecting big things from your kichen in the future!

Posts can be deleted easily.

As per Stu above and another way to look at is. Disable/Enable applies to triggers only, not the execution. Program 2 doesn't have any triggers and a disabled program is the place to use conditions when trigger interference is not desired in that program. This is commonly used for time frames and State variables when the trigger could upset a running program and they are only wanted for their filter condition value. Having said all that, if you disable a program while it is running it will stop it at the next Wait or Repeat line. Making sense?

I am convinced if all Cree bulb reviews were done after 6 months of ownership nobody would be buying them anymore. I have a about a dozen CREE bulbs and they were all great at the beginning. I have one dead one, two that flicker badly with dimming, one that doesn't match the rest in the chandelier now (dims on a different curve), a BR40 bulb$$$ that flick completely out, occasionally, now replaced with another brand., and a another PAR38 that just doesn't work occasionally. IMHO, CREE bulbs have the same problem the PLMs have, cheap filter capacitors on their power supplies. Works great until the receipt is thrown out. I guess I need to get my ship together and call them. I buy mostly the cheap brands now and have no problems but they are always rated "dimmable".

I apologise if this is not exactly what you are asking for without fully understanding your code. Use the "don't trigger me until I let you" approach. Program 1 [enabled] If whatever Then Run Program 2 (If) Else -- Program 2 [disabled] If non-triggerable conditions Then Disable program 1 Do something WAIT a long time, <---Program 1 can't touch us Do something else Enable Program 1 Else Do the negative conditions

The only thing I could think to make this happen is a burned out memory bit in the device in question. To prove this, you could try... -remove the device from the scene causing the problem. -create a new dummy scene -add the device in question into the dummy scene -add the device back into the scene in question -never use the dummy scene This may occupy the defective memory space in the device with the dummy scene link. Then the used scene would occupy a new byte or memory location. It would be worth the experiment and the warning that your device's eeprom memory is failing and shopping time.

There is nothing to trigger your program except the temperature changing. Something has to call the attention of the ISY engine and that would be a temperature change. Then your logic will be evaluated and run the appropriate Then or Else. IOW: If the temperature never changes after you save your program, or ISY boots up, your program will never run.

See Stu's answer above. However, ISY must see this change via all the mechanisms to get there and... ISY must not think the stat is in Off mode when it powers up or the first time the program will be triggered is when the stat sends something other than Off. Querying the stat does not trigger a program unless it causes something to change that is being used as a trigger in that program. If querying the stat causes a status change then ISY is out of sync due to nothing changed since it powered up or signals have been missed due to comm failures. Of course once ISY is up to speed and in sync with your stat then the program works just fine, with good comms. Querying the stat after ISY power up is a good idea to get sync'ed.

Again, if ISY does not see a mode change the program will never run. There is no trigger, without a working thermostat, with a working comm channe to ISY,l and an ISY that knows the thermostat was in the Heat mode in the first place. Simply put with one scenario: If you reboot your ISY and the stat is not in Heat mode the program will never run to see/change it. You also need some other triggers to initiate status testing or the program may never run. You can query the Insteon thermostats 100 times and the program will not run.

Back a few posts you stated "I reread your post... My ISY program isn't looking for a state change. It's looking for them to be specifically on heat mode and if not heat, then set heat." ...which contradicts the later statement you made "check for state changes". I just wanted make sure you understood how the triggers work, coming from a linear code life, and not familiar with event driven software, maybe? Drives some old programmers crazy at first. This only works if ISY sees a change in status, comms are good and working, and doesn't wake up with stat already in that mode. Something has to make your program run and depending on the trigger, you are monitoring for failure, to trigger the same signal you are monitoring may not be the best thing. For your purposes, right now, I understand this is only a watch and correct situation, software, and is working to identify some problem irritating you. Does your thermostats have an Idle mode or waiting mode, based on a short cycle elimination setting? My T7900 has a state called Lockout, a misnomer, but if the stat calls for heat and the cycle is too short it throws out a Lockout status instead of Heat until the timing allows a Heat call again. This can mess with Heat detection programs and I learned the hard way for a bit,

There may be some of the problem too. What causes your programs to check for a state change?

Have you consider what happens if the power fails to both stat and ISY? Stat wakes up and sets mode to Off. ISY wakes up and no status changes from anything it is aware of = no need to change anything. ...ooops. Ice Age.

The two ISY thing is on the slate for UDI in the future IIRC. Something I thought while out blowing snow... Maybe your thermostats are set to off initially as they boot up and then reset themselves to the last known mode (Heat). Maye a longer Wait before sampling the mode again may yield some different results. Perhaps just a series of notifications based on mode changes to monitor what the stats do in the few say...10 minutes or so. But I realise you have been in logical processes for years and probably have already thought of that idea.....maybe? AS an aside. While I was away for months last year my stats were all set at 10 degrees C (50F) and that worked until I was on a cruise in the Carribe and my house temp started to rise back to normal living temps. I got notifications from ISY etc... but could not do anything about it. After some long logical sleuthing I figured out these $3-4K worth of thermostats set themselves back to Home mode after a power failure. This would similar to what you are experiencing and a good lesson to us all to test out smart stats to see what they do after a power failure. How stupid can these companies be. We buy basic electronics for high prices to monitor and keep our houses at a set temperature. So much emphasis is put on smart, communication, schedules, phoney money saving schemes and yet they can't remember what they were doing after a power failure.....duh! I am hearing about people with the Nests cannot block firmware upgrades and some fail locking the stat off. There's the poor bast... has all the bells and whistles and can't control the thing when actually needed. *SIGH*. mwester is right on about this. Makes me laugh about the old trick I heard in a Fla hot tub one night, is the thermostat trick. You take an old mechanical thermostat and put a resistor in series with it across your Mountain summer resort phone line. Every couple of days, you call the phone and if it rings...heat is OK. If the line is busy, your thermostat has closed it's contacts, and you need to call a service person.

I have a gas oven that depends on some high-tech electronics to control the gas valve. I have a tankless NG water heater that depends on more high-tech electronics than any Insteon thermostat I don't want to come home to a block of bits and pieces where my house was previously. In reality this is not likely to happen and either is his house freezing, like the staged, exaggeration scenario picture, he linked to. If he lived above the Arctic Circle I could see worrying about it happening. Not likely where he is unless he is absent for the whole winter without somebody performing the necessary insurance check every few days. The OP has been given a good backup safeguards by yourself . His OP and main concern, here, is how to trust the ISY equipment he has. Even if he installed a mechanical thermostat his high-tech high-efficiency furnace ignitor could fail and his house get really cold. More high tech dependency? It isn't going away in your manual shifted car. Should he now get a wood stove that he can depend on? Maybe the answer is to monitor the easy fail equipment with more equipment. Maybe he should purchase a HA box to send him notifications, if this happens so he can rush home or call a neighbour to investigate. ohhhh.wait.....! He already has an ISY. However, it sounds like the Insteon thermostats are too junky to depend on, for me too. Four separate heating systems may help but restoring from a power outage on Off setting is unforgiveable. Need ISY notifications working. Power outages are hard to handle but the POCO knows your house isn't going to freeze 'cause you won't let it. Ask the St. Lawrence River survivors without electricity for 3-4 weeks. The military boys ate a lot of surplus steaks on the BBQ, though.

See post 21