Everything posted by hart2hart
-
Test Hookup Device for INSTEON Switches
Looks good. I built something less elegant using wago connectors.
-
Is there a way to randomize program order?
I do something similar for irrigation control so minutes per zone can be varied using inline waits. See if this helps $Minute_Counter_I = random number 1 Repeat While $Minute_Counter_I > 0 Wait 1 minute $Minute_Counter_I -= 1 Repeat 1 times Turn light 1 on $Minute_Counter_I = random number 2 Repeat While $Minute_Counter_I > 0 Wait 1 minute $Minute_Counter_I -= 1 Repeat 1 times Turn light 2 on ...repeat pattern for light 3
-
Zwave forced rebuild of Neighbors table?
Look at Heal Z-Wave Network on zwave menu.
-
What does the Query All program do?
It queries all devices to synchronize their state with ISY in case any devices local state changes were missed.
-
eisy R2 UPS Power supply questions
I’m sure that warning is to reflect that normal usb-c adapters start output at 5 v with maybe less wattage so using one of them might under power it. A cable or adapter to go from 2 wire to usb-c can either be bought or easily fabricated. As for the 12v to 5v a quality buck converter can be bought. I’ve considered powering my UD devices with a ups but not done it as while eISY would be powered all the devices it’s controlling would be off and miss the signal so eISY, PLM , and other devices would be out of sync. My thought was to sense power outage and when it resumed to execute a query on all devices to get back in sync. How do you handle it with what you’ve developed?
-
Triggers from other than devices
Great! I put an example of one in an earlier post. There is still something wrong with your credentials to sort with UD.
-
Triggers from other than devices
Great idea. It doesn’t ask for a secondary set of credentials. It’s eisy.local though. Gotta love auto correct.
-
Triggers from other than devices
You’re welcome. Merry Christmas!
-
Triggers from other than devices
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.
-
Triggers from other than devices
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.
-
Triggers from other than devices
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?
-
Triggers from other than devices
Sorry. Type the command in lowercase. It should come back with version 3.4.9.
-
Triggers from other than devices
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?
-
Triggers from other than devices
What do you get from ssh sudo pkg info PG3x
-
Triggers from other than devices
Your url is very different than on mine. Is Insteon.rh your own domain?
-
Automation program issues with new eisy r2
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.
-
Triggers from other than devices
I think that’s only for plugin developers. I’ve never run it. Have you already rebooted after the update?
-
Triggers from other than devices
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?
-
Triggers from other than devices
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
-
Automation program issues with new eisy r2
First thing I’d try is a full reboot.
-
Triggers from other than devices
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.
-
Triggers from other than devices
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!
-
Triggers from other than devices
It is a more simple elegant approach. Did you say you had already tried your eISY credentials before 6.0 FW?
-
Triggers from other than devices
I have been using virtual devices that way since @sjenkins assumed it. Works great!
-
Triggers from other than devices
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.