MikeB

Glad to hear, can't wait to try it out. It's only happened 2 or 3 times for me, so it has been very infrequent and not reproducable.

Can't we telnet over IP?

I had this issue with a previous update, but after a period of time the new version kicked in. When I had the issue, I believe closing and re-starting IE brought the new version in. Since you've rebooted already, I would try clearing out your internet temporary files to see if that helps. The HELP, ABOUT shows the correct version because it's querying the device itself. The problem is that IE has cached the old interface program and that's what you're seeing. IE hasn't gotten the updated interface from the ISY-26 yet.

I think he wants a scenario where, say, his security system alarm goes off for some reason. When it does, the ISY-26 would turn on all lights in the home. Once the alarm is de-activated, he wants the lights to turn back to their previous states (not all off).

Hey Chris - For the record, per my emails to you I've seen a 00:00:00 bug as well. However, I'm not referencing any programs within my programs. Different issue? Thanks

My PLM is definitely FIRM52, and my X10 definitely died for a period of time. Is this OK to use with the ISY-26?

The PLM on my ISY-26 is labeled: 2807Rev2.4 FIRM52 I thought the 4A firmware was only for separate sale/use, not with the ISY-26? Did the ISY-26 ever ship with 4A PLMs?

Funny - I just read this post and went to try your suggestion, and X10 is currently working. Any idea if this is a known issue SmartHome is working on? Do you suggest I swap out my PLM? Should I wait for a newer rev? Thanks

I don't believe I am experiencing any kind of signal strength issues. Hey Chris - I tested by plugging an IR bridge into the same outlet as the PLM. When sending an X10 signal, the PLM flashes, but the ISY-26 does not. Please let me know if there's anything I can try here, or do you think I may have a bad PLM? Thanks

OK... this is weird. After days of X10 working flawlessly, my ISY-26 is suddently not getting any X10 signals. I noticed it first with the RF remotes and motion sensor. I also tried plugging in my IR bridge right at the PLM and using the hard buttons to send X10 signals to the PLM/ISY-26 and the triggers aren't running at all. Almost like some portion of the ISY-26 or PLM is simply dead and not receiving the X10 signals. I've powered off and back on all devices, with the same results. Any suggestions??

I've had no LampLinc, ApplianceLincs, or Icon Lamp/Appliance Modules go bad...

I think either is fine. If it saves some memory in the ISY-26, I would certainly go with Program A. Or, maybe something like this would be a bit easier to read: If ( X10 'A.1.3(On)' is Received Or X10 'A.2.3(On)' is Received Or Control 'Keypad' is switched On ) And X10 A.1.11(Off) is not Received And X10 A.2.11(Off) is not Received And Control 'Keypad' is not switched Fast On Then Send X10 'C.4.3(On)' Set '0A.B9.44.1' On Else Set '0A.B9.44.1' Off Send X10 'C.4.11(Off)'

I don't have a 'vacation' button setup, though it's in my plans. What about that other vacation button thread? Where it was suggested to create a folder and use 'CONTROL' to determine whether or not the contained programs run? Could he eliminate the 'away' check in this program, and put it in the folder instead? And have the program itself simply check the time?

Maybe I'm wrong, but wouldn't that program require you to PRESS that KPL button at PRECISELY 3:39:00pm?

Thanks for the explanation. I'll stick with sending the level to each individual switch.

I'd like to setup a trigger that dims an entire scene (basically a 3-way circuit) to a particular level, but the only options seem to be ON or OFF. Is there a way around this, or do I need to dim each switch individually in the action? Thanks!!

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!