smokegrub

i have two ISYs. The vacation home ISY has worked perfectly until my ISP changed from Suddenlink to Optimum. After they did this I began attempts to do an ISY backup in preparation to upgrade from 4.9.0. When I tried to backup it would get to about 70% and it would fail with the message could not retrieve File .Conf/109 PRP. Now, I am at the vacation home and the ISY will not backup—same results. I can see both ISYs in the Portal but the vacation home ISY will not backup.. When I open with the Launcher the Vacation home ISY displays but the ISY at the other residence does not! To top things off, my wife and I just got Covid and at age 78 I am not at my former skill level. I have rebooted the ISY and I have unplugged and replugged the PLM. The PLM has a sold green light. The ISY has a single solid blue light on the far left. I can control the vacation home devices though the Portal and MobiLinc. I don’t see the vacation ISY’s IP in the router (Apple Extreme). At least I don’t recognize one. It appears the ISY is identified by its MAC Address in setup. How can I determine its IP so I can see if its address is in the router? If its not there, how do I get it there? My gut feeling is that the ISY is not in the router. Sorry for the serious paucity of technical skills. Any help will be appreciated.All my devices are Insteon. I am running Ventura on a MacBook Pro. I am ready to upgrade the ISY technology if that is my problem.

I have the same pending issue except mine is further complicated with two ISY's at separate locations, both of which continue to function perfectly with all Insteon systems and 4.9. My systems are on the same Portal. One is at my primary residence; the other is located 325 miles from the primary residence. I envision no new devices other than Insteon. I have enough devices in reserve to last a long time. Past experience reminds me that this arrangement creates unique requirements when upgrading. The cost of the upgrade is inconsequential, but the technical challenges are surely going to be insignificant. Do I even need to do anything at this time? If I do, I am going to need substantial "hand-holding". I will soon be 78 years young and my old brain is slowing.

FYI everything is accessible through the Portal. Just not thro9ugh the Launcher.

The Launcher opens but no data are displayed for either of two ISYs. Thoughts?

Mine is down also.

Same here.

If anyone is looking for an ironclad longterm solution, forget it. What you invest in today may soon be obsolete. As for me, I will stick with my Insteon system until the final door closes. I also have several backup devices including a couple of PLMs so I should be good to go for a while.

Thanks sir, will do.

Thanks, I thought the answer was no as well but I wanted to first check with those more knowledgeable than me.

I have a home located remotely from my primary residence. The CAO warning of consequences for low CAO tag batteries has caused me concern. I will not return to the remote residence for 8 months because of health (surgery) and weather. The tags are used to monitor motion and temperature at entries. Insteon Hidden Door Sensors also monitor entries. Ideally, I would like to monitor the the entries with the Hidden Door Sensors until their batteries fail then use the tags. Can the tags be set for a minimal battery requirement (a sort of standby mode) and then remotely be brought to full motion monitoring status? The objective being being able to monitor entries for 8 months.

You may wish to use an X-10 Appliance Module. I use them often and they work beautifully and are inexpensive.

There are several 2450 modules being offered on Ebay.

Don't know how or why but the problem resolved itself! Don't care! Thanks for your efforts trying to help me.

Start.jnlp was a part of the download from UDI. Historically, as I recall, only the Launcher appeared on the desktop. Now, both the Launcher and start.jnlp appear. Double-clicking the Launcher produces the error message. Double-clicking start.jnlp launches the admin console. Both ISY's are on 4.9.

A couple of days ago I updated JAVA to Update 311. Thereafter, access to a remote ISY using The Launcher has slowed to a crawl. I am using the following: MacBook Pro 2019 Mac 10.14.6 Mojave Memory: 16 GB Firmware: 4.9.0 UI: 4.9.0 Before proceeding further permit me to note that long before my current problem developed the Launcher stopped working in its traditional manner saying, “You can’t use this version of the application “ISY Launcher with this version of macOS. You have macOS 10.14.6. The application requires macOS 10.15 or later.” That problem was addressed by placing the “start.jnlp” icon on the desktop and using it to start ISY. Since updating JAVA I can still access the remote ISY using this method but things have showed to a crawl. I recently was at the remote location and accessing the “home” location presented the same problem. MobiLinc Pro accesses both sites without problem. I have rebooted the Mac a few times. I have deleted and reinstalled the JAVA update. I have checked the Mac with Malwarebytes. The problem remains. I must continue using Mojave at this time since I have a very important app that will not run with an OS update. Suggestions?

Mine was greater than 100° F today and probably is near 120° during out hottest days. Thus, I see no problem with temperature. Using the tags and Wyze cameras has been very helpful. I did, however, use an Insteon device to power each camera so I can reboot them remotely.

Larry, I didn't know that.

Thank you.

My email account is changing. Does anyone know how I can change the login for my CAO account?

Fortunately, this is the only time I have experienced this failure. Given the distance to this residence from my primary the fact that it occurred alarms me a bit. However, re-entering the serial number of the tag manager should work from any location, if needed. I hope! Thanks again!

My thanks. I re-entered the serial number of the tag manager as if I were installing a new one and the tag manager and tags reappeared in the app! All is well!

In my long ramble I forgot to add that is my messing around in the app I got the message that my tag manager was not connected to the internet.

I have two tag managers located in homes approximately 325 miles apart and with two separate ISPs. Both tag managers have worked flawlessly until recently when the ISP at one location had problems and sent an email of apology stating that users would probably need to power down and restart some devices. It was during that timeframe that the tag manager at that location stopped displaying its tags in the app. I have since travelled to that location and done everything I know how to do (powered down the router and tag manager, rebooted the router, disconnected the tag manager from the router and reconnected the tag manager). The lights on the tag manager all appear normal but the tags do not appear in the app. I am considering re-adding the tag manager to the app but before doing so I thought it wise to seek your sage advice. It appears that a logical next step would be Settings>Account>Add a New Tag Manager>Useful when replacing a defective tag manager with a new one, without having to re-associate each tag. The subject tag manager is not new but I am assuming the app would treat it as new. Thoughts?

Duh! I solved my problem. Three of the scenes were in the scenes category. The others were in the devices category. They were there all along. Forgive me for wasting your time.

It has been a long time since I have done work in the portal. Yesterday, I made several changes including creating spokens for fan speeds. These changes do not appear in Alex (Mac or IOS). I have tried forgetting all devices and discovering them in Alexa. I have tried deleting and installing the skill (Smarthome V3). All I ever get is what was disoverable previously. None of the changes show up. I know the method I used to set up the fan speed scenes was correct because one that I had done a long time ago displays in Alexa and its spoken works. I am probably missing some minor issue and that is why I am requesting help.