Xathros

Hi creeble- You will need to ad an exception for the ISY to your Java control panel. the 99i can only be upgraded as far as 3.3.10. 3.3.10 still does not include the necessary information that the new Java is looking for and will continue to require and exception be in place. Here is the info for adding an exception: Add ISY-99 to exception list with Java 1.7.51+ With the advent of Java 1.7.51 and up, Java applets are now required to contain a manifest file. Those that don’t are now not allowed to run unless you make a security exception for the applet. UDI has released newer firmware (4.1.2) that includes a manifest file and meets the new requirements. The ISY-99 series is not receiving firmware updates after firmware 3.3.10 as it has run out of room for the larger code in the newer firmwares. If you have decided not to upgrade to the ISY-994 series controllers, you will need to work around the new Java requirements and add an exception for your ISY-99i. Here is how to make that exception. MAC: Open System Preferences and double click the Java icon. In the Java preferences, click the security tab. Click “Edit Site List†Click “Add†and enter the URL for your ISY. Acknowledge the warning that this poses a security risk by clicking “Continue†Click “OK†then “OK†and close the Java preferences window. Windows: Open the Windows Control Panel Double click the Java control panel applet. Click the Security tab Click the “Edit Site List…†button. Click the “Add†button and enter the URL for your ISY-99i series controller. Click “OK†and close the Windows Control Panel†This should get you back up and running until you can upgrade to an ISY-994 and the newer firmware. UDI is currently running an upgrade special for owners of the 99i. For $99 you can replace the 99i with the current 994 model and transfer any purchased modules that you have on your 99i. You should seriously consider upgrading to the 994 as already, some newer Insteon modules are not supported on the 99i. Hope this helps. -Xathros

I suspect an issue with Firewall and/or Antivirus. Likely an update applied a few weeks ago changed something. Try temporarily disabling your AV/Firewall and see if the problem is resolved. If so, you will need to add an exception for the ISY to your software. -Xathros

A 4 (or more) way is identical to the 3 way in wiring. You are simply linking additional controllers. -Xathros

In the settings icon (crossed tools) under Lighting Controller, tap to resync with ISY - select UPDATE ONLY -Xathros

Set a static ip for the ISY and use 8.8.8.8 for DNS. Then try again. -Xathros Sent from my iPhone using Tapatalk

I think if you look at the whole network at the top of the tree, you can sort the list by the Insteon address and it will group the buttons that way. I believe they will be listed in A-H order. -Xathros Sent from my iPhone using Tapatalk

No worries. Your always welcome to jump in. -Xathros Sent from my iPhone using Tapatalk

Glad you got it sorted out. As always, happy to help. -Xathros Sent from my iPhone using Tapatalk

Exactly what Lee said! -Xathros Sent from my iPhone using Tapatalk

Change And to Or. Your program says If time is 9:30 AND the value of s.Vacation is 0 So lets say at 9pm the variable changes from 1 to 0, the program triggers and the if is evaluated and runs false (Else) since the time is NOT 9:30 Change the and to an OR - the program will trigger and run true at 9:30 or anytime the value of s.Vacation becomes 0 Make sense? Now, that question makes me think that you have multiple programs for different times of day that might all trigger at once if coded this way. If so, you might think of coding a time range instead: If Time is From 5:00pm to 9:30pm (same day) AND s.Vacation = 0 Notice, I used AND instead of OR here - because of the range rather than a specific time. This will run true at 5:00 as long as s.Vacation is 0 and anytime between 5 -9:30 when s.Vacation becomes 0 -Xathros EDIT: If you need further assistance tonight, make sure to quote my post or mention @Xathros in your reply so I get notified by my phone otherwise, I won't see anything here till tomorrow morning.

Nope. It triggers at your times and anytime the state variable s.Vacation changes value. Once triggered the conditions are evaluated and either Then or Else is run. Remember, a state variable will trigger and if statement that refrences it when the value changes, and integer variable will NOT. That is why it was critical for s.Vacation to be a state variable. the "s." at the beginning is just a voluntary nameing convention that some of use use to identify a variable as a state type. I name my integer variables with "i." at the beginning. Makes debugging a bit easier down the road. Remember, the ISY is event driven. Its all about the triggers! Hope this helps. -Xathros

Well, you could include the variable test in your Ifs. That way when the state variable changes at 4:00, the ifs are triggered and evaluated. If ( On Mon, Tue, Wed, Thu, Fri Time is 3:45:00PM Or On Sun Time is 11:00:00AM ) and $s.Vacation = 0 Then Set 'Kitchen Thermostat-Main' 68° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') -Xathros

No. your new ZWave device should appear at the top of the tree as soon as the Linking window is disappears. -Xathros

62vetteefp- I think I see what you are trying to accomplish here. You can use the same state variable for your home folder that you use for your vacation folder simply testing for a 0 instead of a 1. Then create the following program to watch for your FastOn/FastOff commands at your switch: If Control '24.7A.16.1 outside driveway' is Switched Fast On and Control '24.7A.16.1 outside driveway' is not Switched Fast Off Then $s.Vacation = 1 Else $s.Vacation = 0 This program will set you to vacation mode with a fast on and to home mode with a fast off. Note the IS NOT in the second line of the If. It causes the ELSE clause to run when you issue the FastOff at the switch. Use: If $s.Vacation = 1 for your vacation folder condition and If $s.Vacation = 0 for your home folder. Hope this helps -Xathros

The scene must be setting the button Off when the KPL is the scene controller. I would look at the scene definition in the ISY and check the on level for the KPL button LED for the scene with the ISY as controller and the KPL as controller. I suspect you will find the On Level with the KPL as controller (KPL button selected on left) is set to 0 and with the ISY as controller (scene name selected on left) is set to 100. I don't believe it makes a difference what state the button is in when you set the toggle mode. -Xathros

LeeG- My newest V43 KPLD behaves as the older KPLs behave in Non-Toggle On and Off modes. Unfortunately, the setup on my one and only V43 was done using "Replace with" after an older KPL died so I did not follow the OP's procedure for setting the Non-Toggle button modes. My gut says there is more to the story above and the KPL button may be in Non-Toggle Off rather than On mode. -Xathros

I did set up 8 or 10 custom behaviors to turn on / off lights, on/off tv, lock doors etc. They all worked but until I can send these commands from the local network, I have stopped using them. Right now it requires exposing the non secure http port of the ISY to the internet and sending your login credentials in the clear across the internet. I find this totally unacceptable. After posting a number of times on their site, I have found the lack of response from the developers there to be quite disappointing. Maybe I'm just spoiled by this community but it doesn't seem like the UBI folks are listening to their community at all. I am very interested in the technology and premise of the UBI and I will han on to mine for a while in the hops that they do improve the feature set and get their act together. -Xathros

If your cache was actually at 32Gb, it might take a minute or two for the empty cache process to deal with that. Not sure as I have never tried to clear that large a cache! If you can't get past that, download and install Onyx and run it's maintenance routines. It will clean up lots of things including the Java cache. http://www.titanium.free.fr/downloadonyx.php Hope this helps. -Xathros

In addition to what Lee said above, the solution to this problem is to move the then section to a separate program to avoid the wait interruption at sunrise. Your Current Program (Modified): If From Sunset - 30 minutes To Sunrise (next day) And ( Control 'M1-Sensor' is switched On Or Control 'M2-Sensor' is switched On Or Control 'M3-Sensor' is switched On ) Then Run Program 2 Then Path Else - No Actions - (To add one, press 'Action') Program 2: If Then Set Scene 'Motion Response' On Wait 2 minutes Set Scene 'Motion Response' Off Else - No Actions - (To add one, press 'Action') This will resolve the issue unless you are having comm problems with the lights. Run a few scene tests to see if you have reliable comms with these lights. -Xathros

Anytime. Happy to help. -Xathros Sent from my iPhone using Tapatalk

No. I believe that the 3am query or any other large batch of Insteon traffic can cause the ISY to queue up other activities like network tasks until higher priority tasks are serviced. -Xathros Sent from my iPhone using Tapatalk

Based on their names, that would be a good guess and I must admit that was my first impression as well. The actual difference is: A state variable will trigger an if statement when its value changes. An integer variable will not. Otherwise they are the same. -Xathros Sent from my iPhone using Tapatalk

On the variables page, there are two tabs (integer and State) this variable needs to have been created on the State tab for a change in value to trigger a program. Integer variables do not trigger on value changes. The init is the initial value the variable will be given at power up or reboot of the ISY. Both Integer and State variables have both a value and an init value. -Xathros

I'm not sure. I find the documentation for these micro modules confusing at best. Without doing some specific testing, I can't say for sure. If I get some time this weekend, i'll try to do some testing. I have a spare micro module to play with so it shouldn't be a big deal. -Xathros

KMan- Thanks, Yes I just missed typing the $ prefix on the variables. 62vetteefp- You don't really need another folder - just a program: If $s.Vacation is 1 Then Set 'Kitchen Thermostat-Main' 60° (Heat Setpoint) Set 'Master Thermostat - Main' 60° (Heat Setpoint) Set 'Upstairs Thermostat - Main' 60° (Heat Setpoint) Else - No Actions - (To add one, press 'Action') -Xathros