lhranch

Following the tutorial I found here, I managed to beat my new configuration about the head and shoulders enough to get the Virtual Controller and my generic dimmer to go visible in Admin Console. Success! I had two questions for those with experience in these switches, as virtual dimmers don't seem to present exactly as physical dimmers do. First, the syntax allowed in the program is different for the physical and virtual dimmers. The physical dimmer has controls called Fade Up, Fade Down, and Fade Stop. The virtual one has Brighten, Dim, and nothing comparable to stop. Is this expected? Second (and this seems to be a quirk of MobiLinc Pro only) the brightness reported for this switch is fugazi. On is 40%, whether I turn it on directly or it inherits from the scene when the driving device is 100%. Brighten takes it from 0% straight to 40%, Dim does nothing. Did I define the dimmer incorrectly or incompletely? (EDIT: to be clear, the values shown in Admin Console make perfect sense; it's the values shown in MobiLinc Pro that are wacky.)

Hah! UD has already shrugged the ticket, advising me to get in the side door exactly as @DennisC did!

Well, that pushed the project ahead. It let me install Virtual, and now Admin Console has new virtual thinginess in the menu. Now I gotta read up on what it expects me to provide for addresses, etc. so I can create one. Thanks a bunch, @DennisC !

I dig it. Thanks for all your help, and Merry Christmas!

So far, I'd think the biggest avenue of attack would be the missing docker software. Any ideas there before I file a ticket?

Http failure response for http://192.168.128.90:3000/auth: 500 Internal Server Error For all combinations, on both http and https. Unless password is blank, then get "unauthorized."

pg3x-3.4.9 Name : pg3x Version : 3.4.9 Installed on : Thu Dec 25 17:00:12 2025 MST Origin : misc/pg3x Architecture : FreeBSD:14:amd64 Prefix : /usr/local Categories : misc Licenses : MIT Maintainer : benoit@universal-devices.com WWW : https://github.com/UniversalDevicesInc/pg3 Comment : Polyglot PG3x for UDI eisy Shared Libs required: libc++.so.1 libc.so.7 libcrypto.so.30 libcxxrt.so.1 libgcc_s.so.1 libm.so.5 libssl.so.30 libthr.so.3 Annotations : FreeBSD_version: 1403000 repo_type : binary repository : udi Flat size : 69.9MiB Description : PG3x Plugins manager for Universal Devices eisy/Polisy Release notes for 3.4.9 - 12/18/2025 - Added eisyui-specific navbar - Relaxed plugin rate-limiter to handle plugins with more activity

pkg: No package(s) matching PG3x Which is strange, because Admin Console / Launch PG3 shows a login screen. The ranch has an internal private network with local DNS and TLDs, so things can end in .rh (ranch house). Yes. https://insteon.rh:3000 After the usual complaint about the certificate not being valid, which one entirely expects.

@hart2hart It rebooted itself (wouldn't have noticed except it kicked my SSH window).

Update finished, ended up at 6.0.4. Updated Java Admin Console to match. Still don't seem to have docker anywhere inside. Do I need to "Install Dev Packages" or is that something entirely different?

I don't even seem to have docker installed. The command went nowhere, so I did: [admin@eisy /]$ sudo find / -name docker\* -print /usr/local/lib/qt6/mkspecs/features/data/testserver/docker-compose-common.yml /usr/local/share/gtksourceview-4/language-specs/docker.lang [admin@eisy /]$I'm running 6.0.0. Last time I ran a package upgrade from Admin Console was about a month back, apparently it changed nothing. I'm running another at the moment. There is a button for "Install Dev. Packages." It says I haven't done that, and am I sure I want to. Do I need to? And finally, it looks like I lied earlier (I'll have to go back and re-edit some claims). Although I changed the ID and password used to access the Admin Console, that ID does NOT work for SSH. Only admin works for SSH, and the other ID doesn't even appear in /etc/passwd. But what I said about PG3x refusing all possible combinations at login is still true.

By "lockdown program," I mean the program I need to invoke to disable the automatic motion sensor behavior of these lights, and the "reset program" is the one that restores that behavior. As to what I am trying to do. I think that is all laid out in the original post. Again, the desired operation has worked fine for a decade as long as it is invoked from a physical Insteon device, but not if it is invoked from an iPhone or computer app. @hart2hart : Thank you! I will try these next opportunity when I'm back in the saddle. Meanwhile, if you do locate any more specific instructions, please feel free to lay them on me.

Humor me -- where are the reset instructions? If it exceeds vanilla UNIX stuff, I'll go the ticket route.

In the previous major release, I had set the admin name to a different name and chose a unique password. I used it only in the Admin Console, in both my original ISY and my followon eisy, until I got the notice about the new release 6 upgrade coming, and I had to SSH into the eisy to check it satisfied all the prerequisites; at that time, I discovered my modified credentials worked fine for SSH also. As I reported here, when I performed the v6 upgrade, it reset the admin login to the default admin/admin, and I had to change it to my desired values once more, which again worked fine in both the Admin Console and SSH. (EDIT: This was a misstatement. The admin ID for SSH remains "admin".) Now, having attempted to activate PG3x only for the very first time last night, I find it won't respond to any combination of name and password, and (worrisome) it reports not 401 Unauthorized, but 500 Internal Server Error.

It's easy, but not particularly elegant. It requires me to keep THREE icons -- lockdown program, release program, and actual control of the light -- on a phone dashboard with limited real estate... whereas being able to tie the lockdown and release activity to direct light commands (as I have for the past decade) requires only one.