oberkc

'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.

Additional updates: After I move back into the geolocation zone, I open the log. I see that UD mobile recognizes the transition (at 04:21pm) and logs: "Triggering Geofence Enter: My Geofence" "Network Connected: false" "Network Not connected waiting 30000 milliseconds." The variable that was supposed to update from the entry command did not change however. It was not until I opened UD Mobile at 5:18pm, however, that the log then recorded: "Completed geofence command for id: My Geofence" At that point, the variable updated. Why does UD Mobile now seemingly require me to open the app before completing the geofence entry criteria?

I have done that, several times. I have also deleted the geofence and recreated it with the same enter and exit settings. When I recreated the geofence, it immediately recognized that it was exited the area and gave me the error in the log again

I am not sure I understand this question. How does one determine if they are "set"?

In the recent past, my geofence stopped working. In the geofence are anter and exit commands. The enter command is to change the value of a variable to 1. The exit command is to change the same variable to a value of 0. The geofence appears to trigger as I enter and exit the area, but the variable value does not change. Digging further I notice a log input “there are no specified commands for this geofence trigger”. I am on android. We also have an apple phone where I believe the same type of geofence works fine. As near as I can tell, all apps are up to date. IoX version is 6.0.0 Any thoughts on what is happening and why the variable change does not occur as the phone enters and exits the geofence?

I already have such a program and have had for several years.

Has anyone updated to this latest version. My update to the version before this one created some problems which cost me several hours to fix and my confidence in these upgrades is shaken. I am hesitant to upgrade again without some confirmation that it is a smooth process.

Well, I can tell you that not too long ago, mine had the status for a few parameters, including motion. Blank is a relatively new thing for me. Mine is a hard-wired doorbell. No battery. Thank you both for the responses. Perhaps mine is working fine without the expected parameters being displayed. I know the other night it did not trigger and my wife was not happy. In the past, this has been quite reliable.

@Geddy Thank you for the response. I reauthenticated and restarted as well. I also saw on the instructions the the PG3 remote settings (in portal account!!?? I guess this node server does not work without portal account.) must be "enabled and active". Mine was enabled, but not active. Somehow, (am unsure what action, if any, I took that caused this) I was eventually able to get it to show "active". My test result now shows "success", but the motion node still remains blank: I am not sure whether this suggests that IoX is not seeing the various states of the motion sensor node. If I cannot figure out what is happening, I may start a new thread, as you suggest.

You showed a picture with a single box having two Insteon (and an additional third) switch, which does not match the illustration. And the wires in the pictures of the ceiling boxes don't match the diagram. Still, I can tell you how to modify the wiring in the illustration. Whether or not this matches your installation, I will leave to you to decide. I am not sure that it does. In theory, each Insteon switch requires a constant line input and neutral. One Insteon switch will directly control the load (the two light fixtures in this case.). The other Insteon switch will not be connected to any load. The two Insteon switches will be put into a scene, with both as controllers. Left switch box: connect lower black conductor to upper black conductor and to Insteon black wire. Connect lower white conductor to upper white conductor and to Insteon white switch. Connect Insteon red wire to upper red conductor. Upper left ceiling box: connect all white conductors together, and to fixture screw (this would be the neutral). Connect upper-left black conductor to upper-right black conductor. Connect upper-left red conductor to lower-right black conductor, and to other screw on light fixture. Upper right ceiling box: connect lower left black to one fixture screw. Connect all whites together, and to other fixture screw. Connect upper left black conductor to upper right black conductor. Put a wire nut on upper left red conductor, not connected to anything else. In lower right switch box, connect black conductor to black wire on Insteon switch. Connect white conductor to white wire on Insteon switch. Put a wire nut on the red conductor not connected to anything else. Put a wire nut on Insteon switch red wire. Tie all bare copper conductors together, in all boxes, and to Insteon switch bare wire. Cross link the two Insteon switches, making each a controller of the other. Good luck.

I cannot see from the pictures (sprayed texture and other obstructions in boxes makes it difficult for me to identify source of the various conductors). For me to even attempt to help, I would need to identify total number of "cables" (cables will have either two conductors, black and white, or three conductors, black, white, and red. Ignore bare copper conductors.) coming into each box and to what each conductor is connected. Does each switch control one fixture? You mentioned "three way". Are there other switches that control these fixtures not shown in any picture?

Nice picture. Is this a ceiling box? You want to install a switch into a ceiling box? Will the switch be wired to any fixture? What was here before you opened it? Do you have an idea where any of those wires go on the other end?

I do not know whether this is related to your issues, but I experienced a problem when the hue plug-in upgraded versions (I was already on IoX 6). Upon the plug-in upgrade, none of my existing hue nodes worked, but the upgrade process created duplicate nodes that did work. Unfortunately, I had to recreate all scene definitions and programs that were affected by the change in hue nodes and delete the old, non-functioning, nodes. One thing I can tell you is that the hue plugin appears to still work on IoX 6 for me.

I have 1.2.6. and ring doorbell. As of now, the motion sensor node has no status or any other parameters showing. If I test the primary "Ring" node, the test result is "failure". Programs based upon the motion sensor are no longer triggering.