Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

awysocki

Members
  • Joined

  • Last visited

Solutions

  1. awysocki's post in Migration failed:Request failed with status code 500 was marked as the answer   
    Root Cause Breakdown
    In the eisy-ui log, the installer executes the following sequence:
    Empty Branch Argument:
    When pulling your repository ([https://github.com/awysocki/ACInfinity](https://github.com/awysocki/ACInfinity)), PG3 reads "branch": "null" from the node server configuration. It tries to execute:
    Bash
    git checkout -b Because no branch string was passed, Git fails.
    Branch Auto-Detection Fallback:
    PG3 then queries Git remote HEAD and detects Found branch [main].
    String Concatenation Bug in eisy-ui:
    Once main is detected dynamically, eisy-ui's pg3_helper attempts to register the service. Instead of referencing slot 25 (plugin_25), the script incorrectly concatenates the slot prefix with the auto-detected branch name, attempting to query:
    Plaintext
    Unable to get info for plugin_2main Because plugin_2main is an invalid service target, pg3.ops fails with exit code -5 and rolls back the installation. (Compare this to your PMatter plugin log, where "branch": "main" was explicitly set beforehand, allowing plugin_27 to install cleanly without running auto-detection).
    How to Fix It in Your Git Project & Store Submission
    1. Explicitly Define the Branch in Store Submission
    In the PG3 Node Server Store Developer Portal (where you submitted the ACInfinity NodeServer URL):
    Ensure the Branch field is explicitly set to main (or master) rather than left empty or null.
    2. Verify Your Repository File Structure
    Ensure the root of your ACInfinity repository includes all required PG3/eisy metadata and entry files:
    File / Folder
    Purpose
    Requirement
    server.json (or polyglot.json)
    Node Server metadata definition
    Root directory. Must specify "executable": "acinf_main.py" and "type": "python3".
    install.sh
    Shell script for dependency installation
    Must be at repo root and executable (chmod +x install.sh).
    acinf_main.py
    Main script entry point
    Must match the executable field.
    profile/
    IoX Node definitions
    Must contain nodedef/, editor/, and nls/ subdirectories.
    Example server.json Root Template
    If you do not have a server.json in your repository root, add one:
    JSON
    { "name": "ACInfinity", "type": "python3", "executable": "acinf_main.py", "branch": "main" } Quick Workaround on the eisy Controller
    In the PG3 / eisy UI web interface, go to Node Servers $\rightarrow$ ACInfinity $\rightarrow$ Configuration/Details, manually type main into the Branch field, and save changes before triggering a re-install.
  2. awysocki's post in Migrated to PLUGIN, but no nodes show up was marked as the answer   
    UGH, the only thing that fixed it was to RE-INSTALL the plug in
  3. awysocki's post in Inclusion failed was marked as the answer   
    I tried that and still it won't add, tried excluding it like ZOOZ says and that didn't help.  
    What finally fixed it was to cut power to the switch.  After that everything worked like a champ. You try so many things that the basics are what shoot you in the foot.
    Its all working now.
     
    Thanks

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.