paulbates

You are on the right track. What you need to do is add a program that sends any temperature change to a variable. This program will run independently and capture every change in temp immeadiately and send it to a variable, so you can compare it in your original program Pick one of the 2 devices. Let's use the thermostat current temperature reading Create a State Variable in the Variables tab. Call it Room_Temp_Hold (or whatever you like) Create another program that will capture any changes in temp, when it happens, and send it to that variable. As an example, this is mine for my outside temperature HVAC Outside Temp to Variable - [ID 006F][Parent 0017] If 'HVAC / Outside Deck' Temperature < 150° Then $HVAC_Outside_Temp = 'HVAC / Outside Deck' Temperature ° Else - No Actions - (To add one, press 'Action') Out side temp is used for a number of HVAC purposes. The outdoor Venstar wifi temperature sensor is located on the deck, under the decking table near the grill. This program insures that the outside temp is populated to a variable so it can be compared in programs that need it. Each time the outside temp changes 1 degree, this program is called and updates the variable. To change my program for your use: Where I have Outside Deck, you put the node for your thermostat temperature read point Where I have $HVAC_Outside_Temp, you put the name of the variable you created in the first step above The 150° just provides a value that can never be reached... it makes sure the program captures every 1 degree change in the variable, right when it happens Then, for your original program, do this: IF thermostat setpoint is < than $Room_Temp_Hold THEN turn something on (like the insteon 2450) ELSE turn that same thing off That should do it. Note that the first program only runs on changes from the thermostat. That's important because you'll have to wait for the first temperature change from the thermostat for a valid value to show up and the new program to run for the first time. This will be true every time your ISY reboots (eg power blip). There's a way to address this with the ISY's variable Init function, or by running the first programs "then" in an ISY startup program. But I've never found it to be a problem. Paul

There’s an option on the Configuration tab: - Catch up schedules at restart -check box - Missed schedule grace period in minutes and seconds. you can ask the ISY to travel back in time as far as the value that you set , at restart i’ve not used that. I try to make my programs as resilient as possible paul

Have you tried factory resetting followed by a restore device? Paul

This spacing is sometimes needed because X10 and Insteon share a very close powerline frequency for signaling which interferes with each other. When Car Remote.b is sent, there is likely an Insteon acknowledgement(s) sent in response. The ISY doesn't know this and will send the X10 A15 right away and it will collide with the Insteon acknowledgement (or Insteon re-stransmissions). X10 does not have message resilience built in, so the send A15 is "stepped on". The Wait command accounts for that in this case, the OP has a program waiting for an inbound X10 signal. There'll be no related Insteon traffic at that time Paul

Michael, Its Echo specific. Rob, take a look at this thread. You may have to search around more in the portal section of the forum Paul

Les For the programs that are not reading the sensor, I'd suggest taking out the from / to range. These 2 programs don't need that: Turn on at sunset: Have a program check for sunset only , turn on 30% After 11pm: Have program check for 11:10 pm only, turn off Paul

Les The UM506 universal module is for controlling a device with contact closure when you send it an X10 HC/UC. The PF284 (PSC01) X10 Powerflash Interface is used to remotely detect contact closure and send an X10 HC/UC on the powerline (The ISY can communicate with X10 without the add on module. The add on module lets you name HC/UC combinations) Paul

Assuming this is the eagle eye / ms16a motion detector? Given my experience with X10 RF, the problem is usually there somewhere: Are you able to watch the ISY event viewer, while having someone trip the hawkeye in its installed position and see the A5 / On entry? I would look at the positioning of the X10 RF transceiver you're using to get the X10 RF on to the powerline. That can be tricky because most of them need to be close to the hawkeye, but also in a good position on the powerline so that the PLM can communicate with it. Paul

Delete it from the problematic scene, then re-add it. Test again Paul

Steve I believe that’s the definition of the Insteon device with the address 1B2299. If the admin console still works, go to main, sort the colum by Insteon address to see what it is. If you can, see what scenes and programs it’s in and make a note. Try to delete it... maybe that gets you a back up, and you have to fix one device only. Definitely move to a new card. Try the copy if that won’t work, same downside, the ISY will forget the device at that address. Sometimes I’ve been able to reinstall a device that was deleted and scenes/programs come back hopefully one of theses gets you going with minimal fixes.. Paul

Any chance the battery is older and down on charge, but not to the sensor's battery warning level? My experience with other insteon wireless devices is that they do unexpected things when battery is close to low, and before the low battery sensor tripped. Also, considering what time of year it is, any chance that this sensor is close to the outside and maybe exposed to cold? Cold can effect battery charge. I agree with your split program approach if program runs longer and the sensor sends back an off before its done. Paul

Steve: Unfortunately if there were changes between your last good backup and now, then yes... you would lose those changes. I'm kind of in the same boat, in that my ISY is sneaking up on 5 years and I'm wanting to put a new SD card in it. I've wondered if the old card image could be drug across to the new... : Insert the old card into the SD slot of a PC. "Drag" a copy the contents off of the old card on to the PC in a folder Following step 2 of the wiki, format the new card: Turn off the ISY and put the new card in the ISY, restart it Telnet in to the the ISY and issue an FS on the new card in the ISY Replace the old card with new card in the reader on the PC and copy that image on to the new card Insert that in the ISY, and see what happens You could try that experiment, worst case you still have the old card. Paul

Yes its warranty time. I've seen some functions start failing while others continue working. Paul

Read this and see if the conditions line up with your symptoms. If so consider replacing. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card It might be the file, let's see if there is additional feed back. Paul

How old is your ISY / SD card? That error is -110014 SD DRIVE CONFIG READ FAILED Either the file is corrupt, or the SD card has at least one bad spot on it Paul

It sounds like you followed the procedure, but lets make sure You installed the new 2475DA1 on the ISY and its in the root Main/device folder.. not in a subfolder? You right-clicked on the current 2475D, and selected "remove from folder"? You right-clicked on the 2475D and selected "replace with"? Did any devices show up? When I do the above, I see my other dimming inlinelincs, insteon light bulb and lamplincs as replacement candidates Paul

There's nothing wrong with that. If the keypad will be providing the power through its red lead, which I believe is your intention, then it is a requirement that the keypad be the On/Off version... and not a dimmer Paul

If you want to be sure before you order, take the cover off, and use a short piece of wire across the contacts, it should activate the door. That simulates what the iolinc will do.

Its been 8 years since I set it up, but it looks remarkably like mine. I remember attaching the iolinc's relay here, where it says "terminal screws": My garage had a 3 gang outlet right near there so the iolinc could be plugged in, wired to the nearby door control and I installed the magnetic sensors nearby. Paul

I had to do a double-take.. is that a craftsman? If yes, I have that one. I attached the IOlinc relay (NO & Comm terminals) across the screws on the back of the manual door control... the big button you hit manually to activate the door. Paul

Yes. I was able to wire the IOlincs relay across the contacts to the door control in the garage and was able to mount the sensor near by. We use the openers wireless remotes in our cars normally. The contacts "click" the door control as if you were pressing it manually (see note below). The sensors read and report if the door is in position. For me, that's "down". If its not down, a keypad key lights up... if it is down, its off. As a note, some door controllers do not have easily accessible contact only sensors any longer. You will want to check the manual, or post a link to the pdf for the doors manual and i'll take a look Paul

I use those on doors and windows and they work great. I typically see more than a year on battery life, but that depends how much the door / window is opened or closed. Temps: Though not these specifically, I use other insteon devices and battery wireless sensors outside in Michigan year round. They've seen -20F in the past. Based on that experience I would deploy these in the cold. This next week will potentially be a change to set that bar lower... Installation: I use the iolinc with magnetic sensors designed for a garage setup. For this application, the sensor unit can take quite a beating and sometimes the mounting locations are not ideal. I would still use the iolinc if starting over today. The iolinc is single band, however I've had mine in my garage since 2011 along with a keypad key that lights up when the door is open, and pressing the keypad key operates the door. Paul

If the functions you're looking to implement are even remotely security related, I would suggest ELK for that reason. Nothing wrong with the EZIO, but it would yet another technical solution to learn and support, when it sounds like you already have ELK Paul

Look at the nodelink list of other supported devices... there’s close to 20

To install nodelink on a pi, there is a script from ioguy, author of Nodelink To set it up, you then browse to your pi's ip address @ port 8090 example http://192.168.xxx.xxx:8090/index.htm Configure your ISYs account and pw under System config On the Devices tab, add "Additional ISY Data" You should see these values in your ISY, nodelink keeps them up to date If this didn't show up in your ISY, press Install Nodes from the new page/tab for Additional ISY Data that will appear in Nodelink's configuration page You can use any of these in your program's ifs or assign to variables. I use this at Christmas time to keep certain lights on between December 22 and 27... I don't care what year it is. Its called from another program and controls a particular scene that keeps the inside and outside decorations lit around Christmas: Lights and Lamps off Xmas - [ID 004A][Parent 0006][Not Enabled] If 'Zystem / isydata' Month = December And 'Zystem / isydata' Day of Month >= 24 And 'Zystem / isydata' Day of Month <= 27 Then Set 'Yard / Yard and Lamp Security / Yard light and lamps off - xm' Off Stop program 'Lights and Lamps Off' Else - No Actions - (To add one, press 'Action') Other examples odd and even days can be helpful for sprinkler system programs if your community enforces that. I have programs that prevent / allow operation based on what month it is... I don't want the attic fan/dampers to open in the winter. I control the humidity level in the house, but only during winter months, I prevent the program from running outside of that. You can do things like that. Paul