MikeB

I agree. When people were requesting X10 support, I thought it was a waste of time. Now that it's implemented I think it's great.

More praise for the ISY-26. I had given up on X10 with my system a while back. Powerline signals were weak, and I didn't want to spend money on boosters for something I hoped to eventually replace with Insteon anyway (once Insteon-compatible equivelants are available). I had tried adding X10 back into my system, but was bouncing around between different automation software packages at the time. Some supported it better than others, some were a hassle, some wouldn't allow the control of KeypadLinc secondary buttons (without odd workarounds), etc... The latest firmware on the ISY-26 adds basic X10 functionality. At first I wasn't interested, but then figured I'd give it a shot. I've decided to limit myself to RF devices (which is pretty much all I need anyway), to avoid powerline issues. I had a WGL V572A kicking around (as pictured in this package: http://www.smarthome.com/1135k.html ). I plugged it in to an outlet very close (on the same circuit) to the ISY-26/PLM, and created some triggers. I've been testing it for a while now with - - an X10 IR bridge (powerline, but just for testing) - an X10 PalmPad remote - an X10 SlimFire keychain remote ... and it's been working great. Flawlessly, actually. I now have the ability to use my old X10 keychain remotes to turn on my outdoor lights (front door, driveway, etc.) from my car. I was using my RemoteLinc, but the X10 keychain remote is much more convenient in the car. I get almost 300 feet of range with the standard whip antenna from the V572A mounted up in my attic. 300 feet is pretty much the end of my driveway, no obstructions (other than the attic roof). I'm able to trigger either specific Insteon devices, or entire scenes (for example my driveway lights, which include a bunch of KeypadLinc secondary buttons). I also plan on experimenting with some X10 motion sensors, but I don't currently own any.

Wow, this actually has me pumped. I had pretty much given up on X10 stuff in my home. I plugged my V572A in to a plug close to the ISY-26, setup a couple of test triggers, and it's working great! I also plugged in my X10 IR bridge to a different outlet, and it tests great as well. This opens up a whole world of inexpensive X10 RF devices I could use. I now have use of my X10 keychain controls & palm pads again, and can start experimenting with X10 motions! However - I want to put it on record here that I vow not to go down the bumpy road of X10 powerline devices. I don't have energy or desire to deal with any issues that crop up. I vow to only use RF! Probably. Maybe.

I don't believe this can be done through the ISY-26.

With X10 support now in the ISY-26, I'm considering introducing X10 back into my system - strictly for X10 RF devices. I currently have a V572A X10 transceiver (http://www.wgldesigns.com/v572.html) kicking around that I could use. One thing I'm not up for is troubleshooting and spending money to get my X10 powerline strength up to par. Am I correct in thinking that if I plug the V572A into the same outlet box as my PLM, that X10 powerline strength shouldn't be an issue? Since it will be so close on the powerline? What is everyone else doing? Thanks!

Just a follow-up to this mini review. I've been using my ISY-26 full-time since this original post, and have moved it to a more permanent location in my basement, mounted on my equipment panel. I'm now running firmware release 2.4.9. This is currently beta, but very solid so I'm sure we'll be seeing 2.5.0 soon. With this new firmware, far more advanced triggers and events are possible. I've added: - Timers turn off my closet lights after 10 mins in case they are accidentally left on. - Timers to turn off my bathroom vents & lights after 30/60 mins in case they are accidentally left on. - Fast On triggers that will turn on an entire room or area when needed. - Fast Off triggers that will turn off an entire room or area when needed. My uses are actually pretty basic. Far more sophisticated things are possible. For example, groups of triggers that only run when you are home/away/on vacation etc., triggered by maybe a KeypadLinc button. MANY more sophisticated triggers & events are possible. I have also purchased an Elk M1, which the ISY-26 integrates with. I'm hoping to install my M1 sometime in the next few weeks. I'll be sure to report back when I do. Above and beyond additional features, the firmware updates since my original post have fixed certain issues/annoyances. - RemoteLincs are programmed more efficiently - Interface colors have been improved - Haven't seen any Java errors - No PLM lockups during normal use Overall, the device has been fantastic. Absolutely no complaints about this device. What impresses me most about Universal Devices is that they continue to perfect the ISY-26. Instead of leaving it as a very good product and moving on to their next project, they seem to strive for perfection by continuing to make the ISY-26 better and better.

This seems to be fixed in the latest beta. Thanks!!

Glad it made sense to you, because it had me going bonkers. Thanks Chris!

OK, I've got something odd going on here. In a few rooms/areas of my house, I'm using double-taps (FAST ON/FAST OFF) to turn on entire rooms. For example, in my bathrooms, if I double-tap on my main light switch (FAST ON), I have it turn on a BATHROOM ALL scene, which includes the main bathroom light, the bathroom vent, and the mirror lights. When I double-tap the main switch off (FAST OFF), the ISY-26 turns off the BATHROOM ALL scene. I created these under 2.4.8, and they all seemed to be working fine. Under 2.4.9 I'm noticing one room that is not working correctly. The only thing different about this room is that I have a virtual 3-way circuit with 2 switches controlling the main lights. This means that I want double-taps on either of those 2 switches to control the entire scene. So, here goes: I have a scene called THEATERALL that contains TheaterTable, TheaterMain1, and TheaterMain2. TheaterMain1 and TheaterMain2 are also members of the scene THEATERMAIN (a virtual 3-way circuit). I have a trigger called THEATERALLON that runs as follows: If Control 'TheaterMain1'is Fast On Or Control 'TheaterMain2'is Fast On Then Set Scene 'TheaterAll' On Finally - No Actions - (To add one, press 'Action') I also have a trigger called THEATERALLOFF that runs as follows: If Control 'TheaterMain1'is Fast Off Or Control 'TheaterMain2'is Fast Off Then Set Scene 'TheaterAll' Off Finally - No Actions - (To add one, press 'Action') This basically works the same as my bathroom triggers, except for the OR statement under IF, because I want this to work from either TheaterMain1 or TheaterMain2. This seemed to be working fine under 2.4.8, didn't notice any issues, nor get any complaints. Under 2.4.9 I have odd things happening. For example, if I double-tap TheaterMain2 on, all lights go on as expected. But, if I go up to TheaterMain1 and then try to turn the light off, it goes back on. If I look at the ISY-26, it runs the trigger THEATERALLON which makes the light go back on. For the life of me, I can't figure out why it's executing that trigger. I have other odd things happening, times when I go to turn the switch on but it jumps back to off. Times when I double-tap them all on, but they go off for a second, then jump back to on. Again - this seemed to be working fine under 2.4.8, so I'm not sure what it could be - but it's very reproduceable. If I disable these 2 triggers, the lights function fine on their own. Hopefully this makes sense to someone.. Thanks!

Looks good here opened in Word 2007. I believe it's an XML file.

- triggers based on FAST OFFs from relay switches are now possible - "New Folder" button in the Program Details tab now creates a correctly named folder - Insteon addresses now showing in the Device View This is all I've been able to test so far. I've got something odd going on with a room when the ISY-26 is plugged in, but I'm going to recreate my programs related to that room, restore the devices, and test a bit more before I jump to conclusions.

Very odd. After closing all my Internet Explorer windows, and then re-opening the ISY-26 interface, I saw all the changes. Almost as if my IE was still running a cached 2.4.8 - even though the ABOUT screen showed 2.4.9. Weird.

Can you tell me what differences you are seeing?

Let the Techmall posts begin.

I installed this updated, but am not seeing any changes. Specifically I checked and: - Still can’t trigger FAST ON / FAST OFFs from relays - ‘New Folder’ still creates a folder called ‘New Program’ - Insteon address is not showing in the Device View My ABOUT screen is showing 2.4.9. Anyone else seeing this?

I went ahead and installed the 2.4.9 update. Unfortunately, I did add a few devices and create a new scene or 2 with the 2.4.8 firmware, but I no longer have a pre-2.4.8 backup. Thinks seem OK after the update. What problems should I be looking out for?

How do you configure a static IP on the ISY-26?

On a side note, I'm a fan of setting my devices to static IPs whenever possible. Any drawbacks to setting the ISY-26 to a static IP? Is there a set of instructions anywhere? Thanks!

Someone from UD will chime in I'm sure, but I imagine if you manually set the IP address of the ISY-26, you could use a crossover cable to configure it from your PC. Seems like a big hassle, especially when routers are so cheap nowadays. Any reason you don't have a router?

Hey Mark - Just a note. I had my triggers setup the same way, but recently switched to STATUS instead of CONTROL because if the switch is turned off by something other than the switch itself (like another trigger, or another switch in the house), this timer will continue to run. Something to think about.

Maybe I'm missing something, but if the event is detecting that you are turning the switch on with this line: Why are you having the ISY-26 turn it on again with this line: Wouldn't the switch already be on??

Might want to reset the device or try to manually get that button out of toggle mode. Which reminds me - I'd still like the ability to change the toggle mode on the load buttons of a KPL when in 6-button mode. With the current firmware, this has to be done manually at the switch.

Haven't seen any communications issues, but my Insteon install has always been very reliable. My events have been running fine since this, but I'm still curious what could have caused this. I'll report back if I have any missed events in the future.

I've confirmed this as well - good find Mark! If I double-tap off a switch once, the ISY-26 will not recognize a 2nd double-tap off unless something else is done from that switch first. Can this be fixed?

Right, my concern was if someone turned the vent on and it turned off unexpectedly. That's what my code looks like now, except I'm using 'control'. I'll try 'status' instead. Thanks!!