nowandthen

My frustration is showing. The UDI team is so used to their programming, that they don't understand that someone completely new does not have their level of programming, and system functions. Please work on the setup interface so it is more user friendly. Thanks for listening to my gripes. I hope I am now on my way to re-setting up an eISY/Insteon system.

How do I disable the portal? Looking for desktop app.

There seems to be a delay with every step off the install. After typing the above, I hit a button on the app, don't recall exactly what it offered, but it retried and found the device. Perhaps a message that you may need to wait 1-2 minutes then retry each step. My internet is not slow. Next gripe: "Do you want to enable the 30 day ISY portal free trial?" I do not but the only option is to "Start Trial". ??? Now it's configuring remote access which I do not want. I do not want devices going out on the internet on their own. UGGGHHH! Dang!

Setting up a new eisy. Had isy994 at old house left it behind. Had UD mobile. I deleted and re-downloaded the app. Plugged eisy into my router via network cable. eisy shows up in my router. Set fixed IP, not that it matters. Router rebooted. I unplugged the eisy and plugged it back in. App wants to know what device I have. I selected eisy. App wants to know "How will your system connect to the internet?" I selected Wired. App says ( my wording) connect Ethernet cable, power on system, then scan the QR code on the bottom of the eisy. When I press Scan, it almost immediately returns to what system do you have. By the time I typed this, the QR scan held and I scanned the QR code. Now it's "Looking for Systems". It timed out, wants me to close the window and try again. UGGGHHH!!! Now it wants credentials, Local IP address I get. Local port, I do not. This system will never be main stream when it takes a computer Whizz to set it up. I understand some of this stuff but why is this so hard? Why do I have to come here for help getting this up and running? Please help!

Thanks. I'll just get what UD recommends (post 2 above). I don't care about the looks. It's hidden away. I just thought if the cable I referenced eliminated the the adapter, then I would go that route.

Instead of the serial to USB cable and the separate adapter, can I use something like this instead? https://www.amazon.com/OIKWAN-Compatible-Opengear-Aruba，Juniper-Switches/dp/B075V1RGQK/ref=sr_1_2?keywords=rj45%2Bto%2Busb%2Bcable&qid=1681486226&sr=8-2&th=1 TIA

This applies to scenes. For a single device, the brightness displays correctly. I read another thread about excluding other devices to improve brightness calculation. I didn't quite understand what was being said. That thread mentioned a little calculator beside each device in the scene (I'm blind and dense at times). For others, click on your scene name (node). All nodes (to me, devices, device buttons) in the scene are listed. To the right of each node is a little calculator icon. Turn off the nodes that you don't want calculated in the brightness. In my scene, I have 1 light switch, and 3 KPL buttons. The light is at 59% but the percent shown on the button on my favorites screen showed 40%. To correctly show the brightness, I set the 3 KPL buttons to ignore, now only the switch is calculated and it reports correctly. What is the point of Estimated Status? Why would I want to see that? Also, why is it off by 1% at times, even when only one device is used to calculate? These things can drive me nuts. Sorry. Thanks. And thanks for this App. It's much more responsive than the app I was using.

I'll give it a try. Thanks!

I thought noise too. I almost always use my modified extension cord with one end cut off when I add new devices or replace devices. I did that in these cases. I pigtail to the new device with wire nuts to the extension cord. This allows me to plug it in near my computer. This way I can get it all set up before I commit to it's final location. For the first KPL, I even tried plugging it in to the same receptacle as the PLM. Still had problems. But as I later discovered (and had I know it at the time I did the first KPL), sending a command to the device from within the Admin Console seems to "wake it up", exclamation points become green 1's. Then I write updates to device and all is well. Maybe it is noise issues but I have nothing better to try than the same receptacle as the PLM. I wish we had an Insteon noise detecting tool like we had with X10.

Thanks for all the feedback. I ended up manually setting up the new KPL. Dang I've had several devices die lately. They’ve been installed for years. I replaced a lamplinc, and a Swithclinc. Both gave me some problems in that they replaced, but showed exclamation points after restarting the ISY Admin console. I stumbled upon the "cure", at least for me. Every device I’ve replaced this weekend, have, once having replaced the old device, shown up in the ISY with exclamation points. I found if I click on the device and click On or Off at the bottom of the ISY window, it seems to wake the device up and it then shows the green 1’s instead of exclamation points. Then I select write updates to device and it then updates the device. I occasionally get a can’t communicate with device but it seems to continue updating. The second KPL I changed out did take all the updates from the ISY, but I had to kick start it as well. Thank goodness because that KPL was more complicated than the one above, that I manually updated.

Is there some way that I can see the programming of the old device so I can manually program the new device? The KPL programming of this device is a bit complex.

Sorry for not being clear. I did pullout the air gap for at least 10 seconds, then held it in until the beeping stopped.

I think you are right. When I look at the device details, the bold address is correct for the new device, but below it in a smaller font is the old KPL address and 2486D. So I must be doing it backwards. Makes sense. But still having problems. I reset the new KPL by holding down the set button. I restored the ISY from back up (prior to adding new KPL). added the new KPL. Shows up almost instantly and I can control it from the admin console. Performed Replace with new device. This time selecting old KPL then picking new KPL. It partially updated removing .B and .C but .1 and .D were still there. So I repeated replace with. Now the new device does not show up at all and the old device is back to all "!".

My old KPL is labeled on the device as a 2486D (sticker on device is 2486DIV6). New KPL is 2334-232 (as labeled on the box) , on the device itself, it is labeled 2334-2. ISY shows the new device as a 2486D (once I added it). I backed up the ISY first. Thank goodness! I added the new KPL using Linc Management, Start Linking. Pressed and held the reset button on the new KPL until it beeped. ISY sees it immediately. Clicked finish. New KPL shows up in the root directory of the tree. After several failed attempts at replace, I decided to test the new KPL to see if the ISY would control it, so I clicked "On", the top button lite up, then "Off", the bottom button lite up. So I know it's good at this point. I moved the old (dead) KPL to the root directory (same as the new KPL). Right clicked on the ".1" of the new KPL and selected replace with. Selected the old KPL. ISY does its thing and eventually closes. When I open the ISY Administration panel. The new KPL has "!" by every button (.1, .A, .B, .C, .D). It will not respond anymore, can't turn it on and off like I could before "replace with". I restored the ISY and tried again several times to no avail. (Once the old device is gone, it appears that replace with will not work, as the old device is gone. Glad I backed up before beginning). What am I doing wrong?

I found the problem. HTTPS port in Mobilinc was at 444, but ISY wants 445. I don't recall touching this, at least not in the months past. The HTTP matched at port 80. Maybe this is due to iOS 9 requiring secure communication? HTTPS instead of HTTP? I'm so glad it is working again. Hate the thought of setting up something new.

Thanks everyone. I'm on iOS. I'll head over to the Mobilinc forum. I hate to change. It has worked for the most part but lately has been failing to communicate with the ISY.

Lately this app has given me problems. I went to their website where they say I must be running ISY 4.2.30 or latter and have the TSL set to 1.0 or later. I am running 4.3.26 and TLS 1.2. But it will not work. Worked yesterday but not today. Frustrated! Nothing has changed since yesterday. Any help is much appreciated. Someone needs to make an app that just works.

Update 2: I figured it out. Some time ago I was playing around with remote access, which I don't use, but a friend was having problems so we tested a few things. But a friend was having trouble. I set port forwarding on my router such that the ISY was port 81 instead of 80 and 444 instead of 445. I could access the ISY from outside my LAN using the new port settings, but for some reason Roomie didn't like this and wanted port 80. So all is well at port 80. Perhaps this will help someone else down the road.

Update, in case anyone cares. The device I was using to control the ISY was "Insteon Automation", in fine print it also said ISY-99i. At some point Roomie must have neutered this device. Roomie told me to use "Universal Devices", in fine print ISY-994i. Now all the commands are back. THe command are being sent, but they are red which means there are not getting through to the ISY. More investigating...

I have contacted Roomie, but the reply wasn't on point. I will respond to that email and keep my fingers crossed, but I don't think they have much experience with the ISY. My Various activities have Insteon buttons in the remote screens. However the Roomie is not sending out any Insteon commands from the previously working buttons (worked in January of this year). It’s as if the “Program run then” command has been removed from Roomie. Almost all of my Roomie Remote buttons execute the Insteon “Program run then” command. I tried to add a test button, but the only commands available are for various “Light” and “Scene” control (e.g.Light on, Light dim, Scene on, scene off etc). I cannot find the "Program run then" option any more. Did Roomie remove this? Roomie does not send out any commands that have the “Program run then” command. I know about the program IDs, and they are correct. Like I said, they used to work, now Roomie seems to no longer understand the Program command. I have a couple of button sliders that command individual insteon switches. Rommie does send the command (I can see it at the top of the screen). But nothing happens. These too used to work. The buttons use the switch ID (the 6 digit hex code). If I can find the “Program run then” command I can start trouble shooting why none of the lights respond, but at this point Roomie seems to no longer understand ‘Program run then”. Anyone out there use Roomie Remote? It's always been tricky setting up, at least for me, but once set, it's a good remote. I see the UD wiki has info on i-rule but I didn't find anything on Roomie Remote.

Thanks Lee, That does make sense. I have done it backwards in the past with success. Dumb luck maybe. Next time I will click on the dead/gone device and use replace with. Luckily my friend has not reprogrammed the modules we traded so I can get them back temporarily and hopefully get things squared away..

Hi Stu, Sorry, I failed to mention that I did add the new devices. I added one first. The device showed up in the top level of the tree, with Insteon address. I clicked on it and selected replace with. When I realized the problem I added the second new device, but obviously that does nothing as each device is now looking for a device that is no longer there. The problem is I changed out 2 devices in the same group (they were linked together). But the second replaced device obviously has a new Insteon address. Now the first one is trying to find the original 2nd device but it is no longer there. I can't "replace with" on the second device because it can't find the original first device (it too was replaced at the same time). I have 2 replaced devices linked together but they can resolve themselves because each is looking for the other original, which is no longer there. Put simply, I hope, how does one change 2 devices that fail at the same time that were linked together? Hope this makes sense.

A friend needed older lamplincs as he still uses some x-10. Newer lamplincs do not support X-10. So I swapped him for 2 of my older, slightly used lamplincs. I thought, oh this is easy, I've replaced with before. WRONG! I plugged in the first new module and used replace with. All linked devices are updated except for the other "new" one in the group. Obviously (now, duh) the device it is trying to "replace with" is no longer there. Likewise for the other new lamplinc. Now both have an exclamation point next to them. And cannot resolve the links. Any way to resolve this? Should I go get one of them back and plug it back in to resolve this? He hasn't used them yet. For the sake of a situation where 2 in a group die (surge, etc), what is the solution to this kind of situation? Is there a way to "replace with" when 2 or more in a group die? Any tips are greatly appreciated.

I've had KPLs for years, and never realized until now, that if I press and hold the button (.1 button (load) not sure about .b .c etc) that the switch now retains that level the next time I turn it on. I don't want that. My preference is if I manually brighten or dim for some reason, the next time I turn the light on I want it to go back to the level set in the ISY, but it goes back to the last local level setting. Is there a way to disable this? I did not see it in the user manual. I have 2486D's which seem to be superseded by 2334-222.

Got it! I set button H to Non-Toggle [Off] mode, I didn't realize what it was asking when I went to set it to non-toggle mode. So with the button in Non-Toggle [Off] mode, I also had to change the lamp level to 100% (previously I had it at 0% and even in Non-toggle[Off] it would not dim.) Works great! Thanks Lee! You are amazing!