larryllix

75% of my Ethernet devices do not support manual IP address selection now. I guess those devices could never be used on a complex commercial LAN. These day we have computers and programs to do the tasks humans do not want to do. There are also courses on how to set up DHCP servers properly. On a small system with less than 2-4 devices I could understand not wanting to bother with the complexity of setting up a DHCP server properly. There will always be situations that bypassing current technology could apply but there is usually somebody working on power steering and rustproofing iron. OTH: Insteon addressing is static and permanently assigned without only the factory as a manager, but it is not a publicly accessible system....yet.

With all that experience it should be simple for you to understand how to make use of a DHCP server IP reservation table to meet your needs. Not many want to keep track and manage IP address tables and risk the confusion that usually follows, trying to swim upstream against the crowd. We have seen too many cases of IP entanglement from users here.

There is no blocking of SSH on my two polisies using v5.5.0. I don't know where somebody would have imagined that idea.

Configure all IP address control in your router where it should have always been done. ISY doesn't need a static IP address capability, in this decade.

Did you do the patch to the update script before running the Update? I don't know why UDI keeps letting users fall into this trap and hasn't fixed it for future update paople. It is a cloud based update.

Sounds like you still have the old IoX launcher. Did you delete all traces of the IoX launcher and then clear your java? I have found the new version shows up in various places on Win 10 and Win 11. Sometimes it shows up in your Downloads folder. Sometimes only on your Start menu lists. Sometimes I could never find it. It is very inconsistent with different installations of Windows.

Try finding your noise makers that may be interfering with your Insteon signals. Garage door openers were my problem and became very obvious when I installed a second unit containing battery backup. In fact that one crippled all my Insteon signals until I unplugged it. A FilterLinc on each GDO resolved that problem with my KPL.

Do you know how to use SSH on a PC to connect with your polisy? Do you know your polisy's IP and port address?

The "pkg" updater that should have been included to update at the beginning of the script was forgotten. I guess they haven't fixed the script yet. Run the updater and update pkg first then try your updater click option in admin console again

I always seem to prefer to do these things last thing at nights so I can be up all night trying to recover. When it finally works about 10 AM the next day the sleep quality is the best you will ever get!!

Maybe he prefers kermit to faxes?

Sounds like time to open a ticket with UDI. They are fast and very helpful. Don't expect Saturday responses, usually though. Sometimes the UUID database may get messed up.

Have you checked your subscription timing to make sure it hasn't expired. IIRC you would get a notification about that but accounts can change and things get messed up, warning can be incorrect or forgotten about. IIRC those stats are found at the top right corner menu of the ISY Portal. Recently updated your java version? Going to ping @bmercier, our ISY Portal creator and resident expert. Maybe he can shed some light on this.

Were you attempting to update something when this happened?

That always worked for me but it appears some of those commands have been erasedfrpm the freeBSD os to force users to use the provided tools. That update command has never functioned properly for me since polisy came out. The ssh method always worked though and was used to recover each time. We will get there to a user level system eventually. Sent from my SM-G781W using Tapatalk

Perhaps we need an individual "Do not query" selection for each device instead of a group select/deselect. I have three MS II on AC and several MS 1's on battery power but some were planed to be on AC originally, also. I find the battery device query hasn't stayed turned off since IoP was released, anyway. UPDATE: Just checked on v5.5.0 and it kept it's Off setting with A/C reload, finally. Now to see if I can get Insteon to fix the MS II timer bug before re-releasing it.

I used the laughing emoticon 'cause there was no finger bird.

Yeah @Michel Kohanim reported they found the initial update process was flawed and was fixing it. Sure caused some commotion here for me for a night though.

See (to fix)

Seems to be the winner for me! The pkg utility version was the snag. Despite all the rrors the system threw at me it seemed to upgrade it and made all the other upgrades possible. sudo pkg install -r udi pkg After that, I reset udx and isy, and then ISY booted properly, finally. sudo service udx stop sudo service udx start sudo service isy restart I remembered some of the last ticket help with @Michel Kohanim how udx controlled the UUID assignment (mine was coming up 00.00.00.00.00.01) and the outdated pkg utility was prevented it from installing the newer packages. Thanks all! /Panic off

Thanks. already been done many times now. Best was service stop service start of each udx, isy polyglot Mongol that got me up with an actual UUID but after few minutes the UUID collapses again to 00.00.00.00.00.01 again and Insteon, and all i/o stops functioning again. This thing is just continuously crashing. Power cycled several times and clicked update several times now. May have to try my spare polisy or return to my ISY for the third time. Sent from my SM-G781W using Tapatalk

It seems the update package is permission locked. [admin@polisy ~]$ sudo pkg install -r udi pkg Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.18.4 -> 1.19.0 [udi] Number of packages to be upgraded: 1 8 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pkg-1.19.0.pkg: 100% 8 MiB 8.6MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pkg from 1.18.4 to 1.19.0... [1/1] Extracting pkg-1.19.0: 100% Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. process with pid 17542 still holds the lock process with pid 17542 still holds the lock process with pid 17542 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$ [admin@polisy ~]$ sudo pkg install -r udi pkg Password: Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. New version of pkg detected; it needs to be installed first. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pkg: 1.18.4 -> 1.19.0 [udi] Number of packages to be upgraded: 1 8 MiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pkg-1.19.0.pkg: 100% 8 MiB 8.6MB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pkg from 1.18.4 to 1.19.0... [1/1] Extracting pkg-1.19.0: 100% Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. process with pid 17542 still holds the lock process with pid 17542 still holds the lock process with pid 17542 still holds the lock pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$

After mine rebooting and showing v5.5.0 it has now crashed and shows v5.4.5 with UUID:00.00.00.00.01 ISY Portal cannot find it. Currently running sudo reboot again. UPDATE: IoX Finder found proper UUID but would not launch Admin Console after IoX refresh now shows UUID 00.00.00.00.00.01 and now launches IoX but System Busy will not go away.

Modulus arithmetic is still defective and hasn't supported decimal fractions since v5.0.1. Notification customisations still hasn't been fixed as reported the last three or four versions. Selection menus also fail occasionally.