ryarber

I'm salivating over this feature as well as the ELK module. I already have an EZFlora. The timing of this feature is great.

This is a new device by Intel that will help keep up with energy usage http://www.itworld.com/business/104578/intel-sensor-records-all-home-power-use-one-outlet See what you think.

This, IMHO, makes scenes much more versatile. You can not only vary how the scene behaves as a whole, but you can also vary how each individual scene controller effects the scene. This way, you only might need one scene for bathroom light control, but the scene can behave differently based on which controller triggers it. You can also have an entirely different behavior if the ISY activates the scene via a program. There's a lot more functionality to scenes than meets the eye.

So how about a follow-up? Did you get it to work? It should.

There is a much better way. If you have the jumper set up to only send on commands, then set up a scene with the MS as the controller. This will eliminate the aggravation of the lag time ti takes for the program to activate the light. The MS will turn on the lights, but it can't turn them off. You use a program to turn it off. Do away with your old programs and write new ones using the "set scene" command in the ISY. At something like sunrise , you can have the lights gently come on with a ramp of say 90 seconds to 100%. At something like 9 AM , you can set the ramp to your standard 2 second ramp. Then at midnight, you can set the light level to 20%. The ISY sets the levels and ramp rates via the programs. You need to know the set scene command needs to be se up using the motion sensor's name as the controller and not the scene name. If you use the scene name as the controller, it will not work like you want it to. I think you'll like this method much better. You'll Lso need to set up a program such that the lights will be turned off after a set time. It is a simple program. Itshould look like this. When Conteol 'Bathroom motion sensor' is switched on then Wait 10 minutes Turn 'bathroom light' off When the program is running, triggering the MS again will restart the program and keep the lights on as long as it is sensing motion.

I have been using the "set scene" feature in programs to change the way my motion sensors control the lighting. It has been working beautifully until recently when I began noticing my scene changes weren't being written to the device. After scratching my head a while, I finally realized that I had disabled the "automatically write changes to devices" button. In essence, my program was being blocked because the ISY was holding the changes until sent manually to the devices. It would be nice if there were an alert that pops up when you disable the "auto write to devices" that tells you this will screw up your programs if you do this.

I'd like to be able to see product updates and software releases via Twitter if you have it set up. If not, would you consider it please.

They do sell the icon series which is much less expensive and works well as controller switches. Also, if you are just looking for a controller, you might consider a remotelinc. No wiring necessary, you can put it wherever there is a table to set it on. In addition to portability, they offer more control options for a v2 thermostat

If I'm understanding you correctly, you want a dummy (non load) switch to turn on 3 lights, but only turn off 2 of them? If so, the way I'd accomplish this is to set up a scene with the new switch as a controller and the 2 devices you'd like to turn on and off as responders. I'd use a program to activate the 3rd device whenever the new switch is turned on.

The main caveat that you will see with my method is that during the daytime, by adjusting scene levels, activation of motion sensors will turn the devices off. I haven't really tried using the night only jumper with my scenes yet because I have only a need to turn lights on at night and I don't want them coming on at all during the daytime (outside lights). I have another MS inside that this may be an issue with. I may play with setting it up like this to see if it will work, but with indoor use, the motion sensor's day/night settings will be off. Here's a question for Michel. By adjusting the day/night sensitivity settings, are you actually changing the time the motion sensor can be triggered if you have the jumper set to only send on commands after dark?

While we're on the topic of adding links, I'd like a link added to the .jnlp file so that after upgrade we don't have to type in that address every time.

You are a lucky man indeed. I wish my wife were that easily pleased.

From a mac, I'm getting "upgrade failed: invalad length"

There is another way I think you could accomplish this. If you remove the time from the program's "If" statement and then put the program in a folder. You add the time statement to the "If" statement of the folder. The program should remain true then, but it wouldn't execute until the folder condition turns true at 11:45.

One of the main obstacles in my thought process I had to overcome was thinking I wanted to keep my number of scenes to a minimum. These devices will allow more scenes than you will ever use, so why not take advantage of it to make programming easier and more flexible. Using scenes also makes things work much quicker and you don't have to worry about signals colliding. It opens up a whole world of possibilities. Bottom line, don't be stingy with scenes.

If Control 'Back Patio-Sensor' is switched on AND Status 'Back porch dummy' is off Then Wait 20 minutes Set Scene 'Back Patio Motion' Off Else No Action I have a scene called Back Patio that is controlled by the 'Back Porch Dummy' switch (named as such because it is a non load switch used only as a scene controller). I have a second scene called Back Patio Motion that is controlled by the motion sensor. They have the same responder devices (two flood lights and some can lights). If I switch the Back Patio scene on, then the 'Back Porch Dummy' switch is on. I use the status of the 'Back Patio Dummy' switch to tell the ISY the status of the Back Patio scene. Therefore, if I want the lights to come on and stay on, I make sure that I turn on the Back Patio scene. That way the motion sensor will not be able to override and turn the lights off. If this dummy switch is off, the motion sensor program should work normally to turn off the lights after 20 minutes.

Another thing I have done is created a distinct scene for the motion sensors apart from the usual controlling switches. That way it doesn't interfere with the normal operation of the switches that normally control the scene. I also use the controlling switches for the scenes as indicators of the status of those scenes. So if I have a scene already on and the motion sensor triggers the scene, the program that turns off the devices won't turn them off if it sees the dummy (controller) device on. If that doesn't make sense, I'll try to post the code and make it clearer.

I could see the possibility of writing a program that would just notify you once for a tornado warning and then reset itself after the tornado warning or watch has passed. This could even be easier with variables. With the ELK M1G's ability to give audible messages/alerts, this feature would be quite useful when integrated with the M1G.

CMartin: You should read http://forum.universal-devices.com/viewtopic.php?t=2922 This is something I hadn't considered until learning about it recently. You can just have your motion sensors trigger the scenes, but adjust the scenes according to the time of day by running the "Adjust Scene" action via programs in the ISY. That way, you have the best of both worlds.

Here is an example of how I use my motion sensors with the 4th jumper on (both pins connected). I have outside lights that I want to come on instantly with the motion sensor so I have the motion sensor set up to control a scene (setting programs to turn on a scene based on a motion detector leads to a delay of 0.5 - 2 seconds). However, I don't want the motion sensor's off command to turn the scene off, I'd rather the ISY do that. So this way, I have the motion sensor trigger the scene to turn on, but not off. If the motion sensor sent an off command, the scene would turn off. Having the ISY do this, I can be much more flexible about how long I want things to stay on and which lights I want to turn off and when. I also want to add a word of caution and make you aware if you put a motion sensor under an eave, it will often think it is dark before it is actually dark. I don't use the dark only jumper because I find the ISY much more accurate by specifying sunset and sunrise times rather than lumens at the motion sensor.

I'm not sure you understand what I'm saying. What I'm referring to is setting the jumper to only send on commands and then add the motion sensor as a controller for a scene. That way a scene could be turned on by a MS, but would have to be turned off by a program. Doing this, there would never be a "switched off" event from the MS to trigger your program. There would only be "switched on" events. Your program above would only work if the motion sensor could switch on and off, right? If what I'm saying is right, and if you set your MS up like this, would there be a way to restart the timer if another "switched on" event is sent from the MS? Another question.... Will the set scene command work for dimmers only? IOW, if you have an on/off relay switch in the scene, it would only turn on with the scene on command wouldn't it?

Would it be possible to link the MS to a scene and set it to send only the on command via the jumper and then control the off sequence with programs? That would give you the best of both worlds. The on sequence would be immediate, but the off commands for the scene would be controlled by programs on a timer. The only caveat I could foresee is that I can't see a way to restart the timer if there is no off command ever sent by the MS. Could the ISY be programmed in such a way so that a subsequent On command by the MS be used to restart the timer if a program is already running?

Nevermind, I think I found a solution from other threads. Here's what I came up with.... For the on statement If Control 'driveway motion' is switched 'on' Then Set Scene 'driveway motion' On Else For the Off command If Control 'driveway motion' is switched off And Control 'driveway motion' is not switched on Then Wait 14 minutes Set Scene 'driveway motion' off Else I think this will work the way I want it to.

I evidently don't understand the timing and conditions very well for setting up motion sensor programs. Please help. What I want to do is when my driveway motion sensor comes on, I want to turn on a scene of outside lights. I want that scene to go off in 15 minutes if no further activity is sensed. Can someone help me with a program to accomplish this? I thought I understood this, but evidently I don't. Here's what I had set up. When Control 'driveway motion' is switched 'On' AND 'driveway motion' is not off Then Set Scene 'driveway motion' On Else No Actions To turn off the lights, I had this program set up When Control 'driveway motion' is switched 'Off' AND 'driveway motion' is not On Then Wait 14 minutes (there is a 1 minute delay before the motion sensor turns off) Set Scene 'driveway motion' Off Else No Actions Please help. Thanks.

Getting error messages when logging on stating cannot connect with xxx device. I'm getting two of these messages when I log on. One of the devices has a red ! (a controlinc) and the other doesn't (lamplinc). It keeps happening every time I log on despite the lamplinc never having the red ! and it is query-able. This behavior seemed to be better under 2.7.10, but since upgrading to 2.7.12, the problem seems to have returned to the way it used to be in 2.7.6 and before.