Xathros

See this thread: http://forum.universal-devices.com/topic/13909-call-for-network-resources-crowdsourcing-request/ -Xathros Sent from my iPhone using Tapatalk

OK. I'm in! I assume there in nothing more I can do till you post more? -Xath

This is how I would do this: If Kitchen KPL G is 100% Then Wait 5 minutes Enable Program Back Deck Door Open Else Disable Program Back Desk Door Open Program: Deck Door Open If Control Door Sensor is Switched On Then Send Notification Else No Action Hope this helps. -Xathros

Many of the responses I've observed seem to be cut off mid sentence. I'll try to post an example later. -Xathros Sent from my iPhone using Tapatalk

Excellent. 1) At the moment, there is no way to process responses from network resources. UDI is working on the next generation firmware for the ISY (V 5.x) that is due to go into beta around the end of this year. The ability to read responses as well as the ability to use variables within network resources is planned for the new firmware. 2)I don't know why the ISY truncaates the response message and I don't believe there is any way to change that. Hopefully with V5.x, that will be resolved. -Xathros

Anytime! As always, Happy to help. -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