bmercier

I'm not sure for what app you are trying to reduce rights. But what I know is there is 2 sets of credentials, and you are probably confusing both. The screen shot above allows to create IoX local users. We are going away from this in favor of ISY Portal credentials. So if you are logging in with an email address, that is an ISY Portal username. To create additional portal user, go to my.isy.io, login, and click on the Users tab. Then you can add a user there.

Hi Gary, Regarding the profiles error when checking programs, please try this url in a browser: https://eisy.local/rest/profiles/move/all Wait a few minutes, then try again. If that does not help, please open a ticket. Regarding the 404, I assume this is when clicking on a node? I would suggest to take a look at the eisy-ui log. Download the log eisy-ui log under System | Logs. The log should tell you what is failing, that would give a clue.

Are you using a 994? It would be much better if you had an eisy, and used eisy-ui. You could control what devices and buttons would be shown to your employees in a dashboard like interface.

eisy with current firmware are using newer servers behind an AWS load-balancer that will not route units to non-responsive proxy server. That instance that hung is running older code that is used for 994 and polisy/eisy running older firmwares. We leave those servers running for backward compatibility, but we are not planning to make changes to them. That failure scenario is extremely rare.

One of our AWS servers was no longer responding. Not our code, the actual AWS instance. I just terminated and restarted it, units that were “attached” to this server are reconnecting gradually as we speak.

Alexa is the preferred way to control eisy devices. It would be surprising that Alexa randomly turns devices on or off on its own, unless you have Alexa routines doing this.

Backup using remote eisy-ui should work, but I'm thinking that you may be hitting a timeout. Can you confirm that backup works well locally, and fails only remotely?

When using eisy-ui remotely, the Plugins page are not available. This is because those pages are essentially PG3x, and that can't work remotely.

Please open a ticket referencing this thread and attach the output of /rest/nodes and /rest/profiles We should be able to reproduce the problem and fix it.

eisy-ui 1.0.2 is released. It may take a few hours before the upgrade page shows there is a new version. But upgrading it now should pick it up.

Humm, maybe it won't "downgrade". Hold on, we will have 1.0.2 soon.

Please upgrade packages one more time. You need to be on 1.0.1. 1.0.1_2 was temporarily available yesterday, but that version won't work with remote eisy-ui, and does not include any significant changes over 1.0.1.

Not "all of your plugins". Only those that require ISY Access. By default, plugins cannot access IoX APIs. So if a plugin requires access to the IoX rest API, you need to approve it in the plugin configuration. What this does is provide a set of credentials to the plugin. When using PG3x, those credentials are the same as you use to login to PG3x. When using eisy-ui, a token is created and passed to the plugin. So in the end, if someome keeps alternating between eisy-ui and direct PG3x, plugins that require ISY access are restarted so they start using the new credentials.

It is now possible to use eisy-ui remotely, from Portal. If you have not already done so, please upgrade to eisy-ui 1.0.1. Then on my.isy.io, a new eisy-ui option will appear under "Select Tool". For now, we left the older "ISY Web Access" active, but we may remove this option eventually. Enjoy!

PG3x shows 3.4.16, which is the latest release.