gwarthur

I also just bought a 2450 IOLinc intending to use it as a high water level (clogged drain) monitor. (I can't use Smarthome's water sensor because this is in an outside stairwell that gets wet when it rains. Wet is OK, rising water is not). I connected the Sense and Ground to a normally open float switch. Now, when the switch closes, the 2450's LED lights, but that's it; the status shown for that device on my ISY-26 does not change, but continues to show 'Off'. My question is: what do I need to do to force it to notify the ISY-26 of any change in its status? Do I have to first slave the 2450's internal relay to the sensor status? The relay is NOT set to follow the sensor right now. Also, most of the options listed in the Options pop-up on the 2450 device page in my ISY-26 are a mystery; can anyone point me to a comprehensive explanation of what each feature does? -GA

Jeez! Yep, there it is, big as life. As my mom used to say, "If it had been a snake, it would have bitten you!" I guess I did not rescan the top of the page after logging in. The search feature isn't present until you log in. Thanks Sub-Routine. -GA

On several occasions, I have asked a question - and received the usual speedy answer that Universal Devices if known for - and then later found pretty much the same question asked & answered elsewhere in the forum. Of course, this would not be a problem if I took the time to carefully read through the forum to find the information I needed. But usually, when something breaks, I don't have the patience to exhaustively go through every likely thread; I want to know how to fix the problem NOW. So after a short search, if I can't find the answer, I post a question. Presently, the forum has grown so large - over 6,000 entries, I believe - I see this happening over and over again. Is there a SEARCH module that you could add to the forum that would allow a reader to perform a string search? I think this capability could dramatically reduce your workload as well as making the forum a more effective and user-friendly resource. -GA

When you linked your devices into ISY, did you "...bring Existing Links"? If so, that might explain why your KPL didn't show up in the scene. Under the scene, is the color of the SWLs RED? In all likelihood, ISY does not know about all the manual linkages and thus overwrites what was previously a working version. If you have two isolated switches, I do recommend removing them from ISY, adding them back in using the First Option (do not bring in the links), and try another scene. This will be the ultimate test as to what the problem could be. Hi, Michel, and thanks for your quick reply. I use my ISY mainly for scheduled light control throughout my house. And yes, the two SLRs were in italics and were both red in the scent I tried to set up. I did not encounter the Start Linking dialog box with the three options when I set up the scene. Maybe that was one of the problems? So, as I understand what you are telling me, in order to put together a working scene, any devices that I want to include that are currently tap-linked must be deleted from the ISY and re-added? -GA

sfhutchi, The proper way for a 3-way (all 3 switches control each other) is to drop all the switches in "one" scene as "controllers". With regards, I have had my Insteon gear for longer than I've had my ISY, so I'd gotten in the habit of tap-linking everything. I was reading some forum entried today, and I became intrigued about linking devices from inside the ISY console because it would bring the ISY "into the loop" so that its status would be automatically updated whenever a device in the scene changed state. Right? To try this out, I deleted an existing tap-linked setup with two SLRs and a KDL secondary button. I then created a scene, dragged the two SLRs - not to the scene 'box' on the right - but to the scene's entry in the tree on the left. (Was that right?) Lastly, I also dragged the KPL button to the scene entry in the tree. As I dragged each device to the scene entry, I set them as controllers. The two SLDs showed up in the scene 'box', but not the KPL button. In any case, nothing was linked when I finished. Any idea what I did wrong? I ended up deleting the scene and re-tap-linking everything. Now it's working again, and I'm no worst off, but I'd really like to crack the code and start doing all my linking with the ISY. Any suggestions would be appreciated. -GA

Well, like my mom used to say when pointing out something I was looking for that was right in front of my face, "If it was a snake, it would have bitten you!" I've probably pulled down the Link Management menu fifty times, but just never noticed the "Link a RemoteLinc" entry. Many thanks, marksanctuary. -GA

I just received a RemoteLinc (RL) and tap-linked it to some devices just to see if it worked. It does, but I have a couple of questions: I tried to link it to the ISY-26 (using Start Linking and 'Add devices found in links and keep existing links', then holding down one of the RL buttons in its ON position for 10 seconds) but nothing shows up. In other words, no new devices appear on the My Lighting tree. Am I doing this wrong? Do I have to put the RL into Multi-link mode? In the past, linking devices to the ISY has been straightforward and easy. Also, to get the ISY to monitor RL signals, should I put the ISY in linking mode while I'm tap-linking devices, or should I always link from within the ISY by creating scenes? -George

Have you set a release date for the final version of 2.5?

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. The bulbs are 'N:vision' 30W units, model 28930BD. -GA

If I have been following the forum discussions correctly, the version 2.5 beta - released as a series of version 2.4 updates - has been out and receiving constructive user feedback for several months. I am wondering if its stability and maturity are nearing a point where you will set a date for its release. After going through a prolonged period of pain and misery while I learned the quirks of Insteon devices and the ISY-26, everything seems to be running reliably. The trick of stacking the first Accesspoint with the PLM seems to have made a huge improvement. So having reached a sort of truce with my system, I am hesitant to jump down to the bottom of a new learning curve unless there is the promise of serious added value. 2.5 seems to have that added value; I am very intrigued about being able to write conditional statements. This moves the ISY to a new level of intelligent device control. I just don't want to take a chance on a potentially unstable beta. On a completely different and unrelated subject that probably should not be posted here, you might want to put in your FAQs someplace, thanks to a tech at Smarthome, that if an Insteon device is controlling a light with a CF bulb, the voltage spike that it sends back to its controller when it is switched off can trigger the device's internal switch to immediately turn the Insteon device back on. This happened at my house: I have two identical lamps, both with the same type of 34W CF bulb, each plugged into separate lamplincs. I happened to be in the room when it came time for the ISY to switch one off. I heard its relay click and saw the lamp blink , but then it remained on. This still happens from time to time. Rarely a problem turning it on, but sometimes I find it on long after it should be off. Yet its twin has no such problems. I figure that either the lamplincs have different sensitivities to reactive 'flyback' voltage or there is enough variation in CF bulb construction that one puts out a bigger jolt to the lamplinc than does the other. Without this factoid, you might assume that the problem was with the controller. -GA