Geddy

@telljcl Thanks for the reply and images. Have you clicked on "start" or "restart' on all the node servers? It's strange for them to all being showing disconnected. It's as thought they've never started up. Especially since all show 0 (zero) nodes. The configuration for the nodes needs to take place in the PG3 screens (mostly...at least I've found that's easier and more accurate for some I used previously. I don't have any devices that would use these node servers so I wouldn't be a good one to try to buy/install/setup, but I did just run the Kasa NS on PG2 and it started right away. I'm not seeing any setup that needs to be done for Kasa. So I assume in PG3 it would be the same. Have you read the Kasa README.md information found in the link from the node store? Read here: https://github.com/UniversalDevicesInc-PG3/udi-poly-kasa/blob/master/README.md Once it's starting it should find devices on your network. Since it doesn't require any log-in information. (At least not what I see on PG2 version). But in your RainMachine screen shot above click on "Configuration". That's where you should enter (probably the information you entered from the ISY side). I've always just done the configuration from the Polyglot side (either in PG2 or PG3). That then is what is fed to the ISY (in this case IoP). Then be sure to click on Start or if you find it's running click on "restart". Also, click the "LOG" button and see what is being logged. If there's a setting to change to debug set that and then "restart" the node server. Give it a few minutes then "Download Log" (this will download just that Node Server log). Here's what you want to look for: Once you've downloaded the log then read though there and see if there are errors trying to connect to the IoP or other obvious errors. I wouldn't post the log here (not yet anyway) as I don't think the developer is very active at this moment (I think they're busy moving) so you're going to be relying on others that might use this Node Server to help you from there. Perhaps this gets you going. Post back if you get some of them working or still having issues. Hopefully others with this node can help out some of the configuration settings to help you out.

@telljcl Have you added your IoP to the PG3 settings? Please read this section of the wiki: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#ISYs As @Bumbershoot points out most of the configuration will be as you apparently have attempted, but you need to be sure the ISY on Polisy is properly added in PG3 setup. Otherwise, the information for the node server (or any node server for that fact) won't know where to send the information. Perhaps sharing some screen shots of what you see might help further, but sounds like you're on the right track.

It’s not hard to find…it’s in every ISY994 Firmware release announcement. for 5.3.4: https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ You’d download the one that says “if you do NOT have a PLM”. This way the ISY wouldn’t boot into safe mode if/when the PLM isn’t connected when it boots up. The help -> about section will look different too, but when you use the ISY Launcher to open the admin console FW/UI will still match. So once you do that make sure they match…looking at the part before the version numbers (if I remember correctly).

@GQuack I believe you're referencing this thread - Always a good idea to actually include the link if you're bringing up an old topic that's been closed. Perhaps @lilyoyo1 can explain the process and help you further.

Not sure about the Yolink process, but some others use Alexa routines (and I think Google Home) to make announcements. So if you already have one of those home (monitoring) speakers you could try those first. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3#ISY_Can_Talk_To_You.21_.28Alexa_Routines.29 I just recall others mentioning it on the forums. Might try a search (or Google Site search) for the references to that.

@isyrocks! the easier/better way to share programs on the forums is to right click on the program, select the bottom option ("copy to clipboard") then paste the program to your message/post here. This captures all the important parts, and it makes it searchable and editable for anybody helping you. Result of paste: 00-Query All - KEEP - [ID 0000][Parent 0001] If Time is 3:00:10AM Then Set 'MyISY' Query Else - No Actions - (To add one, press 'Action') Also, is there any reason you're on 5.3.3 on the ISY994? The latest version is 5.3.4 and a simple update/upgrade from what you're running. Very small fixes were made, but still, suggested to go ahead and get up to the latest version since you're almost there already...and you said you have z-wave 500 so it's okay to update. I don't think it would help your issue, but wanted to ask and suggest the update. Your initial "away" program seemed long. If you had it doing a lot of things without the waits there was risk of missed signals going out. Sometimes it might be better to break processes down into smaller chunk programs and have one program trigger additional programs (with waits between those triggers). And you scrambled a large chunk of what you're trying to turn off. It might be something that you have a program simple as: If: armed away then: Run "THEN" of away program 1, wait 10+ seconds, run "THEN" of away program 2, wait 10+ seconds, run "THEN" of away program 3 The "Away Program #" would not have an "IF" value and would be disabled. Thus the only time they would run was when called on by the "armed away" program since they would specifically process the "THEN" of those programs.

While that works as long as you keep your current setup. It's sometimes unavoidable when you change brands of routers. Unless you always make a mental note to change your DHCP back to what you had previously. I don't usually worry about setting DHCP reservations, but it seems to be becoming more expected that people do for situations like this. What's interesting is that another automation process found the Hue Bridge without issue. So somehow the node server is putting the IP it found the bridge at into its configuration for when it gets loaded again and ALWAYS looks at that location. Thankfully it can be changed with the custom configuration setting, but that requires a different way of indicating the IP address.

You stopped reading too soon. That multi function button when pressed as described "resets credentials". It doesn't "reset polyglot". I recall having to reset credentials using the button when I first got my Polisy (about a year ago). My assumption would be that it should still be functional that way. I've actually not tried it since IoP was running on the box. Would need to be a question for @Michel Kohanim or @bpwwer to answer. In this case Polisy = Polyglot It appears in the "old" PGv2 screen it's showing as "Polisy Version 2" logging in, but that's just the Polyglot v2 login screen. When you go for the PG3 login you see:

Nice catch. Yeah, wasn’t on my radar to check since FW/UI didn’t match. But power supply is a step in troubleshooting so glad it was noticed. sadly, I have my ISY behind doors so I don’t see the lights often. They’re so bright though! Glad you got things running again.

@Bumbershoot I'm not sure if it would be something I'd attempt on the IoP. I know @Michel Kohanim had advised against that method on ISY994 in the past in the 5.x process. And I'm not sure what he's doing to get people to the point of having that button available in IoP. I'd suggest opening a support ticket and see if there's a process to update specific IoP processes to get that button. Is there not the auto update function available in 5.4.3 IoP? From the release note there's this process: Either way, let us know what you end up doing. There's been several other posts about this and haven't heard back from anybody as to what process they went through to get it upgraded to have the button available. Apparently that button is introduced in 5.4.4 (the most current release).

@tedolsen thanks for clarifying. Just seemed really strange. If you're still having issues then I'd suggest opening a support ticket with UDI. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com It seems you've tried almost everything. I think if you're having connection issues just changing the microSD card might not really be the fix for you since you have to have it make a connection to the network for you to be able to telnet into the unit to install the firmware on the new microSD card. When you submit your ticket make sure you mention you have 2 different networks and it will not connect to either and be sure to have a clear explanation of the light pattern. It might even be good to take a short video of it and attach that to your ticket. Good luck! Please post back once you get back online what the solution is so it might help others that might have this issue.

just to confirm...you're using a wire to connect the ISY994 to some network device. Right? The ISY994 DOES NOT HAVE WIRELESS...you say you can't get it to connect to a wireless network...how would it? Have you attempted to plug the ISY994 into the AT&T gateway and it still won't connect? And you put it in DHCP status recently?

Why do you have 2 devices handing out IPs on your internal network? Have you always done that or are you setting up new routers? Do you mean to have two different wireless networks? They can't talk to each other since two different devices are handling the connections. Usually this is not an ideal situation. Either the AT&T gateway should handle everything or it should be put in bridge mode and let the eero device handle everything. Since ISY994 is hardwire only and not wireless which device are you connecting it to? I still think this is Network related. Especially since you said you let eero handle one set of IPs and AT&T Gateway handing out a different set of IPs. Sounds like you're connected to the eero and it's not actually sending anything out to the internet. Connect the ISY to the AT&T gateway and see what happens. I think @Techman and @MrBill might be onto something too about the SD card, but my thought is that it's still network related. I think what @Techman pasted above (from the Wiki) just doesn't clearly say the RX light would also be on. If it's always trying to make an internet connection then I think the RX would be on because it's trying to communicate. The flashing memory and error are what are indicating network issues.

@GFuller01 moved your post to a new topic since you seem to have multiple issues and not really related to prior post you tagged on to. It's possible the ISY was setup for Static IP on the device and when you connect it to the current router the DHCP table is different. Therefore the ISY is unable to connect to the router. Have you ever used this ISY? Even though you say it's "NEW". Is it "new to you", or was it still in the box new and never been powered on? What does this mean? You mentioned scan link (from this post), but does it show up on your network? Make sure you've connected all the cables to the correct ports: Be sure you plug the PLM in first and allow it to power on (about 15-30 seconds) then power on your ISY. Please refer to the ISY Wiki for additional setup and troubleshooting steps: https://wiki.universal-devices.com/index.php?title=Main_Page

I don't think this has been covered anywhere. My suggestion would be to open a ticket with support to make sure any steps needed to be done are done in the correct order and the process. It might be different depending on package versions being run. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@tedolsen Please refer to the wiki for what the lights mean: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights What brand router are you using? If you have auto DHCP set on the ISY then log into the router. Does the router show the MAC/UUID connected anywhere (new IP)? It does seem that you're having network issues. Do you have ISY Portal activated for this device? If so, log into my.isy.io and see if it is reporting the ISY online. That should at least give you the remote access URL that you can use to get Admin Console to load (remember to log in with ISY Portal user/pass). It's always best to set a DHCP reservation on your router rather than static IP on the ISY. For this case for sure. If you change the router and available networks it might not be able to connect if the ISY is set to get a a static IP that's no longer being offered from the device handling DHCP routing. If you have a PLM make sure that it is powered on and connected before you power on the ISY. It's possible that putting the network into the PLM port and the PLM into the network port (on a ISY994).

@EricBarish I've never had this experience. If you're setting it up in ISY Portal and then instruct Alexa to discover devices it's instant. I don't use variables, but for any device (ISY, Hue, Kasa, or Wireless Tags) I've never had to wait 24 hours for them to show up in Alexa. Setup the device through my.isy.io. "<echo wake word>, discover devices" couple of minutes later all devices are added to Alexa. Can confirm in Alexa app and on alexa.amazon.com -> Smart Home -> Devices If you're having to wait 24 hours for a device to "show up" on the Alexa app then you are having service issues. Hopefully @EMercado will let us know what fixes this. I think @Athlon identified the issue that the Alexa Skill wasn't enabled (and linked). Makes the most sense. Also an oddity that I've not experienced, and I have several devices that have ramp rate about 1-2 seconds at various times of day. Perhaps you should review that further. If you have issues, and it's troubling to your setup you should start a thread in the Echo area of the forums and tag @bmercier as he's been the primary one to review ISY & Echo issues.

@Bernman Glad you've got the launcher working and see the device. Try the default (admin/admin) first just to be sure that's not it. Then good luck hunting for that information!

Welcome back to the forums. Good luck with what you want to attempt. Just to be sure...make sure you do have an ISY994 and not a very old ISY99i. When was the last time you attempted to access the ISY994? Were you able to get admin console to load? If you can open admin console please go to "Help" -> "About" and post your screen shot of the firmware and user interface you are using. If you cannot (or have not) access admin console recently note: ISY Launcher - a new process for accessing the ISY Admin Console; released in 2018 in this post: https://forum.universal-devices.com/topic/24381-isy-launcher/#comments This method does not require a web browser to remain open as the old (now, very old) process used to. Since most browsers don't directly allow that java process to run. Firmware - If you are on Firmware 4.x then you can use the auto update process to get up to 4.9. This is the last version in the 4.x branch and the auto update to this level does not require much involvement. Release notes about changes in 4.9 are found here: https://forum.universal-devices.com/topic/31907-release-49-isy994-last-release-on-4x-branch/ Update - If you're feeling more adventuresome and wanted to venture into the 5.x world then get ready for some work. It's quite a process and requires that you follow the steps very closely. Make sure you read all the update process steps before attempting so you know what to expect! Since you say you have "simple" programs that are mostly just timers you might not have much to adjust, but if you use scenes and "adjust scenes" in programs then you will have more to adjust. Current release for 5.x branch is 5.3.4 and can be found here - https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ Ultimately, it's up to you to determine if you're good with how it's running just to make your minor adjustments and let it keep rocking & rolling. Otherwise, you can update to the version you're most comfortable with. I might suggest just going to 4.9 if you're already at 4.x just for some slight bug fixes and modifications through the years. Since you don't have a current need for node servers and aren't running a new Polisy then 5.x isn't really necessary. Finally, for review and tips and other help please review the ISY Wiki - https://wiki.universal-devices.com/index.php?title=Main_Page Let us know what firmware you're currently running and be sure you confirm you've got an ISY994

PLM -> wait a bit (I think light should be solid green?) -> ISY Make sure PLM is plugged into correct port on ISY994. Make sure your ISY is connected to your router via network cable (again using correct network port). Make sure your ISY is online. Go to my.isy.io and log in. Confirm there is a green dot for your ISY. If you hover over it then it should show "online since...". If not online then perhaps your ISY Portal has not converted over correctly (since you said you had Mobilinc previously, did you have/use their portal?). Make sure ISY Portal is active on the Admin Console. You should see this on the Configuration -> Portals tab in the admin console: Did you follow the steps to switch from MobiLinc to ISY Portal - https://wiki.universal-devices.com/index.php?title=Main_Page#Switch_from_MobiLinc_to_ISY_Portal I would try with your old PLM first. Using a different PLM is a little more complicated than just switching one out. There's a process you have to follow.

@EMercado Also, check the Alexa App for devices to see if they appear there. There's also a way to check from a website by going to https://alexa.amazon.com/ and the clicking on "Smart Home" -> "Devices". You should see the things you have setup in the Portal in this list and should show "ISY Device address" under the device name. If you don't have devices showing up on the Alexa app or on the website then @Athlon is probably correct that you haven't enabled the ISY skill for Alexa to fully complete the connection. Alexa skill information: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3

@tritip.films What MacOS are you running? Sometimes Mac users have quick success with ISY Launcher. Other times it's a struggle. I don't know why, and it's strange. Even some that it works great for months/years suddenly will have a time it doesn't want to pay well. To me it's just Mac+Java = issues. Make sure you've followed the steps mentioned in the wiki for MacOS users - https://wiki.universal-devices.com/index.php?title=Main_Page#MAC_Users What brand is your router? In your image above you say the *.36 IP is not for the Polisy, but does appear to be for your original ISY994 box since the UUID matches. Check your router IP table (connected devices/DHCP table). Make sure your IP for the UUID/MAC address is what you think it is/should be. Something is reporting the 192.168.1.36 address as an ISY. To me that means you don't have DHCP reservation for your ISY994 box and it's changed. Are you able to log into devices at both the 192.168.1.16 and .36 addresses? Or does only one connect? While logged into your Router look for the MAC address for your Polisy and make note of the IP address. Then in finder add the IP address as described in the Wiki Polisy User Guide (https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can.27t_Find_Polisy)

@MNicholes Do you have 2 step authentication turned on for your Google account? If so, I think this might be a case where you would need an app specific password for Google and apply that to the node server. Using your Gmail address as the user name and the app specific password for the node server setting. Learn more about that from Google: https://support.google.com/accounts/answer/185833 I don't use this specific node server and haven't changed the MyQ app to use my Google account so can't help specifically, but knowing that Google no longer allows unsecure apps to sign in with just user/pass you have to have the app specific password option. So think this would apply in this case. Give it a try. Let us know if it works.

Don't pull that hail mary until necessary! You're not there yet... Log into your router to make sure you see the Polisy IP address from the router. It's possible that you didn't have DHCP reservation for the Polisy and it's changed. Some routers cannot handle the https://polisy:8443/desc routing and must use the IP address. Were you able to use the polisy:8443 url previously or relied on IP address? Also, since you said UD Mobile can access, the device is online and accessible. It's simply that the local IP might have changed. Can you surf to the PG3 web interface? (<polisy IP>:3000)

@Chris McKean glad you got them working! Probably didn't need to remove them, but perhaps could have restarted polyglot for it to force the connection to the IoP once the credentials were correct.