bmercier

As Javier pointed out, the web UI is not available remotely. PG3 Remote Connections allows you to: Use Node Server webhooks. Currently, only the Ring Node Server uses webhooks. Use the new Reinstall all Node Servers from portal UD Mobile Node Server management. Look under Admin | Plugins

Hello everyone, Please note that the menu in ISY portal has been updated. Under Select tool, there is now a new PG3 option: Purchased Node Servers: This option shows your node server purchases, which should be the same list as shown in PG3 under Purchases. Remote Connection: This option is used to allow a Remote Connection from portal & UD Mobile to PG3. The Ring Node Server uses this. This option used to be under Maintenance | PG3 Remote Connection. Reinstall all Node Servers: This option is the same as the PG3 option System | Re-install all node servers. This may become useful if you need to remotely update your node servers. Please note that Remote Connection and Reinstall all Node Servers will show up only if you are using PG3x with the minimum firmware level.

Yes. You can expect a 3.2 which will include this to come out soon.

If you can access it locally, you probably don’t need the backup. Did the owner give you his portal account, or did you set a new one? Polisy should automatically connect to portal when powered on. In your portal account, under the ISY tab, you should see your Polisy uuid, the same that you see in the admin console. Do you? If so, what’s the color of the round indicator after the uuid?

First of all, are you able to access the device locally with the admin console?

This means that UDX is not working. Troubleshooting steps: 1. Leave it a bit of time after boot up 2. Power down, wait a few secs, power on 3. In SSH: sudo service udx restart Sent from my iPhone using Tapatalk

Hello all, Once again we are resquesting help to beta test PG3x. 3.1.37 is now in beta and has again major changes and bug fixes: Changelog: Dashboard now shows node servers connected state in real time Fix the Purchase page with duplicated entries In the purchase page, show the update button only if an update is available Please note that if a node server advertises itself at a version which is different than the version in the store, then the update button will appear. Some node servers will therefore still show the update button although they are at their latest release. Node server re-install: Restart node servers after re-installation if it was running Node server re-install: At the end, display a confirmation message Node servers can now update property names of existing nodes (To be tested further) In node server nodes, property variable can be copied using copy icon Add support for dynamic property texts (UOM 150) - (To be tested further) General code enhancement Security fixes We would appreciate your feedback. Since this is a beta release, the installation is done through ssh with two commands: sudo pkg add -f https://pkg.isy.io/udx13.staging/All/pg3x-3.1.37.pkg sudo service udx restart We would appreciate your feedback.

@MrBill, are you on slack? Please change the node server status to new Sent from my iPhone using Tapatalk

Will look at it later today Sent from my iPhone using Tapatalk

AVremote needs to be fixed by the node server developer. I believe the node server is 2.0.6, but still advertises itself as 2.0.5, which makes PG3x display the update button. Sent from my iPhone using Tapatalk

It will be available later today Sent from my iPhone using Tapatalk

Hello everyone, This is the support thread for PG3x v3.1.36. After updating to 3.1.36, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.0.60. UDI interface 3.0.60 fixes a bug where the node servers loses their connectivity with PG3 when eisy loses network connection. You will have to restart your node servers after the update. You can check the UDI interface version in the node server's logs near the start. 3.1.36 will be available for installation on July 11th,

Hello everyone, Here's the latest changes. After updating to 3.1.36, please click on System | Reinstall all node servers, which will reinstall all your node servers including the new UDI python interface 3.0.60. UDI interface 3.0.60 fixes a bug where the node servers loses their connectivity with PG3 when eisy loses network connection. You will have to restart your node servers after the update. You can check the UDI interface version in the node server's logs near the start. Changelog for 3.1.36 "System | Re-install all node servers" now also updates the UDI interface module for all node servers. This is to update UDI interface to 3.0.60 Minor security fixes Changelog for 3.1.35 Significant rework on error handling in async functions Login API has been enhanced (Login should always work, or give an error message) Restore backup/Migrate from PG3: Made the UI more intuitive Notifications from PG3 now specify the uuid Restart required bug fixed

Portal will give you an offline warning only if offline long enough. If it reconnects within a few seconds, no warnings will be sent. Login to portal, and hover the online indicator and check the date. This tells you when it became online last. It’s a good reliability indicator. Sent from my iPhone using Tapatalk

The most likely reason is ISY getting offline and online on portal.

It should be working. Please open a support ticket and specify your uuid. You may want to check your configuration under My Profile. If "Amazon Echo and Google Home ISY" is set to My Preferred ISY, then make sure your preferred ISY is set correctly. Also on the ISY tab, for that ISY, click Select Tool | Connectivity | Google Home. Do you see your devices?

If core is at 3.1.33, UI will show 3.1.35. That is currently the latest release. UI version being out of sync with core is normal at that version. It’s a known bug. Sent from my iPhone using Tapatalk

Unfortunately I don’t know. If possible, open a ticket and attach todays log. You have at least one failed login, so I will be able to get more info on the problem. Please mention in the ticket that a power cycle fixed the problem. Sent from my iPhone using Tapatalk

Please try to login while tail -f is active. We need to see the error if any when trying to login. Sent from my iPhone using Tapatalk

If you can ssh to your eisy: tail -f /var/polyglot/pg3/logs/pg3-current.log

Hello, There is a known UI problem with 3.1.33: The UI incorrectly displays version 3.1.35 The UI incorrectly displays "PG3x Restart Required", and a restart does not clear this message. 3.1.34 will fix this. Benoit

If you really want to just restart PG3, it has to be through SSH. sudo service pg3 restart

Problem being you still can’t login? What does the PG3 log says? Sent from my iPhone using Tapatalk

There is a known problem regarding logins that sometimes fail. That’s the next stability issue I’m focusing on. I believe a reboot fixes the problem. Sent from my iPhone using Tapatalk

There is a cache problem with the packages. Sent from my iPhone using Tapatalk