bmercier

It is still in progress. The major feature of this release is program edit. In the next release, you will have the ability to add devices. It will have most of it not all configuration options related to Insteon/Z-Wave/Zigbee, and at that point, it will be very close to be on par with the Admin Console.

In eisy-ui, you can also go to the System | About page, or the System | Boot environment.

This is also fixed in eisy-ui 1.2.1

This is not possible today, but this is a great suggestion. I can't promise it, but will look into it.

They will be side by side if the tile is wide enough. If they don't, then edit the tile, and look at the widgets. Do you have more than one "Properties" widget? If so, you may want to go back to a single Properties widget. Widgets are always one below the other, not side by side.

If anyone is having issues with eisy-ui not working & eisy being offline, there was an issue with the initial release. The problem was that eisy-ui would not start if there was exactly one plugin installed. To recover from this, eisy-ui needs to be updated to 1.2.1. There are 2 ways; With the admin console, or through ssh. To update using the admin console: Start the IoX launcher, click add, enter https://eisy.local:8443/desc At the login prompt, use the user admin (default password is admin) Then go to configuration and click on "Upgrade packages" To update using ssh: Open a command prompt and enter these commands; ssh admin@eisy.local (Password is admin) sudo pkg install eisyui sudo service eisyui restart Workaround: It is possible to fix this problem without updating. Go to PG3x at https://eisy.local:3000 Login using admin/admin You should have exactly one plugin. Just install any free plugin. eisy-ui should start and within one minute.

A repurchase should not be necessary. But an uninstall and reinstall may be required. PG3 is sensitive to the plugin name. But licenses are based on the nsid. So unless the nsid changed, a repurchase is not necessary. If the nsid changed somehow, I can update the licences.

You may want to disable wifi completely. Open an SSH session, and use this command: sudo udxops.sh wifi.disable

I would recommend to change your approach. It's not possible to reduce rights to the rest API. If you have a valid user id, it will allow you to do all of that. The recommended approach would be to implement this as a plugin. Basically, a plugin will expose nodes to eisy, and all the plugin will be able to do is expose properties and commands. It won't have access to the rest API (unless you configure it as such). The plugin would communicate with your app on PI using the protocol of your choice - That could be a Websocket for example. The plugin would be setup in developer mode, and stay like that forever. Or, you could publish it to the production store, and sell it or offer it for free (and of course it would require the pi to be pre-installed with your app).

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.