MrBill

to reiterate what @Geddy already said... Files named admin.jnlp (such as the file retrieved from http://isy.universal-devices.com/994i/5.3.3/admin.jnlp ) are a specific version of the admin console. admin.jnlp can also be downloaded from the ISY994 using the url http://<IP.OF.THE.ISY>/admin.jnlp. Each version of the ISY firmware has a matching admin.jnlp that is only designed to work with that firmware. start.jnlp (as downloaded from https://isy.universal-devices.com/start.jnlp ) is the ISY Launcher. The first time it is run it will install a Launcher Icon on the desktop. This is different than admin.jnlp When the launcher is used to correct version of the admin console is determinded and downloaded each time the admin console is opened either from a cloud source (udi server) or from the isy itself. Both of these methods rely on ISY Finder, however ISY Finders behavior is slightly different depending whether its being launched by admin.jnlp or ISY Laucher (which was installed on the desktop via start.jnlp) The Launcher is a newer method which was created to solve two problems: 1) browsers that block java due to security concerns 2) users mixing up versions of admin.jnlp and running the wrong version. If using Windows, ISY Launcher is definitely the best method. Some Mac users report issues when using ISY Launcher and report that continuing to use admin.jnlp works better for them. When using ISY Launcher on Windows it's really not even required to jump through the java cache clearing hoops with upgrading firmware because a fresh copy of the admin console is downloaded each time ISY Launcher is clicked from the desktop. It should be noted that "ISY Launcher" that appears on the desktop is not simply the file start.jnlp saved to the desktop, it was installed by start.jnlp but its not start.jnlp anymore.

Removing the variable from the ISY and re-adding it won't solve the problem. Early On I deleted the geofence from the locative app, and re-added it. I can't remember for certain if I also deleted the app from the phone. For the most part, my wife and mines phone via the locative app does enter and exit the geofence correctly, but not 100%... I still have extra notification programs enabled to manually supervise... which is a PITA...

While most of us have an expectation of what a nodeserver that we might be adding to make the switch from PG2 to PG3 does... I'm surprised that there appears to be no "Try Before You Buy" provision. What if it doesn't do what the user needs it to do? Is there a refund provision? I won't be just buying nodeservers to try them out. If they fill a need that's one thing, if they don't work that's another.

Login via SSH and type passwd at the prompt, and follow the prompts.

@SESamuels the short answer is you need more RED links. Any button in the scene that you want to be able to push and have it update anything (loads or other buttons) needs to be a RED link. Red links are controllers, the blue (or not red) links are responders. Responders only respond they don't control. When adding buttons after one button from the device is already a controller there is a trick question asked. It says something like "XXX is already a controller would you like to add this as a responder" answer NO... you want all of those links to be red. Once they are, then you will need to configure each device in each of the red links. (PS--it's time consuming, but once it's done you won't have to do it again).

I use the date programs in this thread with one minor correction: // Determine Week of Month $iISY.WeekOfMonth = $iISY.DayOfMonth $iISY.WeekOfMonth -= 1 $iISY.WeekOfMonth /= 7 $iISY.WeekOfMonth += 1 $iISY.WeekOfMonth Init To $sISY.WeekOfMonth $sISY.WeekOfMonth = $iISY.WeekOfMonth (the scratch math should be done with the integer variable and then copied to the state variable instead of the other way around) $iOddDayFlag = iISY.DayOfMonth $iOddDayFlag %= 2 $sOddDayFlag = iOddDayFlag at the end of the program (or anywhere after iISY.DayOfMonth is set) note %= is mod or remainder.... then to use it If sOddDayFlag > 0 then it's an odd numbered day of the month else it's an even numbered day of the month --- disclaimer: odd/even portion is typed off the top of my head, if it doesn't work say so and i'll fix it but I'm short time right now and can't test.

This is not a common issue. You may have a defective board. You should ask support@universal-devices.com for assistance. Stay at 5.3.4, no need to downgrade to buggy firmware.

Actually you're correct! it is a 6 button! I missed that point...

I agree. Many don't understand that each controller can have a different configuration for the scene. There's no problem using non-toggle buttons to turn on scenes... I have radio style buttons like OP wants at my front door for the outside lighting, they work great! As a secondary problems Using button A as one of the controllers is problematic, if the load is connected.

Don't downgrade your firmware. 5.3.4 is better than 5.3.0. It is stable and only includes bug fixes since the "official" version 5.3.0. Its labeled "test build" not "beta", it's called a "test build" because z-wave certification costs UDI a significant sum of money, therefor not every release is submitted. 5.3.4 was released July 30th, approx 6 months ago, and is considered stable.

The firmware answer is the best possible answer.. you're up to date and the versions match. I'm not a z-wave expert but @lilyoyo1 might have ideas...

Non-toggle On is sending On the the scene, the scene attributes take over for the on level, at least as long as the link type in the scene is set to "Insteon". I just reread post #1 of this thread over again.... the answer seems obvious? question 1: Is button A keypad 2 a RED link? question 2: did you click that red link and set the scene attributes for when that button is used? Each Red link in a scene and the "root" level needs to be configured individually.

In the admin console head to Help > About and tell us the Firmware and UI versions you see there.

@waffles The import thing to consider with link counts is that ANY Insteon traffic during the link count will throw the link count off. That includes not only any switch being operated but if you have wireless devices such as motion detectors, door sensors, leak sensors etc even the Heartbeat if received during the link count will distort the count. So if you can do link counts when no one is home, disable all programs during the link count and make certain wireless devices are quiet... no motion if you have motions etc. After you get a link count do it again... if it's not the same then there was insteon traffic (perhaps a wireless device heartbeat) during the count. Rinse and Repeat link counts until you have the same number more than once. A quick way to disable all programs is to click "My programs" (or whatever your top level program folder is named) and add a folder condition that will never be true.... I usually use "If cTrue = cFalse" where interger variables $cTrue is always one and $cFalse is always 0, but any condition can be added to My Programs folder that won't be true. This will Prevent any program from possibly doing something while your link counting... be sure to remove the folder condition when you're done.

Fastest method is likely to open a ticket: support@universal-devices.com

@Geddy nailed it... you need to install Java first....

If you have the Pro version of the admin console you'll have these two buttons on the ribbon: the left one is for wired devices such as the 2 keypads you're working with, the right is for wireless devices. When deselected (grey) they will prevent updates from being written to the device until you press again to select (green). This helps especially for what you are doing, it will withhold on the link changes until you are done, then write all to the device at once. If you don't have Pro you can purchase it instantly, via the help menu... it's a soft upgrade and your purchase will apply immediately. This can be done two different ways, but in either of these cases you can't use Button A as a scene controller if the keypad also has the load attached. Button A and the Red wire are going to be doing the same thing. If button A is on then the red wire is on (at some level), if button A is off then the red wire is turned off. If the Red wire is unused then button A will work below. (There is a method to decouple button A from the Load, however it's not supported by the ISY, you might get it to work following instructions somewhere on the web, but the ISY might overwrite it if you ever need to Restore Device, so I wouldn't recommend it.) Let's use Button E, F, G, H as our scene controllers. In all cases I would highly recommend using the disable device writes button discussed above. Single Scene Method: Create a single scene. Make E, F, G, H non toggle, A should be toggle. Add Buttons E, F, G, H on both keypads as controllers (there is a confusing question where it asks "button X is already a controller would you like to add it as a Responder.... Answer NO). Note: The links for all 8 buttons must be RED. Add button A on both keypads as a responder. Add any additional responders. Click on each RED link and program the scene state. Program not only button A to the correct level for the scene, but also the states of the other buttons. Example if we are programing button E on keypad 1 be sure to set button E on keypad 2 to ON, likewise set Button F, G, H on both key pads to off. Rinse and Repeat for all 8 buttons. click on the root of the scene and program what should happen of the ISY (admin console, programs, Alexa, GH, etc activate the scene) Cons: the ISY (admin console, programs, Alexa, GH, etc activate the scene) can only control the scene to a single state. Pro's: less programming time, less resources used (scenes and links) Four Scene Method: Same as above, except create 4 scenes. One for the E Buttons, one for the F buttons, one for the G buttons and one for the H buttons. When using this method, add the A buttons as responders, then add two controllers, then add the remaining 6 buttons as responders. For Example: for Scene E add both E buttons as controllers, add both A, F, G, H buttons as responders. For Scene F, add both F buttons as Controllers (Red links), add the F buttons as Controllers (red Links) then add A, E, G, H of both keypads as responders. Program the Red links as the root level of each of the 4 scenes. Cons: longer setup time, more scene and links used. Pro's: the ISY (admin console, programs, Alexa, GH, etc activate the scene) can activate any of the 4 scenes.

it's working for me, but it's hosted in different spaces on aws for different customers. If you're logged into portal and you've tried more than one browser you should open a ticket support@universal-devices.com I don't know which they need portal login name or UUID but I'd include both for more efficiency.

I hope that you plan on not requiring pushing the button on the front of Polisy as the only upgrade method, mine isn't conveniently accessible. Also wondering if there are plans to make polyglot accessible via the portal?

I'm guessing that @smileyw is confusing "ISY Launcher" (filename start.jnlp when downloaded) and a copy of admin.jnlp which is a specific version of the admin console. ISY Launcher (start.jnlp) adds an Icon to the desktop named ISY Launcher. When using it, it should get the correct the correct version of the admin console. The first thing that you see whether using the ISY Launcher or admin.jnlp is "ISY Finder".

Thanks. I've been wondering about that but haven't had time to figure out if it was my mistake or a bug. Hopefully the menu option will get disabled until it does something.

The terminology "backlight levelS" suggests that each button on a keypad can have an individual level set, as I'm sure you are aware there is only one backlight level per keypad which applies to all buttons. OP appears to be using the buttons as Radio style buttons, where when one turns on the others turn off. The technique is most commonly used as a fanlinc and a 6-button keypad, but the same technique can be used with normal scenes. For example for outdoor lighting 4 buttons at my front door are set to non-toggle, the buttons control scenes name Day, Evening, Late Night and Bright. For example the Evening button is a scene controller for that scene, however the evening scene also includes the buttons Day, Late Night and Bright so that they can be turned off when Evening is turned on. Only one scene can be "on" at a time, and one scene must be on. (Why do I have a "Day" scene for outdoor lighting? It used to be called "Off" until my wife plugged in an outdoor fountain. The ISY normally cycles the scenes, with manual over-ride buttons.

the nodeserver ISY-Inventory does node counts. portal is not Pro. they are two different things. check with support@universal-devices.com (they answer quickly most of the time) be sure to include the UUID of your ISY.

I'm guessing it's a bug with the value.

There's 2 possibilities: The base ISY is limited to 264 nodes. I can't tell how many you have in folders, but I see one of your folders is named "zwaveStuff" and z-wave devices do eat the node count up fast. You probably need to buy the Pro Upgrade to increase the number of nodes to 1024. (I can tell by looking at the ribbon at the top of the admin console that you don't have Pro.) See the help menu to Purchase Modules. Note that Pro is a soft upgrade, meaning it's instant, you don't have to wait for anything to be shipped etc.... The second possibility is that the 8 scene remotes are programmed as 4 scene remote. If pressing the left side of the remote Button makes the LED on the remote flash RED and pressing the Right buttons makes the LED on the remote flash GREEN then they are programed for 4 scene's instead of 8 and will only add 4 nodes to the ISY. They can be reconfigured as 8 button remotes following a procedure in the manual. See Page 9 of the PDF.