Geddy

Hasn't this always been the case since 5.x (something) on Polisy and eisy? It's been defaulted to "Automatic DHCP" since the eisy was released and if not from release of the Polisy a very early IoP update probably set it to where this was unavailable. UDI does not want the devices to be set to static IP on the device anymore (too many support tickets with old ISY99/ISY994) that it was removed from Polisy/eisy settings, but the boxes are still there. Just never populated.

@raydoc aside from the comments above to update the firmware you should review the "replace device" instructions in the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device It's possible you've got devices in folders and they need to be moved out to be replaced. 5 button? Thought they only had 6 and 8. On the main entry for the device right click and see if you have a "group devices" or "ungroup devices". Did you happen to factory reset the (any) device before adding to the ISY994? When you're adding new devices it's good rule of thumb to factory reset the new device as part of the linking process. This should force out any internal links or programming that you don't want introduced into your system. If you don't see the other buttons after you ungroup or group the devices then you should perform a factory reset and re-link it to the ISY994. Since you've probably been running just fine with 4.0.0 firmware I think it's possible to try to fix your issue before updating, but do understand that 4.0 is extremely outdated. Any help/support in the forums would probably be very limited as most have moved into 5.x and even onto the Polisy and eisy product lines. Further, UDI is no longer supporting the ISY994 so only paid support is available with UDI for the next few months. Instances like this with replacing devices or using newer Insteon devices it would be wise to consider further upgrade options moving forward.

@barrygordon do you want it to run the program only if the switch is physically turned on? You might want “control” rather than “status”. If using “status” then anytime the switch is “on” (by any means) the program would be true and run. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Commands#Control_vs_Status

If you read the link I posted there are specific directions to go from Polisy to eisy. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_Eisy_/_Polisy I haven’t attempted such a move so only going off what is written in the wiki and lots of posts in the past that the directions worked when they followed them. Again, the PG3x might change things. As I think the node server migration process was only intended for PG3 on Polisy, but now that many have PG3x on Polisy I don’t know if the portal migration will still transfer the license. You might want to open a support ticket to ask that specific question if not answered here by others over the weekend.

@BrianN324 thanks for the update and glad changing the DHCP to what the old router was worked. I'm the same way with the 994 in the past and fixed it the same way. Now, before you go too much further...turn off static IP on the ISY994 and setup a DHCP reservation in your router. As you mentioned it was just "easier" in the past especially if you were connecting while remote. You probably used port forwarding. That's also a security risk to leave a port open on the router. If you do setup UD Portal you have remote access using that Admin Console URL I mentioned. Just put that into the IoX Finder window while remote and use our UD Portal credentials to access the Admin Console while you're remote.

@tlightne I think @bpwwer mentioned in the past there was a migration for Polyglot only to go from PG3 to PG3x "back in the day" when people were moving from Polisy to eisy. I don't think there's a method to migrate Polisy PG3x to eisy PG3x currently. Since the node servers are assigned to the UUID it might require UDI Support to move the license(s) to the new device. Perhaps Bob or @bmercier can chime in with if there's a process. Otherwise open a support ticket: https://www.universal-devices.com/my-tickets As for moving from the IoX and ZMatter portions I think the migration steps in the wiki still apply: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

@scrutch if you click the "more info" button on the node server page in the store it takes you to the Readme file for the node server. Sometimes that gives you additional setup/use information. https://github.com/UniversalDevicesInc-PG3/Virtual/blob/master/README.md Otherwise, others that use this node server would need to chime in to give assistance. Is there something specific you're trying to do? Maybe that would help others help you. I don't use this node server so cannot help beyond pointing to the "more info" button for assistance and further information/documentation.

@Paulywog57 red usually means the program/device/etc is already in use. Black means it's available to be added to the Alexa skill. Either change the number of items shown to 100 to see the full list (or at least 100 items if you have more than that - WOW!) or use the search box to look for a word in your program to find if it's already in use. You should be able to edit the line if already used in Alexa. Just remember to run "discovery" from the Alexa device (Alexa, discover devices) after you add a spoken. Also, make sure the spoken is unique and not already in use. And it looks like you can still use https://alexa.amazon.com/ (on a computer, NOT a mobile device!) just have to click on "Go to the previous version of alexa.amazon.com" and you can then click on "Smart Home" (https://alexa.amazon.com/spa/index.html#smart-home) and then "Devices" to see what is currently in the Alexa skill all on one page.

@sfroach, you can always find the link in the wiki (linked in my reply above). Or you can get from UDI website and click on "My ISY". It's still required to clear java cache and run a new start.jnlp process if you're using "Local" option for connection. That's usually what will not match. Although if you use the "Cloud" option (even though you're local) it's downloading the proper admin console version and should not give the error you encountered. It just depends on the method you use most. I just continue the practice of clearing the java cache and running a new start.jnlp on each update so not to risk the issues. Glad you're issue is resolved!

This would have been better put in a separate post for help. But sounds like the device has gone bad. Make sure you've got the "Backlight" setting to be on. Then hit the "Backlight" label to the left of it. Note that when you first look at it the option shows 0/0. You might need to adjust it to different settings to make it work. Although, looking at your first post you're still on 4.9 so it might not be "broken" like it is in 5.x. It's been years since I used 4.9 to set Keypad backlighting.

@smokegrub What operating system are you using on your computer? It sounds like you haven't properly cleared Java Cache. Make sure you're checking all three boxes in that process. [EDIT: even though you say you did this in your first post this behavior is usually a result of not clearly java cache completely] In the past Java updates would remove the desktop icon, but didn't actually "delete" it so just running start.jnlp wouldn't add the icon back. Not until you clear java cache and select the "Installed Applications and Applets" would it truly remove the "hidden" desktop icon so start.jnlp would indeed re-add it to the desktop on next run. Also, after you clear that cache download a fresh file from the link @Techman posted above. Make sure you delete/remove any old copies of admin.jnlp or start.jnlp from the computer. If on Windows, open File Explorer (Windows key + E) view the "Desktop" folder then sort by name. It's possible you have a lot of icons on the desktop that might be taking up more space and new icons can't be added or are hidden.

@btreinders split your post out to the Ecobee forum since it was tacked on to a different issue for non-specific problems.

This just means you need to clear you java cache and run start.jnlp again. Best path review this section of the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop Be sure you select all 3 boxes in the process of clearing java cache.

@chris.com could be that the lock is the signal issue more so than the ZMatter. Since Z-wave on the ZMatter dongle is running 700 series it has better range, but depending on how old the lock is it might not be as straight forward to work with the newer series device. Seems locks were some of the biggest issues in the past based on comments elsewhere on the forums. Worth reading to see how they were resolved...if they were resolved. Worth mentioning @Javi here for your comment about the UD Mobile portion. Again, might be best to toss a post into the UD Mobile specific area if wanting to get help there. Have fun playing with all the new features of the eisy + ZMatter + Polyglot

Try this: http://eisy.local:8080/WEB/udajax.htm I'm guessing that's the "web page" you're referring to. Question - how do you need/use this access? I guess there's something for it to be there, but not something I ever use so interested in learning how it is used by others. Note: any devices brought in through node server do not display on the web interface. (at least not when I logged into mine) You'd be better off posting a new topic just for this issue in the ZMatter forum or even looking for a few posts in there that referenced locks. I think there were some posts a few months ago about issues and how they overcame them. In the 5.6.0 IoX support thread there was a comment from @Chris Jahn to up the interview timeout to 40 seconds or more for older/complicated z-wave devices. At least you're able to get them to connect. Some have had to bring the lock closer to the eisy + Z-Matter board to include then install it back to the desired location. To echo what @bpwwer says...I've made it habit not to have Node Server web access and Admin Console open at the same time. Anytime you make an adjustment in the node server side you have to reload Admin Console so it will read the changes.

@BrianN324 you mentioned this. I wonder if you set a static IP on the device itself and it's outside the DHCP addressing for the new router. This was very common for users that setup the ISY994 a long time ago as that was once the suggested rout of keeping the IP address stable. Currently, the suggested option would be through IP Reservations at the router level. And why UDI removed this ability in the Polisy and eisy devices. If you try the above options and still cannot "find" the ISY perhaps review this from the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP.2FRouter_-_Can_no_longer_access_ISY If you can't remember what the IP you used for the ISY994 there might be no other option than resetting it. Hopefully you have a backup of some sort, but if you haven't accessed the ISY994 in a while it might be last ditch effort to reset it. If you know DHCP table used in the old router you could set that temporarily in the new router and perhaps the device would connect on bootup. Then remove the static IP setting in the ISY994 configuration tab and allow automatic DHCP. Unplug the ISY994. Then reset the router to how it was before this and let everything else connect to the router before powering up the ISY again. Depending on how long ago you replaced the router maybe you still have it and can power it up (not connected to the internet or anything, but enough to connect the ISY994 directly to it and maybe plug a computer directly to it to attempt to access the ISY994 that way. (If the above changing the current router DHCP table is not an option for you) One other option I can think of, and would only work if the device is connected to your network is to ask if you have it connected to the UD Portal (my.isy.io). If you have an active portal license for it see if it is showing connected to the portal. If it is then you can use the remote access address from the portal information section to attempt to add that "Admin Console URL" to the IoX Finder window you posted above. Then use your UD Portal credentials to access the ISY994. PS: If you do have the portal access it shows you the "Internal IP" as well. But I think the device has to be connected to the current network, and if you're IP isn't within the DHCP table of the new router it might not be making that connection.

@Bert2013 Probably the same issue reported in this thread:

This was mentioned earlier and resolved….see this post:

Not sure, that’s a question @Michel Kohanim or @Chris Jahn could answer, but it’s been something I have experienced with the eisy for the last few months and hasn’t bothered anything. Especially since they’re both auto discovered. I think it’s become more the norm following the “not found” issue that was fixed in the start.jnlp update recently.

This is normal and not a concern. ISY Finder is listing both the local IP address and local domain address when auto discovered.

@andrew77 take a look at the Coffee Shop area. There have been a few discussions about this question there.

@nowandthen see @Techman and @DennisC posts above. This should fix the “not found” issue. This was reported fixed in another post. The “https://eisy.local:8443/desc” is auto found and cannot be removed. It’s normal for how IoX launcher finds the eisy as long as your router supports local addressing this way.

@CoolToys look at the bottom of the list (I think). It’s whatever name you’ve given your eisy. It probably isn’t just ISY now. Neither the Polisy or eisy “shipped” with the query program as a default program. Many have just gone without, but many will add it (like yourself). It is used to update status for devices. If you don’t have an issue of out of sync devices you might not need it.

@wmcneil best bet is to contact UDI directly to ask them. https://www.universal-devices.com/contact-us/

@andrew77 this is an issue that others have commented on. I think there is an update if you run Upgrade Packages again. I know @DennisC had the issue and think he said it was resolved recently…maybe he can confirm. Otherwise, I think things work okay, but it is an odd error to have randomly.