TJF1960

Hello, I have 2 questions: 1. After having to delete all programs from ISY and re-importing them I noticed that most of them (not all) were disabled (the Enable check box was not checked). Is this common or could it be linked to question 2? 2. I tried to do a restore on the ISY after #1 above and it failed (something about socket error, sorry I didn’t write down the exact error). I rebooted the ISY and then was able to restore. I had the same problem when upgrading to 2.7.14? Could this be an indication of something failing, or is it a good idea, and perhaps necessary to reboot occasionally? Thanks, Tim

Ha Ha, how about: If Control 'Outdoor / Garage Keypad-Pizza Delivery' is Switched On Then Send Notification to 'Mountain Mike's Pizza' Else - No Actions - (To add one, press 'Action') Tim

Is the pizza here yet? Tim

bktong, Yeah, it thru me for a loop too because I also was used to the 1.0, but I must say I do like the refinements they made in the 2.0 version. Tim

Hi kingwr, It has been my experience that the program would remain true when viewed in the program summary page when the folder turns false. Tim

Rev 2.0 Yes. I just found the quote from the wiki for Rev 1.0 "Darkness Sensitivity - The higher the value, the darker it needs to be for the unit to see night. Default = 35. Range = 0 - 255" at http://www.universal-devices.com/mwiki/index.php?title=ISY-99i/ISY-26_INSTEON:Linking_a_Motion_Sensor And I would set my Rev 1.0 motions to 255 for the darkest possible level before d/d trip. Good question, oversite maybe when they modified the original schematics and pcb's to add the adjusment pots or they decided it made more sense to have it operate this way, or just to confuse people...... Tim

Hi bktong, I just pulled the ms from the garage to verify. I have mine set to 5 which lets the garage get fairly dark before the d/d trips. Any number setting higher will alow the d/d trip at a higher light amount (0 = always Off, 1 = darkest before trip, 254 = Lightest before trip, 255 = always on). I seem to recall the d/d set points were backwards between v1.0 and v2.0, seems to me the higher the number the less light was required to trip. But with the v1.0 its just the opposite. Also, unless you are testing the d/d trip levels as per the instructions after every adjustment you must wait for the motion sens time out, then wait another 4-5 minutes before testing the d/d because the d/d will not trip or reset until after no motion is sensed + the time out + wait time for the d/d. Tim

Sorry just re-read your original post. Not sure if you are using the ISY to make the adjustments for light to dark or if you are using the pots. If you are using the ISY you have to have jumper 5 on both pins. But since you mentioned the only jumper on both pins is jumper 3 then you must be using the pots. I never experimented with the pots, only using the ISY and I did get a good low light level using the ISY as the adjuster. If memory serves I set the d/d trip level at between 5-20 to obtain a low light condition before it turned on. Tim

What is the ms version, and does it have the adjustment pot's? If it does not have the adjustment pots then it is not as adjustable as the newer version with the pots. The newer version will allow more of a lower light trip point than the older verions. Another bonus of the newer version is that if you do not want the d/d to ever trip you can set the sensitivity to 0 or 255. Tim

How old are they, what rev? Do they have adjustment pot.'s for dusk/dawn and time out? If so is jumper 5 on both pins? Tim

For what its worth it, the newest MS with the adjustment pot.'s for d/d and timeout (v2.0 or 2.1 can’t remember which) do not evaluate the d/d now until after the no motion / timeout period, which is nice.

Hi kingwr, My question on this subject would be whether existing programs already written and implemented would have to be re-written once any of the code were to be changed as you suggest? While it may make writing programs easier and would require fewer programs, how would this impact current users who have been at this for a while and have hundreds (and hundreds) of programs already written? Tim

Hi gfridland, After a reboot the ISY considers any programs using the motion/dusk-dawn and low batt status conditions as false. I had a similar issue with using any status based on the Insteon motion sensors whether it was the motion or dusk/dawn and also with Triggerlinc’s. I found the solution in the Wiki. I created two programs for each function I wanted preserved in the event of a reboot. One program which monitors the status of the event (say dusk/dawn) and another program which when the ISY reboots will turn the first program back to true if its status was true before the reboot. Program: Garage D/D Status If Control 'Garage MS Dusk/Dawn Sensor' is switched On And Control 'Garage MS Dusk/Dawn Sensor' is not switched Off Then Set Program 'D/D Status Reboot' To Run At Startup Else Set Program 'D/D Status Reboot' To Not Run At Startup Program: Garage D/D Status Reboot If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Run Program 'Garage D/D Status' (Then Path) Else - No Actions - (To add one, press 'Action') Use the first program (Garage D/D Status) in any if statements in other programs where the status or control of the dusk/dawn sensor was used. Now those programs will run based on the status of the new program instead of directly by the sensor. If the ISY reboots the Garage D/D Status program will return to its original state before the reboot. Tim

Not quite sure. I checked my SL dimmers which are v.36 and I still have the all of the on level selections. I wonder if the v.38 are fully supported in 2.7.12? Michel will have to answer that one.

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