webminster Posted June 22, 2023 Share Posted June 22, 2023 Am hoping for some help... I have a Polisy that was running 5.6.o fine until Monday when we had a power outage. After power back online, the Polisy would not connect to Portal, and no Insteon devices were controlled. I've tested network connectivity, and have noticed that it finally did reconnect to Portal. But no device control. I've looked at the AC PLM info/status, and it shows "/ Not Connected". This with the original 2413S PLM. I tried my standby PLM that had worked before I removed it as a spare, and same error. I have a 2413U, and tried that as well. Same message, nothing works. So I'm not 100% sure the cable for USB is the right type, it's from Amazon as a type-A to type-B printer cable. I can't find a reference for what cable I need. I have yet another 2413S on the way, but still confused that all 3 of my PLMs show dead. Can anyone suggest some ways forward, been down 4 days. thanks in advance. -alan Link to comment
webminster Posted June 22, 2023 Author Share Posted June 22, 2023 I installed the VCP drivers mentioned on the 2413U quick start guide and plugged the 2413U into my Windows 10 computer. I see in Device Manager that it plugs a "USB Serial Port" device, which makes me think that the 2413U and the USB cable do work. But the Polisy still shows no connection, after plugging the PLM in and rebooting. -Alan Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 If you are using a serial PLM with Polisy, you need the cabling shown below: https://www.universal-devices.com/product/serial-plm-kit/ If you have a USB PLM, it can plug right in to Polisy. Be aware, if you change PLM's, you need to do a restore PLM for it to work. I would suggest you power down, wait a bit, then power back up before changing parts. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 Thanks for the reply. I'm aware of the serial cabling, the Polisy was working fine before with the 2413S and that cable. Now both of my 2413S's show "not connected" I've tried my 2413U in both USB ports on the Polisy, same thing. I unplugged to Polisy power for 5 minutes, and plugged in the PLM and Polisy, no help. Nowhere near it'd seem to restoring the PLM, any of them. Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 2 minutes ago, webminster said: Thanks for the reply. I'm aware of the serial cabling, the Polisy was working fine before with the 2413S and that cable. Now both of my 2413S's show "not connected" I've tried my 2413U in both USB ports on the Polisy, same thing. I unplugged to Polisy power for 5 minutes, and plugged in the PLM and Polisy, no help. Nowhere near it'd seem to restoring the PLM, any of them. Verify Insteon support is checked on the Configuration tab. Link to comment
oberkc Posted June 23, 2023 Share Posted June 23, 2023 Are there any unusual LED indications on the front of the polisy? Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 To add to what @oberkcsaid above, the description for the Polisy lights is: All three lights on the front light up when powered on If BIOS does not need to be updated, after a few seconds, only the left most stays lit for up to a minute and then, all lights turn off, you'll hear a couple of beeps If BIOS needs to be updated, the 2nd and 3rd light keep blinking while the BIOS is updated and the unit reboots and follows the normal process Everything is operational once only the left most light is lit either initially or after BIOS update If the 2nd or 3rd light keep blinking for more than 3 minutes, then there is an underlying issue. Please review the Troubleshooting section. Is the green light on the PLM? Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 Yes, green light is on on any of the 3 PLMs I've tried. There's only the leftmost (first) LED on after booting the Polisy. I have a program that runs on Polisy reboot, and that works (I get a mail). However, no device control works, and again, the PLM status always shows as "not connected" -Alan Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 20 minutes ago, webminster said: Yes, green light is on on any of the 3 PLMs I've tried. There's only the leftmost (first) LED on after booting the Polisy. I have a program that runs on Polisy reboot, and that works (I get a mail). However, no device control works, and again, the PLM status always shows as "not connected" -Alan Follow my instructions to use the multi function button. First try reboot, wait about 20 minutes and then clear Java cache and download start.jnlp. If that doesn't work, use the multi function button to upgrade packages. Wait about 30 minutes and follow the same procedure to clear Java and download start.jnlp. You may need to reboot again when you get into admin console. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 (edited) I'd already tried the first part. AM trying the second - I click the button once, and nothing on the box - no beeps, no light change, is there any sort of feedback to know the button press "took"? EDIT: wiki says it should beep... but it doesn't. It has not beeped either after the numerous power cycles, never beeps. Edited June 23, 2023 by webminster Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 I've also tried ding the upgrade packages from the AC, and nothing was happened I can see. The PLM issue shown in attached snapshot. BTW, thanks for offers of help... I have a ticket open with UD since Monday, but there's been no response from them for 3 days. Getting a little desperate, sorry. Link to comment
MrBill Posted June 23, 2023 Share Posted June 23, 2023 The PLM needs to be powered on before IoX starts. The PLM address is only read during startup. Shutdown Polisy and then make sure the PLM is powered up and ready to communicate before booting up Polisy. Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 12 minutes ago, webminster said: I've also tried ding the upgrade packages from the AC, and nothing was happened I can see. The PLM issue shown in attached snapshot. BTW, thanks for offers of help... I have a ticket open with UD since Monday, but there's been no response from them for 3 days. Getting a little desperate, sorry. Let's backup a minute and verify a few things. The Insteon 2413S PLM is a serial PLM and for it to work with Polisy, it requires: DB9 to RJ45 converter (Amazon Part) RS232 to USB converter (Amazon Part – Pinout ) 3ft Ethernet cable One or more of the components may have been damaged and may no longer be working. The Insteon 2413U PLM is an USB PLM and can plug directly in to Polisy. Do you have a different cable to try for this PLM? A few things to note: 1. Do not plug the PLM in to any type of surge suppressor, including a power strip that might have surge protection, or a UPS. 2. Try moving the PLM to a different outlet. Choose one with no power supplies or transformers on the circuit. 3. Try a different power supply for your Polisy. Any 12vdc, 2 amp power supply will work. Weak power supplies have been known to cause strange behavior. Be sure to plug the PLM in first and wait at least 30 seconds before plugging in Polisy. If none of this works and you can ssh in Polisy, ssh in and open the log by entering: sudo tail -f /var/udx/logs/log With the log open, upgrade packages Polisy via the admin console. After the log stops updating and Polisy is finished updating, post the output of the log. If you see the same output continually repeating, you may be stuck in a loop, but let's see what happens first. 36 minutes ago, webminster said: EDIT: wiki says it should beep... but it doesn't. It has not beeped either after the numerous power cycles, never beeps. Polisy has a speaker and should beep 4-5 times after it has rebooted. 30 minutes ago, webminster said: BTW, thanks for offers of help... I have a ticket open with UD since Monday, but there's been no response from them for 3 days. That is not like them, you should update your ticket if we can not get you going. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 I know it not like them. But fact. I finally got something from them today, after waiting several days. I'd tried to get responses, even by phone, for days. I understand the cable situation. Please not above I say I've tried serial AND USB, same thing. And yes, the PLM was powered and connected. I'm not new to this, have some sort of ISY for 10 years. And, no, it does not beep. Period. I've tried the upgrae by multi button and AC. Michel had me run a command from SSH. All I see now when it comes back online after reboot is: Fri Jun 23 09:53:39 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: generating sysconfig report ... Fri Jun 23 09:53:40 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: not checking for updates since the system is already upgrading or requires reboot ... Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 2 minutes ago, webminster said: I know it not like them. But fact. I finally got something from them today, after waiting several days. I'd tried to get responses, even by phone, for days. I understand the cable situation. Please not above I say I've tried serial AND USB, same thing. And yes, the PLM was powered and connected. I'm not new to this, have some sort of ISY for 10 years. And, no, it does not beep. Period. I've tried the upgrae by multi button and AC. Michel had me run a command from SSH. All I see now when it comes back online after reboot is: Fri Jun 23 09:53:39 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: generating sysconfig report ... Fri Jun 23 09:53:40 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: not checking for updates since the system is already upgrading or requires reboot ... What command did he have you run? If the command he had you run was to force an update, remember, you need to reboot when it is finished. 3 minutes ago, webminster said: All I see now when it comes back online after reboot is: Fri Jun 23 09:53:39 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: generating sysconfig report ... Fri Jun 23 09:53:40 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: not checking for updates since the system is already upgrading or requires reboot ... Is this from the log? If so, it looks like it might be ready for a reboot. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 I've rebooted 20 times since then. No change, same damn message The command he had me run was: sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.eisy Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 [admin@polisy ~]$ sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.eisy Password: sysrc: unknown variable 'pg3x_on_polisy' Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: starting upgrading polisy ... UDX_UPGRADE_STATUS: available -> active sysrc: unknown variable 'pg3x_on_polisy' Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: need pg3x capabilities to publish mqtt messages ... Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: pkg.conf already has IGNORE_OSVERSION ... Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: making sure we have the right repositories ... Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: FreeBSD.conf is AOK ... Mon Jun 19 17:31:21 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: FreeBSD.conf is AOK ... Updating FreeBSD repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 7 MiB 3.5MB/s 00:02 Processing entries: 100% FreeBSD repository update completed. 33873 packages processed. Updating FreeBSD-base repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 13 KiB 13.7kB/s 00:01 Processing entries: 100% FreeBSD-base repository update completed. 148 packages processed. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 21 KiB 21.4kB/s 00:01 Processing entries: 100% udi repository update completed. 70 packages processed. All repositories are up to date. Mon Jun 19 17:31:51 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: making sure we have the right pkg version ... Mon Jun 19 17:31:51 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: pkg pkg is current ... Mon Jun 19 17:31:51 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: checking whether or not we have a new version for udx ... Mon Jun 19 17:31:51 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: need to upgrade to 3.4.1_5 ... Updating FreeBSD repository catalogue... FreeBSD repository is 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. The following 3 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: ca_root_nss: 3.88.1 -> 3.89.1 [FreeBSD] libwebsockets: 4.2.2_1 -> 4.3.2_1 [FreeBSD] udx: 3.4.0_5 -> 3.4.1_5 [udi] Number of packages to be upgraded: 3 13 MiB to be downloaded. [1/3] Fetching ca_root_nss-3.89.1.pkg: .......... done [2/3] Fetching udx-3.4.1_5.pkg: .......... done [3/3] Fetching libwebsockets-4.3.2_1.pkg: .......... done Checking integrity... done (0 conflicting) [1/3] Upgrading ca_root_nss from 3.88.1 to 3.89.1... [1/3] Extracting ca_root_nss-3.89.1: .......... done [2/3] Upgrading libwebsockets from 4.2.2_1 to 4.3.2_1... [2/3] Extracting libwebsockets-4.3.2_1: .......... done [3/3] Upgrading udx from 3.4.0_5 to 3.4.1_5... [3/3] Extracting udx-3.4.1_5: .......... done executing from /usr/local/etc/udx.d/static Starting uninstall Once udx is fully uninstalled, isy service stops mosquitto not running? (check /var/run/mosquitto.pid). stopping udx @ 1092 ===== Message from libwebsockets-4.3.2_1: -- ===> NOTICE: The libwebsockets port currently does not have a maintainer. As a result, it is more likely to have unresolved issues, not be up-to-date, or even be removed in the future. To volunteer to maintain this port, please create an issue at: https://bugs.freebsd.org/bugzilla More information about port maintainership is available at: https://docs.freebsd.org/en/articles/contributing/#ports-contributing Mon Jun 19 17:32:02 MDT 2023|/usr/local/etc/udx.d/static/udxops.sh: restarting after udx restarts ... [admin@polisy ~]$ Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 13 minutes ago, webminster said: I've rebooted 20 times since then. No change, same damn message The command he had me run was: sudo /usr/local/etc/udx.d/static/udxops.sh upgrade.eisy That helps, now run: sudo shutdown -r now Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 That was already done days ago. Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 1 minute ago, webminster said: That was already done days ago. 23 minutes ago, webminster said: Fri Jun 23 09:53:40 MDT 2023|/usr/local/etc/udx.d/static/pkgstat.ops: not checking for updates since the system is already upgrading or requires reboot ... The log is saying a reboot is necessary. You have indicated you are not sure if the system is rebooting. Running sudo shutdown -r now will force a reboot. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 Yes, it says that. I've done your suggestion before. I just did it again. And it's been power cycled 20 times, that's relly not a joke. I still get that message. I still get no PLM connection on ANY of my PLMs. I think I'm giving up and getting a new one. Link to comment
DennisC Posted June 23, 2023 Share Posted June 23, 2023 2 minutes ago, webminster said: I think I'm giving up and getting a new one. I wouldn't discourage you from getting an eisy, but you could try responding to your ticket and requesting a remote session. Link to comment
webminster Posted June 23, 2023 Author Share Posted June 23, 2023 I've at least finally gotten something today from them saying they didn't respond cuz they don't get notifications when someone replies. I'm trying to work out a repair or replacement with them. This has been insane. Link to comment
Recommended Posts