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.

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.

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.

I upgraded from 5.0.16C to 5.2.0 Everything went well, and all devices are working after Zwave Synchronize. However, a Schlage BE599 door lock is showing a Write Changes pending icon in the device list. If I enable write changes, it will repeatedly attempt to write changes, trying about once every few minutes. Synchronize, Update Neighbors and Repair Links did not clear the issue. The only error I see in the Event Log is: Fri 10/02/2020 12:05:50 : [ZW-TX-FAILED] enc=Ok uid=2.0 cmd=0x85.02 ASSOCIATION It appears to be trying to set an association that can't be set? Other than the Write Changes issue, the lock is working properly and appears to be communicating with the ISY. Status updates correctly in the UI, I can write user codes to the lock, and unlock/lock from the Admin Console UI. Full event log attached. Zwave Dongle Version info: 6.81.00 ISY-Events-Log.v5.2.0_10927-1_Fri 2020.10.02 12.06.42E.txt

Or maybe have an option for a combo Zwave/Zigbee stick like this: https://gatehousesupplies.com/husbzb-1-gocontrol-quickstick-combo/?cmp_id=159600245&adg_id=8992267205&kwd=&device=c&gclid=EAIaIQobChMIzuCXpdK36wIVkIbACh2yFA_9EAYYASABEgK2t_D_BwE

I'll try to help. I believe that the bootloader is no longer necessary. If you are running the latest UI version, it is no longer listed. For Weather data, if only temps are needed, there is a NOAA nodeserver in the nodeserver store that can be pointed to a nearby NOAA site (also has data for some major international airports) to capture temperature data. For Polyglot, I was able to get it up and running on a Rasberry Pi very easily, rather than subscribe to the portal. However, you will need to add the Networking Module to the ISY to use a Rasberry Pi (Rpi) based polyglot nodeserver. Look in the Polyglot section of this forum for more info, it will point you in the correct direction. If you install Polyglot on a Rpi and a nodeserver that accesses local weather data, you won't need a portal subscription. However, if you wish to integrate voice control or other features that require the portal, then that is the obvious choice. A Portal subscription includes access to the Network Module while the subscription remains valid. If the Honeywell thermostat supports Zwave, and you have installed the 4.55 version or later of the Zwave firmware on your Zwave accessory within the ISY you should be able to include the thermostat to the ISY. Zwave inclusion instructions vary for the device. On the ISY, you choose Zwave/Add a Zwave device and then do the inclusion on the device. Many devices require the ISY to be very close (<1.5M or 5 ft) to successfully include. I used an extension cord on the ISY to get some of my Zwave devices included after they were mounted. Since you say your thermostat and ISY are within that range, you should be able to include the thermostat without too much trouble. When the ISY is in Zwave include mode, and the thermostat has signaled it wants to join, there is activity on the ISY UI to show the inclusion. The Event Viewer on mode 3 will show all communicaiton between ISY and the Zwave device. For Sunrise, there is a setting in the program interface to set that up, and you can include an offset to sunrise/sunset if you desire. I've attached a screen shot as a guide. The KPL buttons grouping button is on the far right when you are looking at the primary device of the KPL. You may have to make your UI full-screen to see it. Things in the UI that have changed (mostly just moved) do take some poking around to find. Some new features, such as being able to set the font size are handy. If you are on an older version of the UI than your ISY firmware, strange behaviors will be expected. You can use the ISY Launcher (see thread on that) to insure you always load the correct UI. Very handy if you have multiple ISY units on different versions. When registering your ISY in the portal, use your UUID rather than the older Serial number that may be on your unit. EDIT: Re-reading your info about the alarm panel and thermostat. If the alarm is the primary Zwave controller, then you can join the ISY to the existing Zwave network and have it be a secondary controller. You can add the ISY to your existing Zwave controller by including theISY to the alarm panel's Zwave controller - read the manual pages for both devices, but you generally will put your alarm panel Zwave controller in to incude mode, then put ISY into Zwave include mode so they see each other. After the alarm panel controller enrolls the ISY, you can put the ISY in "Learn" mode and it will ingest the topology of the Zwave system from the other controller. The ISy will then monitor the Zwave network, and will be able to see the data from the thermostat and send commands to it.