11 minutes ago, SteveBL said:

I am having the same problem after upgrading to 6.0.

What problem is this? There's been several problems in this thread. Which do you have? You can highlight a previous post (a portion similar to what I have done) and click "quote selection" to reference prior comments. 

12 minutes ago, SteveBL said:

I can not log on via my PC using my old user name and PW and I'm told to please log on using my portal UN and PW.

This is expected and outlined in the wiki for eisy-ui.

Please referr to the wiki: https://wiki.universal-devices.com/Eisy:User_Guide#Changes_introduced_with_eisy-ui

Glad to hear the update worked well.

I think there are several items which are causing v.6.0 users’ confusion… at least I have been confused on some of what has been posted in this forum. Below is one example of what is causing me (and maybe others) some confusion

 

When I use IoX Finder…

 

Whether I choose “Admin Console (LAN) or Admin Console (Cloud) the only login option for the "Admin Console" is with my Portal credentials…

 

But according to wiki…

Wiki link https://wiki.universal-devices.com/Eisy:User_Guide#Changes_introduced_with_eisy-ui states:

Everything that worked before continues to work the same way:

·         IoX will respond to API requests on port 8080/8443 and require the same local username & password

·         PG3x/Plugins can still be used using https://eisy.local:3000, using your local username & password

 

 

Now wmcneil posted this…

 

 

Great having multiple ways to access but what about the wiki “Everything that worked before continues to work the same way:”

 

Can we have some consistency and establish “best practices”? Just asking.

 

 

@woodchip, 

• After successfully install of IoX 6.0.0 or later: ports 80 and 443 use ISY Portal Credentials, and become available. The only interface which is available only on ports 80 and 443 is eisy-ui, which includes a full PG3x interface fully equivalent to what was available (and still is available) on port 3000 using IoX==local credentials. All other interfaces are available both on ports 80 and 443, as well as continuing to be available on the prior interfaces:
• ports 8080 and 8443 use IoX==local credentials. All of the interfaces which used these ports prior to IoX version 6.0.0 continue to function using these same ports, and using the same IoX=local credentials that they used prior to IoX version 6.0.0
• port 3000 uses IoX==local credentials, and provides a PG3x interface. 

So after installing IoX 6.0.0 , you can choose to use only ports 80 and 443 for all interfaces going forward, or you can continue to use ports 8080 or 8443, and port 3000. So for example:

• If you access Admin Console via ports 80 or 443 using ISY Finder/Start, you will enter ISY Portal Credentials
• If you access Admin Console via ports 8080 or 8443 using ISY Finder/Start, you will need to authenticate using IoX==local credentials

I am not aware of any official best practices for port usage being published. The fact that you can choose to consolidate everything around ports 80 and 443 allows for that simplification if you so choose. That is what I am choosing to do. 

1 minute ago, wmcneil said:

@woodchip, 

• After successfully install of IoX 6.0.0 or later: ports 80 and 443 use ISY Portal Credentials, and become available. The only interface which is available only on ports 80 and 443 is eisy-ui, which includes a full PG3x interface fully equivalent to what was available (and still is available) on port 3000 using IoX==local credentials. All other interfaces are available both on ports 80 and 443, as well as continuing to be available on the prior interfaces:
• ports 8080 and 8443 use IoX==local credentials. All of the interfaces which used these ports prior to IoX version 6.0.0 continue to function using these same ports, and using the same IoX=local credentials that they used prior to IoX version 6.0.0
• port 3000 uses IoX==local credentials, and provides a PG3x interface. 

So after installing IoX 6.0.0 , you can choose to use only ports 80 and 443 for all interfaces going forward, or you can continue to use ports 8080 or 8443, and port 3000. So for example:

• If you access Admin Console via ports 80 or 443 using ISY Finder/Start, you will enter ISY Portal Credentials
• If you access Admin Console via ports 8080 or 8443 using ISY Finder/Start, you will need to authenticate using IoX==local credentials

I am not aware of any official best practices for port usage being published. The fact that you can choose to consolidate everything around ports 80 and 443 allows for that simplification if you so choose. That is what I am choosing to do. 

Based on what UD support is telling me, regarding my open ticket, the problems I'm experiencing are not related to ports but to issues caused when UD moved some profile data into new database tables and apparently my data only partially transferred correctly. :( 

On 9/30/2025 at 8:57 AM, bmercier said:

3. Check out the attached video clip. Is this how the dimmer slider is supposed to work? When you click on a position the light does seem to go to that percentage, but the slider springs back up. And we have two values, an 8-bit value and a percentage. It gets weirder when you click the up and down arrows next to the 8-bit numerical value. 

This is not normal.

When you click on it, it sends the command to eisy. But it will always move back if the command does not work - it reflects the current state. 

What is this device exactly? Is it using insteon, ZWave? Or is it from a plugin?

This is an Insteon 2477D Dual Band SwitchLinc Dimmer v.45. When I created the tile, I selected "Dimmer" from the "Create As" dropdown. I have created other tiles for other dimmers. They all seem to work the same way. 

23 hours ago, chris.com said:

This is an Insteon 2477D Dual Band SwitchLinc Dimmer v.45. When I created the tile, I selected "Dimmer" from the "Create As" dropdown. I have created other tiles for other dimmers. They all seem to work the same way. 

Today, I did an update and reboot of my eisy and this problem disappeared. The dimmer slider seems to function exactly as one would expect now. Did this get fixed? If so, thank you!

On 10/5/2025 at 12:56 AM, chris.com said:

Today, I did an update and reboot of my eisy and this problem disappeared. The dimmer slider seems to function exactly as one would expect now. Did this get fixed? If so, thank you!

I'm not sure why it would be working now. There has been no fixes released that would be related.

Upgrading to 6.0.  I had a hiccup when the Eisy wouldn't connect with the admin console, portal, or mobile app.  Solved by reconnecting it to wifi.  Unfortunately, the plugins are now disconnected in PG3 and not providing any data to the Eisy.  I'll let things sit overnight but obviously this won't work.  Paticularly disturbing is not having any of the Elk data.  Other plugins are also not providing data and show disconnected in PG3.  I've rebooted, restarted the plugins etc to no avail.

So I tried one more thing, reinstalling all of the plugins.  They connected and the data is now coming in so problem solved.  Not exactly a seamless upgrade but it appears to be all working now.  

Edited Wednesday at 06:49 AM5 days by keepersg
solution

Anyone else having issue with Programs with 6.0?    The UD app no longer has my device names, and the Admin Console has lost the ability to Set the status of an Insteon Device (there's no dropdown).

Any ideas would be very welcome!

Edited Saturday at 09:55 PM2 days by CPrindle

Try rebooting your eisy, you can also try clearing your java cache, be sure to check all 3 boxes, then download the IoX Launcher from here:

https://isy.universal-devices.com/start.jnlp

This is the follow-up from my post on 2025-10-02 “Ticket opened 2025-09-01. I will update when it is closed.”

I closed this ticket, subject “Problem with nodedefs”, on 10/03. This resolved the nodedefs issues by restoring a v5.9.1 backup. I was only able to successfully restore an earlier backup after connecting to the isy locally, not through the portal (https://) connection which was the only connection showing in the IoX finder after the v6.0 auto update.

This is the error I was receiving when attempting to restore a backup connecting to the eisy through https:

  

Once I was able to connect locally (http://) to the Administrative Console the restore performed normally. I then, as instructed, proceeded to “Upgrade Packages” from the Admin Console Configuration page.

It should be noted on the eisy-ui site I was running 0.6.0 prior to running  “Upgrade Packages” which changed to 0.6.1 after upgrade. My eisy-ui is now showing 0.6.3 as I have “Upgrade Packages” at least once since in an attempt to resolve on-going issues.

 

I've been working on what I can only call v6.0 issues for the past 10 days:

As I remarked in an earlier post “This UI (v6) is ‘Bleeding Edge’ PAINFUL!” and I stand by that comment. I feel I must be missing something or doing something wrong. Programs that ran fine prior to v6 no longer run and issues with Z-wave defy any logical resolution.

At times, usually after I have made changes to a program or after adding a Z-wave device, I will attempt a restart of the eisy and receive the popup error . This has been causing me a world of hurt to where I now backup after every change.

 

Here is 1 example of an issue I am unable to find a resolution for…

I’ve include an image of my IoX Finder incase I have done something wrong here:

If I connect with an http connection all my battery-operated Z-wave device nodes display with a  “Write Changes” icon. If connecting with an https URL the nodes appear to display correctly.

One issue at a time… if anyone has any insight into what I’m experiencing please reply.

I’ll add this last thought… There appears to be a difference between backups and restores made with http or https connections. So much for the wiki line “Everything that worked before continues to work the same way: (https://wiki.universal-devices.com/Eisy:User_Guide#Changes_introduced_with_eisy-ui)”

 

 

Edited 11 hours ago11 hr by woodchip
Image removed