MrBill

Are you aware that the Ramp Rate and On level are different for each controller? That is, when defining the scene setting the Ramp Rate and On level at the root level are the values that will be used when controlled by the ISY or an ISY programs. Also click each Controller listed with a RED name within the scene and set the Ramp Rate and On Level that occur when that specific controller is used. As for the program, 'Control' would be the feature you would want to use. however, if there are multiple controllers you must OR them all together and realize that "Switched On" (single tap) is different that fast on(double tap), or hold button to dim. At the bottom of this post is an example that catches all the possibilities from two different KPL buttons. With 'Status' I have the most luck using "is Not Off" and "is Off" in an If statement. ---- Manual.on - [ID 00A5][Parent 00A7] If 'DN Back Door Recessed+# / {hide}Lamp 4' is switched On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fast On Or 'DN Back Door Recessed+# / {hide}Lamp 4' is switched Fade Stop Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fast On Or '{hide}OUT Lower Fans - High / {hide}DN Lamp 4' is switched Fade Stop Then $Dim.Lamp4 = 101 Else - No Actions - (To add one, press 'Action')

I wonder if you've reached the maximum number of nodes? Do you have a pro or non-pro ISY? Max nodes non-pro = 254, pro=1023 There is a ISY Inventory node server that will count for you, but if you can't load new nodeservers that's not going to help. If non-pro, you can upgrade to pro version, its a soft upgrade, no new hardware required.

Waits are interrupted anytime an event happens that causes the IF to be re-evaluated. If you always want the wait and action to occur another method is: Program 1 IF some condition Then Run Program 2 (then) Else (none) Program 2 If (none) then Disable Program 1 wait 2 minutes turn off Enable Program 1 Else (none) Or if you want the time to always be extended, that is 2 minutes from the last activity in program 1 then omit the Disable and enable in program 2.... which will cause the timer to be restarted, by program 1 with more switch activity, but will always eventfully end the 2 minute wait and turn off the device.

This is how I dim scene's via Alexa: I'd do the Launcher First, that way it always starts the admin console with the correct version, both before and after upgrade. Note: If you have an older Z-wave board, do not upgrade to version 5.3.1, or for that matter any version past version 5.0.16C. How do you know if you have an older 300 series Z-wave firmware? Look at the back of your ISY, next to Port A If you see a BLUE LED or round dot then shine the flashlight on your phone at the round dot, is it a BLUE LED? If YES, the farthest you can upgrade firmware wise is 5.0.16C. If you wish to move to 5.3.1 you need to upgrade your Z-wave daughter board first, UDI has special pricing based on the age of your ISY.

Glad you worked out your issue. Note however that Firmware and UI versions should match. While there are various ways to run the Admin console the best method is to use The Launcher which will ensure that you start the correct version of the UI... Follow the instructions here to begin using The Launcher:

Factory reset and Reset UserId and password are very similar procedures. Effectively what you did was hold the button too long and perform a factory reset. Then you reloaded a backup which in turn reloaded the unknown username and password again. What you need to do is let go of the button at the point for username and password reset.

The motion sensor also has a light sensor, the program is using it as a heartbeat, its assumed that at least twice a day the dusk to dawn light sensor will change states to either on or off.

As others have said.... you need Pro for them to show up what others haven't said is that Pro is a software upgrade, no new hardware required, pay the fee and you're upgraded. Here's a chart, with the differences, largely you get the ability for more nodes, and more programs, and the ability to use batch mode which are the two buttons mentioned.

Since I don't use that nodesever I don't know but lets tag @bpwwer since he wrote the nodeserver.

Disclaimer: I'm not using that particular node server so I didn't double check that the temp is available to set as a variable. Generally however, variables can be set to numeric values available from Node Servers: Set the first drop down to "Variable", then the Variable you wish to set then use the arrow to the right of = to cycle until you reach the node view, then select the node and which value you want to save from the node. (make certain the precision (number of decimal places) of the variable matches the value being stored.)

You can also "compare links"...caveat tho, unless you understand the results it may flag a false positive. Click a device name in the tree, then right click it, Choose Diagnostics > Show Device Links table. When that table is done populating click Compare. This causes a comparison between the links table in the device and what the ISY thinks the link table in the device should be. If the only mismatch is I believe the first byte after the colon, it's not really a mismatch. To fix, right click device and Restore Device. Another technique is to factory reset the device and then click the device and Restore Device. Using the second method, you've cleared the devices memory and then restored it, without the hassle of deleting it from the ISY, readding it, and then restoring scenes, programs, etc.

Never said the browser was a server. My theory is tho that the .js script running in browser that we can see by viewing Page Source opens a database connection back to Polisy. Likely why they force https on all Polisy pages served. Mine are only guesses and theories, and I won't spitball more about my guesses. I'll be happy to test anything for UDI and assist. As I said up above the outcome at this point doesn't make too much difference to me I don't use this method to access Polisy even while traveling. I read OPs post and said "I wonder if I have that problem or can spot a solution"---so I opened my iPad and tried everything I can think of... including multiple browsers and multiple devices...the only common denominator seems to be iOS itself.

I don't think its a connection to the ISY problem. First it works from other non-ios devices just fine. Second, nodes in the ISY are updating. I've seen the red connections banner at times on my windows laptop but it also goes away by refreshing the page. Obviously the web server on Polisy is working. If I had to guess, and its only a guess, I'd bet on a database connection from code running in browser not being allowed by iOS for some reason.

You can't mix and match neutrals between different circuits. I don't see why you can't install a keypad in the unused switch location, just connect hot and neutral from the same line to it, and put a wirenut on the red lead from the switch.

The only way I've had success using Status is "Is Off" or "Is Not Off". I don't recall for certain, but I don't believe the comparative operators < > <= >= existed in the 4.x branch. They may work with some node type and may not work with Insteon.

I believe that if you don't disable them they will run every time the temp moves. Disabling them will cause them only to run when called by the time program.

I agree with your quote, but have had trouble using Status, I just looked and I have programs where if Device Status is not off then wait turn off when I used control my If bodies do tend to be complicated, such as: Manual.on - [ID 0099][Parent 0098] If '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fast On Or '{hide}Living Room Fan Lights+ / {hide}Lamp 1' is switched Fade Stop Or 'Kitchen Table Light# / {hide}Lamp 1' is switched On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fast On Or 'Kitchen Table Light# / {hide}Lamp 1' is switched Fade Stop Or 'LR Remote -Deb - A-B' is switched On Or 'LR Remote -Deb - A-B' is switched Fast On Or 'LR Remote -Deb - A-B' is switched Fade Stop Then $Dim.Lamp1 = 101 Else - No Actions - (To add one, press 'Action')

There's likely more ways to skin the cat... but I'd use Control instead of Status in that situation. The catch with control is that you need to refer to any switches that can turn the light on.... if there's only one it doesn't seem too much different, but if it's part of a scene, then you need to include all the controllers in the IF statement.

I started to reply but stopped because I figured someone else would have a better idea..... But I would break it up into several programs the First If time is 5:00 AM or time is 7:00 PM or time is 12:00 AM then Run Temp_Range_1 (if) Program Temp_Range_1 if temp <=0 and temp > -5 then set pond heater on wait 1 hour set pond heater off else run Program Temp_Range_2 Program Temp_Range_2 if temp <=-5 and temp > -10 then set pond heater on wait hour set pon2d heater off else run Program Temp_Range_3 etc........ All programs after the first should be disabled so they don't run on temp alone.

For best help with programs, right click on the name of the program in your program tree and select COPY TO CLIPBOARD then paste it in a post here. That way there is no confusion. Offhand it sounds like you need to split this program into two programs. The first watches for the conditions, and runs the THEN body of a second program, that programs first statement is DISABLE first program, the last statement is ENABLE first program.

Curious about the effects of clearing the Safari Cache I first cleared the Safari Cache on my iPhone and then tried to open Polisy. Same result as before, Polisy allows login, but does not "connect". Next I checked the Safari Cache on my iPad Pro, as I expected it had not cleared. iCloud can keep tabs, bookmarks, and history synced across devices but does not appear to sync cache. Nonetheless I then cleared the Safari cache on iPad. Then opening Polisy... Again Polisy accepts Login but doesn't "Connect". Refreshing the page does nothing. Since this holds true across multiple devices, multiple browsers, and even multiple users it appears to be some kind of conflict with iOS, I'm not sure what it would be. Personally this doesn't affect me. I do only carry the iPad while traveling but if I need admin or Polisy I would a remote desktop on a windows machine via VPN and actually can open these. When I encountered this thread tho I was curious, so I tested in 3 browsers, and now 2 devices. Sometimes I have a hunch about browser issues but this time I have none, other than it may flat out be incompatible with iOS.

Click on the button in the device tree, then look for these buttons in the admin console: Click "Buttons Toggle Mode" to reach this dialoge:

Disclaimer: There's more than one way to do this, but this is how I do it which is fastest for me. 1. first turn off device writes using these buttons in the admin console: (the one on the right is for battery powered devices so that may not apply here). Also these button only exist in Pro versions of ISY. Turning off device writes allows you to queue up all the instructions so they are sent out in one heap instead of doing everything as you click. 2. Create a new empty scene. Link Management > New Scene. 3. click the first device to add to the scene. Optionally: hold down the control key and click more devices to add to the scene. Then: right click and pick "Add to scene". At this point you will get the dialog asking if you want it to be a responder or a controller. Repeat this step as many time as needed to add all the devices to the scene. Note: If you're building a scene with many responders and few controllers it's advantageous to add all the responders first then add the controllers. If's it's a scene for 3-way or n-way switching tho, you're going to want all members to be controllers. If it's a scene that sets a scene, i.e. your All Kitchen button then you'll have multiple responders with one controller. 4. now that the scene is created and has it's members added. Click on the root of the scene or the scene name itself: on the right side adjust the dim level and ramp rate for this scene as it will be controlled from the ISY or ISY programs. THEN Also click each RED controller in the scene: repeat as above, set them Dim level and ramp rate for each device in the scene, as it will be controlled from THAT controller. The concept in this step is the hardest to catch onto for new users.... Each Controller determines how the lights will react when turned on by that controller. In my example screenshots, this is a typical 3-way switching scene. One switch at one end of the room, the other switch at the other end. But we can set default attributes for this scene when it's turned on by one switch, the other switch, or when turned on by the ISY. In other words, we set the default dim and ramp rates, for THE ISY and BOTH switches that are controllers. The ISY and programs as controllers might set 100%, the switch at one end might turn on 80% and the switch at the other end might be set so that the lights only come on at 20%. 5. Now that the scene is setup and complete configured Go back to the button in step 1 and turn it on. When you do the ISY will start writing all those instructions at once to the devices. 6. Test that the scene works as you expected. --- so that sums up basic 3-way/n-way switching types of scenes, that is where two or more switches control the same light. In that case both/all switches are controllers so that when you turn on/off one switch the other keeps the other switch in the same state (i.e. the LEDs are meaningful). --- the other type of scene is where you collect groups of devices or to preform a preset action. These scene's may contain members that are also members of other scenes. An example is this All Off scene: When building this scene we need to make everything that we want to respond a responder. If you look at the 3-way scene I used in the example at the top of this post, it had DN Recessed OH (Kitchen) and {hide} DN Recessed OH (kitchen) as controllers. In this "ALL" scene those devices are both included but they are responders. (note: if your wondering about the {hide} labels they are a holdover from when I used Mobilinc, they remove that item from lists in that app). In this scene literally everything on the lower level is included, whether a switch or button on a keypad. In this case I didn't actually configure all of these devices to be off in the scene tho. It's actually just a standard scene, it could work for on or off if I wanted it to. What makes this special tho, is when I added the controller which is a button H on an 8-button keypad I changed the button toggle mode for that button to be Non_toggle Off... in other words when this button is pressed it always sends Off. In this case the controller never sends on, it only sends off. In your "All Kitchen" scene you will want to do the same thing. Except you want to configure on, and off at both the ISY level and the Red controller member of the scene and not change the button toggle mode. Hopefully that's all straight forward and not too confusing.....

You need two scenes: In the first "Kitchen Table light" and "Toggle D" need to both be controllers, and they are the only things in the scene. In the other scene called "All kitchen lights" both "kitchen Table Light" and "Button D" both need to be responders only, and "Toggle A" needs to be a Controller.

If your portal license expired this is likely the issue. As far as I know as of 4AM PST the Amazon problem from yesterday is resolved. Also Not sure where you're located but the problem primarily effected the Eastern half of North America, mostly the western half didn't have issue.