Geddy

@TheA2Z you could also review this post if it gives any tips/tricks. Seems to be similar to what you're wanting to do and how @tazman describes involving Routines. I've never explored this path so don't know if this post is still relevant or not, but know many referenced it in the past.

@UD2)17rrh did you update the eisy recently? If so, have you performed a full power cycle? (not just pressing the reboot button in Admin Console.) It sounds like some processes are not running correctly and the device needs to be power cycled for things to get back in sync. Best practice would be: Pressing the power button 6 times (that's the multi-function button on the eisy) Blue light should turn red (might take some time - if longer than 5 minutes something is probably "stuck") Pull power cord Wait 30-60 seconds Plug device in Wait 3-5 minutes for it to fully boot before attempting to access the web interface or admin console. The credentials for the web access are the same you use to log into the Admin Console locally. Rather than trying to access the web portion from the admin console open a web browser and go to: http://eisy.local:3000/ - See if that gets you to the login screen. If you still don't get logged in try that on a different browser (cache could be stopping you if you've tried multiple times on your current browser).

The only path to migrate to the eisy is with firmware version 5.3.4 on the ISY994. Therefore, you'd have to go through the (possibly painful) path of updating the current system (if you're not running Z-wave you could go all the way to 5.3.4) then making a backup to import to the eisy. Please review the wiki for migration steps: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994 For the backup of programs you could copy all programs to a text document and recreate them manually. It's time consuming, but might be "easier" to do that than updating the firmware to a version that would migrate and run the risk of issues in that firmware update and then more/different issues in the migration. Right click on the root program folder ("My Programs"?). The last item should be "Copy folder to Clipboard". (note: be sure you COPY, you do NOT want export) Then open Notepad (or other text editor - NOT a word processing program because you do not want the text manipulated). Paste in the text file and save as plain text document. This will be all your current programs.

@gschoffstall what does the node server look like on the PG3x dashboard? Does it show nodes? If not then the hub hasn’t linked. If you reinstalled the plugin you might have to link the hub again. Restart the plugin then press the hub button again. If you have nodes being displayed on the web dashboard for Polyglot they should push to IoX when admin console is reloaded. You have been doing a lot of different settings changes…please make sure you haven’t altered the IoX configuration in Polyglot. Click on “IoX Configuration” then “Edit Current IoX” and make sure the IP is 127.0.0.1 (or maybe localhost). Beyond this point it might be best to get help directly from UDI. I’ve got you this far along. I’m not sure why it’s not working and they can diagnose with you to get you running. See link in a post above to start a ticket.

@gschoffstall Have you closed/restarted Admin Console? You should NEVER have to setup anything in Admin Console as you're suggesting. If you have it could have overwritten something the node server was pushing there. Did you see my comment above about not having Admin Console open when you add plugins? Nodes are only added to Admin Console on launch. So if you added Hue and AC was open then you have to close and restart it. The nodes should be pushed into the primary tree of devices. It's been so long since I added mine I forget how they were entered. But you shouldn't have to do anything in Admin Console to make the lights appear in the device list. I put all devices that use a plugin (formerly Node Server) in a "NodeServer" folder. Just easier for my preference. Once the node server finds the lights they should be nodes in the plugin screen. From the dashboard you should now have this: (disregard the number on my Nodes and your screen will say "Hue (1)") Your dashboard (assuming you got the hub to connect to the plugin) should display the node count for your system and should be for all lights and rooms you might have setup previously in the Hue app. You can click on "Nodes" or "Details" (they take you to the same place). Then click on "Nodes" again and it should take you to a list of items it found when it synched with the hub. Look in the "Address" area. That should now correspond to a device in the IoX Admin Console with a "n001_" prefix. That means it is a node from node server (now plugin) in slot 1 and the address is the identifier for that device. In the Admin Console you should see it by a common name seen in "Node Name 1". If you click on that device on the right side of the screen under that name you should see the "n001_#######" information. Now...since you said you did something in Admin Console to make Hue node server 1 it might be okay just to re-launcher admin console. Or you might need to delete what you did there by clicking on that listing and clicking "Delete" at the bottom of that window. Do THAT as last resort! Just close and re-launch admin console to see if it fills in nodes/items in your device list.

No need to get hostile, and nobody suggested this would be closed. You're missing the point. UDI handles support through their support ticket process. Of which you had apparently already started one. @Michel Kohanim has stated multiple times (and again recently) that they do not have the time to read (and reply to) the many posts of the forums. Thus, I suggested you go back to handling your issue through the already started support ticket. Ultimately it comes down to the fact that there are probably many more tools UDI has at their disposal through the proper support process rather than posts on a user-to-user support forum. And it would be wise to know that I'm simply a volunteer here and a user, just like you. So please refrain from getting short when it's suggested that you follow the typical suggested route for assistance that UDI needs to be more involved with. Enjoy your day!

@gschoffstall woohoo! That was "easy"! It's my understanding that you don't need an "active" license for plugins to work. You just need to have the device registered on the portal since all installations use the portal process to assign the license. I'm like you and prefer to do most stuff local, but it is nice to have the access that the portal license adds (my family likes to use Alexa to control a few lights here and there). For the cost of 2 years for only $39 it's a steal! (look at others that have similar offerings and they're like 10+/month. UDI offers a lot of benefit with the portal license for less than $2 per month. It's an amazing deal. Plus, with UD Mobile in active development it's even easier to do so much more from the mobile device while away from the property. But, I get it. Glad that worked out. Happy automating!

HA! That might be the issue right there. If the eisy isn't registered on the portal then you can't install plugins! That's why I asked "Is the eisy registered with your portal account?" Instructions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions If you're not using the ISY994 anymore you can migrate that portal subscription over to the eisy. Portal Migration instructions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Migrate_configurations_to_a_new_ISY Once you get the eisy registered in the portal it should work as expected. If you're stilling having issues start a support ticket go here: https://www.universal-devices.com/my-tickets Yep...device isn't registered with Portal. That's the issue. Once it is you should be able to install without issue.

Yeah, hasn't updated. That's strange. And you said you've performed a full power cycle. Typically that would be the best thing to do even after an update. I know there were some older updates that the reboot button alone wouldn't fully reset the system. Since this is a PG3x update the power cycle really should have helped. I saw this earlier and overlooked it since I'm not sure what this means. Make sure to include it in your support ticket. Perhaps download the log package and include that in the ticket too. It might help UDI review the situation before initial reply and troubleshooting steps. Sorry couldn't get it to magically update. Should be able to get some help from the support ticket though. Be sure to post back what happened and maybe the steps to get it to update in case others have issues.

@gschoffstall I never suggested to clear Java Cache. That won't work for this issue. That's only good step for admin console issues. I think you would be best served by a support ticket. It's late in the day on Friday. If you opened a ticket now you might get a reply Sunday or Monday. In the meantime... Just out of curiosity though try installing another free plugin (like ping). I wonder if it's the Hue trying to install or if your system won't let anything install. Have you successfully installed any other plugins or was hue your first attempt? I just tried installing the Hue into a different slot and it installed without issue. My feeling is you might have a corrupt file on your system somewhere. Not sure when you last updated your eisy, but have you performed a full power cycle of the eisy? Click the power button 6 times The blue light should turn red Pull the power supply cord Wait 20-30 seconds Plug it back in Wait 2-3 minutes (maybe more) Try only logging into the web dashboard (http://eisy.local:3000) Attempt to install Hue - try a different slot than you've been trying.

@johnstonf If you've got a support ticket going with UDI please handle all support for this issue only through the support ticket process. You can post a conclusion here once they get you resolved through the support ticket process. Not fair to have @Michel Kohanim and/or @bmercier trying to resolve both here and through the support ticket. The ticket process helps UDI keep up with issues and resolutions internally.

@gschoffstall I forget that you can open PG3x dashboard from within admin console. I never go that way and just go directly to it on the browser. Shouldn't make a difference though. Just know that if you add plugins with admin console open you'll have to restart admin console for new nodes to display in the admin console. It only picks up changes from PG3x on launch. I usually make the suggestion not to have both open/logged in at the same time. The 404 error is not one I've seen before. You should open a support ticket on that unless @bmercier or @bpwwer might chime in to give an idea on that error. Not sure where "AxiosError" would play into this.

Seems like you're reading the how to install on the node server page I linked to, that's outdated. You should take some time to read the Wiki about the "eisy Dashboard" to learn the steps to install plugins (formerly Node Servers). https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#eisy_(PG3)_Dashboard Some of the "older" node servers plugins haven't updated to the latest "install" notes for PG3x since they haven't been updated recently. PG3x handles all the install process. Once installed That's normal. Looks like you might be on macOS. Click on "Show Details" and there should be a proceed/continue type of option. You should get to the PG3x login page: Login with your admin console user/pass Then you'll want to click on "Plugin Store" Once you're on the store page just look for the Hue plugin there. Follow the steps on the PG3x interface and Plugin Store to install. Then refer back to the link above for the Hue plugin for setup. It's fairly simple, it will start and then push the button on the hub and it should connect and add nodes. REMEMBER: Do NOT have Admin Console open at the same time that you add/install/update plugins. Admin Console must be reloaded to update any nodes added.

Sounds like you might have something stuck that is preventing the update. Please open a support ticket to get specific help for this issue. One thing to check. Go here: https://polisy.local:8443/WEB/sysconfig.txt (you might need to use the Polisy IP rather than "polisy.local"). Look for pg3x-3.2.13 (or actually pg3x-3.2.14). If still showing the old version it should show a date that was installed. Please share the resolution if you can so it might help others should they also get stuck. https://www.universal-devices.com/my-tickets

@gschoffstall Would you be able to share some screen shots of these errors? What "certificate issue"? What's the reference to Github? 404 is an authentication issue. When you log into PG3x you're using the same credentials used to access Admin Console. How are you accessing PG3x? I use: http://eisy.local:3000/ (you might need to replace "eisy.local" with the IP address of your eisy. If you're using https://you.eisy.IP.address:3000 then you're probably getting this certificate error: Click "Advanced" (I already had in screenshot above). Then click "Proceed to...". Then log into the web access for Polyglot (PG3x). Things to check: Is the eisy registered with your portal account? Just to be sure your portal is connected correctly try this Click "System" Click "Switch Portal Profile" Login to current portal account Make sure Admin Console is closed while added plugins (I keep typing node servers!!!) The "More Info" button does not link to the correct location. Once you get it installed refer to this for setup if you have further issues: https://github.com/exking/udi-hue-pg3 I've already got this one installed, but when I go to the hue node server plugin screen this is what I see: You should be able to click on "Install" and then you should get this window: (Make sure you SELECT A SLOT to install to using the lowest drop down marked "Select Slot"!)

I'm not sure if the Polisy might work more like the eisy since going to PG3x so you're probably best as @DennisC suggested of opening a support ticket. On the eisy if you don't plug a network cable in the wifi is enabled on boot and you can setup the credentials in UD Mobile. I don't know if changes were made to the Polisy to be able to do the same. Perhaps it's something that UD Mobile sets up for the Polisy. When you get the answer please be sure to update here so it might help others in the same situation. https://www.universal-devices.com/my-tickets

Yep, it's still there. Try: http://eisy.local:8080/WEB/udajax.htm If that doesn't work use your eisy IP address in place of "eisy.local". There's also been talk of UD Mobile running on computers, but I haven't kept up with that because it's mostly for Mac (M# chips) and Win11 (with Android somehow) - of which I have neither at the moment.

@johnnyt understood. I've suffered similar issues, but never thought that I'd need to turn the device off for the time change. If a reboot is all that might be needed just have your plug reboot it after the time change. Sure it might be better to go through a shutdown process, but unless it's on a UPS it would be just like if the power went off. It should typically recover. Otherwise, just turn it off for the night and back on the next morning. I know Michel has said he doesn't have time to monitor all the forums these days so if you think this process is necessary it might be worth asking UDI directly in a support ticket to see if possible to complete what you're wanting to do. https://www.universal-devices.com/my-tickets

@johnnyt May I ask what's the reason to power it down at that time? No clue about being able to have a program to try to power it down. Why not just leave it on like every other night?

If you tried yourself then it sounds like T-Mobile is like all the other carriers that were slowing this down or disabled this service because of the amount of SPAM sent through this method. It's been commented here many times that email to text was an inefficient way to get alerts (going back several years now). Email to email or using other notification methods is the suggested route. Perform a Google Site Search for SMS delayed notifications and see some of the old conversations. Additionally, just random web searches result with these two topics on the T-Mobile site: https://community.t-mobile.com/apple-8/sending-text-to-my-cell-phone-using-attmomail-net-no-longer-working-51741 https://community.t-mobile.com/t-mobile-com-account-62/text-messages-from-python-program-no-longer-getting-through-52034

@apostolakisl moved this over to the ISY994 forum since it wasn't PG3 related and now seems like you're having ISY994 issues. Good luck getting this resolved.

I do not think this applies to you. Just reviewing the wiki the only "bolded" sections that mentions migration backups is under the portion related to moving from Polisy to eisy. I think it is/was related to the migration from another z-wave controller to the Z-Matter board. You don't use Z-wave so does not apply to you. As @DennisC posted above the move from ISY994 to eisy with only Insteon devices is very simple. You just needed to get both devices updated. Sounds like you were not running the firmware on the ISY994 that would make the migration possible. Could you provide a link that you reference here about not being able to find the ISY994 firmware? All "current" releases from UDI can be found referenced on the forums in the "Current Release Announcements" area. In the migration steps there is a link directly to 5.3.4. If you found a link that seems to imply something was superseded it would be good to know what you read so it can be updated if needed. Glad you found it, but if you're reading the migration steps it is fairly clear in the instructions: (Source: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_ISY-994) Hopefully you've successfully completed the process now.

@DSwallow seems like you've got more experience to try to troubleshoot stuff and digging deeper than most would go. If this is an issue causing you not to be able to access the eisy then I would suggest you open a support ticket for specific help from UDI rather than user-to-user support mostly found here. Their troubleshooting process might be better suited to fixing what might be causing this for you. https://www.universal-devices.com/my-tickets

Try deleting the .state files from UDI. Also clear Java Cache (temporary internet files) and download a new start.jnlp file from the UDI site (click on "My ISY" on the top right). https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored (not the same problem, but it's where stored information is kept) The issue of reliably getting the friendly URL to display (I've found anyway) is a local network issue. Either router or device times out during the handshake and cannot get it to reliably show. I'm sure anybody with more network experience will contest this, but from personal experience I've seen some routers never auto find, sometimes auto find, or always auto find the URL. Because of the issues people have had over the last year I've tested with some "old" routers I had access to and the process was fairly inconsistent. Some of the worst offenders were "mesh" router systems. Also, some people have reported that IoX Finder window sometimes will report both the IP and the Friendly URL address. That's fine, and has been confirmed as "normal" by UDI. Both go to the same device and since they are discovered automatically are unable to be deleted. Once you have either/or in the IoX Finder window you can SAVE the list locally and then LOAD it should the list ever not populate. I think the steps above might help this issue too. At least clearing the Java Cache and starting admin console fresh might help. One last question - are you experiencing any of this on a laptop that you sometimes use outside of the home/network or with VPN? I've found if I'm on my laptop and travel with it and try to log into the ISY my "local" addresses will drop off the list while I'm gone. Typically they will auto discover next time I'm in the home network.

@sjpbailey Perhaps check these posts out: