lhranch

Last night I tried the admin console's own instructions first, and they failed entirely. Then I tried the instructions with the 10-second push. I was a bit disturbed when the switch's load didn't cycle, but when I returned to the console there was a window saying it had seen that device raise its hand and would configure it as soon as I clicked Finish. It completed successfully. If I can remember how, I should lodge a bug against the faulty instructions in the console itself. Thanks for the help.

In a (now closed) thread called "Unknown Address," the OP is referred to the page https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Adding_a_Device#Adding_by_Linking_Method for the proper procedure to add a device whose address label is unreadable or obscured. Unfortunately, this page provides conflicting information. The text says to choose one of the three linking options, then press the set button on the device for 10 seconds until the load blinks, then return and click Finish. The image (and the instructions you actually get from the Admin Console) says to press the set button for 3-5 seconds first, then return and choose one of the three linking options, then click Finish. One or the other of these ought to be corrected. Which one is correct?

I'm not sure whether this is an eisy feature or an Insteon native feature, but I'll try here first. I have a 2477D Dual Band dimmer. It's in a remote location where it almost always responds well... but not always, due to distance, or noise interference, or some other reason. I have a periodic program that queries (via a scene) a half dozen of these very remote devices (other buildings, outdoor installations) and then sends me a notification if any of them are not responding (indicating that there's likely a GFCI breaker needing to be reset so other equipment in that location has power). It works very reliably except for devices at this one location, which fail to respond maybe one out of 10-20 times. Now, the question: While tooling around inside the Admin Console, I have occasionally come across a setting that allows me to increase the retries for failed attempts. I'd like to increase it in this case. But I don't remember exactly where it is or how to get there. When I go looking for it, both on the device screen and on the scene's screen, I can't call it up. Can someone tell me if there is a way to do what I want to do here, and how to access it? Thanks.

I've been aware for quite some time of the "Set Userid/Password" menu in the Admin Console, but never did anything with it. I currently have a long-term tenant in a "vacation rental" residence on my property. It has a number of Insteon devices in it, most notably the thermostat. He was away for several days during which time we had a power failure, and came back to find his home at 103° (for some reason, the thermostat came back up Off). I got the idea that perhaps I could register a non-admin account on the eisy, and give him shared remote control over the units in his residence via a simple smartphone app like UD Mobile or MobiLinc Pro. I tried setting a name and password for User1, and it seemed to be accepted, but nothing ever actually changed. I went looking for how the multiple user feature worked, and found nothing. One posting indicated that whatever plans there were for this feature dead-ended when some other package or protocol was developed. So, rather than trying to reinvent the wheel from first principles, is there anyway to achieve the goal of what I want to do?

Dunno what to tell you. I posted the entire contents of that directory in transaction 3. It's there for anybody to see. Again, maybe it has something to do with me not using the portal services, I really don't know.

The tech at UD identified the relevant file as /var/isy/FILES/CONF/0.UCF . It's binary, so changing it isn't trivial, but it's a very short file and it's doable. I have my secure eisy port set to the value I want now. Thanks, all.

Perhaps it is significant that I do NOT use the portal facility at all? My operation and administration are completely local.

I opened one last night. UDI seems less than eager to accommodate. "...this is not "seemingly arbitrary restriction". This was done in order to reduce our support issues."

So did I, you will notice I am operating from root. I also tried precisely the syntax you used from admin, but it didn't change my results.

OK, well, I have no response to this. My machine clearly doesn't have this file, I'm not imagining it. Perhaps you have some add-on that I don't -- mine is straight factory configuration.

Ooh! I was totally up for this! However: Any suggestions?

Yes, that's just a low-level interface difference between Windows and Mac. MacOS provides a "disclosure triangle."

Yup, dialog box, popup, potato, potahto. October 2023 also sounds like about the same time frame I roached my launcher and had to download a new copy. The images in 42176 are exactly what I was seeing.

In General / Temporary Internet Files / View, I deleted everything under Applications, Resources, and Deleted Applications. Then in Settings, I punched the Delete Files button, clicked all three boxes, and hit OK. Then I launched my copy of start.jnlp, and got the same error. I finally got rid of the message by doing all of the above over again, then deleting my copy of start.jnlp, re-downloading it, and then launching it. Thanks for putting me on the right track.

Every time I start up ISY Launch, the IoX finder scans my network for ISYs, finds them, then puts up a dialog box saying "Error, not found." I think this is because at one point no ISYs were coming up for some reason, so I typed in the DNS name of the ISY and managed to type it in wrong. Now it looks for that bad name every time it comes up. There's no way to remove an ISY entry that never comes up. I haven't been able to figure out where the names are stored so that I could patch it out, and clearing the Java cache doesn't do the trick. Does anybody know how I can remove that bad name from the list of ISYs the finder scans for every time it starts?