Geddy

@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?

HAHAHA! Yet some around here "swap out" their PLM like changing socks. It's shocking sometimes that people just "swap the PLM" as a troubleshooting tip. Personally that's probably very, very last ditch effort in any line of troubleshooting I would consider. And only then would it be after a support ticket (with UDI and possibly even Insteon) and then at their suggestion to swap a PLM. But I digress. Hopefully people that really NEED a PLM are able to pre-order one and get one to get their system running again. If all ISY/Polisy/eisy users order one just to have as a spare it's possible somebody that really needs one for a non-functioning system would miss out when needed. Hopefully Insteon has a good supply rolling in and more beyond an initial shipment. 🤞

HA! "Getty" @ctviggen1 no worries. Glad to give the info. I'm not sure what's the big hope to use a newer version if your current PLM is working just fine. I'd rather use the current device until it wasn't reliable rather than use a new device and then have a "used" device as the fall back. That's why I'm keeping my spare PLM as "NIB" (new, in box) status until it's absolutely necessary. Which I hope is no time soon, but at least there is hope that PLM will be available regularly in the future. And even better that my next spare might be a much improved product. I'm not willing to unplug my working PLM to check the version/date on that one, but thankfully it's been running since 2017 so I'm not going to risk issues at this point. I'm not a person with any retail manufacturing experience, but just my theory would assume there probably wasn't anything actually changed in "versions" for the old Insteon. It's probably just a way for them to track production batches and/or years that some components were used. Somebody that might have more firsthand knowledge/experience of the insides to describe the different versions. Or could confirm if there was indeed any difference from 2.4 to 2.6. I think @Brian H (and maybe others) may have documented changes from very early versions to later versions, but not sure if specifics have been made for such a "small" version change.

Probably get more accurate information asking Insteon directly. If they've received the recent shipment they can at least tell you what version they're calling the current production runs. But @lilyoyo1 is right (and basically confirmed by @Techman in edited OP), that using the same part numbers basically implies that it's the same build as before. But just for reference: Serial PLM (2413s) received in January 2021 is Revision 2.6 and date code was 4520. I think others got some around that same time and might have been the last time they were available from prior Insteon.

@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

Nothing known here beyond the email everybody received. To guess would just be speculation until somebody confirmed directly with Insteon. Probably best to email/contact Insteon directly: https://www.insteon.com/contact-us

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.

Correct. If you get the serial version. Since the USB is also available for pre-order just go with the USB version and not have to worry about additional cables. That is if you're going to use it with the Polisy or eisy. As @nowandthen stated they got the serial version to use with the existing ISY994. The extra cable just adds unnecessary clutter to the cable management system (or lack there of for some) and another possible component failure to have to troubleshoot should there be an issue. (IMO)

@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.

@Lore I didn't have a chance read more about the I/O Links the other day (I don't have any I/O Link devices). Why are the devices setup in reverse? I just checked out the ISY Cookbook and it would appear there's a way to set it up as "Trigger Reverse". Wouldn't that give you the status you want to be correct on a reboot? Sadly, I don't know anything about them other than what's in the Cookbook, but sounds like you might not have set it up as outlined in the cookbook. The cookbook even mentioned the issue of not showing the correct status after query, but that was mentioned to have been fixed in FW 2.7.4 (loooong time ago). Anyway, glad you seem to have it worked out for your need. But it might be worth reviewing the cookbook (link is in the UDI Wiki) and maybe setting up those devices again to display correctly.

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.

@Lore I think current versions of IoX are not putting the "old" Default Query All program back in the system. It would need to be created. Smart suggestion from @DennisC to have it delay a moment as the Polisy starts up. It starts up much quick than the old ISY994 did, but has a lot of dependencies running on initial boot. To make the Query All program set it up this way: 00-Query All - KEEP - [Run At Startup] If Time is 3:05:10AM Then Wait 2 minutes Set 'ISY' Query Else - No Actions - (To add one, press 'Action') For the "THEN" section you'll find "Your Devices" in the action option. Once created you have to go to the summary, right click on the program and "Enable Run at Startup" (Note: "ISY" is the name (or folder name) for your ISY if you renamed it on the "Main" tab. It might be near the bottom of the device list and should have a terminal looking icon next to it: ) You could also just query the individual devices depending on the size of your install and number of items needed to query.

@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.