-
Posts
2671 -
Joined
-
Last visited
Community Answers
-
Geddy's post in Managed to get a folder (not iox) at the top the tree was marked as the answer
Do you have a backup from before folder creation? I'd restore that backup and see if that puts things back to "normal".
Can you share a screen shot of this?
There should be a root folder then a sub folder that would have devices and other folders in it. Didn't think it was possible to add another folder higher than root. What probably happened is you just renamed the root folder. I've done that one on mine and it's not an issue.
I think the default was "Network" then "My Lights". It's been ages since I renamed mine so don't know for sure. Just going off some old images in the wiki.
But as @DennisC make sure you remove everything from the folder first. Right click on any devices in the folder and select "remove from folder". Once the folder is empty you can right click on the folder and select "Delete folder".
Reference: https://wiki.universal-devices.com/Tree_View_(Navigation)_Pane
-
Geddy's post in My polyglot stopped and EISY reboot didn't help was marked as the answer
@kewashi I think in this instance you'd be better off opening a support ticket with UDI rather than trying to get help on the forums. If this isn't a common issue not too many users would be able to help on this and UDI would be able to troubleshoot quicker/deeper/better than waiting on forum posts.
Support ticket: https://www.universal-devices.com/my-tickets
-
Geddy's post in PG3x Plugin Store not loading was marked as the answer
Try accessing Polyglot from a different browser.
If that doesn't work, I recall another user recently that had a similar problem.
If I recall they did the following:
login to https://eisy.local:3000 go to System | Switch Portal Profile then login (to the portal) Screen will refresh back to Polyglot click the Logout button (polyglot web access - top right) Log back in
-
Geddy's post in Has my ISY994i aged out? was marked as the answer
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.
-
Geddy's post in So I'm An Official Hue Polyglot Idiot was marked as the answer
@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.
-
Geddy's post in No fields in Ring Doorbell Motion Node was marked as the answer
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')
-
Geddy's post in Programs missing was marked as the answer
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.
-
Geddy's post in ISY Launcher and Java issues was marked as the answer
This still sounds like your file association is not correct (as I stated before)
Also, please stop posting screen shots as PDFs. You can paste images directly into the post. When viewing the site on a mobile device there's no way to download then view the PDF so posting the image directly in the body of your post is 1000x more helpful.
First, lets make sure Java is setup to run "Web Start" applications. Open the Java control panel and click on "Security" tab. Make sure the top checkbox is checked.
Once confirmed that is enabled, check this that start.jnlp is associated with Java Web Launcher. Wherever you downloaded the start.jnlp make sure it appear like this in the explorer window:
If it doesn't then it's probably not assigned to be opened with Java Web Launcher. Right click and open properties.
This is how it should look on the general tab. If not click on "Change". Usually (if Java was installed correctly) you should see a Java option available when you click on "Change" as a selection in this window:
If not you need to click "More Apps", scroll down to the bottom of the list and select "Look for another app on this PC".
Then then look for javaws.exe in the Java\jre-1.8\bin directory of your programs file (if running 32bit Java it will be in the Program Files x86 folder.
Now, if that association doesn't fix your problem, and you've cleared java cache by clicking all three boxes...
Then, as @larryllix suggested, you might need to forcefully remove IoX Launcher from the Java Cache. To do that, open the Java Control Panel and click View (on the General tab). It will open this window:
If you've gone through these steps and all the steps posted above and it still doesn't work...please open a support ticket and see if UDI can help you get this corrected.
https://www.universal-devices.com/my-tickets
PS:
Changing the router has ZERO impact on Java not working/opening start.jnlp file to put the IoX Launcher icon on the desktop. It would 100% impact your ability to find the device if it was an old ISY994 that you set to a static IP in your old router DHCP table, but it sounds like the device is able to get on the network since you can control it with mobile apps.
What does this mean? If you can't get the IoX Launcher/IoX Finder to run how is everything working fine with Portal? Do you mean that you can just log into my.isy.io and it appears that your device is online?
-
Geddy's post in Help EISY error log entries was marked as the answer
Do you have an active UD Portal subscription? That's been the suggested method of accessing the system (Admin Console) while remote. Port forwarding leaves the system open to port sniffing and risk of attacking...but they don't know what they're attacking. With a UD Portal account you don't need to port forward and just use the URL to Admin Console found in the portal information screen. Just make sure you have a strong portal password and use the portal credentials to log into admin console while remote. (or while using UD Mobile while remote)
Good luck on the ticket side.
-
Geddy's post in Slow Programming Menu was marked as the answer
@buckeyebez welcome to the forums!
This could be a couple of issues. Let’s check the UI and Firmware version in the “Help” -> “About” screen. Please make sure they match. The current IoX Firmware for the eisy is 5.7.1.
Next, check this section of the Wiki to set a higher memory cap for Java.
https://wiki.universal-devices.com/index.php?title=Main_Page#Admin_Console_is_very_slow_or_hangs
Depending on your system you could probably go up to 1024 or even higher if you have a very high memory based system, but most don’t need much more than 1024.
It is strange that you seem to imply that the programs are there, but then disappear after loading a few Z-Wave devices. I know there were some high traffic devices identified earlier this year (I don’t know which ones). Perhaps the devices you are using are very high traffic and could be bogging down the system display. I’m not 100% sure that’s even possible, but a SWAG if the above two things aren’t a fix.
Have you attempted a Java cache clearing (remove temporary files) be sure to check all 3 boxes in that process? Download a new start.jnlp (from UDI’s site and clicking on “My ISY” on the top right), Running that to get a fresh IoX Launcher.
Are you running any firewall or anti-virus programs? What computer OS are you using?
-
Geddy's post in Polisy and Eisy Together was marked as the answer
@phawtrey not entirely sure why you hid this in the Brultech Energy Meters area. Moved to eisy since it didn't seem to have anything to do with where you posted it.
No, this is not possible. Insteon devices can only have one controller. With the Polisy or eisy you have 1 PLM to communicate to the devices. So only one controller can/should be used at a time.
It's entirely possible to have a PLM for each system, but you could only link devices to one PLM at a time. So some devices could be linked to the Polisy and the others to eisy. Kind of awkward, but if you're up for a lot of work keeping things straight go for it. You run a risk of having 2 PLMs sending out power line signals getting crossed and missed since sometimes Insteon signals can become corrupt with a small amount of noise.
-
Geddy's post in Forced to change my router to AP with Internet modem now hue finds bridge but no nodes?lights was marked as the answer
@trevorst The IP has to be added to the plugin in a strange (unexpected) format with square bracket and quotes.
KEY = bridges
Value = ["#.#.#.#"] (MUST include the square bracket AND the quotes!)
"Failed to read bridges variable" means it didn't connect properly.
Now I forget if I had to pres the hub button or not, but I'm fairly certain it might still be needed. Make sure you press "restart" on the plugin then within a few moments can press the button on the hue hub.
Once you get success make sure you restart the node server and also restart Admin Console (if you have it open - please note it's always best practice not to have both Admin Console AND PG3x web interface open at the same time. Admin Console only receives changes/update when reloaded. If you're making changes in PG3x always re-launch admin console (if you had it open) for the changes to show up on the IoX side. I always suggest people not have both open so you don't forget that step!)
If you're unable to get it configured please open a support ticket with UDI to see what other tricks/tips they might have for getting this resolved.
https://www.universal-devices.com/my-tickets
Just looking at my Hue setup realized that I don't have the IP address coded in the PG3x version. I ran Hue under PG2 on a Polisy, but when I changed to the eisy think it setup correctly and I've got a reserved IP for the Hue bridge. I wonder if you could delete the plugin and reinstall if it might connect without forcing the IP as a custom parameter. I know in the old PG2 there was an issue with the plugin storing the IP somewhere and it always looked at the old IP for it even though I did have it move (like you I replaced a router with a different DHCP table).
-
Geddy's post in Unusual Startup - Does anyone understand what this means.... was marked as the answer
@Bob Amott This means you're running an old version of the IoX Launcher.
To fix:
Close admin console Clear your java cache (temporary internet files) Delete all old start.jnlp files from your system Download a NEW start.jnlp file from the UDI website (clicking "My ISY" on the top right) Run start.jnlp to add the IoX Launcher back to your desktop Several months ago a bug was introduced into the start.jnlp code, but was fixed almost immediately.
The 2 addresses are fine, and not an issue. UDI even confirmed this is "normal" and expected, but it has caused some to be concerned. It randomly happens. Because both addresses are "found" they cannot be deleted. Either can be used interchangeably to connect to your device as they are the same device.
Also, if you haven't run an 'update packages" lately please do so to be sure you are at the current versions for PG3x and IoX. There were bugs in early IoX 5.7.0 that have been fixed, but no "official" post/announcement was made (it was posted in the support thread).
Browse to this page: https://eisy.local:8443/WEB/sysconfig.txt
(if you get an alert for it not being secure click on advanced and proceed to page)
Search the page for "isy-5.7.0" and see what you have after the .0. Looking for _5 (as of this posting).
Should see it showing as:
isy-5.7.0_5 Name : isy Version : 5.7.0_5
-
Geddy's post in No node servers appear, unable to update new system to become stable and normal. was marked as the answer
FYI it's this area: https://forum.universal-devices.com/forum/339-current-release-announcements/
All "current release" announcements are made there.
I haven't attempted to update through UD Mobile in a very long time so I'm not sure what's the issue with that. The "Upgrade Packages" in admin console should work. Don't click any of the alerts after you start the upgrade process and you should get another alert that it has completed and needs to reboot. Follow the steps above again to power cycle the system.
After any IoX update you will need to clear the java cache (selecting all three boxes) and get a new start.jnlp file to put the icon back on the desktop. This way the "local" option of connecting through the IoX Launcher won't complain about the UI/Firmware mismatch. The "cloud" option should download the proper UI, but I've found that the local still needs a fresh start.
I'm not sure what you mean by "transferred all the licenses". What licenses and how did you do that? Do you just mean portal account migration?
How is your UD Mobile setup to connect to the eisy? If only through portal then you need the portal credentials. If you have a local network setup that would be the same that you use when connecting through admin console locally.
I think you've attempted a lot of troubleshooting on your own that might have put the device into a point that it isn't an "easy" fix with forums posts. Your best bet would be to open a support ticket and have UDI help troubleshoot and fix directly.
https://www.universal-devices.com/my-tickets/
-
Geddy's post in Plugin for Eisy to Philips Hue interface was marked as the answer
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.
-
Geddy's post in How do I know I installed the Paid version - Notifications was marked as the answer
@johnjces from the looks of your second screenshot it's showing the $15 version is installed in slot 1. So I would use that as confirmation. If you need more official confirmation you should open a support ticket to get UDI to confirm you've purchased the standard license.
You can also see on the UDI portal site the list of purchased node servers.
-
Geddy's post in Not Found Message when starting IoX Launcher was marked as the answer
This is a known issue that was first discovered a month (or more) ago. Has long been fixed. You need to clear Java Cahce, delete any existing start.jnlp or admin.jnlp files you have on your system and download a new IoX Launcher file from the UDI site - https://isy.universal-devices.com/start.jnlp
(Quick search would find many posts about this: https://forum.universal-devices.com/search/?q="not found"&quick=1)
Yeah...it's "secret". If you go to universal-devices.com and click on "My ISY" it right there. Also, there's a post in the "current release" area that links to the launcher file that has been in the same spot since 2018. So I'm not sure what links you seem to be saving that never work after two months, but maybe you can save one of these two links and not have an issue in December.
PS: @lgilsenberg this shouldn't impact you since you're using an ISY994, but just in case you have two entries for the ISY994 after performing the resolution steps above that is normal and acceptable. It's mostly seeming to impact Polisy and eisy users that resolve a friendly URL on some/most routers with "device.local" URL. On the ISY994 I do not think this applies, but if you should suddenly get two entries for the same device that's fine. Either would work.
-
Geddy's post in Can not move anything out of folders to main eisy. was marked as the answer
Right click on the device you want to move to root and select "Remove from Folder"
-
Geddy's post in ISY on Polisy, Email Notifications was marked as the answer
There had been some discussion earlier this spring or Summer that Outlook was having more problems than people using Gmail. Even at one point a user said their Outlook.com account was causing the ISY service to crash.
I might suggest getting an ISY Specific Gmail account and attempting to setup following the wiki setup that was updated after Gmail changed to require 2 step authentication for the account.
Follow the setup here: https://wiki.universal-devices.com/index.php?title=ISY994:Configure_Mail_Server_Settings
For testing though (with my IoP that's not in normal service) I was able to get Outlook to send a test message. It seemed to take a little while to think about it, but it worked.
My setup is as shown here:
NOTE: I do have 2FA turned on for my Microsoft account so I had to go to the account security and create an app specific password for this to work.
Read more about that here: https://support.microsoft.com/en-us/account-billing/using-app-passwords-with-apps-that-don-t-support-two-step-verification-5896ed9b-4263-e681-128a-a6f2979a7944
Also, make sure you have at least one entry in the "groups" for recipients for the test message to go to. It can't send a test message to nowhere! I used my ISY specific gmail account and it showed up in the "inbox" for the gmail account. Sometimes the TEST message is treated as Spam and might end up in the spam folder. But this time it did go to inbox as expected.
Personally, I've had better success with Gmail than Outlook for these types of alerts.
I did have some errors/lines in the error log, but they seemed to be mostly informational lines (-17001 error IDs). I did not check on my primary ISY994 if I get the same lines when sending from Gmail.
-
Geddy's post in Schedule Triggered Programs Staying Always True was marked as the answer
@PLCGuy this is normal. Since it ran true at the time you had it's showing that it last ran true. If the entire icon was green it would be a "running" program (like @DennisC suggests). You can look at the Summary tab to see the activity. I have a couple of programs that run a single time event and they are showing True (as your icon shows) and on the Summary tab, but the "Activity" is "Idle".
It's not as though that program is still firing or applying your "Then" statement. It only runs at that specific time. If you want it to turn false you could put a time range in (from 2:00am - 2:01am) it would turn false after the time range.
Program Icon color meanings in the wiki: https://wiki.universal-devices.com/index.php?title=ISY_Programs:Icon_Colors
"Partly green - not currently running, but last ran THEN code"
-
Geddy's post in Cannot login was marked as the answer
@JSchumann in addition to what @tlightne suggests (Polyglot on the eisy uses the same local credentials as the eisy admin console)if you've performed updates make sure you perform a full power cycle of the eisy. Sometimes updates get stuck (just unsure what is going on) and do not allow the system to properly reboot even though you press the "reboot" button in Admin Console.
You have a few options:
Press the power button 5 times (not holding longer than about 1-2 seconds) - this will reboot the device
Press the power button 6 times - this will shutdown the system - blue light should turn red when "off"
If you don't get successful reboot or shutdown then just pull the power supply, but that should be last attempt because the other methods give the system a chance to gracefully shutdown, thus stopping any processes in work.
Once you have successful reboot or shutdown allow 2 minutes +/- for the system to fully start up and be accessable.
Learn more about the multi function button in the wiki:
https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button
-
Geddy's post in I can't seem to access the admin console on my ISY was marked as the answer
From the sounds of this you're using the very old method of trying to access the admin console. All browsers dropped java support ages ago and that method no longer works.
in 2018 UDI release the ISY Launcher (now IoX Launcher) that @Techman mentions above. You need to download the start.jnlp file and it will add an "IoX Launcher" icon to your desktop.
Here's the release post about the ISY Launcher (IoX Launcher) from 2018:
(more info in the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop)
-
Geddy's post in IoX Finder - Error Not Found warning was marked as the answer
This has been fixed…you need to clear Java cache, download a new “start.jnlp” file from UDI site (click on “My ISY”) and it should be fixed. This was reported several weeks ago and downloading a new IoX launcher seemed to fix it. Make sure you delete any existing start.jnlp or admin.jnlp files before proceeding.
You mention Polyglot, but posted in ISY994 area…moving to IoX since it’s not really clear you’re using the 994. But agreed, with @Javi it’s not really a firmware issue, but you are behind. Many bugs have been fixed and enhancements made since 5.5.9 so you should try to stay current.
You need to clear Java cache and download a new start.jnlp file. Make sure you delete any existing copies on your system before proceeding.
-
Geddy's post in Can't launch the admin console was marked as the answer
As @Michel Kohanim suggests it looks like could be a Java issue. You said you have the "newest" version of Java installed. Which version are you running? If on windows open start menu and type "Java" then run "Configure Java" and click on "About". Should be Version 8 Update 381. I'd perform a full uninstall and clean removal (java removal tool) of Java and download again from java.com and try again.
In the file Michel linked to above I think they're looking for some of the last lines.
Specifically: <upgradeStatus>inactive</upgradeStatus>
Also, make sure you're not running any VPN, Firewall, or Anti-virus software when you're initially running/installing start.jnlp.
-
Geddy's post in Questions about Configuration > System in Admin Console. TPM? Reboot? was marked as the answer
This was something in the early days of Polisy that got added to IoX. I'm not sure if it does anything now, but just hasn't been removed. It's not something I'd push if there's no discussion about it in the forums. Here's a post from @Michel Kohanim about this button.
"Reboot" is supposed to reboot the device. Sometimes it works as expected, but sometimes it hangs and doesn't perform a full system reboot and power cycle is needed.
"Restart IoX" should just restart the IoX system. It's not used as much as it once was when it was "Restart ISY" on the (old) ISY994 devices. It's probably useful if you're working with support and trying to troubleshoot IoX issues and just want to restart the IoX system, but usually isn't something that many often suggest here.
Also, the "Update BIOS" is another button that showed up early in Polisy time that rarely got mentioned and doubtful that it should remain and certainly wouldn't push it unless instructed to do so by support.