Geddy

Just give a link to it and they can review if it helps. But sounds like will end up being PLM issue. Keep us posted.

That has nothing to do with IoX (if that's how your wiring works). It's just acting like a normal switch then. If you can't control from the Admin Console then it's a PLM/communciation issue. If the backup wasn't from the moment you made the conversion then it's highly possible you've made changes that weren't in that migration backup and is what's causing your problem for missing devices and corrupt programs. I would: Remove a switch you can get to easily from the Admin Console that has an exclamation mark on it meaning it cannot communicate with the PLM/Admin Console Factory Reset the switch Search online for the switch type and the reset method and be sure to follow it exactly! Pressing in the set button for a while (usually until the beeping stops) is most often the hardest part, but be sure you look up for your type of device because it can be different from other items Add the switch back to Admin Console - I usually auto link - be sure you select to clear out prior links upon adding Test if device can be controlled from IoX. When you mentioned that your backup was old made me think that you might have made changes and didn't follow the migration steps of making a current backup before moving away from the ISY994.

@JerryR This is mentioned in the "fixes" for 5.8.4.

@awzulich glad Support got you back into admin console at least! Did you happen to include anything about this issue on your support ticket or just trying to get you back into admin console? 15+ year old PLM - that's amazing! I know many have had some fail in just a few years. Mine (knocking on wood) is about 7 or 8 years old (if memory serves). With a WHITE light on it? I'm not sure they ever had one with white led on the side of the PLM. Others (that had older PLMs) might be able to answer if old devices had a white light rather than green. Are you able to control any devices from the admin console or are all your devices with a red exclamation point suggesting they cannot communicate with IoX? That would usually indicate PLM failure or on a bad circuit. Is the PLM plugged into the same outlet you used for the ISY994? Have you performed a full power cycle? Shutdown the eisy (press and hold the power button until it turns red - or press it 6 times and it should turn red after 30-60 seconds - multi-function button info on wiki) Unplug the PLM from the wall Wait a while (sometimes 2-3 minutes) Plugin PLM - allow light to settle (become solid) - should be green (at least "recent" PLMs) (maybe 60 seconds?) Power up eisy wait ~2-3 minutes for it to boot completely Open admin console Do you get any errors about communicating to devices? Take a screenshot of any errors you get on logging in if you can. Try controlling a device (just by turning it on/off). If it work then your PLM is communicating with that device. If your programs still have the statements from your first post it might be a corrupt migration. At this point I might open another support ticket to see if there is something they see in the progress of the migration that could have corrupted your IoX system. https://www.universal-devices.com/my-tickets By chance - before you left the ISY994 did you make a copy of the programs? I usually suggest people make a digital copy of all their programs in case something like this happens. This way at least you have a representation of the programs and you can rewrite them fairly easily. Right click on the root program folder and select "copy folder to clipboard" then paste in a text document. It's probably too late now because if you power up your ISY994 without the PLM it will have a lot of errors and the programs might wipe out and not be of much use. At the very least I would copy from the eisy now to at least have times and schedules even if the programs aren't fully loaded. They'll show the missing nodes (or just say something about the node missing), but times and if's, then's, else text should be available to somewhat help if you have to start completely over. Good luck! Maybe @Techman might have some other tips to try. Either way, if you get support to help you please post back if/when this is resolved to know what was done so it might help others down the road.

How "ancient"? (roughly) How is it connected to the eisy? (depends on your answers to @Techman's questions above.) It's quite possible it is just old enough to have gone bad in the transfer, but not very likely to be the case. Perhaps the cable is not seated properly. I know when the eisy first came out UD had a 2 part cable for the Serial USB. Now it appears to be just one cable. Hopefully that limits connection issues. But be sure that the PLM is connected to a USB port and not the network port of the eisy. Since the "old" serial PLM used what appeared to be a network cable to connect to the ISY994 when you changed to the eisy you have to connect using only USB.

I did use with Alexa for a vibration alert device (attached to our dryer that the end of cycle buzzer has gone out on). The process uses automations within the YoLink app. They are fairly simple based and are easy to setup, but leave a lot of customization out of the process that many take for granted with IoX/Polyglot. While the alerts usually worked, it did seem to have similar issues that many have reported here with links to the Echo system. I experienced a few days where the alerts didn't work. I since started using the YoLink plugin, programs, variables, and notifications to get alerts more reliably. The good thing is you can use both Alexa/Echo connection and the YoLink Plugin to keep the IoX/PG3x system to deliver alerts just as well. You don't have to only pick/rely on one. Note if you get the Speaker hub it doesn't have an ethernet connection so only uses wifi (2.4GHz band only) to connect to the network. When I got my system I got the 1st hub so I could hardwire it into my network. I know 2.4GHz has "long" range, but it also has the most trouble in some mesh/long-range wifi systems where 2.4GHz and 5.0GHz SSID cannot be split (or aren't split). Making troubleshooting connection issues for a system like this more trouble than I want(ed) to deal with. I think the 3rd gen hub has an ethernet port, but doesn't appear to have a speaker. My points for this is that you could get the speaker hub and not have to rely on Alexa for voice alerts, but it's drawback (for me) was wifi only. The other hubs don't offer the speaker so you then rely on the links from hub to other (3rd party) systems for voice alerts (which may not always be reliable and difficult to troubleshoot).

Might be time to open a support ticket to see if other settings need to be adjusted in admin console or underlying system setup. https://www.universal-devices.com/my-tickets Please post back what ends up resolving this in case others have this issue down the road. Glad the PG3x part fixed the UUID issue though!

@mdecou do you have any idea what version PG3x you're running? Not sure if the Zooz stick has anything to do with it, but sometime recently an issue was commented on that no UUID could be resolved by being sure you migrated to PG3x (the Polisy did not come with that version so you must run the process outlined in the Wiki - https://wiki.universal-devices.com/Polisy:User_Guide#Upgrading_to_PG3x). Make sure you pay attention to the note that the user/pass will change for PG3x to match the IoX Admin Console login.

@awzulich as @Techman asks about the Firmware and UI versions this appears an issue when they don't match. Also, make sure that the PLM is connected and that Insteon Support is checked on the Admin Console "Configuration" tab. Reference in wiki: https://wiki.universal-devices.com/Eisy:User_Guide#INSTEON_Support (Note: Screenshot is outdated, but the box is still there.) Once you confirm you Firmware and UI match and the PLM is connected and Insteon support checked you might need to restore the backup again to fix the program issues.

Yes. Exactly. If you want/need to have the ISY at the same IP the current recommended/suggested method is via DHCP Address Reservation at the router level. Since you seem to be running multiple network devices/systems you need to figure out which device to set that reservation on. As you experienced the additional network devices were blocking the ability for the ISY994 to connect externally.

@paulw glad it's working. While I don't suggest going back to the default server I just tested it with my old ISY994 running 5.3.4 and the default server worked fine sending a test. It's possible that it had a momentary outage. Ultimately, glad the Gmail server setup works for you. Most have suggested using an ISY specific account for that. Just make sure you log into that account from time to time as Google is actively closing inactive accounts. I've always been one to try to use the Gmail method so not to rely on UD "default" setup since I know so many others do that don't want to risk a flood of notifications potentially causing delays for my own notifications or damaging the reputation of the UD server that it would suddenly be considered "spam/junk" and not get delivered as expected. That's why many have changed to the Notification plugin for the eisy (and Polisy).

@62vetteefp Lots of good help above, but your information seems to be all over the place. It appears that your ISY994 might not even be on the network. I think you need to review the setup for your network. You have an AT&T modem/router/gateway from what you state above. Connected to that you have an EERO device (this is a router). Do you have the EERO setup as an access point or is it also trying to act as a router? If so you probably have poor network setup and something isn't allowing the ISY994 and your laptop to talk to each other. What is the network cable of the ISY994 plugged into? On your computer what OS are you running? Are you running any VPN or Anti-Virus software? If so turn them all off. No, you DO NOT need to have Portal to be able to access your ISY994 as long as you are local to the device. However when you were logged into the portal could you see the UUID of your ISY994? The UUID should also be the MAC address that you would see on the router. (NOTE: I did just plug my old ISY994 in and it seem to be the case for me. I do NOT have this ISY994 connected to the portal account so it doesn't show up there for me, but did show up in the ISY Finder window and I confirmed by looking at the MAC addresses connected to my router. I say this so that if/when you get on the router that the ISY994 is connected to you should see a MAC address that matches the UUID when you look at connected devices. In the end...I suspect this is a networking setup issue that you have that should be worked our. This also points to it being a network related issue. Sounds like the ISY994 is unable to connect to an outside time server. It's possible that it hasn't been working correctly since the time change (if your area adjusts for daylight saving time). Also by not being able to connect to the time server if the device has floated time it's possible it could be far out of sync of the "real" time.

Do a web search for DHCP reservation for your router. I’m sure there might be step by step instructions available somewhere. Please be sure to read this note from the setup for the Hue plugin that should be key: https://github.com/exking/udi-hue-pg3/blob/master/README.md#notes How are you linking? Are you typing in the address or auto link? If typing in be sure to look really close at the “B” you have…could be an 8 (number eight). Great video from many moons ago on this: https://youtu.be/NMx5yHTU2g4?si=wppSGLBt4FxzpPgd Since it’s an appliance module you might try plugging it in elsewhere to make the initial connection. I’m not familiar with those devices, but know sometimes noise or communication to the PLM can be an issue. I think @IndyMike and @Brian H have a lot of experience with those devices if it continues to fail.

@gschoffstall will you post a screen shot of where you see this error? I don’t use admin console or IoX Launcher/Finder to access the eisy PG3x interface…it’s all browser. On your browser go to https://eisy.local:3000 If that’s where you see the issue there should be a more info and/or a continue to site option. Just continue to the site…since you’re accessing a local device this error is common and can be ignored for local connections (this is commented in the wiki). To bypass this leave the “s” off the url and just use http in the above link to the dashboard. But most web browsers force the https and will give a warning as described in the wiki. If this ends up being an issue with connecting to the Hue Hub then check that you have an IP reservation for the hub in your router. You might need to add the Hub IP to the plugin configuration page so that it will reestablish the Hue Hub connection.

Seems like you didn’t follow the setup instructions that were in the link @Techman supplied. Gmail has required that an app password is set now. Gmail doesn’t allow insecure passwords (I didn’t even think it was possible to turn 2FA off now, but I haven’t wanted to try). Be sure you follow these steps: https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_(unique)_App_Password I’m not entirely sure if you need a from, but doesn’t hurt to be sure it’s included. Just pay attention to the formatting (again…as described in the wiki). Lastly, if you’re trying to send a test make sure you click on a recipient for the test to go to. If you have more than one it doesn’t know where to send the test and might cause a failure. Using Gmail server (if setup properly) does work. That’s what I’ve used from day one. I don’t use many alerts, but know it worked as of the last 3 days.

I believe this is normal. You can find other conversion comments in the forums that seem to indicate this is expected. Make sure you follow the rest of the steps that @Techman linked to in the wiki. Pay attention that the user/pass will now be the same as admin console access. Once you confirm you have PG3x then run the upgrade process again and you should update to IoX 5.8.4 (the current release) If you did not get upgraded to PG3x in the process then please open a support ticket to get specific help for this issue. https://www.universal-devices.com/my-tickets/ If I was running a Polisy I wouldn’t worry about upgrading to eisy until UD made an official announcement that they would end Polisy support/development. No need to worry about it at this moment. Also no major need (from why I can tell) to rush an upgrade to the eisy if you have a working Polisy doing what you need it to do.

@Tony-D unsure how to run Java on rpi5, but you need some sort of java platform like what Windows users have for javaws. Perhaps the best bet since you're on rPI would be to use the direct admin.jnlp downloaded from the ISY994 rather than trying the launcher (that has been the standard for over 6 years). Try: http://ip.of.the.isy/admin.jnlp (be sure to change to put your actual IP address for your ISY994) No browsers are necessary. It's all independent of the browser. Once you have the admin.jnlp it should log directly into the ISY994. Note: If you ever update the firmware you'll need to clear you Java cache and download the admin.jnlp again from the updated firmware. If you still have access to your friend's windows Laptop make sure it's on the same network as the ISY994, download the start.jnlp from the UD website (clicking on "MY ISY" on the top right). It should put the "IoX Launcher" icon on the desktop. Use that to access the admin console. Again, no special browser process is needed. It's directly Java related since all browsers dropped the Java script method used many years ago. One thing to consider is if you set a static IP address on the device and changed routers you could have changed your DHCP table and the ISY994 might not be connecting to the new DHCP range. Since you still have your old ISP and if/when you can get into the ISY994 make sure you change it to Dynamic IP so the ISY994 will connect to the new router. You should then setup an IP reservation on the new router/gateway so the ISY994 is always at that IP. DO NOT SET STATIC ON THE DEVICE! Review these sections of the wiki: https://wiki.universal-devices.com/Main_Page#ISY_Launcher_cannot_find_ISY https://wiki.universal-devices.com/Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop

Not recently. As @Northwoods Ranger said above there were some issues a few days back, but UD fixed them (at least appeared to). I didn't have to do anything for the routines to run again. Perhaps it would be a good idea to reboot the Polisy (full power cycle). I've noticed a few times (as I think others have posted and commented as well) that Echo routines will sometimes not fire and it's apparently an Amazon/Echo issue when they update something underlying that breaks the routines coming from skills. They end up getting resolved randomly. It's somewhat a goofy system (IMO) and sometimes I don't consider it very reliable. I don't run any mission critical processes through Echo routines and rely more on notifications plugin and UD Mobile for alerts. To me relying on a 3rd party system is just begging for issues (as you describe). Sometimes it works...sometimes it doesn't. If I have an alert it's only going to be critical so I prefer to keep things within the IoX/PG3x system to send me alerts rather than sending out to Echo. I'm not sure how to do this either, but I know if you look at the routine it does have a "View Activity" choice if you click on the three dots in the top right of the routine (I'm on iOS). In there you'll at least see if/when the routine was triggered. How are you changing the variable to trigger the routine? If with program you could just "Run Then" or "Run Else" however you have the program setup and see if the variable triggers the routine. If it's a big issue for your system you might be better off submitting a support ticket so UD can help track the issue with you. https://www.universal-devices.com/my-tickets

@arzoo you could use the raw text portion of the find/replace option in the programs to potentially find a time reference. Or I would suggest you copy the root folder to the clipboard then paste in a text editor and search for time or other triggers in the text of all the programs. (right click on the root folder and select COPY folder to clipboard - NOT "export") Have you checked the summary tab for the programs? Anything showing "last run" at the time this happens? You originally said it was happening at random hours so maybe you'll see it during the day rather than 1am time.

@RRoyceus split your post out from another topic that was troubleshooting other issues. Which version are you speaking of? That post was for 1.1.68. Have you updated to 1.1.71 for iOS? (that's what's available in beta test as of this reply). Sync should be in the 3 dots at the top of the Home, Automations, and/or Settings tabs. It shows there for me. Tapping the three dots gives: Synchronize My Account User Preferences UD Mobile Backup Bluetooth Wi-Fi Configuration Show Hidden Nodes toggle

@Guy Lavoie just be aware that if using "wait" should the program turn false while waiting the program will stop running (or run the "else"). If you're going to use the wait sometimes it might be better to break it into multiple programs. You can have programs that have nothing in the "IF" statement and you can use the trigger program to process the "THEN" or "ELSE" of another program. In that other program would be the "wait" portion and not be impacted should the "IF" of the first program be re-evaluated and turn false. Good luck!

@Guy Lavoie welcome to the Universal Devices forums. A lot of what you're asking can be found in the "ISY Cookbook" that's found in the UD Wiki pages (https://wiki.universal-devices.com/Main_Page). The ISY994 has been discontinued (thus probably the reason you were able to get it "cheap"). It still works and is operational at many levels. Some of the documentation/examples in the ISY Cookbook are from older firmware versions for IoX (formerly ISY). Just know official support from Universal Devices is no longer offered. However, the user-to-user help on the forums is always available to help troubleshoot and give guidance. I'm not familiar with x10 signals, but many here are. Hopefully they can help with some of the specific questions you might have. There isn't a "simple" way to make a timer like you're thinking, but there are options. I searched on the wiki and found this topic: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Programs_as_Variables:_SwitchLinc_Emulates_Countdown_Timer (Note the link at the top to a different document as well) One thing to note about ISY programming...the "IF" statement is always being evaluated. Therefore, when your program triggers "TRUE" it will trigger the "THEN" portion. Otherwise, when "FALSE" it will trigger the "ELSE" command. Many programs will only have a "THEN" portion. If you have specific programming questions head over to the IoX Program Support area and post in there. https://forum.universal-devices.com/forum/438-iox-program-support/ Be sure to let us know what you're trying to accomplish and read how to post programs to the forums. Posting programs as text is the preferred method. Again, welcome to the forums. Good luck learning!

@andrew77 glad you’re up and running. What was the actual fix so we know and it might help others if they have similar issues?

@majkman what version of PG3x are you running? Are you on Polisy or eisy? If on Polisy you might need to upgrade to PG3x if you haven't. Details on that can be found in the wiki. If you're on eisy make sure it's updated. Current version should be 3.2.27. If you're not there then you should update. Last option would be attempt to install in a different slot and see if that works.

@andrew77 best bet would be to open a support ticket with UD. https://www.universal-devices.com/my-tickets Sorry I can't help on the macOS side as I don't run that and don't have access to anybody running it. I'm 100% Windows. Seems like macOS throws curveballs now and then with the Java process.