Xathros

I can second the low battery as the culprit. Just had one in my basement do exactly the same thing. Low battery node never triggered either. -Xathros

LOL!

Quoting the hamster in the Sprint commercial, "I don't know where to go with this" Seriously though, I have an 8 button Remotelinc 2 on my nightstand that does way more than one biga$$ Bt.tn could ever do for me and it takes up far less real estate. I'm fairly fure I paid less then $99 for the RL2 (SH shipping included!) and it does not require access to the cloud to perform any of it's assigned duties. Heck, even Apple hasn't figured out how to do eveything with a single button yet! -Xathros

To add to oberkc's excelent reply, depending on what causes the lights to turn on, you may consider using Status instead of Control in the if statement. When using control, this program will only trigger when the switch in manually operated and, in this case, only when turned on specifically rather than fast on or fade up. Status will catch the change in status regardless of how it gets that way - even if the switch is turned on remotely by a linked device or scene. If Status 'Switch' is not off Then Wait 10 minutes Set Switch Off Else Understanding the difference between Status and Control program triggers will allow you much greater capabilities and flexibility with ISY programming. Hope this helps. -Xathros

edokid- Each Insteon device sends control events when actuated. In the case of a switchlinc, the control event is generated by operating the switch paddle. It can issue the following control events: On, Off, Fade Up, Fade Down, Fade Stop, Fast On and Fast Off. In the case of a motion sensor, you only get On and Off. Control events are useful in that they indicate action taken by a specific device whereas status can be affected by other devices. Lets set up an example here. Lets say we have a program monitoring a motion sensor and turning on a switchlinc when motion is detected. If Control 'Motion Sensor' is Switched On Then Set 'Switchlinc' On Wait 5 minutes Set 'Switchlinc' Off Else I walk into the room and the sensor see me. The sensor issues a Control On command and the program is triggered and turns on the switchlinc. Here is what just occurred: Motion Sensor Control Switched On Motion Sensor Status is On Program Triggered By above control event. Program turns on Switchlinc Switchlinc Status is On Notice that there is no control event from the switchlinc. Also notice that we have status of On from both the sensor and the switchlinc. Now, I walk over to the switchlinc and turn it off. What we get here is: Switchlinc Control is switched Off Switchlinc Status is off Status changes for both local and remote actuations whereas control requires operation of the device itself. This can be used to determine which device caused an action. If Control 'Switchlinc' is Switched On and Control 'Switchlinc' is not Switched Off Then Disable Program "Motion Lights" Else Wait 10 Seconds Enable Program "Motion Lights" In the simple example above, we monitor control events from the switchlinc and disable or enable a program that watches the motion sensor and runs the automatic lighting. Since the act of disabling a program also stops that program if it already running, this solves the scenario of turning on a light after the motion program already turned it on. The "is not Switched Off" part causes the else clause to run when the Control is switched off, this delays for 10 seconds then re-enables the motion program. Hope this helps clarify things a little. -Xathros

As long as nothing else causes the program to be run (Run at startup, called by another program etc) then it will only trigger at the point that the inlinelinc status changes (On, off, dim, brighten). It will run then when the status changes to 100% and run else when it changes to anything other than 100%. -Xathros

Status should work just fine. It triggers on status change. In addition, unlike control, it will work regardless of how the inlinelinc was turned on/off whereas control is only valid when manually operated at the device itself. -Xathros

The rapid flashing indicates that the ms did not receive a response from a linked device ( likely the plm). Sounds like either a comms problem or some extra unwanted links in the ms. -Xathros Sent from my iPhone using Tapatalk

If you are following the motion sensor directions for setting parameters/jumpers, the changes should be instant. I added a bit more to my last post after you replied. -Xathros

The motion sensor delay is caused by using an ISY program to turn on the light rather than a Scene like the hub did. There are ways to work around this but one of your requirements from a previous post is preventing a quick on solution from being used. Unless your having communications issues, the delay should not exceed 1 second. Most of my motion light programs operate this way and I don't find it to be a major issue. The root of the problem is the wireless motion sensor. It is one way comm from the sensor to the ISY or Insteon scene. If you want to only enable it during certain parts of the day, you need to use programs to make the decisions (ignore the sensor during the day). If you only wanted different dim levels at different times of day, you could use a scene, get instant response from the MS and adjust the scene parameters from the ISY based on time of day. The solution for manual override is fairly simple. Use a program that watches the switches for manual operation. When turned on or adjusted up/dn, disable the motion programs. When turned off, delay 10 seconds then re-enable the motion programs. The issue with having to stand still or exit the room for 10 seconds to re-trigger a sensor is likely due to the sensors internal configuration. It can be configured for On only, sensing mode with no timeout. In that configuration, there should be little no no dead time between detections. I do agree with you that some automation is no better than the manual switch but in other areas it can be a godsend. The buzzing lights are likely LED or CFL bulbs that don't care to be on a dimmer. Some brands work better with dimmers than others. I use Cree and Phillips LED's from Home Depot and others here have posted good results with them as well. The motion sensors can have other uses as well. I use mine in conjunction with other insteon device activity to maintain a Vacant/Occupied status at my place. If no activity or motion has occurred and no phones are connected, the house goes to sleep, lights off, doors close/lock etc. For this usage the sensor reaction delay is not apparent. I know the ISY seems hard to grasp at first. It's a very capable and powerful controller. Keep in mind, not all that is good is simple and not all that is simple is good. I would urge you to hold onto the ISY for a while longer and let this community help you get started. Hope this helps. -Xathros

Johnny beat me to it!. The din relay if FAR cheaper than the IOLincs and is rock solid reliable. You will need the ISY network module to control the DIN relay but the two items combined is still much cheaper than 7 IOLincs. -Xathros

Glad you got it working and glad I could be a assistance. It will get a bit easier when the new console is released. -Xathros

Andrew- So sorry to hear of your PLM failure but alas, they seem to fail way too often. There is a thread here on how to repair your failed PLM power supply for under $20. If your handy with a soldering iron, it's well worth the effort for a spare PLM. As for the record mismatch, I believe that you are 100% correct in your assessment of the situation and I agree that the ISY should ignore the data following the 00 in the final device link table record. -Xathros

I'm not sure what post you are referring to. I don't see any posts by Michel in this thread. In terms of upgrades to the AC, once launched, it should prompt you to allow automatic installation of any modules that you have recently purchased. To get your desktop icon back: Goto http://<your.isys.ip.address>/admin/admin.jnlp with Firefox. Allow Java web start to open the resulting download. This will recreate your desktop icon using the current AC firmware installed in the ISY -Xathros

Yes, I'm on 4.2.10 and have loaded every version along the way. Ever since Lion, I have had this finder problem. Did you follow the procedure exactly as I posted above? You need to set that finder window to start at your system, then drill down into the hard drive, then your desktop or downloads. It won't "see" anything unless you start navigating from the very top of the tree. -Xathros

Below is what I received from UDI back in May announcing the 99i's retirement: ISY99 Official End Of Life.pdf -Xathros

Hi smokegrub- This is an issue with the MAC finder and how it interacts with Java. Try this: 1) Put the new firmware file on your desktop. 2) Go into the Admin console and select manually upgrade. 3) Proceed through the backup. 4) When prompted to locate the firmware upgrade, first select your MAC from the drop down at the top of the finder window. 5) Then select Macintosh HD from the same dropdown. 6) Now navigate to your desktop and select the upgrade file. Dunno why the finder need to be started at the very top of the tree before it can see anything but this has worked from me since this problem started with Lion. Good news is that the next generation Admin console (now in testing) solves this particular issue for me at least. Hope this helps. You posted that as I was writing this! -Xathros

I would add the fans to that scene and set the on levels to 0 to effectively turn them off when that scene is called. -Xathros Sent from my iPhone using Tapatalk

Mike, I will need to review all of my code to determine exactly what I did to make it work. I have quite a few programs related to the garage doors. Some for ML and others for local control from KPL buttons and even more for proximity related stuff. Here is the ML stuff as I remember it: My Open/Close program on the ML dashboard is a disabled program that uses a State variable to represent the condition of the garage door. 1=open, 0=closed. The program (Dad_Door_Open/Close) is Disabled so that it doesn't auto trigger. I used a state variable so that I can trigger other programs/events based on the change in door states. For this example I believe an integer variable would work just as well. If $s.Dad_Door = 1 Then Set Dad_Garage_Door_Relay On Wait 15 Seconds Set Dad_Garage_Door_Relay Off Else Set Dad_Garage_Door_Relay On Wait 15 Seconds Set Dad_Garage_Door_Relay Off I have a second program that monitors the sensor and sets the variable among other things. If Control Dad_Garage_Door_Sensor is switched On and Dad_Garage_Door_Sensor is not switched Off Then $s.Dad_Door =1 Else $s.Dad_Door =0 The Custom status for the Open/Close are set: True - Open False - Closed Running Then - Door in Motion Running Else - Door in Motion I don't remember if I set the Icon as Door or Door Reversed but one of them works correctly and the other is backwards. Hope this helps. -Xathros

Mike- I know it seems strange but... Mobilinc displays the Icon based on the status of the program (True or False = Then/Else). Running the empty Else section makes the program False which causes ML to display the opposite Icon. It doesn't matter that there is nothing in the else to run, simply that the else WAS the last thing to run. Make sense? -Xathros

With the Hub, you likely had the sensor as a controller for the Light scene. With the ISY, you currently have the sensor tell the ISY that it switched on, then an ISY program tell the Light to turn on, There is a delay in this configuration mostly due to the time it takes to receive and send the various insteon commands. I have had the same issue with the sensor timeouts in the past. I resolved it by setting my sensors to only send on commands and setting them to occupancy mode which sends an on with every detection of motion rather than waiting for the timeout. Then revise the program to watch for the on command from the sensor and build your timer into the program instead of using the sensor timeout. If Control 'Motion sensor' is switched On Then Set "Light" On Wait 1 minute Set 'Light' Off Else In this configuration, the timer is restarted with every detection of motion and turn off after 1 minute of no motion detected. Some will dim the light 30 seconds before turning off as a warning. You can simple add that into the then section if desired. Instead of using the Fade Down to turn off your lights, I suggest using a scene with a defined ramp rate to get the fade rate you want. Set the scene "Fast On" for instant on and set the scene "Off" for it to fade off. Fade Down should be followed by a fade stop. It was not intended to be used as you have used it here. Hope this helps. -Xathros

Sorry. I guess I shoukd have said "Many" instead of "Most". Safari can be problematic with the ISY. There are workarounds for many if it's issues but an alternate browser is often easier for some. -Xathros

Most of us mac users here just use firefox for the isy stuff. -Xathros Sent from my iPhone using Tapatalk

I do receive the upgrade announcements. I believe there was a place on the UDI website to register for them - this was years ago. I'll see if I can find that for you. I would install the current beta 4.2.10 or wait for the 4.2.11 which I suspect will be the final within a week or 2. -Xathros EDIT: Register here:http://www.universal-devices.com/my-account/

Yes, I believe there are some coding possibilities built in. I have not explored it's capabilities in that reguard. So far, I have just built network rules to simulate clicking the controls in it's web UI to turn On/Off or Cycle a relay. There may be the ability to query the relays via the web but since the ISY's network module is one way at the moment, that wouldn't work. There may also be the possibility of the PLC code in the relay executing a /REST call to the ISY to update a variable or set a device/scene state but again, I have not explored that possibility as of yet. As I recall, each relay can be configured to be either off, on or previous state at power up. They do however require power to remain in the On state so they are not mechanically latching. -Xathros