Craigb

I don't think this is a universal occurrence. I've run my ISY 99, ISY 994, and Polisy boxes on UPS power since 2010 while the PLM is always plugged into the house wiring with no power backup. In the more than a decade of use, and many short or long power outages, I've never had the communications between the ISY/Polisy and PLM become locked up due to a power failure. I'm not sure what's different about our respective installations, but serial comms lockup is not an expected result of a power failure to the PLM while the ISY stays powered.

You can't "remove" a button from the KPL in the Admin Console. You can remove it from all scenes which will make the button non-functional (it will light on-off, but won't do anything else) - but it is always part of the KPL. After removing it from any/all scenes it was part of, then just right-click on the button in the admin console and rename it to "D". Unused buttons on included KPL's still show in the Admin console - always. Just name them somethign so you know they are unused.

@tazman, Thanks! That worked.

I'm trying to add my Polisy to my UD Mobile app on Ios 15.7 as a local network connection - not via portal. I DO NOT use the ISY Portal, I only use Local Network access (I use a VPN when away from home) When I try to add the Polisy local IP address (https://192.168.x.xx and port 8443) and test, I get an error that the IP address must begin with HTTP, not HTTPS. When I enter the IP address as HTTP://192.168.x.xx and port 8443, I get an error that the "App transport Security Policy requires use of a secure connection" Using various related URL's such as http://polisy.<privatedomain.pvt>, adding /desc at the end of the URL, and/or adding port to URL or not, letting UD Mobile try to connect to Polisy on Port 80 as http - all result in one of the same two errors. Anyone have a way around this seemingly Catch-22 issue? Polisy is running Ver 5.4.4 UD Mobile version for Ios is Ver 0.9.2 Again - I do not use the portal. All connections are via local network only. Note: UD mobile works fine in this config with my ISY's - but not in secure transport - as HTTP only.

Ordered!

Many devices with noise/surge supression will kill off powerline X10 and Insteon signals. One solution I've found is to take a 14 gauge 3-wire extension cord about 6 feet long (the flat ones used for window air conditioners or appliances are good), and coil it into a coil with about a 6 to 8 inch (15-20 CM) diameter, using cable ties to secure it. The coil acts as a choke to isolate the powerline control signal from the filter in the surge/noise supressor, and then nearby X10/Insteon devices will again work. Note: powerline control devices (neither X10, Insteon nor anything else) will not work correctly when plugged into the output side of any power conditioning device (surge protector, UPS, etc.) that filters the power line noise.

I see a different screen layout in Ver 5.4.4: You may be on an earlier version.

For my garage door, I changed from a 2450 I/O linc after one too many "all On" events. I use a Fibaro FGBS-222 "implant" unit, coupled with a 12V brick supply and an external relay. The Implant uses a FET output, which may not handle spikes properly. So I use the implant to fire a transistor driven relay contact closure.

Yes, timing is important! Read twice, execute once.

I'll add that the password can be reset to the known default admin/admin without doing a full factory reset on the ISY. Procedure here: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Resetting_Your_Userid/Password I'd do the following: - Download launcher and locate the ISY on their network. If an issue with wifi use a direct Ethernet cable from the ISY to the router or the laptop to connect initially. - See if previous owner set the user/password to admin/admin. Reset password if they did not. - Log into the Admin Console and make a backup of the system - Then start working with the system to determine how/what needs to be changed.

I know that Smarthome has removed the ALL ON command from their firmware for units shipped in the last couple of years, but some of us have older modules that still respond to an ALL ON command. For those modules, ALL ON commands can still cause issues. Tonight I may have discovered another possible source for ALL ON commands I have an older 2456S3 - date code 1152 - that was beginning to fail by intermittently not responding to ON/OFF commands in the last two-three months. I just hadn't got around to replacing it. I'm assuming the power supply is failing due to old caps that are failing. I've had two ALL ON events in the last month, after having none for several years. I have no Insteon wireless devices (one possible source of interference-caused ALL ON events) in my system, having replaced all of them with Zwave wireless devices a few years back. I believe the failing Power Supply in the 2456S3 module may have caused it to send or created the conditions that made the 2 recent ALL ON events happen. I've replaced the failing module, and will see if that ends the random ALL ON events. Just something to keep in mind if you still have older modules and are getting random ALL ON events.

I've had decent results with the Fibaro FGFS-101-EN Its reliable, and the only thing that's odd is that the temperature is only available in degrees Celsius. Battery is CR123A and life is over a year.

To answer some of your other questions: You can run Polyglot locally currently on a Raspberry Pi or on a Polisy box or in the cloud (which I understand you are not interested in cloud-based integrations) with a cloud ploy setup. To run a local polyglot server linked to your ISY, you need either of a ISY Portal account, or the Networking module for your ISY. Either opens up the access to the ISY's nodes for on-network reading/writing to the ISY. If you aren't interested in portal integrations (Alexa, etc.) then the network module will allow you to use Polyglot without any third-party Internet access to your system. To upgrade to versions 5.1.0 or later, if you are using Zwave, you also need to upgrade the Zwave hardware in the ISY to the 500 series Zwave module. Carefully read the release notes for 5.3.0 in this thread: https://forum.universal-devices.com/topic/30939-release-530-is-now-available/ as it covers all the items you need to know to update from 4.7.x to 5.1.0 or later. Version 5 introduces vastly different and improved handling of Zwave devices, and adds support for Polyglot node servers. Because it is a major change, depending on your programs, you may need to do some work to get them fully functional after the upgrade if you have Zwave devices.

Upgraded from 5.1.0 to 5.3.3 yesterday. No issues. Both older Schlage locks (BE369 and BE599) work fine after a Zwave/Synchronize Polyglot nodes work fine after restarting the nodes in Polyglot server.

Installing a Zwave module requires two steps: 1. Installing the physical zwave board 2. activating the zwave module. Go to Help/About in your Admin Console. If your About does not show a zwave module, you need activate your zwave. From the wiki at: https://wiki.universal-devices.com/index.php?title=Z-Wave:_Ordering/Assembly_Instructions Hope that helps.