oberkc

How critical is the 30-day interval? How about 28 days? 31 days? If not overly critical, why not simply charge it on the first day of each month, using the system variables for day?

I must admit that I have never noticed this either. I tapped one of my dimmers and it came to the local ON level, as expected and which was reflected in the admin console. I tapped it again and it went to 100% as expected, but this was NOT reflected in the admin console. I also get the same results as you if I dim things manually. I don't know whether this is by design or whether we are both experiencing comm problems.

What is the "garage system"? Is it insteon garage door kit using the IOLinc?

I have now updated my ISY-994 software to 5.3.2. Update appeared to go without problems. Unfortunately, the one z-wave switch that I use as a test case (yet unsure about the other z-wave switches in my house) stopped updating. I excluded it, and added it back, and it is now back in working order. Good news: I can now add the "custom button press" node and can use that node in a program "control" condition. Before, I could not do this. Disappointing news: KPL buttons that are responders in a scene do not respond to this z-wave switch in the same scene, as a controller.

I continue to find little problems with the Mac computer OS. I mostly have found workarounds, but sometimes that takes a bit of research and I usually find it frustrating. I am undecided whether to continue to use a Mac when it comes time to replace my current machine.

Yes, as should be yours, I understand.

Unfortunately, I use MacOS and hovering over the link does not yield any file name. When I download the file using the provided link, I get a folder, with three sub-folders, and numerous folders below that, but no file anywhere that I can find that ended in 5.3.2.zip. There is only one .zip file, and it is named DEF.zip. Update: I downloaded the file using a different browser (firefox, in this case) and get a folder named 5.3.2.zip. This did not happen with Safari. Interesting.

While I have upgraded to numerous versions over the years, it is suddenly unclear to me which file is the one to choose. Is it the "DEF.zip"? Has something changed in the naming convention? I thought they used to be called "insteon_X.X.X.zip" or something similar.

I just checked mine, to be sure. In a program, I can... add action Your Devices Pick a scene Drop-down list of a variety of options Is this not available to you? (unfortunately, I am only on v5.2 but I was hoping it is the same for 5.3)

As far as I remember, it has never been possible to set any "value" of a scene, other than ON or OFF.

Just to be sure...does your ISY show the PLM as "connected"? (TOOLS>>>DIAGNOSIS>>>PLM INFO/STATUS)

Well...the steps I suggested will replace one device with another, including scene controller and responder relationships. That is the purpose of the "replace" function. If scene membership were not a concern, one would simply delete the old and add the new. Feel free to check out the wiki link provided by lilyoyo1.

Yes, it is.

Well...I just saw that the PLM is available where it was recently not in stock. That may be a small sign fo something.

1. Get a new keypad dimmer. 2. Add it to the ISY. 3. Remove old KPL from any folders 4. Right-click old KPL >>> replace with....

In Interesting. When I take that same path, this is what I see, including the little red "x" next to each device. Are you saying that you have no devices listed!!?? Unfortunately, I don't know enough to conclude what this means. Yes, I find it plausible that there might be something wrong with the portal account.

No, I do not expect that this would help. In the portal, I see a red "x" next to each device. This is how I would delete them. Neither do i, but I have no insight into the design of alexa or the interface between it and other electronics.

The only thing that I can think to do would be to remove the devices from the portal and add them back, trying to rediscover them after adding them back. Another option is to get rid of the ISY skill from alexa and add it back. i apologize if you have already trid these things.

I don’t know that it would be easier to start from scratch, but the limited number of devices and scenes makes me optimistic that your troubles will be few and easy to identify correct, if there are any. As far as I know, the launcher only works on newer versions of the software. For earlier versions, there was an associated launcher. You may have to go back in the forum and find the announcement for your version. Hopefully, a link to the correct launcher will still be there and still work. Yes, the loading of java could cause a warning. I assume there is some security issue with this, but don’t know how serious. I believe this is why there are periodic complaints about the continued reliance on java. Personally, I have not experienced any problems that I can trace to java, but I am probably not a hogh value target.

Well, part of my problems may have been associated with rplacing -300 series baord with -500. Most of my zwave problems were associated with recent versions.

To clarify the response from lilyoyo1, this device is not "natively" compatible with the ISY. Having said this, your original device could potentially work via amazon alexa or the google portal (requires portal subscription from universal devices). Alternatively, there is a possibility you could directly control it via a network resource. Having said all this, I think there are better options available. Also, be aware (if not already) that there is a whole section in this forum regarding latest software version, which includes an overview of the update process in some of the threads: https://forum.universal-devices.com/forum/15-current-release-betas-and-bug-reports/ Regarding the benefits of updating the firmware....it allows you to connect to devices that did not exist and to do things nobody could even envision when you initially purchased your ISY. This includes new insteon devices, z-wave devices, connection to alexa and google home, and connection to the latest mobile apps. In addition, for those willing to get into additional hardware, you can connect to hue lighting, harmony remotes, Sonos systems, Lifx bulbs, luton caseta devices, roomba vacuums, MyQ garage door openers, some thermostats, etc... The update to version 5 software will not be trivial, if your experience is like mine. Though, in fairness, much of my update problems were associated with my z-wave devices. Still, you can expect the need to go through each of your programs to make sure that they translated properly and update them if not. I understand you will have to upgrade in steps. It looks like a direct upgrade to 5.3 from v4 software would violate the instructions that I see.

If the old and new scenes contain the same devices, I see no reason to turn the old scene off. The new scene levels will override the old levels.

Notes added above. Am unsure if this is your problem, but it caught my attention. As far as troubleshooting techniques, have you tried manually running each program (then path) to see if they actually do what you want? Do you know how to do this? I am also unclear: is this a program that used to work, but now does not since the upgrade to 5.3? For what it is worth, Imwould also tend to do this with multiple scenes: Less read/write to devices. This has the potential to extend the life of your devices and provides fewer opportunities for communication problems to arise.

I do not think mobilinc pro is being updated anymore. If an iOS update broke it, I assume it is going to stay broken. While unrelated to your problem, I also noticed that mobilinc pro is not even available in the google play store if one is on android 11. My guess is that it is time to find another solution.

did you try to use the node in a scene or program?