Questions After (Auto) Update to IoX v.6.0.0

[woodchip]

15 minutes ago, bpwwer said:

I think you should have included this information along with a list of features that are not yet present in the eisy-ui in the release announcement. I'd also be interested in seeing a time line when each feature will be added (roughly, like maybe in each quarter of the year).

About the only thing I see eisy-ui currently doing is replacing the PG3 main menu and showing nodes and programs.  I'm not really convinced that the way eisy-ui shows nodes is actually an improvement over the way the admin console does.

Also, I wouldn't classify this as beta software. Beta typically means feature complete although not all features may work correctly and there are certainly bugs.  By your own admission, this is not feature complete. 

What's there tends to work pretty good.  I like how the variables are displayed and modified.  However, I was a bit shocked that I couldn't even look at programs.

I am looking forward to seeing how this evolves, it does seem to be a good start.

Ditto!

[Athlon]

@woodchip

Main Menu (upper left corner):

    

 

Then Settings:

  

 

Then Reinstall Plugins:

Edited Tuesday at 05:06 PM by Athlon

[woodchip]

30 minutes ago, Athlon said:

@woodchip

Main Menu (upper left corner):

Then Settings:

Then Reinstall Plugins:

 

Right! Think I did this yesterday, now after trying it again... no change. 

[Whitehambone]

On 9/29/2025 at 11:22 AM, mmb said:

What are you seeing?

Fyi I lost PG3 access and logged a ticket. UD said do the upgrade and see if it resolves.

I haven't upgraded and I'm seeing it.

@mmb Did you get access back to PG3?  I just opened the Admin Console to back up Z-Wave and IoX.  Once I finished, I opened PG3 to back it up and was unable to.  It is like PG3 is not running.  I rebooted several times, but there were no results. I did not upgrade. 

[mmb]

32 minutes ago, Whitehambone said:

@mmb Did you get access back to PG3?  I just opened the Admin Console to back up Z-Wave and IoX.  Once I finished, I opened PG3 to back it up and was unable to.  It is like PG3 is not running.  I rebooted several times, but there were no results. I did not upgrade. 

Yes I did get access to PG3.

After trying many many things including submitting a UD ticket it occurred to me to log out then log in again. That worked.

PS. I did get notifications in UDMobile that PG3 was shutting down and starting up during reboot, so I knew it was running.

Edited Tuesday at 05:50 PM by mmb

[bcdavis75]

Ok, I assume I'm dense but how exactly do we access the new dashboard?  I don't see a link to it in the eisy finder after upgrade.

 

Also, the announcement said something about Homekit integration now be included--but what does this mean and how do we actually use it?

 

Thanks!

 

[mmb]

3 minutes ago, bcdavis75 said:

Ok, I assume I'm dense but how exactly do we access the new dashboard?  I don't see a link to it in the eisy finder after upgrade.

In your web browser:

https://eisy.local

or

https://xxx.xxx.xxx.xxx/

[Athlon]

6 minutes ago, bcdavis75 said:

Ok, I assume I'm dense but how exactly do we access the new dashboard?  I don't see a link to it in the eisy finder after upgrade.

 

 

 

http://polisy.local/

or

https://eisy.local

[bmercier]

1 hour ago, woodchip said:

Right! Think I did this yesterday, now after trying it again... no change. 

@woodchip from what I see here, there is a problem with nodedefs. You should open a ticket and include the screenshot.

Also please include the output of:
/rest/nodes

/rest/profiles?include=nodedefs,editors,linkdefs

[brians]

On 9/29/2025 at 9:48 AM, bmercier said:

The login with portal credentials is expected.

The auto-update, I'm not sure. 

I just updated my Polisy - no issues. However It is still prompting for my local credentials which work.

 

When I login to new web eisy-ui I have to use my portal login.

I reboot Polisy and still is prompting for local credentials. It is working but I am wondering why everyone else seems to be prompting for portal credentials now?

UPDATE: I figured it out.

If I use https://x.x.x.x:8080 then it uses local My Lighting credentials.

If I use https:// then uses Portal.

I am used to using hardcoded IP since MDNS was broken in previous versions (seems to be fixed now). Therefore the way I was connecting did not prompt to use portal login and I also did not have issue with Home Assistant Integration credentials since I use http://x.x.x.x:8080 in my config.

Here is screenshot which shows better... the first one will use My Lighting credentials. The two bottom portal credentials...

 

 

Edited Wednesday at 02:03 AM by brians

[woodchip]

14 hours ago, bmercier said:

@woodchip from what I see here, there is a problem with nodedefs. You should open a ticket and include the screenshot.

Also please include the output of:
/rest/nodes

/rest/profiles?include=nodedefs,editors,linkdefs

I will follow your suggestion and open a ticket. Where do I find/access the outputs you suggest I include in ticket? Tks.

[Geddy]

3 hours ago, woodchip said:

Where do I find/access the outputs you suggest I include in ticket?

Try putting eisy.local:8080 then the above lines in a browser. 

http://eisy.local:8080/rest/nodes (xml display - I'd save to text file to put on ticket)

http://eisy.local:8080/rest/profiles?include=nodedefs,editors,linkdefs (copy text and save to text file)

It should ask you to login to display. Since it's local try the local credentials. 

[woodchip]

 

39 minutes ago, Geddy said:

Try putting eisy.local:8080 then the above lines in a browser. 

http://eisy.local:8080/rest/nodes (xml display - I'd save to text file to put on ticket)

http://eisy.local:8080/rest/profiles?include=nodedefs,editors,linkdefs (copy text and save to text file)

It should ask you to login to display. Since it's local try the local credentials. 

Tks

[wmcneil]

I have successfully installed 14.3/6.0.0 . After the install, it appears that rest get http commands are continuing to work with port 8080 . I tried configuring one in Network Resources for port 80, and when I click on the Test button, I get a error window popup with a "TCP client request failed" message. This is in a AC session that was opened using port 80 and ISY Portal credentials. Is rest going to continue to work only with ports 8080/8443, or will ports 80/443 eventually be supported?

[wmcneil]

2 hours ago, wmcneil said:

I have successfully installed 14.3/6.0.0 . After the install, it appears that rest get http commands are continuing to work with port 8080 . I tried configuring one in Network Resources for port 80, and when I click on the Test button, I get a error window popup with a "TCP client request failed" message. This is in a AC session that was opened using port 80 and ISY Portal credentials. Is rest going to continue to work only with ports 8080/8443, or will ports 80/443 eventually be supported?

Answering my own question: When I tried out using port 80 and ISY Portal credentials, I neglected to add authorization to the Network Resources entry I created. After correcting that mistake, port 80 is working for rest correctly.

[woodchip]

Ticket opened 2025-09-01. I will update when it is closed.

[noobmuch]

My experience:

nodes 404 error - reinstalling plugins no joy

Integer Variables 500 error

programs populate

Admin console sees Polisy and shows version 6.0

Login via admin console nothing populates. System busy/open folder icon in bottom left corner

power cycle Polisy no changes

 

[woodchip]

On 9/30/2025 at 1:58 PM, Athlon said:

http://polisy.local/

or

https://eisy.local

While attempting to resolve my issues with the new UI I noticed I am unable to establish a secure connection to my eisy... http: but not https:. Anyone with thoughts on this? Am I missing something?

On 9/30/2025 at 1:58 PM, Athlon said:

http://polisy.local/

or

https://eisy.local

 

On 9/30/2025 at 1:58 PM, mmb said:

In your web browser:

https://eisy.local

or

https://xxx.xxx.xxx.xxx/

While attempting to resolve my issues with the new UI I noticed I am unable to establish a secure connection to my eisy... http: but not https:. Anyone with thoughts on this? Am I missing something?

Edited yesterday at 01:07 PM by woodchip
Update detail

[noobmuch]

Logging in with Brave fixed my nodes 404 error that I was having with Safari.

 

 

[Geddy]

2 hours ago, woodchip said:

Anyone with thoughts on this? Am I missing something?

If using https add :8443 to the end of the URL. That might help. No port used is usually looking for :80. Since you're local to the device there's no real need to use https. There's no external comunication happening. Just browsers default to https these days. That's why only local devices need to add specific port that the eisy might be listening to. I think the ultimate goal is to make it the 443 port, but it's been 8443 for a while. 

If able to access with http that is fine. Don't complicate things that don't need to be complicated.

[Oakland Jeff]

I'm having the same https problems... no secure connection, even with :8443 appended.

I'm also confused why the admin console reports  IoX 6.0.0, but web ui reports 5.8.0

And where are we supposed to be able to see the OS 14.3 version number?

[wmcneil]

port 80 is the default port for http, so if no port is specified, port 80 is used

port 443 is the default port for https, so if no port is specified, port 443 is used

ports 80 and 443 use ISY_Portal credentials, and are available if running IoX >= 6.0.0 . These ports provide access to eisy-ui

ports 8080 and 8443 use IoX==local credentials

So if 14.3 and 6.0.0 are installed correctly any of these should work

https://eisy.local/WEB/sysconfig.txt  OR https://polisy.local/WEB/sysconfig.txt OR

https://eisy.local:8443/WEB/sysconfig.txt  OR https://polisy.local:8443/WEB/sysconfig.txt
 

If 6.0.0 is not installed correctly, the ports that use IoX==local credentials should still work:

https://eisy.local:8443/WEB/sysconfig.txt  OR https://polisy.local:8443/WEB/sysconfig.txt

 

 

 

[wmcneil]

I specified only https posts in my post above, and neglected to also specify http ports. Here is the complete list:

 

So if 14.3 and 6.0.0 are installed correctly any of these should work

https://eisy.local/WEB/sysconfig.txt  OR https://polisy.local/WEB/sysconfig.txt OR

https://eisy.local:8443/WEB/sysconfig.txt  OR https://polisy.local:8443/WEB/sysconfig.txt OR

http://eisy.local/WEB/sysconfig.txt  OR http://polisy.local/WEB/sysconfig.txt OR

http://eisy.local:8080/WEB/sysconfig.txt  OR http://polisy.local:8080/WEB/sysconfig.txt

 

If 6.0.0 is not installed correctly, the ports that use IoX==local credentials should still work:

https://eisy.local:8443/WEB/sysconfig.txt  OR https://polisy.local:8443/WEB/sysconfig.txt OR

http://eisy.local:8080/WEB/sysconfig.txt  OR http://polisy.local:8080/WEB/sysconfig.txt

Edited yesterday at 03:44 PM by wmcneil
fix typos

[woodchip]

43 minutes ago, Geddy said:

If using https add :8443 to the end of the URL. That might help. No port used is usually looking for :80. Since you're local to the device there's no real need to use https. There's no external comunication happening. Just browsers default to https these days. That's why only local devices need to add specific port that the eisy might be listening to. I think the ultimate goal is to make it the 443 port, but it's been 8443 for a while. 

If able to access with http that is fine. Don't complicate things that don't need to be complicated.

Good to know. I knew this to be a local connection just didn't understand why others were posting the eisy URL as an https:. Thanks for the clarification.

[SteveBL]

I am having the same problem after upgrading to 6.0.

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.

The actual upgrade went well and UD Mobile is fully functional.