oberkc

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?

Certainly, if you have a small load (such as LED Christmas lights) on this, the lights can glow when off. Lamplincs apparently have some sort of "sense" current on them to tell when the load is manually turned on/off. This current can cause Christmas lights to glow dimly when off. I cannot explain why this lamplinc would work differently in programs versus scenes. I would expect the lights to dimly glow regardless of how turned off.

See above for suggestions. I expect that this will turn on the light when motion is sensed. Since none was specified, there is no automatic method here to turn the light off. Manually turning off the light will NOT trigger the program again.

I thought you had an ISY? That is what I use.

I would not be quick to simply buy another one. My experience is that they just keep running. I think the best option is, as suggested by mecheng70, to find your ip address from the router. Alternatively, I believe you can find it from a terminal or command prompt, but this would vary depending on your computer OS. I am also unclear whether the "https://isy.universal-devices.com/start.jnlp" option will work on older versions of the ISY software. I don't think there is any harm in trying it, but don't be too discouraged if it does not work on yours. Hopefully, it will work.

Another thought...if you have the ISY and have, or will be, automating your house, I think it is a good idea to include ZWAVE into those plans. There are zwave devices that do not have equivalent insteon or x10 counterparts, you can sometimes find good deals on zwave devices, and it a hedge against the risks of a single-vendor system. I started very small with zwave and it worked out pretty well...it did not take a large number of devices for me to experience good reliability. Get a couple of range extenders or outlets and see if that works. I would generally avoid zwave switches to start. My experience with zwave switches is that they can limit your program options and triggers in ISY programs. yes, I would update your ISY software to the latest 5 version, being sure to add the 500 series zwave card. Make sure you read all the instructions and cautions. It will likely involve a fair amount of time if you already have a lot of devices and programs.

In my case, I found moving the lock to be easier, but the effect is the same...get them close to each other.

I had trouble with mine, as well. I think I ended up removing the locks from the door and moved close to the ISY. Excluding and factory reset of the locks was a necessary step, as well. Once included, I have reinstalled on door and it has been solid ever since. My working theory is that z-wave repeaters, for some reason, are not effective for including this particular lock. Maybe there needs to be a stronger signal for include/exclude operations than for routine open/close.

I did not see a way to change icons.

I can add favorites, but do not find the process overly intuitive. How far do you get when trying?

To clarify...do you have control of the wifi at the condo, or is it public? The reason that I ask is wondering if you have the opportunity to set a static IP address.

Logged into new app. All seems to work, based on quick check and adding of favorites.

Ok. I just looked it up and downloaded to my phone. It seemed to download fine (android version 11). Unfortunately, I will have to wait until later to go any further, since I do not have my portal login credentials.

I suspect that your android OS is too old. In the play store, in the app description, is there not an eligibility requirement for andoid?

I have never learned to read those logs. My perception is that garage door openers can be a serious source of interference when they are running. Is that a possible explanation for what you are seeing?

This is true (at least older versions). The relay does not transmit status and cannot be used as a scene controller. Thanks for the update to your trigger reverse and query. Hopefully, that will remain solid for you.

Thanks. The only problem with "trigger reverse" that I recall is that this setting does not apply when queried. So...if you have the typical 3:00am query, this might cause a state change for the sensor. Any program that might be triggered by a state change would run. Also, I assume it would render the KPL buttons being inaccurate until toggled again. Perhaps this has been fixed in newer versions of the IOLinc? Are you experiencing this problem?