Xathros

Mike- This would indicate to me that you have a number of programs reacting to the change in status of devices as they are queried. This does not mean that the devices actually changed state but rather that the ISY is seeing a status change from unknown to whatever the query returns as it runs. You can likely verify this theory by de-selecting "Query at startup" then reboot the ISY and wait a minute to make sure its up and running then run the 3am query and see what happens. I would expect the same result as what you were seeing at startup with "Query at startup" selected.. -Xathros

Thanks Dwight. A community like this one is a rare find on the Internet these days. I'm proud to be a part of it. -Xathros

Go to system preferences on your mac. Select the Security & Privacy Applet General Tab Unlock the Applet with your system password Select "Anywhere" under allow apps from" Then try to run the admin console again. Hope this helps -Xathros

There are 2 settings on the Configuration / System tab in the admin console that may have an effect here. Query at startup and Catch up schedules at Restart. The first will do a query of all devices at boot and the second will try to run any programs that should have been run based on time prior to the restart. Try de-selecting both of these options and see if that helps. -Xathros

By "Switch' triggers every time motion is sensed" Larry means "Control is switched..." The ISY supports both Status and Control events. These can often be interchangeable but there are some very specific differences that when understood, offer much greater control and flexibility in your programs. I will attempt to explain here: Status will trigger a program any time that the status of a device changes regardless of why the status of the device changed. When triggered, status (and the rest of the IF statement as a whole) will be evaluated and a true(Then) or False(else) determination will be made and the appropriate branch of the program will be run. any time a program containing a status test is triggered by other means, the status will still evaluate based on the current status of the device being tested. Control requires specific manual operation of the device locally. For instance, "IF Control 'Switchlinc' is switched On" will only trigger when someone manually presses the On paddle of the switchlinc. It will not trigger if the switchlinc is turned on by a linked device. It will not trigger if the switchlinc is manually turned Off, fade down,fast off,fast on, fade up etc. Only On at the paddle. If this "Control switched On" is used in an If with other triggers and is triggered by any of the other triggers, the if will evaluate false since this control event did not trigger. Devices always have a status, control events only exist for the brief moment when they occur. Hope this helps. -Xathros

This appears to assume that a sensor should see motion or a light/dark transition at least one every 25:59. For many this should be just fine. I however have a few detectors in places that can go weeks in the dark without any motion. For those, the low batt node is my only hope since there is no heartbeat from these sensors. I can only hope that the next gen motions from smarthome gain a heartbeat like some of the newer wireless devices have. -Xathros

I would try a factory reset as Brian suggested above. If that fails, it's time for a replacement. I'm in a similar situation with one of my 2 wire dimmers. This is the second failure I've had at this location with one of these. In my case the load is a single fixture with 2 40W incandescent bulbs. I'm rewiring and replacing with a micro dimmer and standard Switchlinc. No more 2 wire for me. They just don't seem to be very robust. -Xathros

Easy if they are on the same network. You can pass variables or set devices/scenes on/off all via the /rest interface using the network module on the other ISY. This is supposed to get even easier with the 5.X firmwares due yearend or early next year. -Xathros

Anytime! Happy to help. -Xathros

On Level Applied Locally set to Zero? -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