MikeB

Hey Joe - It's too bad that you purchased the ISY thinking it was something it was not, but I've never heard anyone from UDI ever say they would implement anything but the most basic X10 support. Their product description page doesn't even mention X10. Where exactly did you read about the ISY's X10 support? It sounds like you didn't do your research before purchasing. If you had read anything regarding the ISY-26 and X10, you would have understood that minimal X10 support was added only as an afterthought. I can understand how you would want additional X10 features, but the majority of ISY-26 users are Insteon users who maybe have a few X10 devices left kicking around (like me) - if they have any X10 at all. I would personally rather see UDI focus on adding forward-looking features rather than additional support for a technology most people are looking to replace anyway. That being said, make sure you fully understand how the ISY and its X10 features operate before giving up - it's very possible that you can do what you need.

When I ordered my ISY, SmartHome's web site showed out of stock - but Michel knew and told me that they had some there. It shipped promptly. If Michel says they're there, then I'd say they're there.

Hey Mike - I (and Mark apparently) have been having some oddball KPL programming issues, which might be related to your problem. Almost seems that links to KPLs are getting created/deleted when they shouldn't be, at least on my system. Here's a link to the topic I started: http://forum.universal-devices.com/view ... =3924#3924

Keep in mind that there are plenty of RF and hardwired IR extenders out there as well. You could use one of those products to get an IR receiver in every room of your house, all pointing back to your ISY-99.9 wherever you put it. That's my intention.

Maybe someone else can chime in, but I believe this is incorrect. I don't think there's an issue with the ISY knowing the status of a KPL load button (unless something is wrong). You cannot, however, control a secondary KPL button from within the ISY unless it is a member of a scene. You must make it a member of a scene, and control the scene instead. However, now that I'm creating more complex ISY programs that depend on the ISY knowing the status of many switches accurately, I have been having issues where I'm finding switches that are not correctly getting their status updated (plus other random KPL programming issues that I suspect are somehow related). In general, my solution has been to remove the device from the ISY, factory reset it, and re-add it. Not a good way to troubleshoot, but it seems to get the job done when I need a quick fix. My guess is that if you had removed the KPL from the ISY, re-added it and recreated your links it would have started reporting its status. All that being said, I don't have any KPL loads that aren't members of scenes, so someone please correct me if I'm wrong.

Sorry, there was a bug in my original message. The button is in TOGGLE mode. This code seems to be working well for me.

Hey Mike. Bigger monitor? The ISY has a "Floor Plan" feature which lets you create graphical "locations" and drag/drop your lights into it. This might help, but if I remember correctly Michel said they would be dropping that function in a future release because no one was using it. I was actually surprised to see it in the latest firmware, but it is still there. Maybe that function would help you. In the ISY-26, scenes = groups. You can turn a scene on or off, but the ISY-26 does not keep its current status. Some people create programs to keep it's status (eg. if light1=on & light2=on then the program is true).

Hey Mike - There is a page (My Lighting) that lists all devices, their status, their address, and the address type. It's not a graphical representation, but a list. There isn't a page to show the status of a scene, because the ISY-26 doesn't track the status of a scene. Though, you can create a program to do that.

Hey - My understanding is that this is now working. I have a long laundry list of stuff to work on over the next couple weeks, so I don't think I'd be able to test this for a while. I'm sure by then someone else will have already confirmed. But, again, my understanding is that this now works.

That's a really good idea... thanks for sharing! The only downside I could see is that with FAST ON, it will ignore the set ramp rate. So, if you prefer a smooth ramp up, you'll miss out on that.

I'd create a separate scene...

Some kind of communication issue. Test it a bunch of times - "on, off, on, off"... see if you can get it to go out of sync.

That's an interesting one! You should swap the CFLs around if possible to see if the problem follows the CFL or stays with the LampLinc. What brand are they? I did notice something similar a couple times in one of my bathrooms. I haven't seen it in a long time, but I no longer have CFLs in there (I didn't keep them there for long). It happened when I manually controlled the switch (a SwitchLinc V2 Dimmer). They were probably Honeywells. I haven't noticed an issue anywhere else in my house. I have a few locations with Honeywell and Sylvania CFLs.

Ahhh, I see - thanks. So, is this a known issue with the KPL v1.5? If you need any info from me on it, let me know...

Hey guys - Has anyone installed a KeypadLinc v1.5 yet? I usually add devices to my ISY-26 via the 'New Insteon Device' option, and simply type the address. I just installed a new KeypadLinc v1.5, and despite trying several times, the ISY-26 kept coming back with a 'Request Failed' error. I almost gave up, but I tried the 'Start Linking' option instead, and the KPL added fine to the ISY-26. I went ahead and created all my links, and other than the initial discovery it seems to be working great. Any ideas?

I still have this program called "Schedule 1" that at 3:00am runs "Set Scene 'My Lighting' null". I thought this was a nightly poll, but I'm not certain... Can this be deleted? What is its purpose? Thanks!!

For the record - I just created this program here as a test, and it seems to be responding correctly.

Release candidate for 2.5 is out now anyway... this issue should be fixed.

Sorry for the delay in getting back to you. You're correct - when I click those buttons, it does fill in the status on the ISY. Doh!

If you swap your PLM, be sure to reboot your ISY and do a "restore modem (plm)" to recreate links on your new PLM. When you add a device to the ISY, it creates a link on the PLM so it will be notified of any switch presses (which will allow you to create your triggers). If the PLM is replaced, the new one won't have any of those links (until you run a "restore modem (plm".

Great topic! I started off using my ISY-26 for some basic tasks, but lately I've been giving it a bit more work to do. Currently, it does the following for me: - use it to manage/link all my Insteon devices - turn my front door lights on at sunset, then back off later in the evening - turn on my inside and outdoor holiday lighting at sunset, then back off later in the evening - translates my X10 keychain remote to turn on my driveway & front door lights from the car - translates my X10 motion sensor to turn on my driveway lights when motion is detected at night, then turn them back off 5 mins later - allows me to double-tap certain light switches to turn on or off entire rooms (bathrooms, etc.) - sets lighting scenes in rooms via KPL secondaries, and keeps the LED lit unless the lighting changes (see: http://forum.universal-devices.com/view ... highlight= ) - turns off entire floors via KPL secondaries, and lights the LED if a light on that floor is on (see: http://forum.universal-devices.com/view ... highlight= )

I agree... not showing a current status on the ISY was simply a symptom of the actual problem he found - that his program wouldn't respond to a control when he pressed the remote button.

There hasn't been much public info on the IR yet, but I'm fairly certain you would send a single IR command that would trigger a scene on the ISY.

Hey Michel - I'm seeing the same thing here. On one of my RemoteLincs, I've created links in the ISY for 4 of the buttons. Those show a status in the ISY interface (ON or OFF). The other 2 buttons, however, do not show any status in the ISY interface.

Try plugging it into your router.