Xathros

Change the port to 8080 like in the URL that works? Check Encode URL Increase timeout to 1500 -Xathros

Open/Close as well as any other battery powered Insteon device will NOT respond to queries as they are sleeping. They should however transmit control and status when activated assuming that are within range of a suitable dual band device. Move on to near the 2413 PLM or an access point and operate it, see if it works there. -Xathros

Triggerlinc has no ISY settable options. Triggerlinc does have jumper configurable options of: Single Node or dual node. In Single, it sends On and Off for the one node as the magnet is moved away and into proximity. In the 2 node configuration, it only sends On commands (For the Open node when the magnet departs and the closed node when the magnet is returned) The above is from memory but I believe is accurate. -Xathros

Make the dim button a responder to the scene with the main on/off buttons but set the on level for the dim button to 0. This way if you turn on or off the main scene, the dim button will be turned off. No program necessary. -Xathros Sent from my iPhone using Tapatalk

Personally, I wouldn't expect ANY battery powered device to be queried at startup or during the 3AM query run. -Xathros

I do something similar for the perimeter mercury vapor lamps at the office. I use a 110V plugin module to drive a contactor for the 220V running the lamps. -Xathros

As it should be. -Xath

As always, happy to help. -Xathros

I was not aware of that ability. Thanks for the useful tip! -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