DirkM

Michel fixed it on the server side (I suppose), after that Manage Modules prompted to install ISY Portal and it's all good again.

Thanks, MrBill, did both with no change. Manage Modules comes back with all up to date and Portal is missing ini the Configuration tab, so nothing to accept.

Thanks, Dave, I made some progress this morning. Resetting Polisy without PLM brought ISY back to life. Running sudo service isy status now returns isy is running as pid 1116. Running sudo service pg3 status returns pg3 does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable though. After I was able to find ISY I reconnected the PLM and restarted Polisy and everything seems to be still working. I added some NodeServers and see them appearing in ISY and I was able to link an Insteon switch. The only thing missing for now is ISY Portal. The portal thinks Polisy is offline, Help / manage Modules says everything is up to date but I don't see Portal Integration as product listed under About (was working before I messed everything up). I also don't have Portals under configuration anymore. Tried to remove and re-add Polisy from/to Portal but still the same.

I managed to break ISY on Polisy to the point where it's completely invisible. Not found anymore in ISY Launcher/Finder. Not via IP address. Not via Polisy. Polisy is fine though. I tried resetting Polisy which removed all my nodes and reset the password but did not remove/reset ISY and ISY is still nowhere to be found. Tried sudo service status isy but only get status does not exist in /etc/rc.d or the local startup directories (/usr/local/etc/rc.d), or is not executable. I'm a Linux Noob but based on this I would say ISY is installed: [admin@polisy /]$ uname -a FreeBSD polisy 13.0-RELEASE-p4 FreeBSD 13.0-RELEASE-p4 #13 releng/13.0-n244760-940681634ee: Wed Aug 25 16:44:58 UTC 2021 ec2-user@bsdev.isy.io:/usr/obj/usr/src/amd64.amd64/sys/POLISY amd64 [admin@polisy /]$ pkg_info -bash: pkg_info: command not found [admin@polisy /]$ sudo pkg update Password: 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.pkg: 100% 107 KiB 109.9kB/s 00:01 Processing entries: 100% udi repository update completed. 400 packages processed. All repositories are up to date. [admin@polisy /]$ sudo pkg upgrade 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 (1 candidates): 100% Processing candidates (1 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: bash: 5.1.8 -> 5.1.12 [udi] Number of packages to be upgraded: 1 1 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching bash-5.1.12.pkg: 100% 1 MiB 1.3MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading bash from 5.1.8 to 5.1.12... [1/1] Extracting bash-5.1.12: 100% [admin@polisy /]$ sudo service udx restart Stopping udx. Waiting for PIDS: 1097. eval: cannot create /dev/speaker: Device busy eval: cannot create /dev/speaker: Device busy eval: cannot create /dev/speaker: Device busy CURRENT OS 13.0.4 No need to upgrade the OS libwebsockets already removed flashrom already removed net/avahi already removed dns/nss_mdns already removed pkg already installed dbus already installed ca_root_nss already installed dual-dhclient already installed bash already installed mongodb36 already installed p5-IO-Socket-SSL already installed git already installed sudo already installed polyglot already installed mosquitto already installed powerdxx already installed e2fsprogs-libuuid already installed c-ares already installed rapidjson already installed mongo-c-driver already installed npm already installed isy already installed tpm2-tools already installed tpm2-abrmd already installed python38 already installed python3 already installed py38-cryptography already installed py38-netifaces already installed py38-pip already installed py38-pycryptodome already installed py38-yaml already installed py38-dateparser already installed py38-holidays already installed py38-certbot already installed py38-aiohttp already installed py38-zeep already installed py38-sqlite3 already installed py38-pillow already installed Starting TPM security services Starting udx. [admin@polisy /]$ sudo service isy restart Stopping isy. Setting permissions for ISY directories/files udx is running as pid 2222. you can disable uftdi driver by adding isy_load_uftdi=NO in /etc/rc.conf 11 1 0xffffffff81d40000 8320 uftdi.ko Starting isy. [admin@polisy /]$ Is there a config file or directory that I can remove to reset ISY?

To answer my own question, http://ipaddress:port/admin.jnlp allows downloading the admin console. I did that for both, ISY994 and ISY on Polisy and now got two shortcuts on the desktop that allow direct access across subnets.

Yep, that did the trick. Thanks, Dirk

I had my Polisy for a year now, didn't do much with it other than the initial linking to my ISY994 and playing with NodeServers which worked great at the time. Yesterday I did update my Polisy, got into ISY via launcher, was able to sign in using admin/admin, changed the user ID and password, logged out and back in, confirmed PLM was found, all good. However, in Polisy I get ISY automatically discovered at https://192.168.1.44:8443 however the username and password need to be set in the settings menu. after adding ISY on Polisy. It also still see the old ISY994 info on the dashboard. Tried linking it back to the ISY994 and get the same message now. I'm using Polisy / Settings / Polyglot Settings / ISY Settings to enter IP, port, username, password and https. Polisy shows version 2.2.13, Frontend Version 2.2.9-5, ISY Version 5.3.0 (which is old ISY994 version form before I tried to connect Polisy to ISY on Polisy 5.1.1) Am I missing something obvious? Thanks, Dirk

Ok, it seems that start.jnlp works different than admin,jnlp which I used before. The latter would allow me to add an ISY and remember it while start.jnlp doesn't remember manually added ISYs. My ISY is on a different subnet (IoT) vs. my computer and while I can add and access the ISY via my.isy.io address (using the portal ID and password instead of the local ID and password), start.jnlp can't find it using the local address. I found this out when admin.jnlp stopped working for my ISY994 after the 5.3.4 update. Apparently the admin.jnlp I used was from 5.3.0 and neither supports the new ISY on 5.3.4 nor the Polisy on 5.1.1. So, my question is: where do I get the admin.jnlp 5.3.4 for my ISY that supports different subnets and hopefully also works with ISY on Polisy 5.1.1.

I'm excited to see the progress made with ISY on Polisy over the last year and resumed playing with it. One issue I'm seeing is that the ISY launcher does not remember Polisy or finds it automatically on my network, I always have to add it manually after which it works fine but then it's gone again the next time I open ISY launcher. I cleared my cache used the newest start.jnlp and it reliably finds my ISY994 but not the Polisy. Is there a setting on the Polisy that I have to change for that to work? Thanks, Dirk

Thanks Lee, my 2487S should arrive on Tuesday. I will replace the faulty one and then contact Smarthome, it should still be under warranty.

Hi there, I have had a KeypadLinc 2486S in my garage for more than a year now. Something happened 2 weeks ago and now the buttons seem to be stuck in brightness level 1 when on. They do light up but I can barely see it. I can use ISY and change the LED brightness to 15 but that doesn't make a difference. I tried a full restore, leaving it powerless for 30 minutes, nothing makes a difference. Does that mean it's time for a replacement? If I have to replace the KPL, can I use a 2487S? Will ISY allow me to do so since it's not the same model number? Thanks, Dirk

Thinking about this, it might the fact that I added the thermostat adapter manually (with a bunch on TriggerLincs) instead of letting ISY detect the type. Would that cause the v.00 and the missing groups? Thanks, Dirk

I added a 2441V thermostat adapter while ISY was still at 2.8.16 and it was listed as v.00. Seemd to work ok though and let me do some basic settings while shoing the temp. I upgraded ISY to 3.1.2 but the 2441V still showed up as v.00 with only one group, not the 4 groups that I was readin about here. Only after deleting and re-adding the 2441V I now see 4 groups and v.91 as version. My question is: Is there a list of Insteon devices vs. ISY version that shows the minimum ISY version for a certain Insteon device? Like in my case where the list should say "upgrade to ISY 3.1.2 first before adding the 2441V". Or is there a way to make ISY re-evaluate a device without deleting/adding the device? Thanks, Dirk

Ok, as it turned out, I had quite a few failures when doing a scene test. Everything worked fine when using the switches or controller KPLs but when using the PLM/ISY I got failures and unreliable results. I don't have any v.35 devices, so that's not the issue. I put a 10A FilterLinc in front of the UPS, cleaned up the setup with PLM/ISY and SmartLinc and now all the failures are gone (at least on the scenes that I tested). I still have to go back and test folder conditions but that's for another day. Thanks for all the responses, it's still a long way before I will know what I'm doing and especially what the ISY can do for me.

The ISY PLM is plugged directly in about 6ft away from the breaker (that has a phase coupler too), no power strip or surge suppressor for the PLM. There is a UPS on that same line that several computers are plugged in. I will try to add a FilterLinc between that UPS and the outlet and see if that makes a difference. The interesting thing is that ISY thinks the scene is off (and all devices in that scene) but all controllers in that scene are still on. I have 4 light scenes linked now and if it happens it is usually not the same scene twice that stays on.