Geddy

@matthewjocko some things to try: perform full power cycle. Pull the power supply. Wait a minute and power back up. Allow 2-3 minutes for system to fully boot. one of the options in the menu should be to switch portal profile. Be sure you login to the correct profile. force a refresh on the browser page. If after these steps it’s still slow or cannot install plugins open a support ticket to get help from UD to try to get things running correctly. Please post back what resolves this for helping others should this be an issue.

You had similar issue with another plugin. Do you leave admin console running 24/7? It's not designed to be left open and I expect as @Panda88 suggests some data might be cached and/or only loaded at startup of admin console. Some windows have options of running a query on the values, but that's not ideal. For the plugins you are experiencing problems with in the log page put them into debug mode then restart the plugin and wait 5-10 minutes. Then download the log package and PM to the developer for those plugins. Since you're having this issue with multiple plugins it might be best to open a support ticket with UD to see what's causing this on your system. If you close admin console after using it and data isn't there upon loading then it seems to be an issue pushing the data from PG3 to admin console on launch. https://www.universal-devices.com/my-tickets

Look at the program tree. What is the color of the icon for this program? Is it partially red? If so, then it did fire it just fired FALSE. Thus it would run the "ELSE" of the program. You have nothing in the else so that's fine. You can also look at the Program summary tab and it should show when the program last triggered and if it was true or false. When you said it didn't "run under geofence" what do you mean? Correct. If you only want to trigger (TRUE = run THEN) between the times in your "IF" then you have it set correctly. You can test that when it's within your time statement and tap the "Trigger Enter Command" in the Geofence. From what you've posted it looks like UD Mobile should trigger your geofence and in doing so if it's after 15 minutes before sunset should run the THEN of your program. I would test during your "IF" window of time by tapping the "Trigger..." in the app. Then I would test by going for a drive ("well" beyond your geofence area) then when you enter the geofence area it should trigger. When you get home if the lights aren't on check admin console to see if the program ran. If it didn't then something might be wrong with the geofence on the phone. That gets a little tricky to fix. I would turn off the "Run at Startup". This could trigger the program if your device reboots in the middle of the night (anytime that the IF would be TRUE). My last thought to test would be to create another test geofence area and have it directly turn a device on when crossed (not in a program, but the actual device). If that works it could be something with UD Mobile and calling on the program. My geofence (radius=750) is setup to turn on a light no matter what. It is triggering the device directly rather than through a program and seems to work every time I enter the geofence. I'm on iOS 18.2 (build 22C152) with UD Mobile 1.1.83, but it's worked well for quite a while.

(bold added for emphasis) I get what you're saying. UD has always said that documentation is probably their weakness. I think as Michel has claimed "they're developers, not document writers". While it might be a pain to sort stuff out on the fly it is sometimes easier for trial and error than trying to read/guess what the documentation is saying. Seems that you are taking testing to an extreme of getting things figured out before going live. Some of the more detailed questions/issues you might have might be something that only you have faced (at least recently). Many that made the switch when the eisy came out had a difficult time with the process as it was super green and new to everybody at the time. But the basic answer to this "question" is (if I recall) that if there's no network cable connected when the eisy boots up then wifi is enabled by default. If a network cable is connected then the wifi is disabled. I never setup the wifi on my eisy since it sits next to my router. For me there's no need to have the wifi as a "fall back". If my LAN goes down then probably my whole WAN connection is toast. I don't see a need to have it as an option (for my situation). I'm with you on this. UD Mobile has been undergoing some UI changes and I expect that the documentation hasn't kept up with the changes. It's probably still referring to items that were there when UD Mobile and eisy were released (two years ago). For your issues it might be something that is better handled through the UD Support ticket path if they're stacking up and you're just looking for issues in the system. https://www.universal-devices.com/my-tickets Otherwise, for a user-to-user forum for support we're here to help, but understand that just making comments about the documentation without asking an actual question or describing what you're attempting to do probably won't garner much help/support because nobody knows what it is you're looking for help on. That's probably why your initial post didn't get a reply for a couple of days.

@mikek understood. Maybe somebody with this product has figured more out and can answer your question.

@mikek I'm not familiar with that device, but @kzboray had a post that might give more details from a couple of years ago. Take a look and see if it might help answer some questions (or raise even more). And here's a post from @brians that could also help:

The last trigger shows changed at 10:52am. I assume this is well past the Sunrise +15 minutes in your program. So it would only trigger the ELSE since it would be false. If you triggered the app during the time shown in the IF then it would run TRUE and the lights would turn on (as you seem to acknowledge worked in your testing). If you wanted to test during other times change your geofence automation to Command: Run Then. This would mean every time you enter your geofence it would perform the THEN of your program. You currently are running the "IF" and it will only turn lights on if the program is TRUE when you entered. Additionally, is this program enabled or disabled? If it's enabled it will run at the times you have in your program daily independent of your geofence status. You might want to disable the program if you don't want it running daily. By disabling the program when the app called on the program IF as you cross the geofence it would (only then) turn those specific lights on. PS: Please note that the best way to share programs is by using the "Copy to Clipboard" function by right clicking on the program. Then post the text directly into the forum post. This makes it easier for anybody helping with the program to not have to describe what to change or type it all over. Photos are good for non-text information.

Ah the dreaded curse of the mac. Got any windows machines handy? I only ask because I'm not versed in Mac at all, but they are tricky. First off don't unzip the file you download for the firmware. That seems to be problem 1 for mac that they somehow auto unzip. It might be best to create a new post to get help upgrading the firmware directly in that area rather than tagging onto your original issue of programs not loading. If that problem was resolved then mark the solution and allow the threat to close. Then starting a new topic to get help about updating firmware in the device specific area would be the best.

The portion of the wiki you quoted is related to the multi-function button. You press it twice and enter or exit wifi setup. To use the UD Mobile app to connect to the eisy and to setup wifi you should refer to the UD Mobile documentation: https://wiki.universal-devices.com/UD_Mobile If the device was already setup and on your LAN then why did you want to change it? You need to read the installation information: https://wiki.universal-devices.com/Eisy:User_Guide#Installation

Yes, but the (larger/original) card needed to be modified some to fit inside the dongle. I think it removed the part that could be screwed into the body of the Polisy, but it's been a minute since I installed the internal in the Polisy. I agree though...not sure I'd want to open up both devices to put it inside the Polisy when the USB enclosure should work well enough.

Originally there was an internal card for the Polisy. I think that is no longer an option. It’s only the ZMatter dongle now. It is USB and includes 2 antenna. It is shown on the UD site and store. No need to open up the Polisy.

Follow these instructions: https://wiki.universal-devices.com/Polisy:User_Guide#Upgrading_to_PG3x I believe nothing really “happens”, but give it a few minutes then power cycle the system. After you enable PG3x you should be able to upgrade correctly and backups should work again. Did you make a backup before you attempted the first time? What IoX version (and UI) are you currently running? What version PG3 are you currently running?

@matthewjocko what product are you using? Your PG3 version is outdated, but your ISY version is showing a later version than what's been mentioned in the current release area. If you are on a Polisy you need to run the process to update to PG3x (Please read the wiki for assistance: https://wiki.universal-devices.com/Polisy:User_Guide#Upgrading_to_PG3x) If you're on an eisy you need to get your PG3 version up to date. Not sure how/why it isn't so that's why I think you're on a Polisy. Once you update to PG3x you should run the "reinstall all plugins" process (found in the menu of the PG3 web access). I'm not currently local to my device so cannot access to let you know where to look, but it isn't hard to find. If the normal update process is not updating your PG3 then I would suggest you open a support ticket with UD to get them to help bring you up to the current versions for your system. Then things should run as expected. https://www.universal-devices.com/my-tickets

@garybixler I would suggest opening a support ticket with UD. Something doesn't seem right, but not sure what to suggest since you've been rebooting and apparently reloading stuff. It might be stuck in a loop somewhere. https://www.universal-devices.com/my-tickets Please post back what they suggest to get things working again so we can learn and hopefully help others should this happen to them.

It could be noise happening with the query program. I might try moving it to a different circuit for a few nights to see if it still comes on. If it doesn't then there might be noise on the original circuit. Remember noise isn't always from something "new" it could be something old that's failing or impacted by yet another item that's introduced noise into the system. Are you running the Query All program that used to come set by default? Many have added it to Polisy/eisy devices (I know I have). The default program was set to run at 3am (if I recall). I like thought @gregkinney gave about copying programs to a text file to search for the device, but the program tab has a find option that you can look for devices, raw text, and other options (just FYI). Query All program: (I offset mine to 10 seconds after 3am just because) If Time is 3:00:10AM Then Set 'ISY' Query Else - No Actions - (To add one, press 'Action') Last consideration might be to leave the event viewer open and set to level 3 and copy that to a text doc to search for the device...just know that will have a lot of data and could cause other issues. It might just give you what the other log(s) gave you. If there's not a command actually triggering that device then either the device is failing or it's a noise issue causing it to come on randomly. Does it come on at any other time without being triggered?

How does your scene look in the UD Portal for Alexa? I've got a scene that is my hall light switch. It's showing as scene, but under "Alexa Cat." shows as a Device\Light. It works just fine. I'm not sure if you have it as "Scene" in the "Alexa Cat." and it isn't working that way. Try to change to "Device\Light" and see what happens. Since direct devices work it's either something isn't setup correctly with the scene (i.e. the root controls aren't correct) or something is "wonky" in how Alexa handles a Scene as a category. I only have a few scenes exposed to Alexa and they're all showing a category of Device\Light (since they're mostly just 2 way for halls or stairs with lights are either ends.

This is normal and default. Don't try to change it.

@jlamb be sure you make a text copy of all your programs! Right click the root folder in Programs tab and select "Copy Folder to Clipboard" (Make sure you use the COPY option and not export!). Paste that to a plain text editor (not a word processing program). Save that file so you now have a text version of all your programs and can recreate them should things go crazy due to the change in the plugins. In addition to what @DennisC suggests if you use Network Resources they will likely need to be resaved as well.

If the echo issue has been going on since you replaced the PLM please make sure that your Portal license is still active. Log into the portal check if the ISY is "online" (green dot/circle). If it is then choose "Select Tools" -> Information -> ISY Portal Access License -> License Active If the ISY is online and your portal license is active it's possible there is a portal outage. Since @abrayshaw is having a similar issue and the portal is saying the ISY is offline it's possible there are connection issues. I just checked my connection remotely and it appears on. I can command devices remotely using the Alexa app on my phone so it does appear to be working as long as your device has an active portal license and connected to the portal.

Do you have the Alexa app on your phone? You link the skill in the Alexa app. More info from the wiki: https://wiki.universal-devices.com/ISY_Portal_Amazon_Echo_Integration_V3 Since other devices work you must have set it up at one point in the past. Depending on how long ago you might have used the older skill that I think wouldn’t work for new devices, but not sure. Since V3 is available now it would be best to be sure you have that skill (again in the mobile Alexa app). Over the past year I think Alexa auto discovers devices, but if not then as @paulbates suggests to ask Alexa to discover devices. Note the directions for the skill were written a long time ago so some options or locations in the Alexa mobile app might be different. I don’t use it enough to know what to say w9ld be different so hunt around in the app until you find skills.

Have you just been rebooting from the admin console option or performing a full power cycle by using the multi function button or pressing and holding the power button? Since it appears multiple plugins are not connecting you might have a failed update and would need to open a support ticket with UD to check the system for hung processes. I would suggest opening a ticket: https://www.universal-devices.com/my-tickets/ Please be sure to post back the solution from support for this issue to help others if they should have similar issues.

Unsure how this works, but remember that the Hue plugin hasn’t been updated in a long time and isn’t using an official API for its workings. My suggestion is after you make the changes on the phone app make sure you aren’t logged into the Admin Console. Open the web access for PG3x and restart the Hue plugin. It might pick up the new light names. You might have to do this several times. Once you see the new node names in the web access then log out of that and open Admin Console. It should then update the names to match the PG3x nodes seen on the plugin. If simple restarts of the plugin don’t help you might have to remove the old device names and then restart the plugin. I would suggest you get things setup the way you want them before connecting the plugin in again because it apparently isn’t instantly updating device names.

First I would update to the current firmware (5.8.4), while that alone might not fix the issue working with the current firmware can help limit other problems that have been addressed since your version. Then be sure to review the steps in the wiki for Gmail account setup. These were confirmed earlier this year. Some options might have changed slightly, but they still work. https://wiki.universal-devices.com/ISY994:Configure_Mail_Server_Settings#Configuring_gmail_Account I’m not exactly sure what your errors mean as there isn’t specific meaning in the wiki for those errors and most mentions in the forums relate back to ISY994 issues, but might shed some light on what resolves them (I didn’t read many of the older posts….use Google Site Search to find them). Since using the eisy you might want to review using the Notification plugin and UD Mobile or even Pushover to get alerts sent to your mobile device rather than the older email method.

@andrew77 have you confirmed the lamp is turned on and works when not plugged into the lamplinc? Is it possible the lamp got turned off or the bulb blew? If the lamp operates correctly then try the Lamplinc in a different outlet on a different circuit in the house (maybe closer to the PLM) to be sure it's not a noise/communication issue.

@joeria cool. But know that since it's in the non-production store it could have some testing that is being worked on so probably keep a close eye on it for any issues. It sounds like there was some issues with Google based on reading other posts in this area of the forums. Hopefully they're being worked out.