MikeB

I haven't used an IRLinc in a while, so I just tried it out here. It's a newer IRLinc (with credit card remote). I plugged it in, then on the ISY Admin Console clicked LINK MANAGEMENT, then ADD BUTTON TO IRLINC. I then followed the on-screen instructions: - press and hold IRLinc's SET button for 5 seconds - release, and the light on the IRLinc will go out - point a compatible remote at the IRLinc and press a button - light will start flashing if a compatible IR command is received - click OK button on the ISY Admin Console - device shows up under My Lighting - repeat the above steps if you want to learn more codes, otherwise click CANCEL I am getting a "request failed" message after hitting the CANCEL button (Michel - is that normal?), but otherwise the IRLinc is working fine here. Are you clicking OK once the IRLinc starts flashing?

Many ISP's now block the use of outside mail servers for just that reason - so many people have infected PCs sending out malicious emails without their knowledge (nevermind the intentional spammers). They do this by blocking typical outgoing email ports (25, etc..). Even if it's workiing for you today, don't be surprised if it stops tomorrow or next week. If you can, it's typically more reliable to use your ISP's outgoing email server.

Those will not work. Please save yourself some grief and return the USB PLM for a serial PLM.

No... the opposite. Add the IRLinc to the ISY through the Administrative Console. To do this, click the LINK MANAGEMENT pulldown, then choose ADD BUTTON TO IRLINC and follow the on-scren instructions. This will allow you to create links betwen your devices and your IRLinc, THROUGH the ISY's interface. This is quicker and easier than using the IRLinc's manual tap/tap method and ensures that the ISY is aware of all your devices and links - which is extremely important if you want a stable system. The advantage of using the IRLinc instead of the ISY's integreated IR receiver is that you can use the IRLinc buttons in scenes. This means that if your ISY gets turned off, unplugged, dies, whatever - your IR controls will continue to function. The ISY's integrated IR receiver only works through Programs, which means if the ISY is ever disabled for any reason your IR commands will not work. I hope this is more clear.

I would link the IRLinc THROUGH the ISY's interface - don't link the IRLinc to your IR codes independently of the ISY. Since you'll be using the IRLinc for your IR, you must use NEC codes. The RC5 code requirement is if you are using the IR receiver built into the ISY, which you won't be. I believe Michel is suggesting you use the IRLinc because its virtual devices can be added to scenes, which will execute independently of the ISY. The ISY's built-in IR receiver, which I think works great, works only through Programs.

Hey Eric - Good observation. Dimmer devices are not considered ON unless they are 100% ON. Using > than 1% should work, but keep in mind you can also do a NOT OFF. So, instead of saying: IF SWITCH1 STATUS IS ON say IF SWITCH1 STATUS IS NOT OFF

LOL! Gotta hit on those things that she might find useful. My wife loves KPL scene buttons that set room lights to specific levels with one button press. She loves the "whole floor / whole house off" buttons we use before we leave and before bed. She loves the automatic nightlight scenes I setup for our kids bedrooms. She loves the remote control of our lights from our bedroom and theater room. She loves how the holiday lights turn on and off automatically around the house. In my experience, once you setup a few things that she likes, she's much more accepting of the more oddball things that she normally couldn't care less about.

I do have an Elk M1 security system, but I don't currently integrate the Elk-124 with it - I run the Elk-124 standalone. I'll help as best I can, but to be honest I'm not nearly an Elk expert. You might want to check out www.cocoontech.com - there are many members of that forum with heavy Elk experience. I know many people use wireless sensors with varied success. I personally prefer hardwired whenever possible. I paid an alarm company to wire the motion, door and window sensors in my home. I feel the price was reasonable and worth it, and though I might have been able to do it, certainly not with the efficiency that they were able to. Most wires were run through the attic and/or basement. Wires ran between the floors via a stacked pair of closets (1 on each floor). You would need the wireless expander. Correct. It communicates directly to the ISY via the ethernet connection. The only PLM you need is for the ISY to talk to your Insteon devices (which I assume you already have). I personally prefer the look of the ELK-M1KP2 and ELK-M1KP3. The KP3 has a plastic front cover to hide the keys, so offers a cleaner look some might prefer. I think the ELK-M1KP is quite ugly. Yes - our touch panel software for the Nokia (and PC) can arm and disarm the Elk through the ISY! Here is a screenshot: http://www.interfacego.com/products/nk8 ... /nk8-9.jpg While I wish the Elk/ISY integration was a bit more full-featured, the Elk is currently your only option that I'm aware of if you want to integrate with the ISY. Hopefully more and more people will be interested in this integration which might give UDI incentive to add additional functionality. Good luck!

As of today the Elk is the only security system able to be armed/disarmed from the ISY. It's also an excellent choice - lots of capabilities, and very well supported in the DIY community.

Wow, that's very close to mine... maybe just a couple of bad switches? I have no use for this switch at the moment - drop me an email if you'd like to borrow it as a test. What hardware rev is your PLM?

OK, I hooked up the newest SwitchLinc Relay that I have (which isn't too new). It is: 2476S labeled v2.5 date code 0739 ISY shows it as firmware v.2C. The ISY is seeing local status changes with no issue. What is the date code on your problem switches, Mike?

Well I don't have a Relay newer than hardware v2.5 - though I haven't hooked it up to check the firmware level. I'll give that one a shot later today if I can. Is it possible you simply have a couple bad devices?

While you COULD do this, what you really want to do is create a SCENE in your ISY. This duplicates what you already did (but no need to manually link). I would: - unlink your 2 devices manually - create a scene - drop your devices into the scene as CONTROLLERS

I just wanted to test fully. Local control status updates to the ISY are definitely fine here with this switch. My PLM is showing firmware v63 through the ISY. It is labeled Rev 2.75.

OK. I hooked up the following switch for some quick tests. No load attached: v2476D labeled v4.0 date code 0828 I added it to the ISY via the address, and the ISY detected it correctly as a SwitchLinc Dimmer. ISY shows the firmware level as v.35. ISY is seeing status changes when the switch is controlled locally. I was able to adjust the ramp rate of the switch via the ISY, but the switch did require a reboot to activate the new ramp rate. I was able to create a scene containing both the above mentioned SwitchLinc Dimmer and an ApplianceLinc, and the scene seems to operate fine. This is the newest SwitchLinc Dimmer I have. I will leave it on my test bench for a few days - please let me know if there's anything else I should test.

I'll bite.. I have SwitchLinc Dimmers installed, labeled up to version v3.2 (ISY shows v.27), with no apparent issues. I also have SwitchLinc Relays installed, labeled up to version v2.5 (ISY shows v.2C), with no apparent issues. I do have a SwitchLinc Dimmer still in the box labeled v4.0 that I could hook up and run some basic tests when I have some time. Sorry I haven't been following all the threads - what kind of symptoms should I be looking for?

I'm surprised the WAIT and FADE STOP did not work for you. How many seconds did you WAIT for? How many seconds does it take for the FADE DOWN to finish dimming your lights?

I don't quite follow, but I can tell you that a "Fade Down" will not actually turn the device off. You'll need to issue a "Fade Stop" at the end (maybe after a WAIT command) to get the device to register as "Off."

For the record, this has been working fine for me: If From Sunset + 20 minutes To 9:30:00PM (same day) Then Set Scene 'FrontDoor' On Else Set Scene 'FrontDoor' Off I am using a standard location for my location (Boston, MA).

Hey Gary - Smarthome has had issues in the past with devices coming from the factory with links leftover from testing. Because of this I ALWAYS factory reset new devices before installation. I would like to hope that you weren't sent used units, and given how new the Motion Sensor is I think it's more than likely leftover links from testing. Glad to hear you're all set!

I wonder if maybe it's some old link left over from the factory? If you haven't, I'd remove the Motion Sensor from the ISY, factory reset it, and try re-adding it.

Thanks for testing! Darrell - Could you tell me why you thought that might be an issue? I want to make sure I understand how this program would work on the ISY. Thanks!

Sounds like a bad PLM. The LED should be on, and flicker with Insteon traffic.

Just curious - why would the WAIT in the THEN section be necessary? Just want to make sure I understand...

Also, check out this thread I started a while back: http://forum.universal-devices.com/view ... light=kids Maybe the basic idea could be useful to you?