15 hours ago15 hr 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?
15 hours ago15 hr 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 15 hours ago15 hr by hart2hart
2 hours ago2 hr 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.
1 hour ago1 hr 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.
44 minutes ago44 min 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
40 minutes ago40 min 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.ThanksOf 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.
15 minutes ago15 min 20 minutes ago, larryllix said:ThanksOf 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.
Create an account or sign in to comment