paulbates

I've had good luck with PLMs as well. If starting over in a new house and using Insteon, the I would do these things Have a whole house power conditioner installed in the panel. They cost ~$125 + installation. I would do this with any PLC technology; its an insurance policy for any/all electronics. If you can find one, also install a phase coupler. The Insteon signalinc wired coupler is no longer available, but this is the one I would pick today I agree that a lot of people have reported problems in "the thread" and that there have been regular requests for help here that get debugged as a broken plm. At the same time, there are people that don't have problems, and chances are that they don't report in that they are working. We don't have real stats on the members that don't have problems or the percentage of each. Paul

Glad you made progress. Its one of those things that it can be hard to achieve, but once you get past it you can forget about it and it just works. I followed generic directions similar to what io_guy posted above, but they were specifically for the pi. I've had nodelink for a while, preceding his "all in one" script. At that time I hunted around the forums and Rpi docs and worked it out that way. This one took me a little time because I'm not experienced at linux either, just enough for basic administration tasks. Paul

Hi Dave There's 2 methods on the linking menu to add devices Start Linking - where you tell the admin console to wait for insteon devices to be locally put in set mode Add New Insteon Device - where you type in the Insteon Address to start the linking conversation from the ISY Whichever one you tried, try the other one and see what happens Paul

It looks like these last parts didn't take: ### Creating directory mkdir: cannot create directory ‘/home/pi’: Permission denied bash: line 31: cd: /home/pi/node: No such file or directory Your user account doesn't have the rights to create the directory to put Nodelink in as specified by the script. Create another directory where you'd like to put Nodelink, with an account that has the right privileges ### Downloading NodeLink /home/pi/node/NodeLink.exe: No such file or directory Since the directory couldn't be created, nodelink can't be downloaded to it. This command should do it, when executed from the directory you intend to put nodelink in: wget http://automationshack.com/Files/NodeLink.exe ### Modifying startup script sed: can't read /etc/rc.local: No such file or directory sed: can't read /etc/rc.local: No such file or directory This is where the script sets up nodelink to start when linux does. This will be dependent on your version of Linux, and the directory where you downloaded NodeLink.exe. Also, if you use sysctl, etc. I don't know this so don't have specific advice on how to complete it. Paul

It will be a little slower, but you can force access via SSL, get into the console that way, and set the port back Add an entry to your same IP address, with :443 at the end: Once you get in, go to configuration and return your http:// port back to 80. Your ISY will appear in the finder once again and you can delete the manual entry in the finder Paul

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