oberkc

What does it mean when all my hue nodes have the little green "write pending" icon? There is no option to "write updates to devices" that one can find with most other nodes. The nodes otherwise seem to respond as normal. I have restarted the plugin (v1.07). Is this a problem? What action should I take in response?

I would consider the possibility that it is not the lock, itself, that is the root cause of your problems. I use one of the Schlage BE469 with zmatter dongle and it works quite well for me. Barring a faulty lock, I believe it is unlikely that your problems are due to some inherent incompatibility between the lock and EISY/Zmatter. I recently experienced some "flaky" zwave performance with some outlets and blinds. With much help from UD I isolated it to one failing zwave device that was causing the communication between other zwave devices to fail. Zwave appears to create communication path between the hub and each device, with specific devices acting as repeaters along that path. When one of those devices along the path fail, communication between the hub and other zwave devices for which the failed device is part of the communication path will also fail. Perhaps, in your case, the communication between the hub (EISY) and lock is compromised for some reason. Range? Other zwave devices? Batteries? I also became a little more comfortable with the function of network healing, neighbors, and the zwave log. You might experiment with watching the log while you exercise the lock from the EISY. Watch for errors to see if there are potential clues. You might try updating the neighbors or rewriting the device links to the lock. Of course, there are no guarantees that this will work, but it might provide some insight into why you are having some problems.

Out of curiosity, I checked the wiki. Unfortunately, it appears out of date. Regardless, it seems to say that one must use the method I suggested. I also have a vague recollection that using the generic "start linking" process did NOT work for me. I look forward to a report from @PapaBear

Well, I was not so sure that this is the case for the MSII. I had a recollection that for this device, it needed to be done a specific way. Perhaps I am wrong about this, but it certainly does not hurt to try.

I continue to wonder if you are not doing it correctly. When I attempt to do so, the pop-up windows look differently than the ones you have. Here is how I believe it needs to be done: Choose "link Management" and navigate to Motion Sensor II, as shown below: You should get a pop-up that looks a little differently than the one you showed. The pop up is not "auto discover" but should have the device type prepopulated with the motion sensor II. Manually add your address in the top box. Choose "OK". Hopefully, it should find it.

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

To be clear, I did not open UDM when I arrived home (3:42pm) and only did so now (5:06pm). When I opened UDM at 5:06, the variable changed as it should. The following messages appearing the log: 3:42pm Triggering Geofence Enter: My Geofence 342pm Geofence ID: 3 Network Connected: False. 3:42pm Geofence ID: 3 Network Not connected waiting 300 miliseconds 4:03pm Geofence ID: 3 Network Not connected waiting 180000 milliseconds 403pm Geofence ID 3: Network Not connected waiting 450000 milliseconds 5:06pm Geofence ID 3 Completed geofence command for id: My Geofence 5:06pm Geofence ID 3 Completed geofence command for id: My Geofence 5:06pm Geofence ID 3 Completed geofence command for id: My Geofence

Out of curiosity, I went to UDMobile and settings and plugins. For what it is worth, the yolink plugin opens with no spinning wheel.

If only things were this easy. 1) I can assure you that there have always been entry and exit commands. If it was this, I would have known how to fix it. That is the first thing I checked when things stopped working. 2) Which makes sense, but the phone has access to the internet. I am listening to streaming audio. I get email and text (internet texting through google voice). If UD Mobile does not have access to the internet, there is some issue between the phone and the app. 3) I received no crash messages or any indication of battery saver condition. The charge state is at 80%. The phone is confirmed NOT in battery saver mode. Furthermore, for unrelated issues, I frequently restart the phone and did so before arriving home just a few minutes ago. The variable (entry criteria command) did not change values as it should have. The phone is now on wifi. This is actually my second pixel 9. The first was ultimately replaced by google after a LONG (and painful and duplicative) series of troubleshooting steps by both google and Verizon on a failure by the first phone to be able to establish a wifi hotspot. The replacement pixel 9 exhibited no such trouble. I find it hard to believe that there are faults with the second phone that would contribute to this current experience with UD Mobile. In fact, UD Mobile geofence worked fine on this phone until recently. Unfortunately, the technology in my life has been acting up enmasse lately. I am dreaming about the days when I did not have to spend hours troubleshooting gadgets. Thank you for your thoughts thus far.

The phone has been another long story since March, but I won't bore you with the details. The current phone has been in place since August and it has worked with with UD Mobile at one point. My android (Pixel 9, android version 16) does not have a permission "allow background usage" as near as I can tell. Otherwise, permissions (location and notification) appear correct. Update: I found the "allow background usage" user the settings for "Battery Usage". I have confirmed that it is set to "allow background usage".

As I researched this more, I remembered that there is thread about a "Hue V2" plugin. I think the duplicate nodes are part of this new plugin. I further suspect that the new plugin became merged with the original when loaded to the store. When we were notified of an "upgrade", it loaded the new "V2" version. When I go to the plugin store, I notice that there is a 1.6 version (now a paid) and there is a 0.1.11 version. I suspect that we were on the 0.1.11 version when we got the upgrade notice. I wonder if going back and reinstalling the 0.1.11 version would bring ups back to the pre upgrade state. Unfortunately, I have already deleted my old nodes and recreated all my scenes and programs with the new nodes.