Geddy

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!

@auger66 and others, Yes, looks like it was an internet outage. There's a post about:

Yes, there were several in the past. When the only way to migrate was to have ISY994 with 5.3.4 firmware (that meant it basically had to be a 500 series Z-wave or no z-wave). Now, UDI has indicated that 4.9.x firmware can be migrated to the eisy, but didn't specifically comment that the 300 series Z-Wave would. You might want to open a support ticket to get confirmation that it is not possible, but for most users the assumption would be that 300 series is still not able to migrate. (NOTE: The wiki was updated to include ISY994 migration from 4.x firmware, but still indicated the Z-Wave needs to be 500 series: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994) It depends how large your Z-wave system is as to how much work that would take. I would strongly suggest you make a text backup of your programs -- right click on "My Programs" folder and the last option should be "Copy Folder to Clipboard". Paste that into a text editor (for Windows use Notepad). Now you have ALL your programs in an "easy" to read text document. This will help you recreate any Insteon+Z-Wave programs once you reconfigure your Z-wave on the eisy (with the ZMatter dongle). I'm not a strong Z-wave user, but always see other users suggest that you exclude z-wave devices if you're going to set them up with a new controller. So perhaps (again, depending on the size of your z-wave system), I would remove (exclude) them all from the existing ISY994 system then follow the migration steps just for the Insteon devices. You should be able to fairly easily backup and then restore the Insteon portion to the eisy. Then you could add the Z-wave support with the ZMatter dongle and even start adding Zigbee items. How large is your total installation? It should go fairly smooth if you just focus on the Insteon side. Make sure if you're using any Network Resources that you will have to click on each of them and re-save them (that's noted in the migration instructions, but one most people overlook). If you're thinking you might do this in stages remember that the ISY994 will enter into "safe mode" if it's booted up and no PLM is attached. It's not advised to have multiple PLMs running (it's possible, but tricky and could cause lots of communication issues). To get around this if your ISY994 were still to manage Z-wave there is a different firmware so the ISY994 wouldn't go into "safe mode". I'd pull the band aid off and make the move all at once. It will be growing pains for sure as the likelihood of it being "smooth" diminishes for those that don't read the directions first and just try to blow through it too quickly. Take the time to review the processes before attempting any of the steps. So you have an idea of what should happen in each step. Then make the commitment to migrate and spend the time rebuilding the Z-wave network once the Insteon system is up and functioning as expected. It's a lot harder (at least somewhat more difficult) if you're trying to attack issues in both systems at once. You've got this! Go for it! Good luck!

@andrew77 and others, Seems was an internet related issue. Please see this post:

@bmercier sorry...you're correct. Was just looking at the initial subject of your post.

@Kentinada and others this looks to have been a Portal issue. Should be resolved based on @bmercier post.

It's doing exactly what you suggested in an earlier reply. Or did you not mean it that way? That's the only way I've seen to "increase the size of memory Java is permitted". That's what's been tossed about for years if/when admin console is slow and also for things like the font size being "remembered" from multiple logins. It's not "robbing" the system of much memory (these days). Usually I don't even set the min, but I did based on somebody's post at one point that it would be good to set min/max. I forget who it was. Sad thing is sometimes the memory setting has to be reset after some Java updates. But most of the time I'm not using Admin Console enough or long enough to notice any performance issues with it or with the rest of my system. Still blows my mind that you've got buttons off the edge like that. Not sure what device that is, but I think last time I checked most of my devices all buttons were available. Perhaps it's your overall screen resolution not allowing the admin console to fully create the buttons. But that would just make your text smaller! Admin console font size and color choices have long been items people complain about. And I admit to be one of those confused as to why nothing has changed to make the whole thing easier to read. I guess it's just not something that is high priority to update/recreate.

How did you restart the device? Did you just use the "reboot" button in Admin Console or perform a shutdown/power cycle or just a SSH command? When was the last time you ran an update? I think it might be best to open a support ticket if you're getting errors like that in a simple restart process. Something might have gotten corrupted and need fixing.

Interesting question. Not one that is easy to answer. Since Insteon uses a Hub for their own admin side the PLM is only required for systems outside of the Insteon brand to control (i.e. UD products and maybe others). There's a similar question recently posted in the Coffee Shop area that's interesting to see that many still come back and rely on Insteon for system reliability. Depending on how old the PLM was it could have been in the bad days of product life for those. Or hit-and-miss on having it stay reliable for you. But have to image for the "few" that come here to post that they have had PLM issues there are a lot that don't post here that might not have a single issue for years and years. It's a chance we take relying on the PLM to talk to our systems, and many see it as the weakest link. Glad you got it fixed. PS: There is/was a PLM repair service that posted here from time to time and had sales up on ebay to repair PLMs. Also there were quite a few posts in the past about how to repair yourself if you're handy with devices in anyway. Just try a Google Site Search on the forums for PLM Repair. If you think the PLM was defective and could be repaired.

@William Olsen I think @DennisC hit the nail on the head and @GHenry backed it up. Your programs are only running AT a specific time. This program ONLY runs AT 6:00am. Further, in your image above that program is DISABLED. Even if not disabled the slim red line along the left side of the icon indicates that the last time that program triggered it triggered false. Meanings of colors on the programs can be found in the wiki: https://wiki.universal-devices.com/index.php?title=ISY_Programs:Icon_Colors For your program to run the THEN portion it would have to be the very moment it was 6:00:00am and below 40.5°F the program would be true. If it doesn't happen that way exactly at 6:00:00am the ELSE runs (meaning the program is FALSE). The first part of this statement seems to be accurate since your weekend programs are showing enabled and run at startup if you rebooted the device after you manually set the temp on the thermostat the "ELSE" would trigger at start because the program is showing "[Run At Startup]". If you disabled the program and the temp changed then it is either on the thermostat or another program is triggering it. That's where the find & replace that @DennisC mentions come into play. Find what other programs mention these thermostats. Last question - before you migrated from ISY to eisy did you happen to make a text backup file of your programs? I don't think it's specifically in the wiki method, but it's long been a suggestion to make a text backup of your programs so they can be easily recreated should something fail. My expectation is you had to recreate the programs from memory and aren't exactly as you had them in the ISY994. My final suggestion might be (do you still have the ISY994 backup you used to migrate?) make a full backup of your system now make a text backup of the programs - right click on the "My Programs" folder and then select "Copy folder to clipboard" and then paste that into a text editor - like Notepad (not a word processing file/document). Then SAVE that text documents as your current programs. if you still have your migration backup from the ISY994 restore that again to the eisy DON'T DO ANYTHING TO THIS RESTORED VERSION! IMMEDIATELY make a TEXT BACKUP of your programs. (again, copy "My Programs" folder to a text file) Restore the eisy backup you made in step 1. Now you should be back to where you were and you might have a valid text backup of your "old" programs that were on the ISY994 and can recreate them again in the eisy. But I think just adjusting your programs to run in a range would be what fixes your issue. Furthermore, as @dbwarner5 suggests unplug the eisy and adjust the thermostat. The issue is you might need to leave it unplugged more than 12-24 hours to span a day of when your temp settings change. Good luck! Please report back with changes you attempt and any further findings you have.

Where did you find this? What @larryllix was suggesting is the settings within the Java console. -Xms512m, -Xms1024m, or higher Only use one for "max" setting. I find 2048 works on my system. For reference: I have usually had both a max and min set just for ease. To set this (if on Windows) open "Configure Java" (opens the Java Control Panel). Click on the "Java" tab then "View" and you should get a "Java Runtime Environment Settings" window. In the "Runtime Parameters" you can add the values. "-Xms1024m -Xmx2048m" - That's my current settings. I'm running on a desktop with 16GB Ram and don't keep Admin Console open longer than I need it to update/change things, and even then that's rare. With my settings I usually get about 3 or 4 weeks out of themes settings staying. It's very random when it "resets". I'm not sure if it's a Java temp setting getting flushed or the ud*.state files being flushed in a temp directory that's resetting it. I just know it's bothersome, but only takes 20 seconds to reset and re-launch for it to take hold again.

There's probably a command that support can give you through SSH to reset the network DHCP Lease on the Polisy. Even though you left it unplugged for an hour more than likely it's trying to pickup the old IP from the lease from your router even though it's changed. I agree with @kzboray to open a support ticket and get the best route that way. https://www.universal-devices.com/my-tickets Once you get this resolved please post the fix here to help others should they have this issue in the future.

@DannyFresh Looks like it is indeed an Amazon/Alexa app issue...a recent thread on their forums is discussing it (unrelated to UDI). https://amazonforum.my.site.com/s/question/0D56Q0000CYidpiSQB/cant-find-scenes-anymore Honestly, I've never added a scene as an option in Alexa so thankfully haven't had an issue. What happens if you delete the Scene from the ISY Portal run the "discover devices" on the Alexa device (or app). Does it forget it or wipe it out if it can't find it through the portal connection? If so then add back as a different device - you can add a scene but classify it as a light (Category) Perhaps even changing the scene to another category might push it into a different section in the app (just a shot in the dark). I'm on iOS and as of today if you open the app, click on "More" (lower right) then click on "Skills & Games" and scroll all the way to the bottom there's an option for "Your Skills". After clicking that it will show you what skills you have installed. I wonder if you disable the UDI skill and then clean up the listings on ISY Portal and then re-connect the skill if it will wipe everything out in the process. I know @larryllix has commented before that Alexa will randomly remove devices it cannot connect to because he's had to rebuild some routines because of that issue in the past. And @larryllix yes, I really miss the old alexa.amazon.com site. It was so easy to use a computer to update/change things. Agreed that many companies are forcing users to rely on their mobile device to update/use/manipulate their stuff. As some here complain about the Java access to admin console I hope that never goes away (or changes to another computer based option) because trying to program intricate home automation on a mobile device is painful. (IMO)