bmercier

Adding nodes is not yet available, but this is coming soon. The current production eisy-ui (1.2.2) does not have the capability to add nodes. The beta release (1.3.4) does and supports insteon, ZWave, Zigbee, Matter and also through plugins.

@bpwwer If you find bugs or issues, it's best to open a ticket. If the audience is UDI and likely to trigger a conversation to troubleshooting, a ticket is more appropriate. If on the other hand you have something to say that is likely to benefit other users, then feel free to post here. If I see issues posted here, I will definitely look into it, but they may be overlooked as well as we don't continually monitor the forum. Issues posted here are not tracked either.

@awysocki Great question! I should have addressed that in my original post. In addition to what @bpwwer was saying, having it integrated brings these benefits; Management of plugins will be available through eisy-ui remotely on my.isy.io. With PG3x, that was not possible. The only way to manage plugins remotely was with the use of UD Mobile. This makes the whole solution more robust, especially when it comes to authentication. Although we were able to unify the login experience, this was still 2 products under the cover, and we had to go through hoops to make this work. PG3x was an older product that was an evolution from Polyglot -> PG2 -> PG3 -> PG3x. The codebase needed to be refreshed and re-thinked. There were "features" that were no longer necessary and could be confusing. For example: Support for multiple IoX, when most if not all users are just using it to connect to IoX. The local store had an optional developer mode that became needed (or let's say more convenient) when we introduced stricter permissions with PG3x. For development purposes, there is no need for a local store that is not in developer mode. A beta store, with plugins that may or may not share the same nsid with the production store. That made licensing harder to understand for users. This opens doors for a better plugin configuration UI. At this time, plugins can only be configured through "custom params" and "custom typed params". You have to go to the plugin configuration page. With this integration, we will be able to do things like right-click on a node and show plugin-specific configuration. We will be able to add more elaborate configuration UI that goes beyond a list of parameters. The current release does not have this yet, but this lays the foundation for more elaborate configuration, integrated with the rest of the UI.

@bpwwer PG3 and PG3x will continue to work with IoX, so they still can be used for development purposes. PG3 was already no longer maintained (except by yourself). Now, the change is that PG3x will also no longer be maintained. So for those older plugin that just needs to be maintained, they can stay in PG3 or PG3x. To debug production installations on eisy-ui, you can do things similarly. Install the production plugin in eisy-ui (There is no need for a local store for this), and using sudo, you can access files and logs. The installation location is /var/eisyui/ns/*and it follows a similar stricture as PG3/PG3x.

5.8.4 is quite old. These instructions will bring you to the latest production release: https://forum.universal-devices.com/topic/46914-os-144-release-is-now-available/ This will give you access to the latest eisy-ui production version. At this release, there are still some gaps with the admin console though. But we have 1.3.4 currently in beta that is coming very close to what the Admin Console offers, and more. And you can expect some more incremental updates in the coming weeks. Once you have eisy-ui, upgrading to the the latest release is a breeze.

We have published a new release of eisy-ui, version 1.3.4 in Beta. This new release introduces 2 major features: Integrated plugins Insteon / Z-Wave / Zigbee / Matter UI This post details the new features related to Insteon, Z-Wave, Zigbee, Matter UI (Protocols UI) With eisy-ui 1.3.4, we're introducing Protocols: a complete, browser-based experience for adding and configuring your Z-Wave, Zigbee, Matter, and Insteon devices — no Java Admin Console required. Device setup has traditionally meant navigating the Admin Console. It worked, but it was never as smooth as it could be. With this release, you can manage your protocols and devices directly from eisy-ui. What's New We didn't just move the existing experience to the browser. We took the opportunity to improve it with smarter device inclusion, deeper configuration options, and a more streamlined workflow. Z-Wave Z-Wave setup is now faster and more flexible. SmartStart with QR Code — add devices by scanning a QR code, with support for both standard mesh and Long Range inclusion. No more manual search and pair. Z-Wave Region Selection — configure your region directly from the browser, including support for the US Long Range region. Protocol and device-level configuration — full access to Z-Wave protocol settings and per-device configuration, all in one place. ZMatter USB Dongle firmware upgrade — eisy-ui now links directly to the dongle firmware upgrade instructions, so you always know where to go when it's time to update. Step-by-step instructions here. Insteon Everything you need to manage your Insteon network is now available in eisy-ui. Device linking — add and link Insteon devices directly from the browser. Protocol and device-level configuration — full control over your Insteon setup without leaving eisy-ui. Advanced i3 Keypad settings — we've added a full suite of i3 Keypad configuration options, including: Load Detachment — detach the load and buttons independently for more flexible control. Load Button Selection — assign which button controls the load. Night Mode — configure Night Mode properties and behavior to suit your space. Matter Adding Matter devices is now straightforward. QR Code and pairing code inclusion — add devices directly from the browser using a QR code or manual pairing code. Enhanced inclusion and mDNS debugging — better visibility into the inclusion process to help troubleshoot connection and inclusion issues. Protocol and device-level configuration — manage your Matter setup end to end from eisy-ui. Zigbee Zigbee is now fully supported in the browser. Add devices from the browser — no extra tools or additional steps required. Protocol and device-level configuration — everything you need to manage your Zigbee network, right where you expect it. One More Thing: Scan Anything Across all protocols, adding devices just got even easier. QR Code scanning via uploaded image or live photo — if your hardware supports it, snap a photo directly in eisy-ui, or upload an image of the QR code. Either way, no manual entry is required. Everything, In One Place eisy-ui is ready for you today. Your devices, your protocols, and your configuration — all from your browser. This is the first release of the new Protocols UI, and we look forward to improving it further based on your feedback. Thank you for being part of this journey with us. We can't wait to hear what you think.

We have published a new release of eisy-ui, version 1.3.4 in Beta. This new releases introduces 2 major features: Integrated plugins Insteon / Z-Wave / Zigbee / Matter UI. This post details the new features related to integrated plugins. For a while, eisy-ui had PG3 integrated into the UI. But under the surface, if was still using the former PG3 as a separate service. With version 1.3.4, you can now run your plugins directly in eisy-ui, without PG3. In a way, this is a complete rewrite of PG3. All the existing plugins should work without a change as eisy-ui is backward compatible with PG3. Differences with PG3 Production vs beta store. In eisy-ui, there is only one plugin store: the ”production” store. Most plugins that are in the beta store also exists in the production store. If you are using a plugin from the beta store that does not exist yet in the production store, the developer will have to publish to the production store. Plugin developers that want to publish a beta version of their plugin can do so using the “Beta” edition. In PG3, plugins could have the “Free”, “Standard” and “Professional” editions. The addition of the “Beta” edition will allow developers to publish beta releases of their plugins. Beta releases will have an expiration date that is tied to the version. This will allow them to publish additional beta releases as new version comes out, allowing users to restart a beta trial on the new release – something that was not possible in PG3. Local store For developers: The local store in eisy-ui is implicitly in developer mode. This works virtually the same way as PG3, but it’s a bit easier to use as the store entry features only the relevant fields. Understanding plugins in PG3 vs eisy-ui Plugins in eisy-ui, just like plugins in PG3, are installed into IoX “slots”. With 1.3.4, you have access to plugins in eisy-ui and PG3. But a plugin in a given IoX slot can only live in PG3 or in eisy-ui. If a plugin is installed in PG3, then you need to go to the PG3 Dashboard to see the plugin. Conversely, if the plugin is in eisy-ui, you need to use the “Plugins (Beta)” option to see the plugin. Migrating plugins from PG3 to eisy-ui Migrating your plugins is easy. Go to Plugins (Beta), then “Migrate from PG3”. You will see your PG3 plugins and will be provided with buttons to either migrate them individually, or all at once. This will stop the plugin in PG3, install the plugin in eisy-ui using the same IoX slot, and migrate the configuration. This way, your programs should continue to work with the same nodes, but now managed by the plugin in eisy-ui. If something goes wrong, you can always migrate back to PG3. When you migrate from PG3 to eisy-ui, the plugin stays in PG3 as-is, but is marked as “migrated”. If you have to revert, it can be restarted with the exact same configuration. Beta plugins can’t be migrated. Plugins in developer mode can’t be migrated either. Developers have to recreate the store entry and “install” from there. It can use the same plugin folder though. Backups eisy-ui backup & restore will backup and restore your plugins. Make sure to take a backup after migrating. Once the plugins are removed from PG3 (or PG3 is disabled), you may notice that the backup size will be significantly lower. When backing up PG3, all the plugin folders were saved, including the plugin code & dependencies. That is not necessary. eisy-ui backs up only the data; The database, and some of the known data folders. When restoring a backup, the plugin gets installed, and the data from the backup is restored. Having a smaller backup footprint will allow us to introduce automated backups in the future. Known issues This is still very new, which is why this is released as beta code only. We are aware that the 4 node.js plugins (ST-Inventory, ST-Sonos, ST-Nuheat, ST-Ecowitt) are currently not working. There is no “reinstall all plugins”. This will be added in an upcoming update.

"ASC" means Ascending order

You must have upgraded from the Staging repo a few days ago. Upgrade packages again.

Please open a ticket.

First of all, it would be very odd to lose the Favorites page following an upgrade. Did you restore a backup or something? The only solution really is to restore a backup from just before the upgrade. Just restore eisy-ui, like this:

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.