stillwater

@DennisC Thanks, yes I had thought of that but hadn't gotten around to doing it.

THanks. I got it to work with the eisy. (The eisy is sitting on my network with isy"restored" from 994i backup but not yet connected to the plm or actually doing anything.) @DennisC It's because I have parts of the house I may not have been in and for example guests have left. And it's not all lights, there are other devices also. It's not a feature I use every day but it's nice to have. Thanks for your helpful suggestions, though.

@Geddy Thanks for the clarification about Mobilinc App vs Mobilinc Connect. I have the 4.17 version of the Mobilinc App also. I suspect I am still using Mobilinc Connect to connect to the ISY 994i. The Error logs contain lots of Mobilinc traffic that I assume wouldn't be there if I was going through the portal. I think i had an ISY at another house signed up for the portal but not this one. I think I didn't realize I could use the Mobilinc App through the Portal. I'll try to find the documentation for that. Thanks again this is a big help.

Yes! Sorry I meant to post that. All that was needed was to install the eisyui package. Michel was on it immediately even though I said it was not at all urgent. Typical of UDI support!

Thanks. I've looked at the wiki on UD Mobile and then clarified on the App that I can do the following that are important to me: Change variable values (wiki said you can't edit variables but maybe that means their names) Run program if and then Enable and DIsable programs There does not seem to be an option to source the device list by current status. I have something like 70 or 80 devices so it is a long list and helps to be able to sort by on/off to see what is on. In Mobilinc HD at the top of the device list there are buttons to sort A-Z, Z-A, On-Off, and Off-On. It would be great if this or something similar could be implemented in UD Mobile.

Thanks! I didn't see how to sort the list of devices by those are currently on, which I can do in Mobilinc. This helps in making sure that stray lights aren't on when I am not home. I hope that this can be added in the future if it isn't possible now.

The first line in the eisy migration wiki says that Mobilinc Connect is not supported on EISY. I assume this means my Mobilinc HD app will not work. What, if anything will I lose in moving from Mobilinc HD to UD Mobile? What will I gain in addition to EISY compatibility? On Mobilinc, I like that I can order devices by ON/OFF status so I can easily turn off lights that shouldn't be on. Is this possibie in UD Mobile? I assume one can see and change variables in UD Mobile, and that UD Mobile will work remotely even though I have Starlink (CGNAT). It would be nice to be able to edit programs on UD Mobile (can't do this on Mobilinc, though one can enable and disable programs and run program then statements, which I make frequent use of) Anything I should be aware of before transitioning? (I can hold on to the 994i for some time while waiting for UD Mobile to make further strides). Thanks in advance....

The wiki https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration says "All Network Resources will be migrated seamlessly, however, you will need to open and save each one individually." Is it still true that I will have to open and save each network resource or has this been improved in the latest version? Also I just noticed that Mobilinc Connect is not supported on eisy, so I will have to learn the ins and outs of UD Mobile before transitioning.

Just for the record it appears that the eisyui package was not installed on my eisy. This explains why I was able to access the PG3 dashboard but not the eisy-ui. I now realize that eisy-ui is new and that what I am vaguely remembering from when I first got the eisy (or maybe polisy before it) was that there was a system dashboard that was separate from the polyglot dashboard. I'm not sure what I would have used that for but that's what i thought I would find in addition to the new eisy-ui, which is sort of a preliminary version of a replacement for the java admin console. I'll go look for more documentation but in the meantime I can use eisy exactly as i used the isy994i.

Renaming the launcher and finder temp files to .statx (equivalent to deleting them) did indeed cause finder to show the 2nd root name (what was ISY) in the finder. Also seems to have fixed the problem about the configuration settings being reset on reboot. (this seems odd but I'll take the win)

I have submitted a ticket. Michel asked me to boot and send him a shot of the end of the boot sequence. There were two warnings about /var/polyglot/.cache/pip or its parent not being writable and serial package not found. Then there was no /var/udx/.udx_install_cleanup Then "isy service failed since no process with id 3637 exists" But for the record, no vlans, vpns, firewall, or antivirus. I tried Chrome on Mac, Chrome on PC, Safari on Mac, and Edge on PC. I do have malware bytes on the PC but I don't think it does anything -- realtime protection is "inactive." I cleared java cache and started finder and it still lists the eisy NAME as ISY. even though I had renamed the root names (NETWORK and ISY) . I will search for ud*.state file(s) The PC is windows 11 and the Mac is Tahoe 26.2/. I can't imagine why browser would allow access to the PG3 dashboard (eisy.local:3000 .... ) and not the normal http or https ports.

If I wasn't clear, the response to https//eisy.lcoal/ is ERR_CONNECTION_REFUSED

Thanks! @Geddy you have explained why the Finder designation of my EISY changed from IoX to ISY -- it's because the "restored" IoX top node is named ISY. Except I changed the name and it's still ISY in finder... I tried accessing the sysconfig.txt file and the eisy either refused to connect or did not provide any data,. Then I power cycled EISY. Still no luck with eisy.local. The finder finds it but now with no type or version listed. EISY still at version 6.04. Upgraded Packages again. After a very short time it said packages upgraded successfully. I did not "Install Dev. Packages" at this point or previously. I power cycled the eisy again. I also rebooted the PC, mostly because I hadn't done that in a while. EISY still at 6.04. Otherwise no change. If it matters, the EISY is not connected to a PLM. FYI I did not execute any "random commands" via SSH. Also after each reboot the settings in configuration change -- Insteon support is turned off. Matter is turned on, and Zigbee and Zwave are set to auto (I had saved them as OFF). There is also a new box that says Migrate to Zmatter Zwave that I can't get rid of -- I don't want Zwave, Zmatter or any other Zs. I will set up a ticket. (But I'm tempted to just keep the 994i and wait another year)

Thanks but I can get to the admin console using java the old fashioned way using the launcher. I wanted to look at the new eisy.ui. The instructions say to use point a browser to eisy.local or to the IP adress of the EISY. This doesn't work. ALso http:eisy.local:8080/desc (referred to in the pinned post at the top of the forum) just gives a page of xml

I've had an ISY-994 forever and bought an EISY some years ago to replace it but never did, though I did access the UI once or twice and upgraded the software on occasion. I finally started the process yesterday but forgot about the eisy web ui. First I "restored" the backup I created on the ISY-994i (from the admin console). Then i noticed that new packages were available so I upgraded from the admin console . I think the eisy had been on 5.9.0 or maybe 5.9.1. 16 hours later I couldn't access the eisy.ui either by eisy.local or [ip] IOX finder did not find it. (it did before the upgrade) I attached to the EISY via SSH-- according to ps -aux, no named processes taking any CPU time. I rebooted eisy and -- same result (after a short period where there were some processes doing things) I referred to this document https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide and was able to add the eisy to the finder -- it shows up as ISY rather than IoX though, -- type eisy and version 6.0.4, so that's progress. SSH works. Admin console is accessible. But I can't access eisy ui by any of the suggested methods (from the same wired LAN) I have a Unifi edgerouterX but can't imagine it's a firewall issue. I tried to connect to eisy ui with both a windows 11 machine and a mac. Firewall was off on the Windows machine. From the finder I found I could load the polyglot 3x dashboard (eisy.local:3000/dashboard). This connected to the portal and authenticated. After doing that I got different responses from Chrome on the PC -- eisy.local didn't send any data or refused to connect rather than not being found. Is there a page name I should use (like eisy.local:80/ui ? There is something I am missing! Is there some setting in the admin console or that i can access by SSH to turn on EISY-UI? Should I do a factory reset on the EISY and start over??

USR-N5x0 series -- ( USR-N510 has one port and 8 ports on the USR-N580) affords ethernet TCP/IP to RS-485 or Modbus conversion. Can use ISY/IOX network resources to send TCP/IP to the USR-N5xx. I have used the USR-N580 but not with ISY/IoX

THanks!

I've been away from any change to my Insteon system for years. Ten years ago I walked unawares into the limit on links in the PLM. Is it still true that all of the PLMs and Insteon Hubs have the 992 link limit? Thanks!

Is your Query ALL (typically 3am) program enabled? (This used to be pre-installed on the ISY). This is designed to set all the insteon devices to conform to what is in the ISY, but I've seen cases where all the insteon traffic associated with this Query can cause devices to change states to those not intended -- especially if the PLM is marginal. You may be able to see in the event log what time the switch happened and see if that corresponds to when the Query All program ran (if it's enabled).

If I understand your question, the ISY REST interface is the answer. https://wiki.universal-devices.com/index.php?title=ISY_Developers:API:REST_Interface It's worked well for me. I am a little rusty but I think you can turn scenes and devices on and off directly. You can also set integer and state variables. Changing a state variable can trigger programs. So you can do pretty much anything with it. Others may also be able to point you to better documentation or best practices.

Yes the LED indicators can be turned off in the ISY Admin Console.

I have not been a fan of what Insteon's previous managements did with the product line. So I feel like I should say something nice about Insteon when I have the chance. Some years ago I bought a couple of 2663 outlets because I thought separately controlled outlets might come in handy. Today I installed one in a temporary application and was pleasantly surprised by the look and feel -- unobtrusive control buttons, tamper resistance (i hadn't focussed on this when I bought it) and of course it just works with ISY. I haven't explored whether it's possible to turn off the LED indicators (as it is with the wall dimmers -- a very useful feature for young guests who are extremely light sensitive at night)

Too bad there's no confidence about PLM pro future. I have several PLMs I would sell on Ebay to people who need them if I were confident that the PLM pro would be available in a reasonable period of time. Insteon leadership should realize that there is benefit to them from releasing the hoarded PLMs that I and others have and firm up their plans and public commitment to the PLM pro.

Good point. This is one reason my Sonos system operates solely over ethernet cable. But that isn't easy for every installation.

There are a variety of a situations where the Insteon powerline transmission makes things easy that are harder with various RF only systems including wifi, For example: 1) something in a faraday cage (metal cabinet) that has power inside 2) something at a chicken coop or gate or other installation that has power from the same transformer but not any other need for wifi Finally with 2.4 GHZ wifi, no matter how spiffy your own installation, you can still have issues in dense urban areas (apartments or townhouses) owing to channel congestion and poor channel decisions out of the control of a particular user. While there may be solutions to these issues with some forethought, with Insteon it's just a matter of plugging something in. (Well assuming no interference which can be its own hell). I am not advocating one vs. the other, just saying that there are reasons why wifi might not be the best in a particular situation.