TJF1960

Hi Michel, My ISY hung after installing 2.7.12 with the power,tx,rx leds lit solid. Unplugged the plm for 10 seconds plugged it back in and after a bit the same leds were again lit solid. Unplugged the plm for another 10 seconds this time it finished booting and seemed ok. I had disabled the firewall and anitvirus programs (McAfee). I also noticed IE window didnt closed down like it has in the past. I reinstalled the new update, again the IE window didnt close fully but the ISY updated and rebooted and seems to be fine. This is the very first time I have ever had a problem installing an update (I don't know if it means anything or not). The other thing I noticed, which is great, after installing 2.7.12 and accessing the admin console thru http://www.universal-devices.com/99i/2.7.12/admin.jnlp- Java application is that for the first time since this has been available I don't get the message window opening saying "An optional update is available. Do you want to update the application?" I have opened it numerous times today and it opens right up. Thanks, Tim

I hate to jump on the bandwagon, although its not a real big deal, but I have had the update download message pop up pretty much since this method of opening the admin console was available. In Java I tried increasing the size but it was set to max (1000). Also tried to update but it is running the current version. And when I clear the cache the desktop icon disappears. After reinstalling it continues to display the update download available message. I am running XP pro vers. 3 Thanks, Tim

You could take your 2 programs and place them in a folder, set the condition of the folder to something like If "Leave is on" then the programs in this folder will run. Create a new folder with a condition like If "Leave is off" ...... Inside this folder have a program like If Status "Leave" is on and from Sunset to Sunrise (next day) Then Set "Kitchen Lamp" 30% Else Set "Kitchen Lamp" Off Tim

I have got into the habit of backing up before adding any devices or changing any programs or scenes, learned the hard way. As far as the i1 message, Michel will have to answer that one, and hopefully he will be able to offer some suggestions as to the root cause of what happened after adding your triggerlinc. Tim

Hi wwat, 2.7.10, for me anyway, has been extremely stable with the exception of adding rf devices. The work around has been to factory reset the rf device (unless you want the links from it added) then Link Management > New INSTEON Device then adding a name, address and selecting [10.02] (2421) TriggerLinc and selecting option 3 Add devices found in links and keep existing links. I have added a couple of ms in version 2.7.10 and haven’t had the problem you described though. It did seem to take a little longer than usual when linking but once complete everything was fine. I am surprised you were able to get it to link using option 1. I tried quite a few times using that option and never had any luck. I know I have had some weird things occur once in a while after linking or restoring a device. Things like some kpl buttons not working correctly (or at all) or devices turning on or off when they shouldn’t. It was suggested to me to remove AP’s to prevent rf traffic on the power line (unless linking an rf device of course) and to disable programs from running which could turn devices on and off and be sure no devices are operated while in linking mode. Once I started removing AP’s, suspending programs and , in my case making sure no one else is at home, all of my weird anomalies disappeared (knock on wood). During linking of an rf device I will usually disconnect all but one AP or Dual Band device. I don’t know if one of these things caused your trouble or not but I thought it was worth bringing up. Did you happen to factory reset the triggerlinc before linking? As far as the antivirus and firewall, I don’t believe its an issue unless you are restoring a back up or upgrading firmware. Tim

Hi Steve, No, that wouldn't be it, that is actually how I assumed it was (I know I shouldn't assume). If jumper 3 is making good connection to both pins on the ms and the d/d is showing a status of off, the light shouldn't be turning on. I can only think that the ms are bad, but unlikely, 2 defectives??? It a long shot but try removing jumper 3 then pressing the set button as per the instructions then trip the motion. The put the jumper back on, press the set button then trip the motion again. Then put it back in the drawer until its d/d status changes to on. Then pull it back out into the light and wait for d/d status to change to off. If that doesn't work try factory restore again and restore in isy. If it still doesn't work right there is one more thing that I would try. Get a good, firm grip on the motion sensor, and as hard as you can, chuck it against a brick wall because I can't think of anything else it might be (or you could try and get an exchange unit, might be a better way than the brick wall thing). Sorry I couldn't be more help. Oh and remember while you are waiting for the d/d status to change make sure the ms is in a position that it won’t see you because if it trips due to constant motion the d/d will never change status (this minor little detail trip me up for quite a while). Tim

I too have played with the new rev 2.0 ms about a month ago trying to figure out the d/d operation. I use the ISY to program the options and finally settled on a setting of 5 for the d/d in my garage. A setting of 5 resulted in a pretty dark garage before the light would turn on. Setting to 0 or 255 basically seem to disable the d/d operation and the status would stick to which ever level it was at when set. I seem to recall the operation of the d/d settings were the opposite of the wiki too. One nice benefit is that SH increased the adjustable range of light to dark in the v2.0. Another thing I noticed which I don’t remember in the previous version is that the d/d status will not change while the ms time out is in progress. Once the motion has stopped and the time out ends, then 2-5 minutes later the d/d will change status if it needs to. In other words the light controlled by the ms will not prematurely activate the d/d status. Try setting the d/d to a setting of 5 and leave the time out at .5 thru the ISY, if the d/d status is off then put them in a drawer and close it for 5 to 10 minutes to see if the d/d changes. If it does (or not) put them in the light where they will not detect any motion for 5-10 minutes. I did this a couple of times just to cycle the d/d status a few times. They have been working great ever since. Tim

I can confirm. I had this happen every time I created a new program or copied a prgm in 2.7.8 and 2.7.9 However in 2.7.10, for me anyway, it is now just an intermittent occurrence. Every so often it will happen. I haven’t figured out the rhythm to it yet. Tim

This is a problem in 2.7.10, the fix is to factory reset the ms and select Link Management > New Insteon Device then add a name, address and select [10.01] (2420M) Insteon Motion Sensor from the drop down box and then press the Add devices found in links and keep existing links. Tim

I noticed the newest (rev2) ms dusk/dawn will not change status until the ms is off for 3-5 minutes. So the light turned on via the ms will not affect the d/d operation. I cannot think of a way, even thru the use of programs, which would not affect your set up, one way or another. If the lite is on, your ms d/d will turn dawn on. Once the ms turns off it wont turn back on via motion until the d/d is back to dusk. Sorry I couldn't help more. Tim

I am having the exact same problem as hart2hart with 2.7.10, MS v1.1 and 2.0 Thanks, Tim Edit: I did find that the MS could only be added by New Insteon Device and selecting Add devices found in links and keep existing links Tim

Hi gfridland, Sounds like you have ruled out stray x10 and insteon signals triggering the scene via the log. Have you looked thru the program summary tab in the isy to try and match times with the scene turning on? Or you could disable all programs for a night to rule them out once and for all. Please keep us posted. Tim

The beauty of the ISY is that it is the brains behind the whole HA. If you have to manually link v35 SL devices the ISY is no longer in control. Not to mention the fact that manual linking is/can be a lot of extra work. I am sorry but if I had problem v35 SL's I would want the next rev. and be done with it. But thats just my opinion, Tim

If you want the program to continuously run until false you can add "Run If" in the "Then" section. Prgm: Entry Lite Status If Status 'Entry KPL 1 Lite' is On Then Set 'Entry KPL 1 Lite' Off Run Program 'Entry Lite Status' (If) Else - No Actions - (To add one, press 'Action') This prgm example will keep trying to turn off the entry kpl 1 lite until the status of the lite changes to off. Tim

If I understand correctly, it should be possible. You may need to add a couple of programs to do it. I have mine set so that after 5 minutes of no motion in the room the On level reverts back to the original programmed level. But if motion is detected within the 5 minutes the lights turn back on to the manual switched level (preset scene on levels).

I would like to clear up an incorrect statement I made. At 10:00PM the folder will turn "True" and stay true (I dont know what I was thinking ) However if you want the programs to run in the folder only as specified times then using "From 10:00PM to 6:00AM next day) would turn the folder true at 10PM and false at 6AM. Sorry about that. So any program in that folder can run if their conditions are met while that folder is "True." Program name: MBath Sink Lite 0% Adj If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Wait 2 seconds In Scene 'MBath MS-Sensor' Set 'MBath Sink Lites' 0% (On Level) Set 'MBath Sink Lites' 1 (Beep Duration) Else - No Actions - (To add one, press 'Action') If this program (Program name: MBath Sink Lite 0% Adj) was in the folder and the folder became "True" this program still wouldn't run until something called it to run. But if this program (Program name: MBath Sink Lite Day) were also in the folder: Program name: MBath Sink Lite Day If Program 'Time Sunrise+10 to Sunset-10' is True Then Wait 2 seconds Run Program 'MBath Sink Lite 0% Adj' (Then Path) Else - No Actions - (To add one, press 'Action') Then if the folder were "True" and the If statement (of MBath Sink Lite Day) became true then this program would call the previous program (MBath Sink Lite 0% Adj) to run. Tim

Hi Wayne, Right, you simply link the MS to the ISY, then link the SL to the ISY. Then create a scene in ISY and drag the MS and SL into the scene. A program without an "If" statement will not run until called upon by another program (or selecting "Run Then" in the "Program Summary" tab). Any programs (even "Then" only programs) in a folder that is "False" will not run. I believe the folder will only run for 1 second. It will turn "True" at 10:00:00 PM, then turn "False" at 10:00:01 PM. Better to have "10:00 PM to 6:00 AM the next day." Tim

Hi Wayne, I have set up 4 different on levels for our masterbath. Each of the on levels is instant when motion is detected. In the evening the lites turn on with motion to 75%, after 9:30PM they turn on at 30%, after 3:30AM if we are up they will turn on to 60% and during the day they do not turn on at all. I have also set up a manual override which will turn on to 80% with a single tap or 90% with a double tap. 5 minutes after the motion shuts off with no further motion I have the programming resume its normal daily schedule. If the motion turns off then back on during the 5 minute time period the lites will turn on to 80 or 90% whichever tap was used. I have been very happy with the way it all works, although on a few rare occasions it would be nice to have the lites stay on after the ms turned off. I have done some experimental programming which would trick the system and give the appearance the ms off trigger was ignored. It worked pretty well but was very program intensive. I like Michel's suggestion of using folders and had I used them as he suggested it probably would have cleaned up my programming a bit. In fact when I continue with the experimenting mentioned above I may be able to utilize them to make programming easier. Anyway for now it works fine. In order for this to work the SL and MS have to be linked to the ISY. Scenes are then created in the ISY for the SL and MS as needed. I believe the scene adjust works in this situation because the on level and ramp rate is stored in the SL and not the MS. If they were stored in the MS this wouldn’t work without putting the MS in programming mode. Tim

I have since included this set up in our master bathroom but included extra programs to offer 4 differet On levels depending on the time of day or night. I also created some programs which when the light is turned on manually during the day will reset the On level so that any motion will turn the lights on, until 10 minutes after the last motion detection then resets the On level to the previous state. It has been working very well so far (about 3 months). In fact I have added similar programs to our entry hall light and my work room light. I dont see why not. The two halves of the case have a seal and the battery door is sealed as well. I used 1 outside for about 6 months without any problems. Tim

Hi oktane, That is correct. If you select the MS to adjust, your only options are 0% and 100%. The adjust scene part of the program should look like: In Scene 'MS-Sensor' Set "Dimmer' 55% (On Level) ( "MS-Sensor" and "Dimmer" would be replaced with whatever name you have given them, and the On Level is replaced with your desired level). Also it is important when selecting the ms that you scroll up to the devices and select the ms, not select the scene the ms is in. Hope that helps. If not maybe you could post your program and some of your specifics. Tim

Hi Michel, Right click on Low Batt node and select query? Doesn't do anything. That is what I figured, again right click on "1" and select query and it doesn't do anything. Suggestions? Should I just wait for the final beta version?

I have been unable to clear the "low batt" indicator from a motion sensor on the admin console by doing a query on the node. I have tried with the ms in linking mode and not in linking mode. Nothing happens when I press the query button, no progress bar or anything. Nothing on the event viewer, even at level 3. Speaking of query, I noticed also that when query is pressed for the ezflora nothing happens either. All of the other devices are able to be queried. Am running 2.7.7 alpha. Thanks, Tim

How about a relay and I/O Linc? Relay coil wired to load side of GFI. Relay contacts connected to I/O Linc sensor input. When the relay de-energizes the I/O linc sends an Off or On depending on how you want it to report the GFI trip. And, if you want to get a little MacGyver-ish - wire a solendoid actuator to the I/O Linc output. Write a program where if the GFI trips the I/O Linc energizes the solenoid which presses the reset switch on the GFI!!!! (just kidding). Tim

Hello Michel, Here is the link to the icon appliancelinc. http://www.smarthome.com/2856S3B/ICON-Relay-INSTEON-Appliance-Module-3-Pin/p.aspx

Confirming, I have the same problem with the icon appliancelincs installed in the last week with 2.7.7alpha when installed with "start Linking." If installed with "new insteon device" then they came up as v.00 Icon appliancelincs installed on 2.7.6 registered properly using "start linking." Tim