eisy-ui 0.7.2 is out.

Release notes for 0.7.2

• General usability enhancements

• Link to documentation

• Link to Admin Console

• Upgrade packages page

• Home page defaults to Nodes when there are no favorites

• Disabled remote logging by default

• Hide node properties that are marked hide=true (Like Admin Console)

Here's what the upgrade packages page look like:

eisy-ui 0.7.0 is out.

This release includes several bug fixes since 0.6.3. Whenever you have a chance, please use upgrade packages in the admin console.

The main new addition is the Programs detail page, which allows you to see your programs.

Here's the first alpha release of eisy-ui.

If you are familiar with SSH, you can proceed with a manual install of eisy-ui for testing purposes. For now, I'm expecting just a few installs by technical folks. If you are not familiar with ssh, please wait for the beta release. If you have installed this alpha release, please give this post a "Thanks" and feel free to provide feedback.

Prerequisite

Please run an Upgrade packages from the admin console.

eisy-ui relies on new APIs available only on the latest IoX. The latest PG3x 3.3.19 is also required.

To install eisy-ui

1. Go to the latest post in this thread to find the latest alpha release
2. Install: sudo sudo kg install -f <package name>
3. Start the service: sudo service eisyui restart

Using eisy-ui

1. Launch your browser to: https://eisy.local
2. Login with your portal user and password

eisy-ui features

Favorites page
This allows you to create a dashboard like page to interact with your nodes. Organize them the way you like it. Just display the properties and controls that are relevant to you. Use widgets to create an intuitive interface to manage your lights, color bulbs and thermostats. Group relevant nodes within the same tile.

PG3x integration
You can access PG3x from within eisy-ui. For the most part, it's just the same PG3x served within iframes, except that there is now a single sign-on.

In PG3x you used to have to login with your IoX user and password, and there was a separate portal login that was required. That portal login could be reset using System | Switch Portal Profile. This is no longer the case.

With eisy-ui, you login once to eisy-ui with your portal user profile and can access PG3x. That's it.

Portal connection
IoX used to make the outbound connection to portal. This is no longer the case. When eisy-ui is installed, eisy-ui connects to portal instead of IoX. This change is transparent. This however lays the groundwork for multi-connections to portal which will allow parallel requests from portal to eisy, and thus enhance speed.

Rest API
The IoX rest API can now be accessed on ports 80 and 443. However, this works with your portal credentials instead of IoX user and password. The rest API can also be accessed using a JWT, but that's beyond the scope of this post.

Logging
eisy-ui's log is on the file system as you would expect, but it is also sent to our cloud log server. Eventually there will be a setting to allow/disallow this. But for now, this can't be disabled. This allows us to troubleshoot problems that may arise more easily.

Backward compatibility
Please note that IoX can still be accessed directly on port 8443 and 8080, using IoX user and password.

PG3x can also be accessed directly on port 3000, using IoX user and password, just like before. However, it is not recommended to switch between using PG3x from eisy-ui vs directly on port 3000. If you do so, you may have to use System | Switch portal profile when using PG3x on port 3000.

The only permanent change when eisy-ui is installed is that IoX no longer connects to portal. So if your eisy is offline, make sure the eisyui service is running.
 

FAQ
Can I see the eisy-ui log?

At this time there's no UI to see the logs like PG3x does. To see the logs in real-time:
tail -f /var/eisyui/logs/ui-current.log

What devices are supported?

https://eisy.local/nodes, which is the main page to see your nodes is very similar to what you are used to in the Admin Console, and this supports any nodes.

The Favorites page likewise supports any nodes. There are specialized widgets that allow to make a better UI like switches, sliders, etc. You can create a nice UI for thermostats and color bulbs in particular. There is however no specific widgets for locks. Only the "Generic command" can be used for those.

There is also no supports for scenes or programs yet.

I have a 994/Polisy, can I install eisy-ui?

Unfortunately no. eisy-ui can only run on eisy.

What's next?

In addition to a nicer UI, the goal of eisy-ui is to replace the Admin Console. One of the biggest upcoming feature will be the ability create and manage programs. We will also make enhancements based on the feedback from this alpha release.

Eventually, the Favorites page tiles will support scenes, programs and variables directly. This will allow such things as displaying the status of a node, but control through a scene or program.
 

Here's a few screen shots
 

This is a major release that upgrades the OS to 14.1p6, includes Initial Matter support, installs HomeKit plumbing, installs eisyui plumbing, and fixes many INSTEON, Z-Wave, Zigbee, and plugin issues.

BEFORE YOU START

1. It's imperative that you take a backup of your IoX, Z-Wave, and PG3 settings.

2. This upgrade is upgrading your OS. As such, the unit will reboot in the process and the Admin Console will simply get disconnected (does not close). Please do not turn off the unit till you can get back to the Admin Console.

3. If you have never upgraded your unit, it's best to make sure you have release 13.1 or 13.2 of the OS (https://eisy.local:8443/WEB/sysconfig.txt). If you do not, please do not upgrade.

4. In order to get Matter supported on WiFi, we had to change WiFi settings so that it will now use 802.11a/g which is significantly slower than 802.11ac that you are used to. Although you won't see much impact for command/control, download speeds for local Admin Console will be slower. It's our top priority to get WiFi back to the ac range you are used to. 

-- Polisy does not support Matter when connected using WiFi.
 

INSTRUCTIONS

1. Backup Z-Wave and then IoX

2. Backup PG3

3. Please ONLY use the Admin Console | Configuration tab  | Upgrade Packages button. Do NOT use ssh.

4. Unit will reboot and Admin Console will become unresponsive. Do NOT attempt reboot until you can get back to the Admin Console.

Enhancements

- Faster boot times.
- Power button no longer allows package upgrade.
- Homekit service using Matter Bridge. This requires a plugin that will be available next week.
- eisyui service. Currently in development.

- Matter

Initial support for light bulbs and plugin modules:
-- WiFi direct.
-- WiFi through a Border Router such as Google Nest Hub or Apple HomePod.
-- Thread through a Border Router.

- Zigbee
-- Support Relative Humidity and Temperature Measurement Clusters.
-- Support thermostats.

- INSTEON
-- LED Control for i3 Dial and i3 Paddle.

- Programs 
-- Added 'Unix Date/Time (seconds)' to the set of system values you can assign to a variable.

- Admin Console
- Log Viewer and Capture for Matter, Zigbee, Z-Wave, and other logs.

Fixes

- System
-- Infrequent crash at iox boot up due to timing.
-- SMTP mail removing new lines.

- Plugins
-- Wemo/Roku support through WiFi.

- Z-Wave
-- Fixed problem where Z-Wave migration would fail to migrate any Z-Wave devices.

- Zigbee
-- Fixed problem of nodes not being created for devices with multiple buttons.
-- Query Zigbee devices after they are added.

- INSTEON
-- Fixed problem where some commands were missing from InlineLinc devices.
-- Fixed problem where INSTEON would stop responding (usually caused by using I3 Dial).
-- i3 Paddle and i3 Keypad buttons default links.

- Programs
-- Fixed problem where node status changes caused control conditions to run (only affected plugin nodes).
-- Show Unix Time status values as Timestamps

- Admin Console
-- Some characters not displayed correctly in Admin Console.

 For Developers
-- Plugin timestamp support.
-- Allow plugins to define their own status names in nodedefs.
-- Fill in device type field for Zigbee (so Philips hue can be recognized).
-- Added <rpnode> to Zigbee nodes. 
-- IoX events are now posted to MQTT.
-- Fix ISO8601 Timestamps for node property history and events.

With kind regards,
Michel

This release contains minor enhancements and bug fixes.

Important Note:

Please do not unplug your unit from power. 

Instructions:

1. Backup your unit.
2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. 

Fixes:

 - Insteon I3 Paddle and I3 Keypad buttons default links
 - Show Unix Time status values as Timestamps
 - Faster IoX Backup
 - Some characters not displayed correctly in Admin Console

For Developers:

 - Allow node servers to define their own status names in nodedefs
 - Fill in device type field for Zigbee (so a UI can properly identify devices)
 - Query Zigbee devices after they are added
 - added <rpnode> to Zigbee nodes
 - added <NodePropertyHistory> to system options
 - Initial support for posting events to MQTT
 - Fix ISO8601 Timestamps for node property history and events

There has been a few releases not publicly announced - here's the details:

Release notes for: 3.2.27 

• Change timestamp format to YYYY-MM-DD HH:mm:ss.SSS (Same as python interface).

Release notes for: 3.2.26

• Enhanced reliability of the plugin's status node connected state.

Release notes for: 3.2.25

• Fix for UD Mobile remote connections.
  • Some messages were too big and would not reach UD Mobile, causing a "spinning wheel".
  • This fix is in PG3 only. An update to UD Mobile will be coming as well.

Release notes for: 3.2.24

• When reinstalling a plugin, don't delete the existing plugin files.
• Add support for plugins to override the polling values.
• Plugin license check tolerant of connectivity failures.

Release notes for: 3.2.23

• Added feature to allow system to automate a reinstall all plugins automatically, which will be used for emergency updates by UDX

This release contains minor enhancements and bug fixes.

Important Note:

Please do not unplug your unit from power. 

Instructions:

1. Backup your unit.
2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. 

Fixes:

- Remove default time events from event viewer
- Occasional issues when restarting IoX

Features:

- Better support for Philips Hue (including support for enhanced hue)
- Support Zigbee Color XY / Temperature
- Allow user to manually specify Zigbee radio channel (for Securifi devices)

Here's the latest PG3x release.

Release notes for: 3.2.22 - 04/16/2024

• Make Plugin license check tolerant of connectivity failure on startup
• Change logs time format after midnight from 24:xx:xx to 00:xx:xx
• Developers: Add capability to update the plugin name

Here's the latest PG3x release.

Release notes for: 3.2.21 - 04/15/2024

• Add capability to upload a zip file to the "data" plugin directory (For selected plugins such as the Audio Player

Here's the latest PG3x release.

Release notes for: 3.2.20 - 03/12/2024

• Disable the global MQTT queue (Fix to the Auto-Logout)
• Minor fixes
   

Here's the latest PG3x release.

Release notes for: 3.2.19 - 02/26/2024

• Enforce ISY access security - For plugins that require ISY access, user has to click Allow ISY Access
• PG3x Logging to syslog now only includes the startup and shutdown sequence
• On addnode, if creating the node on IoX fail, log the error
• If oAuth authorization code exchange fails, log the token endpoint response

ISY Access security

Starting with this release, plugins can no longer directly access your eisy/polisy using the rest API unless you allow it. Most plugins don't need direct access. Some plugins like Backup and ELK may need it. If the plugin needs direct ISY access, a checkbox "Allow ISY Access By Plugin" will appear in the configuration page.

If you are using the Backup plugin,  you need to enable ISY Access. 

If you are using the ELK plugin, and if you are using ELKID or ELKNAME you must enable ISY Access as well. 

Here's the latest PG3x release.

Release notes for: 3.2.18 - 02/07/2024

• Rate limiter: Increase limits on the global queue
• Add support for the upcoming python interface oAuth module
• When UI requests "customs", return a key for all requested "customs"
• Fixed Authenticate button which sometimes does nothing
• Fixed devd configuration when in developer mode

We have a major OS upgrade to FreeBSD 13.2p9 which also includes major stability fixes for the plugins. This is not urgent.

If you wish to upgrade, please follow the same procedure as always, either:

Admin Console | Configuration tab | Upgrade Packages button, or

One click on the Power button.

You will have to reboot after the upgrade. So, it's best to use the Admin Console to be notified when the process is completed. If UD Mobile is setup for notifications, you can use the power button and you'll be notified on UD Mobile. 

With kind regards,
Michel

This release contains minor enhancements and bug fixes.

Important Note:

Please do not unplug your unit from power. 

Instructions:

1. Backup your unit.
2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. 

Fixes:

Release notes for: 5.8.0_1 - 01/03/2024
- Fixed reboot on polisy when using ZMatter in original mode
Release notes for: 5.8.0 - 01/01/2024
- Fixed system crash (for Insteon users)
- Fixed subscription causing crash when bombarded
- Misc bug fixes

Features:
- Integration of sqlite database for recording events/property changes
- Node property history database - disabled by default

Support discussion:

With kind regards,
Michel

Here's the latest PG3x release.

Release notes for: 3.2.17 - 12/19/2023

• Allow to remove a node server even if the store entry no longer exists.
• When auto-logout, add a message in the UI.
• Add a rate limit on MQTT inbound messages from plugins & UI.
• Fix addnode for cases where the ISY request fails with an http error.
• When viewing a plugin, hide the readme and changelog if they are null.
• When new version is available, have the update button appear. Previously a restart of the node server was required.
• Make PG3 logLevel persistant
• Fix setController on first startup. Previously, setController will fail if addnode is not finished.
• Fix store edit UI (We could get a JS error due to accessing an incorrect field).
• Minor bug fixes and logging enhancements

This release contains major enhancements for migration from 4.9 to eisy/polisy and an updated BIOS to address some of the most recent security vulnerabilities. 

Important Note:

Please do not unplug your unit from power. 

Instructions:

1. Backup your unit.
2. Please click on the using the Upgrade Packages button in the Configuration section of the Admin Console. 

Fixes:

1. Thermostat min/max validation incorrect from some Z-Wave thermostats
2. S2 verification popup appears when using SmartStart
3. Mouse button click on Unix
4. Random crashes 
5. Added Rust to dev packages (needed for Kasa)

Features: 

1.  Support ISY994 version 4.9 backup/migration 
2. Add auto/on/off configuration setting for enabling Z-Wave/Zigbee
3. New installations default to ZMatter/Z-Wave

API

1. Add event indicating all nodes for a device have been added
2. dd 'hint' field to all nodes

With kind regards,
Michel

Here's the latest PG3x release.

Release notes for: 3.2.16 - 11/9/2023

• When PG3 start/stop, send a single notification (instead of one per plugin)
• Auto-install default node servers after login
• Add install.log to the log packages
• Include stderr to install.log

Here's the latest PG3x release.

Release notes for: 3.2.15 - 11/6/2023

• Fix IoX showing disconnected following initial startup
• Fix store selector being blank following initial startup

Here's the latest PG3x release.

Release notes for: 3.2.14 - 10/26/2023

• Add capability to restore a backup from another PG3x
• Minor bug fixes

Here's the latest PG3x release.

Release notes for: 3.2.13 - 10/24/2023

• Fix purchase process so it is edition-aware (This fixes the license check)
• oAuth: Add the scope to the token endpoint (Some oAuth servers needs it)
• Fix adding nsdata/oauth to the custom table (Fixes a bug that could prevent oAuth Authentication)
• When installing a plugin, display the purchase date and expiry in local time

Here's the latest PG3x release.

Release notes for: 3.2.12 - 10/23/2023

• Fixed 2 regression bugs introduced with 3.2.11

Here's the latest PG3x release.

Release notes for: 3.2.11 - 10/23/2023

• Fix license check for node servers with multiple editions.
• UI: Rename Node Servers -> Plugins.
• UI: Hide the developer menu when logged out.
• UI: Fix Migrate from PG3 backup file selection.
• UI: Updated reinstall all confirmation message.
• oAuth: Add logging of authorization failure.
• Enhance error handling when isy is not found in the config.

Here's the latest PG3x release.

Release notes for: 3.2.10 - 10/12/2023

• Fixed the profile upload when in developer mode

Hello everyone,

Here's the latest PG3x release.

Release notes for: 3.2.9 - 10/09/2023

• Restore process: Allow restore to a new system (it will do a reinstall all)
• Restore process: Go back to login after completing restore
• Fixed the "No IoX was automatically discovered on your local network." error.

1. Using IoX Launcher access Admin Console
2. Run IoX Backup (NOTE: if running Z-Wave run Z-wave backup first then IoX backup)
   • Menu -> Z-Wave -> Backup -> Click "Yes" to update/replace Z-Wave backup
     • No progress is shown, but backup is made
   • Menu -> File -> Backup IoX -> Save file (will be a .zip file leave it intact)
     • Process bar will advance. Please do not make any changes to system during this time.
3. Click on Configuration tab
4. Click on Upgrade Packages button
   • Click "YES" to confirm
   • 
5. Leave "Warning" box on screen. (Okay if you don't, but it is found to be a good reminder not to change/close the system)
   • If UD Mobile is setup for system notifications you should receive a few notifications that device is offline (as well as node servers are disconnected) and alerts when it comes back online.
   • 
   • 
6. Notice of update complete and if system should be rebooted
   • 
   • 
7. Click Reboot button (system should still be on Configuration tab in Admin Console)
8. Admin Console window will close
9. Allow system to process the reboot (An undetermined amount of time should pass. Polisy will beep several times once rebooted). Will usually get alerts on UD Mobile that the device has gone offline and online again. 
10. If the update was for IoX firmware release please Clear Java Cache (be sure to select all three boxes in the process.
    • 
11. Delete any OLD copies of start.jnlp or admin.jnlp you might have on your system.
12. Download a fresh IoX Launcher from UDI site 
    • Found by clicking on "My ISY" on the top right of the website
    • Direct link: https://isy.universal-devices.com/start.jnlp
13. Run IoX Launcher and log into Admin Console as you normally would
14. Confirm Firmware and UI match on the Help -> About menu
15. Launch PG3 from Admin Console
    • Menu -> Node Servers -> Launch Polyglot V3 (PG3)
    • Or og into PG3x using the IoX Launcher or typing the URL directly into your browser
16. Once logged in if this was a Polyglot update confirm PG3x version at the bottom of the dashboard screen. 

NOTE: Make a habit of not changing anything in Polyglot if the Admin Console is open. Any changes made in Polyglot need to have the Admin Console restarted to push any updates to the IoX system. It's best practice not to be logged into Polyglot and Admin Console at the same time to avoid any conflict in changes or simply to have the changes visible in Admin Console. Only log into one system at a time!

Trouble Shooting:

If you cannot log into Admin Console after an update:

• Power Cycle the device 
  • Using the multi function button to shut down then pull power for 10 seconds
  • Using the multi function button to force a restart
  • Refer to the wiki User Guide for the device you are using for proper button pushes
    • Presses should be short, but not too short, but not held more than 2 seconds
• Be sure you cleared Java Cache correctly
• Be sure your Java is updated. IoX Launcher is designed to run on current versions of Java available directly at www.java.com. Using different versions might impact some parts of IoX Launcher and make it difficult/impossible to access and use Admin Console. 

If you cannot access Polyglot (PG3/PG3x)

• Power Cycle the device (see steps above)
• Attempt with a different browser
  • Tested working all browsers will load PG3/PG3x local web services
• Turn off any antivirus/firewall/pop-up blocking software

Additional Comments:

It is "normal" for the IoX Finder window to display both a local friendly URL name and an IP address for the same device. It may, or may not, display this after an update. Do not be shocked if it does, or doesn't. Typically IoX Finder will report the first handshake for the name/IP for the device you are using. In some instances it is reporting both the IP address and the eisy.local (or Polisy equivalent). Lines that are "Found" and added in the process of looking cannot be deleted. This is expected behavior. 

If you have added the Portal URL to the Admin Console sometimes that will stay through a Java Cache clearing because it is stored in a UDI*.state file, but it is normal for this to also not appear after an update. If you use the Portal URL to access your device (even while local) please remember to use your Portal Credentials when using the Portal URL to access the Admin Console.