MrBill

If you're using an ISY don't set options at the switch, because the ISY doesn't know about the change made at the switch. Instead change the setting via the ISY. If you have on-level set to 60% in the admin console using the dialog shown in the screenshot above, and you have written the change to the device using the button to the left of the dialog box then turning the switch on manually at the switch, or using the on button in the ISY on the device node should turn the device on to 60%.

You cant pick your own colors, only choose between a few theme's under File > Theme's the pink/purple color is complained about a lot, but sadly it's still used. On thing that Improves it's readability greatly is to increase the font size, but don't use font size 14... it doesn't format drop-downs in Programs correctly (the others work tho).

Java 8 is the only supported java. However, it updates every month(ish) like everything else. Current is Java 8, Update 331... sometime or another that will advance beyond update 331...

Do the scenes always work if controlled manually from the ISY? for testing purposes add Wait 15 seconds between each of the Set statements. Is the PLM plugged in where it always has been? Have you plugged anything new recently? Like a charger for a new gadget? or even changed an LED bulb.... What I'm getting at is the sounds like a garden variety Insteon noise or signal sucker issue. The ISY is doing what it's supposed to but the message is not received. ALso Open Event Viewer Level 3 and watch to see if the ISY is generting Insteon traffic.

@kzboray the linked wiki has actually been updated to use a single scene with controllers set differently. I use 4 different scenes for the fan and then have Alexa setup to turn on or off the correct scene. It's expensive to eat 4 scenes per fan or fan group, and if all my fans had fanlincs i would feel that pain but reality is I don't have fanlincs everywhere, nor do I need them.

originally, when firmware was updated the user would go to http://ip.of.the.isy/admin.jnlp and download the new version of the admin console directly from the ISY. Eventually browsers started liking that method less, throwing security warnings about using unsafe java... etc etc. Users also seems to have great difficulty clearing the cache and deleting old copies of admin.jnlp when they obtained a new one. So in 2018 The ISY Launcher was born to solve both of those issues. Launcher (start.jnlp) is downloaded from https://isy.universal-devices.com/start.jnlp and since it's an https site (rather than http from the ISY itself) browsers are a little bit happier about downloading it. The first time you run start.jnlp it will install an icon named ISY Launcher on the desktop. That's what you should use to run the Launcher going forward. Launcher when launched immediately runs ISY Finder, and as such the two are often confused Launcher is not Finder and Finder is not Launcher. Depending on the type of record in Finder you'll get various choices of things that can be started using finder, an example this one for the ISY994, allows us to start The admin console either from LAN or from Cloud. In this case cloud is faster because it's fetching the file from UD's cloud server which runs from AWS... the LAN alternative is slower because the ISY has to serve it up encrypted for transport... a job that the ISY994 is very slow at preforming. The above described all works great on Windows, and most MAC users don't complain, but some do... and I've never figured out why. for those users it's best to simply use admin.jnlp that they download from the ISY. When using the ISY Launcher icon, it's really not, in theory, necessary to go thru the hoops of deleting the java cache and re-installing etc as often as most people seem to. Personally I vary rarely clear my java cache and re-install. My local network can have up to 4 ISY's running on it (only 1 is actually production but I have a second 994, and 2 Polisy's) and at any given time there might be 4 different firmware version loaded, needing 4 different admin console versions... Launcher manages all that. The only time I really clear my java cache is when a java update installs. So the best advice is download and run start.jnlp which installs ISY Launcher on the desktop. Use that going forward. When you're forced to re-install due to java updates, download a fresh copy of start.jnlp instead of using the one you might have laying around from last time because UD does at times revise that file. .... and if that procedure doesn't work because you're using a Mac, then use the http://IP.of.the.ISY/admin.jnlp and store the file on the desktop. Just remember that when firmware is upgraded you must manually clear the java cache, delete the current admin.jnlp and download the new one.

Scenes: https://wiki.universal-devices.com/index.php?title=ISY994i:INSTEON_Device:FanLinc-KPL_FanLinc_KeypadLinc_Configuration

Someone else had this problem too. Open a ticket support@universal-devices.com (they do answer on weekends but more slowly than weekdays)

THIS IS NOT COVERED WELL ANYWHERE, NOR IS IT INTUITIVE... after you set the dropdown, press the button to the LEFT of the dropdown. IN this case "On Level" I'm not sure why its so hard to make this either more intuitive, or add a line of on-screen instruction.

What your reading on the label IS a "D" not an "O" If you look really closely the left corners are square, the right corners are rounded: so you have the device correctly added to the ISY at this point. Edit to add: It will never be the letter O the characters are hexadecimel so they stop at F in the alphabet

You're missing a step or 2.... after 5 and before 6 you need to load the firmware. the bootloader firmware that comes up in in step 5 isn't compete. You should install the same firmware the backup was made with, which will reboot again. THEN restore the backup.

What you're describing sounds like mismatched firmware and admin console... so I'm suprised they match. the issue @Techman refers to is about the use of "adjust scene" use in a program. that particular program statement won't update automatically and requires manual intervention. 4.9 is in this thread, if you want to try to go back. I'm curious tho what's going on with your programs.

Changes which number, the 6 digits you just replied above? There's many cases were people can't read the label, smarthome has a poor font choise... D and 0, 8 and B, are some of the numbers/letters that are hard to tell apart. the 2 devices i.e. sensor/relay part is correct...

What happens when you check Help > About? Is the firmware version 5.3.4?

if step 2 is linking to ISY then you're good. If it's manual linking then no, don't do that. Once the single scene is created you need to set the attributes 3 times. Once at the root level of the scene, and once for each controller. Here's a scene similar to what you describe: The root level of the scene (selected in the screen shot) is how the scene is processed when controlled by the ISY itself (i.e. manual control, program control, or portal/alexa/Google home control). Then you must click each of the two scene controllers and set the attributes again. (each of the 3 controllers could in fact control the scene differently.)

Did you just complete migration? IS PG3 pointing to IoP or back to your 994. is this the Occupancy or Occupancy V2 node server that you're referring to as the portal node server or something else? I susupect that you're using one of the Occupancy node servers and it's still pointed to a 994, I don't think the migration tool migrates that from reading the list of checkboxes on the migration tool. If this is the case you just need to re-add the occupancy node server to your new IoP installation. It still should show the slot occupied and "unmanaged". I believe @jlamb is trying to say that the slot is not showing unmanaged. I suspect his problem tho is detailed above... he's using one of the Occupancy node servers and it wasn't migrated by the portal migration tool.

Definitely not a technical limitation. But overall there are only a very few of us that make every switch in the house a smartswitch and desire the feature sets being discussed. The two forces that are at work on manufactures are that the masses just want a remote control switch as an upgrade to the timer for the front lights, or maybe to have a few lights turn on at dusk and off later on, etc, but not whole house control (at least in North America, Europe appears to be more energy conscious), that's still a very small percentage of the market.... the other force is price competition in the market... gotta drive the basics to market at the lowest cost possible to gain sales in a crowded marketplace.

heh... i didn't actually look i just assumed he linked the PLM or the never built superPLM

welcome to the forum! that link is nothing new to most of us...

Much better to use the portal for remote access. less than $1/month and if you're a new Polisy owner it comes with 2 years included. That said, I do have an IP reservation configured via the router so that I never have to figure out what the IP is on the local network.

if you haven't discovered what @apostolakisl is alluding too above, you can Right Click a program name and choose Run Then or Run Else to test those clauses. If they don't work the first thing to look for is a folder condition anywhere above the program (folders can be nested, and folder conditions are inherited). As I mentioned already stay away from folder conditions until you really understand how IF statements the ISY work.... there is a learning curve beyond simple time based conditions.

there are several threads that detail DIY replacement of the crappy capacitors. The capacitors in later versions of the hub seem to last longer than earlier versions. There are also 2 ads on ebay that may be of interest to you: Insteon Capacitors Schlyguy is also a member of this forum, these do ship from Canada but I had mine in about a week. PLM repair I can't personally vouch for this guy, but I have emailed with him and his ad has been repeatedly posted without anyone coming back to complain about the service they received.

did you reboot between and Note this line at the bottom of the 121.sh

Shine your phones flashlight on it.... it will reveal itself as a blue LED. Your z-wave version will also be 4.55.00. That is a 300 series board. Firmware version 5.0.16C is as far as you can go. Help > About: make sure the UI version is also 5.0.16C and not just 5.0.16.

My advise is don't use folder conditions as a beginner. Advance to that in the intermediate to advanced levels of skill. the folder "My Programs" has a folder condition. it must be true for anything under it to run.