webminster

Well, yes, there are reasons, including: * lack of time, between family and new job; * I've seen that some people have had some issues with the polisy upgrade, and I don't have the time to do it, or troubleshoot an upgrade gone bad. I'm on 5.8.4 ATM, and not having issues, so I want to put it off to a time I have time. And not happy getting reminders 3 times a day, including middle of night. It seems that the only way to stop the upgrade messages on UDM is to disable PG3 notifications, which also probably kills the plugin connection notices as well. Wish there was more control over which messages could be suppressed... -Alan

Actually, turning off the system notification in UDM did not help. I still got an upgrade available notification.

Appreciate the answer. Is there something that defines what all is suppressed by that, assume it isn't just the update notification.

There's an update for IoX I don't plan to run soon, but I'm getting 'Upgrade available' notifications on UD Mobile about 3 times a day (including at 4AM). Can someone point me to a procedure to disable this sort of alert? Don't want to disable all notifications. Thanks in advance. -Alan

Thanks, that's helpful, got it working. The note about the variable/program startup refresh was good.

I'd like to create a favorite that can enable/disable a behavior, using a state variable. Swear I had this work before, but now I can't replicate it. What I've tried to do in UD Mobile is to create a favorite from a state variable I have in IoX. I'm using that variable as a condition to enable a program folder. I've tried to change the properties of that node's View Type to "switch", as I'd like to create some sort of toggle. What I've seen doing this is that the switch toggle then flips the value of the state variable between -2 and +2 (depending on precision - higher precision shows like -2.14 and 2.14 for instance). I also note that the toggling isn't completely deterministic - sometimes the state of the toggle doesn't correspond to the numeric value, as in toggling the switch from 2 (on) to -2 (off) shows the switch graphic go to off, then back on, even if the value is -2. I assume this isn't a supported way to control a state variable, but is there some way to create such an effect? Thanks in advance.

Same symptoms observed here.

Thanks for that info. Too bad, I assumed it would be stored in a more stable location.

For some time, I've had an issue that is a bit of an annoyance. Hope someone can let me know if this is fixable. I have IoX and admin console 5.8.0 running on my Polisy, and current Java on Windows 10 on the client side. Sometimes when I launch the admin console from the IoX Launcher, the window forgets the size of the window as I left it, opening full screen. Also, all the hierarchy is expanded on the left side. I reset the window size and the folders opened to my favorite look, and close the console. If I launch it again, the window opens like I left it. This is good for awhile, until it reverts back to full screen. Have not found a correlation of this and any other things I'm doing (not Java updates, etc.). Is there a way to stop this behavior? Thanks in advance. -Alan

Michel finally logged in via remote and got the issue fixed it seems, update either installed bad or incomplete. Thanks all for entertaining questions.

I was always replying from web site. I finally got a reply after 4 days by mailing to the sales email address. They said in their reponse they do NOT get a notification.

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.

I HAVE

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.

That was already done days ago.

[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 ~]$

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

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 ...

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.

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.

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

It is.

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.

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

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