gviliunas

Since the Z-Wave module is not fully reset in an ISY reboot, be sure to power-cycle ISY rather than just using the button in the ISY configuration tab to reboot.

@larryllix Your post had me stop and think how much better and more reliable all of our systems would be had Michel also been CEO of Smartlabs / Smarthome...... Sometimes your the bug.... UDI-Smarthome could have been the BIG windshield... Okay, maybe I over-simplify. It's a thought. In Vino Veritas

Turning this whole discussion around is UDI now debating whether or not to support Insteon on the upcoming ISY on Polisy platform. Although UDI will continue to sell the 994i, I think we will begin hearing the death-knell for Insteon if this is not supported by Polisy. As an Insteon user, I hope SmartHome wakes-up to a growing realization that UDI and UDI customers have a large influence over their fate. " Lead, Follow, or Just get out of the way "

Upgraded my mixed Insteon / Z-Wave system from ver. 5.3.2 without any issues.

Thanks @Bumbershoot and @Jimbo I was fixated on the 2.2.9-5 value that I didn't notice that this was for the "frontend." My version for the backend is 2.2.11 so all is good - we are all seeing the same thing. Operationally, no issues. everything is working as it should for me.

How do you update Polyglot on Polisy? I'm using Polyglot version 2.2.9-5 but not automatically offered the option to upgrade. Check for Polisy upgrades yields no updates available banner.

@macjeffIn may part of the world, Weather Forecaster is the only job where you can be right 20% of the time and still get a big salary increase at the end of the year. I hope that your Tsunami was "Moderate" or lower. Also, "Winter Weather Advisory" is just not sexy in February..... LOL

@mbkingYes, I have same the same issue with the overall log. The individual NS logs are updating but the the main log stream has stopped. I think this was due to an update from this last Sunday 2/7 and not the 12.2 OS update. I've been running 12.2 for a few months. 2021-2-7 07:47:20 [polyglot] info: Caught SIGTERM/SIGINT Shutting down. 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: ISY-Inventory read ECONNRESET 2021-2-7 07:47:20 [polyglot] error: MQTTS: clientError: HarmonyHub read ECONNRESET 2021-2-7 07:47:20 [polyglot] info: Ping(10): NodeServer Disconnected. 2021-2-7 07:47:20 [polyglot] error: unhandledRejection REPORT THIS!: MongoError: interrupted at shutdown at Function.MongoError.create (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/error.js:31:11) at /snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:497:72 at authenticateStragglers (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:443:16) at Connection.Pool.socketCount [as messageHandler] (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/pool.js:477:5) at Socket.dataHandler (/snapshot/polyglot-v2/node_modules/mongodb-core/lib/connection/connection.js:333:22) at Socket.emit (events.js:159:13) Since all is working, I am going to wait for Polyglot 3.x I searched previous instances of the above mongo-db error and the solution seemed to be a factory reset on Polisy due to suspect db corruption. I'm going to wait for 3x before trying that as the current restore from a backup file requires lots of manual work and, as I stated, polisy NS functions are working.

I don't have this issue either with either version BUT, I have seen some strange presentations when opening the Admin Console. Sometimes, a program with a "Devicexyz Switched On" condition shows instead an "undefined ruleset" instead instead of the control construct. Even with this, the program was working so I knew ISY was interpreting the condition properly. I have also seen limited device features, as in your example, and Z-Wave devices on the Main page not showing the proper node features. In the past, I would re-define the condition, save, and move on to fix the Program issues. More recently, I discovered that I only needed to close and re-open the AC and the program had magically fixed itself and Z-Wave nodes on the Main page would be shown correctly. Not sure if anybody else is seeing this but this is an easy fix to try first.

@JTsao, This has been an issue mentioned for many years. Usually this is related to the battery failing on the old version 1 Insteon motion sensor or caused by programming issues with the keypadlinks. Here is some information: https://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events There is also a very long thread on this Forum but I can't locate it. You should search... Since getting rid of all my MS1s and following the KPL best programming practice, I haven't had any all-ON events (for years now). Good Luck

Updated from 5.3.1 without any issues. Everything is working properly. Thank you Chris and the UDI team!

@tom.karez@gmail.comI looked up the Linear WD500Z-1 and these appear to be based on the older 300-series Z-Wave chip. These don't support Network Wide Inclusion so yes, ISY is probably going to need to be within a few feet of each switch to be able to include into your system. The operating distance with these devices should be greater once included. In these situations, I know that some have temporarily used an extension cord to move ISY near these devices for inclusion. After inclusion, some have found it good to position ISY horizontally and use a Z-Wave repeater nearby. https://products.z-wavealliance.org/products/1032/embedpics

It seems that I read that the 994 supports up to a 32Gb card now but can't find the reference. You may want to open the ticket with UDI support to confirm this. Good Luck EDIT: I found the reference from UDI: "Max SD is 32GB SDHC. With kind regards, Michel"

The first think that I would check is the power supply. If you have another "wall wort" with center-positive 2.5mm X 5.5mm connector, 12-30VDC, I would try this first. If the ISY is older, strange problems could be caused by a failing SD card. There are WIKI articles describing how to change and re-initialize the SD card. Save the old card if these don't work and submit a support ticket to UDI. They provide excellent support.

@LarryCRetired Is the MS seeing an uncovered window? I have a MS in my kitchen. If I don't close the blinds covering the window at night, the air currents across the cold window, at night, trigger the Motion Sensor.

@Michel Kohanim done! Thanks

******** My experience detailed below has been fixed with version 0.32 of UD Mobile. After installing and entering ISY Portal credentials, the sync operation now completes successfully without needing to configure the Local Connection ********* ************************ Got an invitation to install and give UD Mobile a try. (I thought that this was an updated geofencing client but was in for a good surprise) I'm using a Google Pixel 3a phone with Android 11 1. Downloaded UD Mobile from the Google store. 2. Entered ISY Portal credentials - Save 3. See Remote Connection Settings - Save 4. Sync ISY with UD Mobile - Yes Observe lots of transfer activity 1st try, the sync stalls with java.net.SocketTimeoutException: timeout (no Screenshot) 2nd try, try again. This time stalls at Inserting: Network Resources (See Screenshot attached) 5. 3rd try: Notice that on the Remote Connection Settings page there is an "Advanced Settings" area. 6. In Advanced Settings, entered IP and credentials for Local Port Settings 7. Clicked to Add New Local Network - Populated with current WIFI info (Thanks for that button!) - Save 8. Select to Add New Local Network and click on the WIFI SSID previously added - Save 9. Sync - Notice this is much faster than the previous sync via the ISY Portal. 10. Received "Finished with Error" message (See Screenshot attached) 11. 4th try: Back into Settings, try sync again. This time the sync finished with no errors. Although I had not had a need for mobile ISY access, I like the look and feel of this app. I can see myself making use of this to check light and thermostat status when I'm away

@WFPI believe that when you do a device replace, it is normal, at the end of the replacement, for the Admin Console to close. This isn't a "crash." I think you are warned of this in the replace dialog.

You need to split the problem to determine if it is caused by an Insteon device or by a change to your home environment. If the problem affects only 1 device, I would try to move your ISY and PLM to an outlet on the same circuit as the device. If the device now works, I would look first for any changes to your environment. Has something new been plugged-in? If the device doesn't work, I'd suspect the device. If it affects all of your devices and if the PLM is more than 2 years old, I'd suspect the PLM. (Search on this forum for" Repair of 2413SPLM When the Power Supply Fails." You can also try Restoring the PLM. Be sure NOT to do a "Remove PLM" or "Replace PLM" in your troubleshooting. If the problem still exists, Open the Event Viewer, set this to Level 3, and try to turn lights on and off a few times. Copy the results in your response.

@Michel Kohanim Command was successful but nothing was upgraded: [admin@polisy /usr/local/etc/pkg/repos]$ sudo pkg upgrade Password: Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. Checking for upgrades (0 candidates): 100% Processing candidates (0 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date. [admin@polisy /usr/local/etc/pkg/repos]$ uname -a FreeBSD polisy 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 r365882 POLISY amd64 [admin@polisy /usr/local/etc/pkg/repos]$ IS it possible that the FreeBSD url in update121.sh is incorrect? If I go to "https://pkg.isy.io/FreeBSD-base/\${ABI}/latest" I get a 404. I am guessing that the url needs to have ".../FreeBSD:12:amd64/" in the path

@Michel Kohanim [admin@polisy ~]$ uname -a FreeBSD polisy 12.1-RELEASE-p10 FreeBSD 12.1-RELEASE-p10 r365882 POLISY amd64 [admin@polisy ~]$ Hmmm Did this upgrade to 12.2? Here is the full upgrade output: [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121.sh | sudo bash Installing FreeBSD-base updates Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.txz: 100% 97 KiB 99.5kB/s 00:01 Processing entries: 0% Processing entries: 100% udi repository update completed. 356 packages processed. All repositories are up to date. Checking for upgrades (5 candidates): 100% Processing candidates (5 candidates): 100% The following 5 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: boost-libs: 1.72.0_2 -> 1.72.0_3 [udi] git: 2.28.0 -> 2.29.2 [udi] icu: 67.1,1 -> 68.1,1 [udi] node: 15.0.1 -> 15.0.1_1 [udi] sqlite3: 3.33.0,1 -> 3.33.0_1,1 [udi] Number of packages to be upgraded: 5 The operation will free 11 MiB. 36 MiB to be downloaded. [1/5] Fetching sqlite3-3.33.0_1,1.txz: 100% 1 MiB 1.5MB/s 00:01 [2/5] Fetching node-15.0.1_1.txz: 100% 7 MiB 7.4MB/s 00:01 [3/5] Fetching icu-68.1,1.txz: 100% 10 MiB 10.8MB/s 00:01 [4/5] Fetching git-2.29.2.txz: 100% 5 MiB 5.2MB/s 00:01 [5/5] Fetching boost-libs-1.72.0_3.txz: 100% 12 MiB 13.1MB/s 00:01 Checking integrity... done (0 conflicting) [1/5] Upgrading sqlite3 from 3.33.0,1 to 3.33.0_1,1... [1/5] Extracting sqlite3-3.33.0_1,1: 100% [2/5] Upgrading icu from 67.1,1 to 68.1,1... [2/5] Extracting icu-68.1,1: 100% [3/5] Upgrading node from 15.0.1 to 15.0.1_1... [3/5] Extracting node-15.0.1_1: 100% [4/5] Upgrading git from 2.28.0 to 2.29.2... ===> Creating groups. Using existing group 'git_daemon'. ===> Creating users Using existing user 'git_daemon'. [4/5] Extracting git-2.29.2: 100% [5/5] Upgrading boost-libs from 1.72.0_2 to 1.72.0_3... [5/5] Extracting boost-libs-1.72.0_3: 100% Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. All repositories are up to date. Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. pkg: No packages available to install matching 'FreeBSD-*' have been found in the repositories lookig for .pkgnew files... Preserving files that are unique to Polisy lookig for any left over .pkgnew files... Upgrade complete, please reboot using: sudo shutdown -r now [admin@polisy ~]$ sudo shutdown -r now

Thanks for your help @Michel KohanimThe upgrade was successful. 5 packages were upgraded successfully. Installed packages to be UPGRADED: boost-libs: 1.72.0_2 -> 1.72.0_3 [udi] git: 2.28.0 -> 2.29.2 [udi] icu: 67.1,1 -> 68.1,1 [udi] node: 15.0.1 -> 15.0.1_1 [udi] sqlite3: 3.33.0,1 -> 3.33.0_1,1 [udi] Number of packages to be upgraded: 5 After a reboot, Polisy is running version 2.2.9-5 normally. Checking for updates does result in the "No updates available green banner..."

Sorry @Michel KohanimI think the url here: https://pkg.isy.io/script/update121 is bad, I get a 404 error when trying this [admin@polisy ~]$ curl -s https://pkg.isy.io/script/update121 | sudo bash Password: bash: line 1: html: No such file or directory bash: line 2: syntax error near unexpected token `<' 'ash: line 2: `<head><title>404 Not Found</title></head>

Maybe I declared victory too early.... I am actually seeing the same behavior as @macjeff. After a Polyglot restart, you get the green "No updates available..." bar BUT, one day later, the bar no longer appears. Past history has been for updates to be released at least every week. I plan to wait a few weeks and see if any updates are received and successfully installed. @Michel Kohanim, You mentioned optionally upgrading to freebsd 12.2. I started down that path using freebsd-update but received a warning that I would be overwriting the "polisy" kernel with a generic version. I stopped when I saw the warning. Do you have a procedure to safely perform FreeBSD upgrades?

ISY 5.3.0 Most people might be aware of this problem/solution. I wasn't until last weekend so thought I'd document this in case some are still having problems with Z-Wave and Control program triggers. I'm using a Homeseer WD200+ switch (v5.14 firmware) in an entry hallway. I rely on being able to detect "Control" conditions in order to properly trigger entry and exit programs. Sometime in the recent ISY update past, "Control" stopped triggering my programs. While looking through this, I discovered a new feature UDI added to the device Z-Wave menu: "Add/Refresh Button Press Node." I clicked to add this new "Detect Button Press" node to my WD200+ Hallways switch and then used this new node as the Control test condition in my programs. WORKS PERFECTLY. Just to be clear, my issue is with triggering udi programs. I have not tried using a button press node to trigger scenes and am not sure this will work for those needing a z-wave scene controller.