hart2hart

You’re welcome. Merry Christmas!

It’s all installed by their standard installation. Something is clearly off so feels best to get to root of it rather than potentially compound it.

All I can think is doing the three button press credential reset but at this point I’d enter UD ticket. They’ll figure it out quickly.

If you know ip address of eISY, try following replacing 999s with eISY ip address as a shot in the dark http://999.999.999.999:3000 Is it giving same error when you type in credentials?

Sorry. Type the command in lowercase. It should come back with version 3.4.9.

Are you using the menu option for Plugins Launch Polyglot at top of AC to try to get to PG3x? If so does it launch a browser and if so what does it send over as the url address?

What do you get from ssh sudo pkg info PG3x

Your url is very different than on mine. Is Insteon.rh your own domain?

At this point the web ui is still a work in progress. I use good old AC to maintain and add stuff to the eISY.

I think that’s only for plugin developers. I’ve never run it. Have you already rebooted after the update?

As long as you’ve got a good set of backups, I too would run update packages but a little risky as UD not working today so if it goes south you’re stuck with us for help. Do you have shell command to monitor progress of update via ssh?

The method mentioned in post uses three button press ensuring you have physical access to the eISY to reset to admin/admin https://forum.universal-devices.com/topic/42985-pg3x-password-recovery

First thing I’d try is a full reboot.

I’m looking for the reset instructions but see if following helps that I got from an AI model (perplexity) A 500 Internal Server Error on eISY’s PG3x typically indicates a backend service issue, like the PG3x Docker container crashing, database corruption, or a failed node server connection (e.g., “could not get ISY”).[universal-devices] SSH into eISY as admin and run docker ps to check if PG3x containers are running; restart with docker restart pg3 if not (exact container name from docker ps).[wiki.universal-devices] Check PG3x logs via SSH docker logs pg3) or IoX logs for specifics like ISY connection failures, then upgrade packages in IoX to refresh.

There are some reset instructions but I think you’d be best to submit a ticket to UD to get it sorted out. Merry Christmas and Happy Holidays!

It is a more simple elegant approach. Did you say you had already tried your eISY credentials before 6.0 FW?

I have been using virtual devices that way since @sjenkins assumed it. Works great!

It uses you eISY username and password or if you’re on 6.x fw it uses you portal login. The then methods works great but if you just want to review PG3x try authentication methods above.

Guy gave you how to start with PG3x and install it. It’s straightforward. No tech knowledge required. In parameters for plug in in just enter a number say 10 as the key and switch as data and as I recall Restart the Virtual plugin. The switch will show up at the top admin console tree. You can get more sophisticated and define it this way to send in the name you want. Key Data 10 {"id": "10", "type": "switch", "name": "Patio:Landscape Lights"}

Link it to a switch and then look at switches Insteon addresses via AC show device links If you try the start linking button in ISY and press and hold the set button does it show the address? As I recall it won’t link correctly but maybe it’ll show the address. Can’t recall.

You could also leverage a Keypadlinc button to also trigger your programs with an ‘Or’ keypadlinc button A is On/Off. I’ve also used the virtual device plugin to create virtual switches and then turn those on / off as a favorite. Again put those as Or clause in existing programs to trigger them.

First thing that comes to mind …Create programs that turn them off or on and sets the required variables at the same time. Put the program as favorite in UD mobile in a group called back yard lights. if you use Alexa, you could expose the programs for spoken commands.

Enter a ticket with UD.

Remote and local gives information for your station. One does the work local to device and the other gets data for it but from the WF cloud servers

Shot in dark. Did you just upgrade to 6.0 branch of FW? If so, it uses the portal credentials for authentication vs the local.