I remember reading something about a new usesr interface, eisy.ui. Right now I am using the Admin Console which required Java Runtime Environment. I know every time I update Java I need to "rerun" the startup file to get the Launcher to bring up the Admin Console.

Will the new UI be easier to use? I have lots of folders and scenes created through the Admin Console. Do they automatically port over to the new UI?

Is there a Users Manual for the new UI?

You should be able to access it via eISY.local from your web browser. It a work in progress and is not ready to replace all of AC yet. That’s assuming your eISY is up to date.

Edited Thursday at 11:01 PM1 day by hart2hart

13 hours ago, hart2hart said:

You should be able to access it via eISY.local from your web browser. It a work in progress and is not ready to replace all of AC yet. That’s assuming your eISY is up to date.

How would my router know where eISY.local is?

These names have never worked in any LAN/Router system I ever had. I have no local DNS server.

42 minutes ago, larryllix said:

How would my router know where eISY.local is?

These names have never worked in any LAN/Router system I ever had. I have no local DNS server.

Have you tried it?

I'm not a network guy, so I am sure others would be able to explain it better then I could. But I thought eisy broadcasted it's name across the network.

Oh, all routers I have had in last 10 years had DNS built-in. Just use the router address if needed.

I did things the old fashioned way, adding my controllers to my PC's local hosts file. There is never any confusion as to which one is eisy, polisy, polisy2

28 minutes ago, DennisC said:

Have you tried it?

I'm not a network guy, so I am sure others would be able to explain it better then I could. But I thought eisy broadcasted it's name across the network.

Oh, all routers I have had in last 10 years had DNS built-in. Just use the router address if needed.

Thanks
Of the 7 routers I have owned, they have only ever supplied the IP address of external DNS servers. There was no local DNS server or file containing local name conversions. Routers always contain a NAT translation table for the DHCP server.

This has always been a problem because the ISY URL, always given out here, has never worked on any system I have owned. The IoX locator always disappears sooner or later, and then the links to reload it, never work, making it a real struggle to recover and access my polisys or ISYs.

20 minutes ago, larryllix said:

Thanks
Of the 7 routers I have owned, they have only ever supplied the IP address of external DNS servers. There was no local DNS server or file containing local name conversions. Routers always contain a NAT translation table for the DHCP server.

This has always been a problem because the ISY URL, always given out here, has never worked on any system I have owned. The IoX locator always disappears sooner or later, and then the links to reload it, never work, making it a real struggle to recover and access my polisys or ISYs.

I understand what you are saying. But, reinforcing my previous disclosure about not being a network guy, I don't think eisy.local relies on DNS. I "think" eisy advertises itself on your local network using mDNS (Multicast DNS). It is not a "real IP address". It is just yelling out "is there anybody called eisy.local" and eisy replies.

I also don't think its the same setup as IoX Launcher.

25 minutes ago, DennisC said:

I understand what you are saying. But, reinforcing my previous disclosure about not being a network guy, I don't think eisy.local relies on DNS. I "think" eisy advertises itself on your local network using mDNS (Multicast DNS). It is not a "real IP address". It is just yelling out "is there anybody called eisy.local" and eisy replies.

I also don't think its the same setup as IoX Launcher.

Network devices do not communicate by URL names. A DNS server has to be contacted first, which then supplies an IP address for same, or passes the request up to the next DNS server, usually google or similar, to be used by network devices. Then network and Internet devices use IP addresses for communications.

LAN devices do shout out keepalive signals occasionally, to keep the router aware they are there but no URL names are used. Only IP addresses are used at this point in connection time.

LAN devices contact a DHCP server with their MAC address of the hardware and receive an IP address from it, so they can be contacted by their assigned IP address.

4 minutes ago, larryllix said:

Network devices do not communicate by URL names. A DNS server has to be contacted first, which then supplies an IP address for same, or passes the request up to the next DNS server, usually google or similar, to be used by network devices. Then network and Internet devices use IP addresses for communications.

LAN devices do shout out keepalive signals occasionally, to keep the router aware they are there but no URL names are used. Only IP addresses are used at this point in connection time.

LAN devices contact a DHCP server with their MAC address of the hardware and receive an IP address from it, so they can be contacted by their assigned IP address.

My explanation might have been an over implication. From Wikipedia:

Multicast DNS (mDNS) is a computer networking protocol that resolves hostnames to IP addresses within small networks that do not include a local name server. t is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name System (DNS). It was designed to work as either a stand-alone protocol or compatible with standard DNS servers.

When an mDNS client needs to resolve a hostname, it sends an IP multicast query message that asks the host having that name to identify itself. That target machine then multicasts a message that includes its IP address. All machines in that subnet can then use that information to update their mDNS caches.

13 minutes ago, DennisC said:

My explanation might have been an over implication. From Wikipedia:

Multicast DNS (mDNS) is a computer networking protocol that resolves hostnames to IP addresses within small networks that do not include a local name server. t is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name System (DNS). It was designed to work as either a stand-alone protocol or compatible with standard DNS servers.

When an mDNS client needs to resolve a hostname, it sends an IP multicast query message that asks the host having that name to identify itself. That target machine then multicasts a message that includes its IP address. All machines in that subnet can then use that information to update their mDNS caches.

Thanks for that info. I guess I have never had one.

On that same note: I had to upgrade my java again and now have no IoX finder again. None of my links work anymore as they appear to have all changed again..

I can only download the start.jnlp app now.

However java apps cannot be installed on the Windows Taskbar. ☹️

Here we go again.

Edited 13 hours ago13 hr by larryllix

I always "save" the list of controllers in IoX finder. Then whenever a java update or whatever causes something to go missing, I reload the IoX file I saved earlier, and I'm back in business. I also list the controllers by IP address, not by name.

Also (in regards to the discussion above about multicast DNS), what happens if you have two or more eisys on your network? They can't both be eisy.local.

1 hour ago, larryllix said:

Thanks for that info. I guess I have never had one.

On that same note: I had to upgrade my java again and now have no IoX finder again. None of my links work anymore as they appear to have all changed again..

I can only download the start.jnlp app now.

However java apps cannot be installed on the Windows Taskbar. ☹️

Here we go again.

Out of an abondance or curiosity, does https://eisy.local open eisy UI? Note: If you previously used port :3000, make sure it is NOT at the end of https://eisy.local before hitting enter. Sometimes browser cache comes in to play and you do not want to start eisy UI using port 3000.

2 minutes ago, DennisC said:

...and you do not want to start eisy UI using port 3000.

Because that will open polyglot instead... 😄

2 hours ago, Guy Lavoie said:

Because that will open polyglot instead... 😄

UD is moving to single sign on solution across all of their platforms. That's why we are seeing logins with portal credentials.

Using port 3000 is a local login. When eisy.local, UD Mobile, or pg3 is signed in with a local account, certain plugins stop (because they are using portal credentials) and then restart ( so they are visible with local credentials).

I don't recall the list of plugins this impacts off hand, but I know one of them is Elk.

There have been several posts in the forum from members complaining about plugins stopping and restarting.

3 hours ago, DennisC said:

Out of an abondance or curiosity, does https://eisy.local open eisy UI? Note: If you previously used port :3000, make sure it is NOT at the end of https://eisy.local before hitting enter. Sometimes browser cache comes in to play and you do not want to start eisy UI using port 3000.

No. eisy.local results in a Not Found error in the browser.

My bookmark https://my.isy.io/index.htm works fine for ISY Portal though. That would be an assumed port 443 then.

My bookmark http://192.168.0.165:3000/dashboard works OK for PG3x also.

Edited 8 hours ago8 hr by larryllix

22 hours ago, j.rieff said:

Is there a Users Manual for the new UI?

UD has been updating the wiki here and there with eisy ui information:

https://wiki.universal-devices.com/Eisy:User_Guide#eisy-ui

It's very much a work in progress. I have a few folders and find the main list very lack luster and difficult to migrate. It had a period of time that folders would automatically expand and they don't seem to keep their memory from one use to another. Because it's not very useful (to me) I haven't used it very much up to this point.