Geddy

@bpwwer I agree with @MrBill about not forcing/pushing updates. His thoughts about possible updates being pushed while away are huge. And we've seen a lot of users on here that have systems in two houses and one might be their seasonal home so long distances between properties. While I see that the desire is for PG3x to be accessible remotely, much like IoX, that's a plus, but sometimes when traveling the last thing I'd want to do is be stuck on questionable wifi in a hotel (or somewhere else) and trying to troubleshoot/fix/band-aid a system back home. This makes perfect sense! Usually that's what the forums replies have been if somebody came in and was running an "outdated" system. Especially since eisy and PG3x release. But also during the ISY994 v5.x transition. This brings me back to a comment on the forums a few months ago about perhaps UDI has a new page/area on their website showing what the "Current Supported" versions are. Yes, it is another place to keep up with something, but would be a simple place for those that are more active on the forums to point others to for an "official" listing of what versions are tested and supported "at the moment". If users aren't willing/able to update to the latest versions then the forums remain the place to get the user-to-user help. But from the official support it should be limited to only the most recent builds. As you say...new builds should be fixing the bugs that many might experience on older machines. However, the big "BUT" to all this...there has long been those that just setup the ISY994 and never touched it again. I think what IoX (and Polyglot) has evolved the system into can no longer be considered a "set it and forget it" type of system. There are just too many moving parts if you have any node servers integrated into your system. So the issue becomes how involved will users be in maintaining their systems? That's where it gets dicey and could leave the door open to having options of how/when to update/upgrade. Good luck! No "easy" way to make everybody happy, but at least the question is being asked. So thank you for that!

As @tmorse305 suggests a routine would be the way to make a simple phrase trigger an action. Be careful using just “good night” though. At some point in the past Amazon thought it would help by having Echo reply to a “Good Night” with some smart-ass quip. So I changed my “good night” trigger to, “Alexa, tell Amazon you’re programmers are f*ing tools”. The first time I wrote that out for a house guest staying the night they thought I was joking…until I uttered the phrase and everything turned off - in order. Now, I will also caution this…perhaps a program would be better suited for this process as you can control what order lights go out. Mine start at one side of the house and move to the other (as if I’m heading to bed). We don’t have a big house, but being able to time the lights from the kitchen to the master closet really helps keep enough light up during the walk to bed. The program can be disabled and not have an “IF” statement so it’s only triggered by Alexa/voice or a routine (or other methods). “Alexa, turn “program X” on”, runs the “THEN”, and “Alexa, turn “program X” off”, runs the “ELSE”.

Like me, my eisy doesn’t like to jump the gun on updates! That or it slept in on a Friday. Thanks for the explanation @bmercier!

@smileyw @brians Sadly this has been a long standing UI issue that many have brought up through the years and nothing has been changed. It ranks up there with font size and colors. I (personally) doubt this is high on the list of correcting at this point with the focus on continued development of eisy/Polisy, PG3x, and ZMatter. Certainly the only way to get more attention to the issue(s) is to submit support tickets, but based on how long comments of UI "bugs" have been in the forums I wouldn't expect any large changes anytime soon. (Try a Google Site Search for font size or color hard to read) https://www.universal-devices.com/my-tickets/

I don't have Google Home so can't help directly, but I think the same thing happens on an Alexa/Echo Show. It's more than likely just an anomaly with the UI on the cloud systems. Something might not be reporting back the actual status. It never bothers me because I don't usually stare at the screen of my Echo long enough to care. If the light acts correctly following my voice command I'm happy. I don't care what the "smart" device is displaying that I told to do something. If it (the "smart" assistant) did its job what does it matter what a temporary screen shows?

Not sure, but I think from some comments it was eisy targeted. It could have impacted some Polisy if they have converted to PG3x. I think it was more targeted to PG3x and IoX 5.5.9 based on reading this thread and maintenance thread(s).

@KConover Feel free to let UDI know - https://www.universal-devices.com/contact-us/

Well that explains my reboot about 10:25 eastern today. Thanks.

Google Home turns the display off? Isn't that normal? Or do you mean something else?

@HHarris Welcome to the forums. We split your post out to a new post as you had it posted in a Win11 issue, but say you're on Win10. What has changed that your ISY994 is not found on the network? Did you replace your router or did you update the ISY994 firmware? What firmware are you running? If you changed your router please review this section of the wiki: https://wiki.universal-devices.com/index.php?title=Main_Page#Changed_ISP/Router_-_Can_no_longer_access_ISY Also, please review this section and observe the lights on the front of the ISY994 and report what you see: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs/Lights

Check if you have another power supply available to test on the Echo if you move it back and they return again. It could be that the brick of the power supply for the Echo is flaky and where you're using it is causing the noise. I recall there being other posts that cell wall warts started causing noise randomly. So it might not be the Echo itself, but it's power supply. Depending on how old the Echo is you might get Amazon to replace the cord, but they don't usually offer that kind of option. I've seen elsewhere that some have been able to get Amazon to issue a credit for the amount of a new cord, but it's also difficult to get. Good luck.

@asbril Since UD Mobile can call on the program directly it is possible that you just make the geofence trigger the "THEN" of your program. Since a Geofence can have multiple commands just add another command, select "My Programs" -> "Run Then" Otherwise, you could still use the variables and have it set a variable and then trigger any number of programs off that variable. I still wonder where your "Occupied is true" portion came from.

@vbPhil as answered above i3 aren’t fully supported yet. Great news from UDI in a recent news post though has many hoping for full support as UDI land Insteon are working together! UDI release: https://www.universal-devices.com/i3-support/

@KConover you're certainly correct in the information is "outdated", but it was written for the ISY99i and ISY26 (both long since EOL), but the "basics" do still apply to IoX programming. The amount of edits and changes that would need to be made are too numerous to try to update all old pages. Most would look at the list and see that "My Devices" is in the same sort order as "Insteon/A10" and select that as the option. Plus, the page you linked to hasn't been updated since 2011. Yeah...have to take some blind faith jumps in relating 12 year old documentation to what you're looking at today. The principal still works...the naming is different. Wait until you try to read the 692 page ISY Cookbook. That's more current ("published" in 2018), but still uses the same image from the page you link to. UDI would almost have to start over with the wiki to bring things "current". Even then they would be evolving. There's so much valuable information available in the wiki that still applies, it's just not verbatim.

@asbril are the "home" and "home/ seno iphone" state variables? I don't think the Geofence setup in UD Mobile adds any variables. You would need to trigger a variable in the app. Did you ever run Geofence when you ran Mobilinc? That required the app to set the state variable then you have a program trigger when the state variable changes. Where do you have anything for "Home Occupied is True"?

@mmb Thanks for posting, but this has been posted (different article) and discussed in this thread:

@GJ Software Products for specific help with an issue please submit a support ticket. Forums are typically not where UDI will watch for issues such as this. It's best to get individual help for this issue so UDI can troubleshoot and see what your system is doing privately. https://www.universal-devices.com/my-tickets/ Also note for easier reading, and searchability, in the forums please use "Copy to Clipboard" by right clicking on the program then paste as text (rather than a screen shot). It helps others by becoming searchable should they ever have a similar issue.

Yes, the eisy has Admin Console that is identical to the ISY994. There are a few changes for support of the eisy and if you run node servers it will add additional devices. And I think you can also setup eisy without the phone app, but the app does make it a lot easier (for most). Remember if you make any changes to your ISY994 to make a new backup before migration so it's current. Don't think today's backup will be the best option if you tinker with things and forget about it before you get the eisy and migrate. Lots of great threads in IoX Support and eisy forums area as well as the UDI Wiki to read through to learn more.

So...just like all the Z-Wave issues "we've" been having? I think the biggest issue is while there's a "Z-Wave" standard not all manufacturers adhere to it as some might hope. I feel for UDI in that their support ticket could will probably jump significantly again once the additional devices are supported. 🤞 My hope is users realize that it's not UDI but the device manufacturer devices (UDI is trying to support) that are causing the problems. Most haven't considered this being case with the Z-Wave debacles many faced.

@ctviggen1 seems that you're plowing into the eisy and not taking the time to read any setup instructions found in the Wiki: eisy User Guide. It would have given you most of this information.

Click the red "x" to the left of the UUID for the ISY in the portal. You could offer it up to others (in the Coffee Shop forum) or list it on ebay. Otherwise, electronic recycling is best option. Perhaps you could see about sending back to UDI if they are doing any sort of referb ISY994 or need parts for OEM ISY that they're still supporting. There was a trade in option, but think it was limited for how old the ISY994 was and had to be purchased directly from UDI. Not sure if that is still available or applies in your case.

If you're not using it then it's probably no worry. The Firmware will work, you might have issues if it was a 300 series board. Since you got your primary concern taken care of and not using z-wave then I wouldn't worry about it at this point. @lilyoyo1 helps determine which board might be installed in this post:

@Joe Casullo Keep us updated on what happens. Would be interesting to see if there's a software/firmware/driver fix or if you have a device issue.

IMO (and purely as a user) with a system as complex as yours I wouldn't even attempt a "dry run" out of worry of what happens in an attempt to go back to an old system. I know that there's been a few bumps along the way, but it's a lot better than the initial release time of the eisy. And going to Polisy had been fairly easy, but the ZMatter board did add some complexity in that regard. Even if you wait until you feel it's a little more safe there's bound to be something that will bite you because it's your system and UDI can't program for everything in everybody's system to migrate without a hiccup. Just got to be ready for anything. Many have probably updated without major issues that they haven't even had to post on the board. While as with everything else in the world when there are issues you hear about them 10-fold. (You know the "saying" that it's easier to complain sitting behind a keyboard than to somebody's face...well...forums give everybody that medium.) The issue becomes - "when is the best time to migrate"? Well, given the number of people actively going through the process now I'd actually say RIGHT NOW would be perfect. You'd have the most support from other users on the forums with issues. You'd also be a great help to UDI for migrating a complex system for finding any additional bugs that need to be ironed out. If you wait the user-to-user support on the forums becomes "well, when I did it (x-months ago), I did x-y-z to fix that issue". That would prove two things...x-y-z didn't get fixed (mostly because UDI didn't know about it by way of support ticket). And that if you thought waiting would be better it still wasn't. I'm kicking myself for not migrating to the Polisy from the ISY994 sooner. I waited until I had the eisy to migrate from ISY994 all the way to eisy. I have about 100 nodes and less than 100 programs. My system was uber simple. (IMO) I had everything migrated within 30 minutes. That was about 2 months ago now. The other side of me is saying...why wait? Just do it! Rip off the band-aid! Make the leap! Come on in, the water's fine! I would say plan for the best, but be prepared for some bumps along the way. There is a very strong user support system here to help you in the process.

It uses the ISY Portal login. You need to setup an account at https://my.isy.io/index.htm then you can get into the ticket system and start a new ticket.