oberkc

I also recall that some have experienced communication problems when an Insteon device is protected by certain types or brands of GFCI outlets. Hopefully, that won't be the case here.

If I recall correctly, you must add some sensors a little differently. Rather than "start linking" option and pressing the set button (and hoping that the ISY can hear it), you must go to the drop-down menu and add the MSII by selecting it from the menu and manually entering the requested data.

I have understood that "matter" is in the early stages for UD and, as such, documentation and user manuals is not something we should expect. I have had some luck with matter devices over wifi, but matter devices over thread have not worked consistently for me. In fairness, the thread devices (nano leaf bulbs) I have tried also do not consistently work with echo or google, either, and am willing to consider the possibility that the problems might be with the nano leaf bulb, rather than with the EISY. I keep looking for other thread devices to try, but I don't see many around.

I suppose, now that we have a little bit of integration with Apple HomeKit through the matter plug-in, one could use siri as a voice assistant. This may not be quite as good due to the limited device support but may work for some people. The Hue plugin underwent an update to address a change in the API, I understand. Unless your plugin updated automatically, I am surprised that it stopped working for you. It has been rock solid for me. I unknowingly updated my plugin and broke it, but was able to get it working again. Unfortunately, it took a not-small amount of time. Between alexa and google home, I have settled upon alexa for a voice assistant, but mostly because that is what I started with. I have some google hub devices around and they seem to work fine as well. I just don’t want to take the time to maintain both systems. In both cases, it has taken me a while to get efficient at adding new devices and understanding of the difference between scenes and switches and lights and sensors and with navigating through the Alexa app. After time, it has gotten easier.

I understand that the new interface is a work in progress and does not have all the intended capability at this time. I do not believe one can see or modify programs at this point.

If you have this window, it sounds to me that the launcher is installed. So you have the launcher istalled, but it cannot find the ISY. I recall that, at one point, launchers were specific to the ISY software version but the current launcher version is ISY-agnostic. Does your launcher show a refresh or find (I don’t recall the Exact phrase) option? Did you try this? Do you know the ip address of your ISY? Do you recall the software version of the iISY?

Are you certain that you have no programs triggered by any of these devices?

To add support to the others' diagnosis, turning on a switch from the admin console will NOT cause linked devices to respond. This is normal. @paulbates and @Guy Lavoie have given you good feedback and viable options to which I add a third (requires the use of polyglot). This approach has become one that I like: Create a virtual switch from the applicable polyglot node server and add the virtual switch to your IoX scene, as a controller, that contains your keypad and two switches. Add the virtual switch to Alexa. Unlike real switches, I find that activating virtual switches from the admin console (or Alexa) do cause linked devices to respond.

'Twas not me. And, it turned out, I spoke too soon. Entering the geofence just now failed to trigger the action.

Update: In a further attempt to try different things to see if I could get this to work, I have created a virtual switch and used this instead of a variable. Now, my entry and exit criteria are simply turning this virtual switch off or on. (Prior to this, the entry and exit criteria was swapping a value for a variable between 0 and 1.). At this point, the geofence seems to work. I don't know for sure whether the geofence now working was related to the change in criteria, or whether this was coincidental to some other change that happened in the background of which I have no knowledge.

It's in my house, the duplicate nodes are a problem with devices beyond just insteon. I have seen duplicate nodes on new hue devices, new yolink devices, and I even see a scene that keeps coming back after I delete it. I even thought I have rebooted my eisy, but I will try again.

@Kentinada Those are known as "wago" connectors and are available at may typical home improvement stores. Otherwise, cut the end from an extension cord and add the connectors.

@TJF1960 I was a little premature in my proclamation that I do not get any errors. Just now I synchronized and received two errors: could not match ST paramName: AME could not match ST paramName: ST I see nothing about "let the dev know" or any reference to any node server. I don't know if this is new or whether I just missed it before.

I hope this fixes the problem. Thank you for the feedback. I will look forward to having my geofence back.

I get no such message