Geddy

Read here for ISY994: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights Correct, but you do have to install the latest firmware after you access the ISY994 the first time after you install the new (micro) SD card. https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Replacing/Formatting_an_SD_Card Step 3 is key! I believe if the SD card is new when you first boot the ISY994 it will put a very basic firmware on the card so you can at least access it with IoX Launcher. From there you must manually install the latest firmware. That's what Step 2 does (using the "FS" command when you telnet to the ISY994). But I've never done the process so don't know exact expectations. What do you mean by this?

Yes, somewhat of a bug, but not sure it's a fixable bug. The UI changed when IoX 5.x came out. On the admin console to write the "On Level" you have to click the button on the left to be updated for the device. As for the admin console not showing the "On Level" if you make the change in the mobile app it should update. I just tested with a dimmer switch and the UI did update. I was about to say reloading would have fixed that because usually information is only updated/read on load. But mine did update when I changed with UD Mobile and had admin console open. (and dangit... @Techman swooped in and answered before I could post since I was testing the update with the app while having admin console open. Thanks!) The same is true if you set the backlight of a switch. With that though it will always show 0% so that is an issue that's been buggy since 5.x (maybe even before). But that's a different option you aren't concerned with.

Note to add: for some the ISY994 will continue work just fine. The new hardware adds a lot of additional functionality, but for those that have a system working for them and not looking for expansion(s) the ISY994 will remain a reliable controller. Just understand, as with all aging technology, the possibility for failure is there.

As @auger66 points out it's probably the portal subscription has expired. Check by logging into the portal (my.isy.io) and then follow the image for License Information Renew that for a year or two. Note the rate did increase in the last year (or so). But still a deal by any means! This sounds like you've had a Java update and it wiped out the link with the shortcut on the desktop. To resolve this follow these steps: Clear Java Cache (temporary internet files) Check all three boxes! The 3rd box will/should delete the desktop icon (if you have iox launcher on the desktop). If it doesn't just delete it. You mention "Click to launch console.jnlp", not sure where that came from or how old that is. The "IoX Launcher" method has been around since 2018 and the preferred method since browsers dropped Java support. Make sure Java is up to date Just get the "standard" java version available directly from java.com https://www.java.com/en/download/ As of today it is Version 8 Update 391 Delete any start.jnlp or admin.jnlp files you have on your system Download a new start.jnlp file from UDI website https://isy.universal-devices.com/start.jnlp Go to Universal Devices site Click on "MY ISY" on the top right and you'll get the same file linked above (start.jnlp). Run "start.jnlp" and accept any Java warnings This should add the icon to the desktop for "IoX Launcher" Run IoX Launcher and you should now get a window showing as "IoX Finder". If you're local to the ISY994 it should auto populate, but if it doesn't you would need to add it manually. More information can be found in the UDI Wiki should you need more help: http://wiki.universal-devices.com/index.php?title=Main_Page Post back and let us know how it's going.

@JohnH are you sure it didn't come with screws? In my box (I got the eisy a year ago) there was a bag with the bracket and inside that bag another bag with 4 screws: 2 longer ones (about 1cm in lengh) and 2 short ones about 5mm (1/2cm) in length. Probably best to contact UDI through their site to get actual screw sizes though. https://www.universal-devices.com/contact-us/

For me some of the "fixes" were reason enough to press that upgrade button. Seems like you're stuck on the "feature" items that probably do help developers/backend side more than stability of the platform. For your specific questions you might be better off contacting UDI directly through their website (probably ticket option, but sales email might also be an option). Michel has (several times) commented that they're buried in development at this time and not reading the forums as closely as they used to. https://www.universal-devices.com/contact-us/ or https://www.universal-devices.com/my-tickets

Why? Since 2018 the suggested method has been to use the IoX Launcher (formerly ISY Launcher). Downloading the start.jnlp file linked above by @Techman is all that is needed for reliable loading for Windows (and usually MacOS). Access via other OS (as you said you also use ubuntu) has been documented elsewhere on the forums. While not as "easy" it possible. Just have to figure out how to do it. And if you're running ubuntu then hopefully you're able to figure that out. But basically the start.jnlp/IoX Launcher process replaces the "need" to have a version specific "admin.jnlp" file.

Yes If on the router, no. It means the same (generally speaking). At the router level typically in the DHCP settings is the IP reservation option. Just depends on your equipment. Glad you got it working!

No, just some have attempted to make a direct connection since with Zigbee there might be a link available, but for Hue I think the only/best method is still through the Hue Hub/Bridge. Fine? Yes, if you added a second hub that had not been in the system at all it probably added correctly. Sounds like the first one changed IP address and the plugin is looking for it at the old IP. That's where you need to hard code it in the settings in the dashboard for the plugin. That's fine, until the IP changes. The plugin information used to (I haven't looked at it lately) encourage an IP reservation so this exact issue didn't happen. It's probably wise to set a DHCP reservation for that 2nd hub since it's connected and working correctly. For the first hub you'll either need to force it back to the old IP (if you know what it was) or hard code it and hopefully discover it in the plugin.

I'm not sure if it's needed, but could be. The plugin has to authenticate with the Ring service. I've never attempted without an active Ring subscription. One of the release notes though indicates this: So might be a requirement. Maybe just an account...not an actual Ring subscription. This is normal. It's the same for my doorbell pro "motion" node. My floodlight cam has information on the Motion, but the "lights" node is blank on that device. My motion program triggers for middle of the night motion runs as expected. ~Door-Motion - If '~NodeServers / ~Ring / ~FDoor (Motion)' is switched Motion And From 11:50:00PM To Sunrise - 60 minutes (next day) Then Set '~NodeServers / ~Hue / Couch' On Wait 5 minutes Set '~NodeServers / ~Hue / Couch' Off Else - No Actions - (To add one, press 'Action')

In this instance "dashboard" = "admin console" All you need to do is ensure you have an active portal license and then run the Alexa Skill (I believe v3) and set up devices in the UDI Portal. PS: Assuming you're originally starting on this wiki portion: https://wiki.universal-devices.com/ISY_Portal_Installation_Instructions Here's the wiki info for the Alexa Skill: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3

@DualBandAid Did you attempt to directly connect bulbs to the eisy? Best I've seen is to simply use the Hue plugin (formerly Node Server) and control items that way. It's possible that the Hue Hub changed IP addresses in your network. Do you (or did you) have an IP reservation in the DHCP settings on the router? If the hub changed IP address during this the eisy is looking for it at the old address. You will need to hardcode the current IP in for the bridge. From the plugin "more info" config page: Make sure you include the square brackets [ ] and quotes around the IP address. I had an issue with the IP address changing when I first set it up and PG2 had a rough time getting the bridge connected again. When I setup PG3 I had a reservation made and haven't had to hard code the bridge. Make sure you've got all the lights in the bridge before you connect to it. Also, if any devices are on outlets that can turn them off (making them unreachable to the Hue Bridge) be sure to have them powered ON or at least "reachable" when you begin the linking process.

This is for devices that are shared with you. If the new camera is in your same account then it should be found by the existing plugin setup. You might need to restart the plugin or query devices for it to discover newly installed devices. I haven't added new devices since having the plugin so don't fully know the process for updating to find new devices.

Are you trying to just mark them read/seen or do you want to delete them all together? iOS is like @dbuss says for Android. Top right there's a trash can that allows you to delete all alerts. What's the point of keeping them after seeing them? Just delete them all. Otherwise, I don't think there's a way to mass mark them read. Not many reasons (IMO) to keep them after glancing at them.

Use voice discovery command: "Alexa, discover devices" (replace "alexa" with your current "wake word")

@ISY4Me not seeing anything in the GitHub reademe https://github.com/UniversalDevicesInc-PG3/udi-sun-poly/blob/master/README.md Maybe @bpwwer might know…looks like he made the conversion to PG3.

When you access using the my.isy.io link you should use the portal user/pass credentials. This is usually an email for user ID. When you connect locally or using port forward (meaning directly to the device from outside your network) you should use the local/direct connection credentials. This will usually be admin/pass (whatever pass you use when local to the device). Security tip…since port forwarding means you bypass all security to connect to the device you should make sure you’re not using the “default” user/pass combination. This is always how it has been…nothing new for those connection credentials.

@MarkJames make sure that your IoX Launcher has been updated on the computer you're using. In Admin Console check the Help -> About and make sure Firmware and User Interface are the same version. Typically missing programs indicate a mismatch of this. Just clear your java cache (checking all 3 boxes) and download a new version of IoX Launcher from the UD Site (clicking "My ISY" on the top right will download the file).

Do you have a network cable connected to it? If you're looking at the Help -> About and see "Internet Access: Disabled" that is NORMAL and expected. That is not intended to be available any longer. In the Admin Console click on the "Configuration" tab. Then on the "Portals" tab. Make sure there is an "Active Services" area and it says "Registered". It might be pending. Also, even though you said the portal says the device is registered, but offline, do you have an active portal license? Confirm on the portal: Next, what are the lights on the front of the ISY994 doing? https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights Perhaps power cycle and watch the lights. Compare to what the Wiki has for any errors or issues during bootup. Finally, make sure if you have a network cable from the ISY994 to a switch or router then make sure it's actively connected to your network. Log into your router and look for "Connected Devices" or something similar. Look for a MAC address that is the same as your UUID (I think that still applied to the ISY994, I know it does on Polisy and eisy).

@thedishking please update us on what you get back from support. In the meantime have you performed a full power cycle? On the eisy please press the power button 6 times (in semi-rapid succession). This is the "Shutdown" method using the power button as the "multi-function button" (as explained in the wiki). After about 20-30 seconds (maybe a little longer if it's struggling) the light should turn red. That will indicate the device has powered down. Pull the power supply and wait about 10-20 seconds. Plug the device back in. Wait about 3-5 minutes for the machine to fully boot. While waiting for the machine to boot clear your Java Cache (yes, again), be sure you check all 3 boxes in the process. Delete any OLD start.jnlp or admin.jnlp files you might have on your system and download a new one from the UDI Site (https://isy.universal-devices.com/start.jnlp). Before trying to get into admin console try the PG3x access either by going to http://eisy.local:3000/ (or http://eisy.local:3000/ NOTE: click on "Proceed to eisy.local (unsafe)" if/when you get an alert that it isn't secure.) If your router isn't working with friendly local URLs try replacing "eisy.local" with the IP of your eisy. If you do not know the IP of your device you can find it by looking in your router for "Connected Devices" (or something similar). Typically if you cannot get into the device through PG3x or Admin Console it's a matter of the device needing to be power cycled to start up normally. Although it is interesting that you can access via SSH and UD Mobile. Are you running any VLANs or firewalls (or antivirus programs) on the computer you are using to login?

More than likely the setup is requiring there to be credentials. Would you want to test/use a "fake" gmail account? The setup info in the Wiki is accurate for setting up using their higher security settings. Not sure if the list of error codes would help (even -1 isn't referenced): https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages My guess is you're in the very small percentage that would be running a local server so the setup is focused more for those using a free email service, their own ISP, or some other hosted email. All would require some sort of authentication. If can't figure it out probably best to get support directly from UDI through a support ticket. https://www.universal-devices.com/my-tickets

@SLP Since you just have limited Z-Wave currently I would remove them from the ISY994 before trying to migrate. This way you've got a blank slate on the Z-Wave side and only the Insteon to migrate. I don't use much Z-Wave so don't know the "proper"/best way to remove them from the system, but if there's an exclude process I would do that. Then delete them from the listing of devices. One important step I usually suggest to everybody in the migration phase is to make a TEXT FILE copy of all your existing programs. Go to the Programs Tab and right click the "My Programs" (or root) folder and then select "Copy Folder to Clipboard". (note...use the "COPY" option...don't use/click export). Paste that into a text editor program (Windows use Notepad). Make sure you read/review the migration steps in the Wiki before attempting. Don't try to read as you go as the steps can be somewhat confusing and reading them before attempting gives you an idea of what will come next and make sure you follow them accurately. Setting up the Z-Wave on the eisy w/ ZMatter should be fairly simple and straight forward with low number of devices. Just search the forums for the devices you have in case others have had issues adding/controlling them with the ZMatter dongle. Good luck!

@JSchumann glad you got it connected. There have been several posts about not getting it to connect and not much follow up to give clues how to make it successfully connect. As for the missing part for low battery not sure. It might be best to open a support ticket to see if there's something wrong with the way the MS2 is being added to IoX these days. https://www.universal-devices.com/my-tickets I do not run any motion sensors so cannot comment further on things to try.

Best support in the industry! Insane how quick replies are received. And great thought of keeping the text files to refer to when things changed. I usually only keep a couple in the cloud when I make backups. If only more users would implement that as part of their backup process it would make recreating programs when they go south a lot easier to self diagnose or help others on the forum point to a direction of enlightenment.

With that it might be "simple" to just rebuild the Z-Wave network and not even think/plan/deal with migrating the Z-wave. You might want to look through the ZMatter forum area as some people have had issues with locks. Things to watch out for will be the motion sensors. At least from reports of others in the forums. I'm not familiar with triggerlincs just be ready to battle with battery devices. indeed! It's an awesome ability and a tip I try to always suggest because there have been a lot of people having programs not make the migration correctly and they don't get the programming correct because it was something they set up ages ago and think they did it the same, but it doesn't work as it "used to" on the ISY994. Good luck!