gviliunas

I tried configuring my ISY on Polisy with the same settings that are currently working on my ISY. I am using smtpout.secureserver.net (godaddy server) on port 80 and see the same problem as @whyworkwhen I try to send a test e-mail.

@mbkingThanks for your help! It worked and the finder now finds ISY on Polisy.

I had previously upgraded to version 5.04 and was able to connect to ISY on http://<ip address>:8080/desc via the finder. I have not used ISY on Polisy for a few days and several update packages were installed via the Polisy web page. Now the finder cannot find ISY on Polisy. - The Polisy service is running on Polisy. Tried rebooting Polisy. - If I try to update via ssh session, I get: [admin@polisy ~]$ sudo pkg update Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. - If I check https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/ There is no file "packagesite.pkg" only packagesite.txz

I was able to upgrade my polisy isy with problem but after this could not communicate with the PLM or any connected Insteon devices. Restarting ISY or disconnecting / reconnecting the PLM did not help. Rebooting Polisy solved the issue. Confirmed that LAN access to ISY now works properly.

PLMs shipped with DB9 to RJ45 cables. I was expecting to use this to connect the PLM to Polisy when the time came.

FWIW, I pair my multisensor 6s in non-secure mode. They seem to respond a little quicker this way.

Upgrade SUCCESS but expect a whole lot of beeping. I followed Michel's steps above. My system was already at the prerequisite versions. Step 3 required several minutes to complete then needed to enter: "sudo shutdown -r now" for the reboot. Over ~ 2min there were 14 beeps in this pattern then I could login and all was good. beepbeepbeep beepbeepbeep beepbeepbeep beepbeepbeep beep beep Thanks to the UDI Team for all of their excellent work!

A few days ago, I remember Michel warning not to upgrade until further notice. They were having a problem moving to OS ver. 13 You may want to submit a ticket.

Michel's Home Automation in "G" ?????

@whywork, I just tried the manual update and am seeing the same problem as you...

I just had occasion to restart Polisy via the System / "Reboot Polisy" drop-down link in the web page. In the past, when doing this, I would hear 2 beeps followed by a long pause while Polisy reboots then 2 more beeps telling me that Polisy is again running. Now, after selecting the reboot, I hear 4 beeps followed by the long pause then 3 lower-tone beeps followed by 3 higher tone beeps, a short pause and then 1 beep followed by a longer pause and a final single beep. Old sound pattern: (shutting down): beep beep (Polisy back up): beep beep New sound pattern: (shutting down): beep beep beep beep (Polisy back up): Lowbeep Lowbeep Lowbeep Highbeep Highbeep Highbeep beep ....... beep Everything appears to be working properly. Is this a new feature? Polisy version: 2.2.13 Frontend: 2.2.9-5 Isy 5.3.3

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

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.

@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