PurdueGuy

This can also be done with DSCLink since version 1.1.4. There is a repeater option in the config to send all DSC alarm data though the relay server. I know, but this program gives status and control. I can arm/disarm directly from it, see when sensors tripped/untripped, etc.

I also run the DSCLink to go between my RaspberryPI and Envisalink. I added 1 extra software piece, so I could allow multiple connections to the Envisalink. It allows multiple connections, and runs a web server that you can easily access via smartphone. More info here: http://forum.eyez-on.com/FORUM/viewtopi ... 33a961d4c0

You can control the light directly from the Admin Console? Can you run the program again, but with the Event Viewer set to level 3?

UDI has the upgrade price of $129 here: http://www.universal-devices.com/sales/products/ You can email sales@universal-devices.com, or Michel might reply here.

I've read the programs, but I am not exactly sure what you want. Can you describe that without programs? This is what your programs do: A) At sunrise + 1 hr, set it to 90% At sunset - 1 hr, set to 90% C) At 9 PM, set to 50% D) If you run the KPL fast on/off or the stairs fast off, set to 50% If those are running as you want, then you could combine A + B into: If Time is Sunrise + 1 hour Or Time is Sunset - 1 hour Then Set Scene 'Hall and Foyer / Hallway Stairs 90%' On Else - No Actions - (To add one, press 'Action') However, if your real desire is something different, like: A) From Sunrise+1hr to Sunset-1hr, keep the lights at 90% From Sunset-1hr to Sunrise+1hr, keep the lights at 50% that would be a different set of programs.

I will try to call the Insteon support line this Friday to ask about it. Unfortunately, both of my new KPLs are in my roommates room, so it's a pain to get time to test. I posted about this on the SmartHome forum, and there are a few other threads. Seems to be an issue. http://www.smarthome.com/forum/topic.asp?TOPIC_ID=14530 https://www.smarthome.com/forum/topic.a ... C_ID=13594 I answered that in my response earlier with "when I push the KPL button, the individual button light (not the overall KPL backlight) turns and stays on, and the event viewer shows a DOF being sent out." Yes, doesn't seem to help with some of these new KPLs. With older KPLs, that would fix it. The buttons behaves normally. My other devices that work correctly with non-toggle-off will blink twice I think, then turn off.

I know that ISY "knows" the state of things, and adjusts its own state based on traffic is sees on the network, and how things should be after afferent events, and that the new state isn't based necessarily on direct traffic. The button is set to non-toggle-off, and when I push the KPL button, the individual button light (not the overall KPL backlight) turns and stays on, and the event viewer shows a DOF being sent out. On other KPLs that work, the button is set to non-toggle-off, and when I push the KPL button, the individual button light (not the overall KPL backlight) turn, flashed a couple times, and turns one...and the event viewer shows a DOF being sent out. I simply have a couple KPLs (reported as "2334-2 KeypadLinc Dimmer 8 buttons v.43) that refuse to play nicely with the non-toggle-off settings. Take button 7, it is set up as a Controller of nothing, and a responder to a single scene (which has the levels set to off). That program is as follows: If Control 'Devices / Guest / KPL Wall / KPL Wall.7.NS Off' is switched Off Or Control 'Devices / Guest / KPL Wall / KPL Wall.7.NS Off' is switched Fast Off Then Wait 5 seconds Set Scene 'Scenes / Guest / Guest Off LEDs' Off Else - No Actions - (To add one, press 'Action') If I have the program enabled, and click the KPL button 7, the individual button lights up, the program run, waits 5 seconds, sends the scene command, and the button goes out (the 5 second wait is just to allow any other traffic to clear, since I wanted to troubleshoot anything else). If I have the program disabled, and click the KPL button 7, the individual button lights up, and stays on.

These KPLs are not responders to other programs or scenes. They are the only controllers. Even if I don't have another device in the scene, they still don't turn off. ISY thinks they are off, but they aren't. If I run a query, ISY will then show them as on.

I have seen the same thing. I have buttons set to non-toggle-off, and I verify via the Event Viewer that they send DOF/DFOF. However, the lights stay on. Sometimes a factory reset followed by a restore device gets it correct, but not always. The most recent problems seem to be with the new Dual Band dimmer KPLs. I have 2, and they never seem to want to cooperate. I got to the point where I put the non-toggle-off buttons into a scene, and when any of them is activated, I want 5 seconds, and send a scene off to turn them off (a band-aid, I know).

If memory serves: 1) press the Off button 2) press/hold the Set button until it beeps 3) press/hold the Set button until it beeps (2nd time) 4) press/hold the Set button until it beeps (3rd time) That essentially puts it in non-toggle-off and it won't come on.

You verified there isn't a scene you forgot about? Or a program? To check the device, in the Admin Console, click the device, and check the right side for a section called "Membership." That will tell you what scenes a device is a controller for, and what scenes it is a responder to. To check for programs, go to Programs -> Summary, right click on any program, and choose "Find/Replace," locate the responder in the middle drop-down, and click "Find." Any programs with that device will be highlights, and you can check them.

If you don't want to use non-toggle buttons, you should be able to set the level of any button as off. Remember that when you add a KPL button as a controller, you might have different levels for the main scene (controlled by ISY) and the scene that the KPL button has. If you set the main scene to have devices the way you want, then you can click on the controller for that scene (red italicized text), and click "Copy Scene Attributes From "

Correct.

You would do that if you are using a program. If, however, you want to use an Insteon scene instead, check here: http://wiki.universal-devices.com/index ... TEON:Scene An Insteon scene will be quicker to respond than a program.

It could be either. If you leave it as toggle, you can allow it to turn all the devices on or off, depending on the button state. Each press would alternate between the scene selected and all devices in the scene being off. If you have it set to "on only" then every button press will result in the devices going to the scene as desire. If you have it set to "off only" then no device can have any level other than off...if you go that route, you would have to use a program to set the desired state of the lights.

To add to what Michel said, you can also create a scene, with that KPL button as a controller. You can then set the desired on/off/dim status for each device independently (and fade rates for dimmable devices).

Usually you drop the leading zero, at least for REST commands, etc. Try: Basement ..... ${sys.node.24 7 6D 1.ST} Bedroom 1 .....${sys.node.24 7 38 1.ST} Bedroom 2 .....${sys.node.24 8 58 1.ST} Bedroom 3 .....${sys.node.24 8 D7 1.ST}

I have a DSC system with DSCLink. DSC has a zone definition (26 I think) for Home Automation. That won't trigger an alarm, but you can have it trigger chimes, etc. Then with DSCLink, it can trigger events in ISY. If you have an EnvisaLink to run your DSC connection, you can setup zone followers for some key motion sensors.

In this case, if you only have 1 button and it is never called via another scene, then using "If status" is ok. However, if you introduce other things that could turn this KPL on and off, you'd probably want to use the "If control" instead. That way, only physically pushing the KPL button will kick off the program. For instance, I have a "Away" button on 2 KPLs, 1 at each door. I can hit either of them, and kick off my "Away" program, which uses the "If control" method. That program will turn off both KPL (to keep them in sync or if I ran from a mobile app). If I used the "If status" it would run twice, nearly immediately. Once when I hit the first button, and again when the ISY turns off the second (note, it might be fast enough the program runs to completion or it might be interrupted). In my case, running twice might cause issues with my alarm system commands, etc.

I can access the folders via their ID. I have a folder called "Downstairs" which is program ID "000E" I access it via: https:///rest/programs/000E That shows all my folders in that program.

You didn't read my post. I actually agreed with you for some things. And for the record, I do NOT use Vera as an intermediate for variables/virtual devices that the ISY lacks. Vera is simply becoming a passthrough for the mobile apps that I like and use (HomeWave and AutHomationHD). Many of the plugins developed for Vera are to overcome lack of conditional logic (Combination Switch, Vacation Ghost, Smart Switch, Countdown Timer). I never used PLEG since I would write my own LUUP conditions, so I can't comment on that. As for abstracting some things away, the plugins can help (such as the SQBlaster plugin), but whether I put the same HEX string in a Vera scene or an ISY network resource, it's identical...6 of one, half-dozen of the other. And I am enthusiastic about ISY not just because of conditional variables, but also support and updates. 2 years ago Vera was great. Now I have outstanding Vera bug reports and trouble tickets...no resolution, no movement. Z-Wave with ISY is still beta, but I fully expect it to mature and be just as good as Insteon on ISY.

Is this a 2342? A 2444 is a Micro Open/Close Motor Control. If it is a 2342, did you put the remote in link mode first?

That's the great thing about ISY. Put anything program you want in a folder, a give that folder conditions. They can be something like:if ((Home==0 & Vacation==1) or (Home ==1)) My "Home" variable is set by either:- setting it via a program directly - program runs by pressing a KPL button that turns off the house - program runs by the alarm going into away mode - program runs by unlocking a z-wave deadbolt via a PIN My "Vacation" variable is set by a program. I have a program that is exposed as a scene in Vera. Programs are also callable directly from an HTTP URL via the REST API. Create a program that sets the variable, and another that unsets it. Variable are definitely exposed via the REST API, but I am not sure if they are exposed via SOAP, but I would think they are. Virtual devices actually make it harder. A UI/Mobile App developer needs to know about each type of device. Add a new type, and you need to add support for it. If it uses native ISY variables under the hood, they could update those, but that's doing it somewhat blind. I can see basic virtual devices for setting native ISY variables (you could do a home/away/vacation mode easily), but I personally wouldn't want virtual devices to contain their own variables. That could end up being a spaghetti mess that developers have a hard time developing.

I use Prowl for notifications from ISY. The app is $2.99, but no monthly fees.You can then send direct messages via Networking Resources, or via email.

What is the "Front Spot light program" doing? Or more appropriately, what is your end goal? We'd need all programs defined, and what you want them to do, so we can evaluate what is happening.