arw01

Michael missed an i in the 99 part of the url put that i in there and you are good to get the dashboard. http://isy.universal-devices.com/99i/3. ... board.jnlp However, my windows 8 machine won't actually run it as it says it has no program, even though Java is installed. What is the actual application path and file name that would run the dashboard.jnlp program?

Why not just use a program to adjust the level it is turned onto. Buy one of those new micro modules and use a scene where you don't have to re-program anything.

Baa, you are no fun! Do you suppose you could use this little beastie to tell if your TV is on? INSTEON Micro On/Off is compatible with latching, single momentary and dual momentary switches. By default, it comes programmed for latching switches such as paddles and toggles; it is easily configured for single and dual momentary switches with a simple reprogramming procedure during installation. Due to its hidden nature, we highly recommend using a home management controller (such as HouseLinc) or the free INSTEON app with INSTEON Hub to manage Micro Open/Close. How would it know what was turning on, a 7 watt led, or a 30 watt LED tv?

very small, just reading about them. Michael, now that they are public, tell us all about them! Your NDA should be void now.. http://www.smarthome.com/2444-222/INSTEON-Micro-Open-Close-Module/p.aspx

Did I mis-read the specs where it said it works on 24 volts? Why not a simple reed switch separated by some foam. When you sit it closes down and the reed is close enough to activate.

Thank you. Michael, I would like to see a message that tells me the clock was set (maybe the difference in time) when I manually do the sync. Also, how about showing on the configuration screen the last time it synced the time please. Thanks Alan

Well done video. Would like to see it at much higher resolution. Curious about the keypads used in the video. And especially the mention of in the ground moisture sensor that works with the irrigation.. Thanks Alan

Well the status didn't seem to be helping keep the lights on while I moved around the basement. The control method I have watched, as another astute member posted above, the summary tab confirms every 10 seconds it sends another motion on and resets the program timer. I would like to thank you again for your extreme patience getting the way it works through. I should bookmark this thread to re-read in the next day or so and really get it all sunk in. Alan

Tom and Michael, maybe I missed it and feel free to ignore the noise if I did, but how about running some checksums on the file(s) zipped and unzipped as well. Could Tom have some firmware in the ISY that is a little flaky maybe, a EEPROM that isn't reliable. Any way to run a MD5 on that file itself on the ISY?

Another thing that will be nice, is when the tv api's open up a bit with all the "skype" cameras they have to know if they think the rooms are occupied as well.

Most excellent. Certainly a wiki worthy post there, and I think maybe, just maybe I have it. The timer has been set to 5 minutes so I can see if it works as intended this time and does not shut off the lights while I am down here moving around. I have tweaked my occupied basement program to: If Control 'Motion_Media-Sensor' is switched On Or Control 'Motion_Stairs-Sensor' is switched On Or Control 'Basement_Stairs' is switched Off Or Control 'Media_Exercise' is switched On Or Control 'Media_Middle' is switched On Or Control 'Basement_Stairs' is switched On Or Control 'Media_Popcorn' is switched On Or Control 'Media_Middle' is switched Off Or Control 'Media_Keypad' is switched On Then $OCC_basement_svr = 1 Wait 1 hour $OCC_basement_svr = 0 Set Scene 'Basement_Off' Off Else - No Actions - (To add one, press 'Action') 60 minute timer for any motion in the basement, if no motion in that time, turn off all the basement lights I am sitting here watching my motion sensor Media. I watched the ISY update to on status and am just waiting on the time out now. I have confirmed the dogs do not activate the stairs sensor as they race up and down the stairs to bark at the no see ums. The time out has come and gone and the status updated to off. Here is how I have that motion sensor configured:

I will check that lee, I think I have them sending on constantly with motion. Reading some wiki entries, some threads, I still cannot quite get my head around the non-standard way the ISY deals with the if then else process. After reading I understand the program will get re-evaluated when the device changes status if you use status. And will get re-evaluated with control if the particular control test occurs. Thanks to an example from the wiki, I know understand that control device is not off causes the if to evaluate for on, brighten, dim as well. Oh well, will sleep on this one and see if I can get my head around it tomorrow!

I have moved mine around a few times lately doing some programming on old swiches that are not happy with access point versus having the PLM into the same outlet that feeds those switches with hot. No issues, just don't forget to plug in the plm or you will be wondering why your switches are not reacting to programs all of a sudden.

So what do you have your tasker do for you? And how quickly does it react when you get into an area that you set the parameter for?

you create a scene, assign the kpl button to it and set the scene off.

I am still struggling with when it will evaluate the if statement. Also my logic here does not work as I expected as I was moving all over the basement and the lights went out on me. The motion detectors SHOULD have kept that wait restarting a few times unless I don't understand that either. I was expecting any motion status to re-do the then clause. So if after 5 minutes I trigger the motion status on again, it would restart the wait. If we simplify this to make it easier for me to get my head around. If status motion_1 is ON Then start the timer Else nothing I think it should run that timer when I see the red light on the motion signal my motion. Then each time I see the red light on that motion sensor again, then it should redo the THEN causing the timer to start over?

Just a thought form a fellow newbie, but I would set the on level with a program and not the motion sensor trigger itself. I would just use the motion to turn on the scene. Then the program can adjust the level at the times it is supposed to. You could put a test to see if the light is on already, and if it is, then put a wait for x minutes before you adjust the scene. I do not know, if adjusting the scene level while the light is on would affect the light. I have not tried that yet.

It could also just be a loose wirenut on the connections.. a bulb that has a little bit of a weak fillament if it is not CF. Move it and see if it follows, but I would check the wirenuts myself.

I think I have it. The program does not run at all unless one of those devices has an event, regardless of what the event was. So if by theory, I could sneak around the motion detectors, and trigger a device in the if clause with a off that was not part of the if's, then the else should run? Alan

Oh do tell.. the little 50 cent tags you can put your phone or tap against to get them to "activate"? Share more on your tasker set up and the challenge you speak of here please. I am guessing that tasker opens the browser to send the command and then that tab is left open and you have to come along and close it manually?

can you show us a screen print of your scene setup with the sliders etc..

I don't understand why the else is not triggered automatically. When I ran the if statement manually the else triggered. Anyways I think I had a logic error there. I wanted occ_basement_svr to be true whenever the timer was running, so I have set it true before the wait starts now instead of trying to use the else clause. I assume that is because the program does not evaluate dozens of times a second like I was used to with the misterhouse perl loop we I used to use before buying the ISY to make life easier on me and my wife. That else clause would only occur if I ran it manually or used another program to run it. If Status 'Motion_1-Sensor' is On Or Status 'Motion_2-Sensor' is On Or Control 'Basement_stairs_OH' is switched On Or Control 'Media_Exercise' is switched On Or Control 'Media_Middle' is switched On Or Control 'Basement_Stairs' is switched On Or Control 'Media_Popcorn' is switched On Or Control 'Media_Middle' is switched Off Then $OCC_basement_svr = 1 Wait 1 hour $OCC_basement_svr = 0 Set Scene 'Basement_Off' Off Else - No Actions - (To add one, press 'Action') 60 minute timer for any motion in the basement, if no motion in that time, turn off all the basement lights

That did not work as expected. I put the else clause in, made a trip down stairs which tripped both motion sensors a few times (only verified by the red led blink), and I turned on Media Middle and then turned off Media middle. When I returned to my console the occ_basement_svr was still sitting at 0. I expected it to have been at 1 due to my hitting the motion sensors and the switch. The program was listed as RUNNING, so obviously the wait condition was active. When I manually ran the program if condition, it immediately set the variable to 1 from the else clause. If Status 'Motion_1-Sensor' is On Or Status 'Motion_2-Sensor' is On Or Control 'Basement_stairs_OH' is switched On Or Control 'Media_Exercise' is switched On Or Control 'Media_Middle' is switched On Or Control 'Basement_stairs_OH' is switched On Or Control 'Media_Popcorn' is switched On Or Control 'Media_Middle' is switched Off Then Wait 1 hour $OCC_basement_svr = 0 Set Scene 'Basement_Off' Off Else $OCC_basement_svr = 1 60 minute timer for any motion in the basement, if no motion in that time, turn off all the basement lights

Since the Else clause would indicate something happened either by motion or a activation of a switch in the list, then I should be setting the variable for occupancy to 1 in the else.

I have a couple of them, and when I added them to the ISY I told it to remove the links by accident and they didn't work anymore. I had to create a scene just for them and manually tell the ISY to put the links back in by adding them to the scene. Do up a screen show of the scene and post it up. Also an event trace might be helpful, then we know if any attempt to even turn on the light was actually made. Alan