MrBill

There is only one polyglot2 instance running on Polisy, you currently have it pointed to your ISY, you can redirect it to ISY on Polisy. Polyglot2 can only support one instance of ISY, either the 994 or ISY on Polisy but not both. Polyglot3 has more options and I'm not entirely up to speed on it.

Last night when we left and returned GeoFences worked correctly on both phones!! That's the first time it's worked that way for awhile...Both phones... leaving and returning. A greater sample size is needed but the common denominator was IOS 15.1.1 was installed on both yesterday (which claims it's only a bug fix for dropped calls on iPhone 12 and iPhone 13). For those who have installed iOS 15.1.1 what is your GeoFence experience?

Try Help > Manage Modules and/or Configuration Tab > Portals may be waiting for you to accept.

Never fear support will be on it!. They answer tickets within a few hours usually... maybe a little longer on weekends, but you'll get a reply today. UDI support is awesome!

Here is a better way to accomplish the same thing you have. Note: of course I just used some random devices in my system to create the example. aaa Test - [ID 00E6][Parent 0001] If 'Door Switches / Front Door' Status is On Then Send Notification to 'test1 ' content 'my alert' Repeat While $cTrue is $cTrue Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Else - No Actions - (To add one, press 'Action') Note that when using the "Repeat" statement.... "repeat" appears at the TOP of the loop that is repeated--and each line that is to be repeated is idented--. So when the status changes to On, the notification will be sent and then the repeat loop will start forever. Notice that I used "While $cTrue is $cTrue" which looks like it would never end, but alas the If statement will still terminate the program when the Status of the If statement changes to false. You could also use something like Repeat "for 999999 times". $cTrue is an Integer variable that is always set to 1, it never changes, thus the little c for Constant at the start of the name. If you do want to be reminded with another notification every 3 cycles you could extend the loop the way you did and move the notification inside the loop... like this: aaa Test - [ID 00E6][Parent 0001] If 'Door Switches / Front Door' Status is On Then Repeat While $cTrue is $cTrue Send Notification to 'test1 ' content 'my alert' Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Set 'Attic Fan#' On Wait 5 minutes Set 'Attic Fan#' Off Wait 20 minutes Else - No Actions - (To add one, press 'Action') (or you could even nest a repeat under the repeat.... but lets keep it simpler) The method that you used to loop probably works fine in this case, because once the sensor trips I'm guessing the status is going to stay wet until you're there. It would take a long time to dry enough to get the sensor to actually turn off (if it even does... something in the back of me head says leak sensors must be manually reset). to be clear I do use Run Program <itself> (then) from time to time to create endless loops, that's how it was done before V5 when "repeat" came into being. Note: If the sensor can change status it's likely better to loop to the IF than the then.... in other words "Run Program <itself> (if)". In the case of "Run Program <itself> (then)", without testing I believe that once the second iteration starts, when the THEN block re-runs, I believe that the IF is no longer being tested to stop the program. There is two parts to this line: The first is who gets the notification the second is the content of the message... In this case we are interested in 'Leak Sensor Water Alert - Level 1' (I'm not sure why there is a space between the tick mark and the L that is weird....) That points to the top line of the next screen shot: so you would just click the RIGHT end of that line and edit the contents of the notification in the popup window. Note that ${sys.node.#.name) is the node name that triggered the program... in this case should appear instead of ${sys.node.#.name) Note however, as you have the program looping above, the replacement probably only works the first time the notification is sent and likely doesn't work on the repeated notifications after the Run (then path). First, you must move the dead sensor up to the root level. That is it must be under "My lighting" with the new sensor, The "replace" function does not work if any devices are in a folder such as "Leak Sensors". Second, Put both devices old and new in linking mode. Click the name of the OLD sensor, then right click it, and pick "Replace <Old Name> with" and there will be a context menu with the possible new sensors that you have already added to the ISY. I'm not sure what will happen if the old sensor is so dead it can't be put in linking mode, but try it with just the new sensor in linking mode and see if it works. You should only need to do this once, and it will include the related nodes such as heartbeat. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:INSTEON_Device#Replace...with

Correct. Try to get rid of them one device at a time. With wireless writes disabled, put one device in linking mode, then right click the device name and Write Updates to Device.

We need someone that's better than me at reading level 3 logs... there are many members that might but i'll tag @kclenden in case he's around.... He's an amazing link wizard. That new button you got... When you press it and turn it to grey the 1011 icons will turn grey, and they are inactive or deselected. When they are green the ISY will be trying to write them constantly, which slows down communications because each has to error out 3 (?) times. So keep them grey and see if you can put one device at a time into linking mode, then right click the device and write updates. I was surprised when you said this. Did you confuse Restore Device with Restore PLM? Really "Write updates to device" is all you should need but I did also suggest trying "Restore Device".

In the future watch for changes that require wireless writes and make sure to stay on top of them. Not sure what firmware version you're on, but there was a long time bug that was fixed around 5.2 (it existed for most revisions of 5). The bug was linked to wireless devices that were scene controllers and programs that used "Adjust scene" which would generate the need for wireless writes. Not sure what firmware version you're on but it should be 5.3.4 unless you have a 300 series z-wave board in which case the last firmware that works with the 300 series z-wave is 5.0.16C

I don’t have my laptop but I think you want “my products”

I hate to recommend doing it because if it doesn't solve the problem for you.... but it is a soft instant upgrade... Help > Purchase Modules.

code the code button seems to be working,... maybe a browser cache issue? That looks like it's cycling thru multiple devices, which is where Teken was going with his suggestion. just to be clear, "pro" is a feature level, it adds to the number of nodes and programs allowed and gives you these two buttons on the admin console ribbon The one on the right, shown in the off or deselected state is what teken is talking about. Do you have those two buttons?

Try putting device in linking mode and right clicking the device and doing "restore device".

Also, its not documented (other than somewhere in a forum thread) but Total Nodes = Scenes + Insteon + Z-wave + NodeServer Nodes + Folders "Programs" includes both programs and program folders combined. The reason "Folders" is listed last is because it was added later than the others.

Node server ISY-Inventory A very simple nodeserver that creates one node.

@johnmsch Also don't be intimidated by the 5.3.4 update instructions.... you've already done the hard update from v4.x that most of that is written for.... going 5.3.0 to 5.3.4 is a cake walk.... it will take you longer to let the ISY backup than it will to load the new software and let it go thru the reboot process. excluding making the back-up this should take you 10 minutes, 15 tops.

System -50001 -16 is "Password not accepted" Source. Also "Test" could end up in your spam folder. Instead, try right clicking the name of a program that sends a Notification and picking Run Then or Run Else and send an actual notification. --- FYI... I actually use the SAME comcast account in the To: for the notification to be sent to. (I can only speak for iPhone) but I use the Exchange app for various email accounts with notifications turned off completely (who gets too much email for notifications? ) So for the ISY Comcast account I downloaded the free app "Spark Mail" and Only added the same @comcast.com account (the same one the ISY is sending From:) So, in short my ISY's emails are From and To the same address. then I turned on Notifications for Spark Email.

I know that there is no point for any of us to open a case with Apple. All we would do is spend a lot of time troubleshooting something that we all know from other posts on the internet is broken for everyone. I would suggest that everyone go to apple.com/feedback and send a feedback on the topic tho. Something along the lines of: "I'm aware from online posts, including Apple Support forum, that iOS 15 broke GeoFences, what I don't understand is why this is not a priority bug fix. iOS was released on September 20th and almost 2 months later there is no fix that anyone knows of in sight. App Developers themselves state they are waiting on Apple." Apple does human read every /feedback (or they claim they do) but even if they are read by an AI bot getting enough /feedback submitted with the words iOS 15 and GeoFence and broken and bug can't hurt anything. Send /feedback to apple today!

In version 5 you need to watch the forum, not the admin console, for updates. The version 5 branch doesn't give that cool little flag that an update is available. At this point you should upgrade to v5.3.4 using the manual upgrade procedure. From your current version its a simple upgrade, just backup first (always--just in case) then select help > manually upgrade and upload the still zipped upgraded file to the ISY. the rest the ISY will handle. (You also need to do the clear java cache etc as the directions indicate). WHen you log back into the admin console after the upgrade just check Help > About to make certain both Firmware and UI versions are the same. for the comcast mail server: Make sure there is a : in the From Field (From:user@comast.net... what is before the : doesn't matter but there must be some string a : and then the user@comcast.net), make certain the TLS box is checked and port 587.

If you can wait a bit until UDI releases the version of "ISY on Polisy" that supports z-wave via the Zooz 700 series USB stick then you only need Polisy. If you have an immediate need you could do that with an ISY-994 with Z-wave. Personally I'd prefer to wait.. the ISY994 is soon to be obsolete.

Depending on your skill set, one could create an cloud space someplace to do the processing. a middleman of sorts. State variables can be set via the Portal API or through the ISY API with open port. You'd have to do all the programs there, probably via something like php. ...or actually the same on a local machine such as an RPI....

Mines not a lot different that yours: I had a several hundred more programs at one point, but after learning more about how things worked I knocked a few hundred off programs off the count and cut state variables in half.

bookmarked! Agree with @asbril as well... 2048 is double the number I thought that it was

@ewind One more program. I neglected to take reboot of the ISY into account. Bonus Humidity -40.Startup [Run At Startup] If (none) Then Enable Program Bonus Humidity -40.Start Disable Program Bonus Humidity -40.Body Else - No Actions - (To add one, press 'Action') The condition this corrects is if Body was running which causes Start to be disabled then when the ISY is rebooted, this additional Program with the Run at Startup flag will enable the Start Program, (the body program should normally be disabled, the second statement just ensures that). If don't mind a humidity notification always during ISY start up you could instead simply use the original 3 programs and enable Run at Startup on the .body program.

So... Universal-devices does have a mail server you can use by simply checking the box "Use Default" on the configuration tab > emails and notifications sub tab. HOWEVER, about a year ago UDI's server was getting deluged with spam and they made a change to how your ISY identifies itself as a legitimate sender. As a result older firmware, can't use the default mail server. If you haven't touched your ISY in years, then that would probably mean you're on the 4.x branch and you can use the notification in the admin console to upgrade to the latest and greatest version of the 4.x branch which I believe (without looking) is 4.9. The default mail server will work with 4.9 If you're by chance on the 5.x branch, there's more questions before telling what version to upgrade to. You can find your firmware version by opening the admin console and looking at Help > About. -- I don't know what google told people in their email because I don't use google services very often, but I believe you should still be able to create app specific passwords -- Originally I couldn't use UDI's default server because even white listed I had notifications ending up in Spam folder. UDI's since changed something because when I've tested things for other posts the Spam problem seems to have gone away EXCEPT when you press the TEST button to send a test email... the TEST emails are still classified as Spam. -- Personally my ISY uses a dedicated email account that I created via my Comcast account, and it works very well. I can provide the SMTP settings if you happen to be a comcast customer.

My phone worked for a long time after Locative was reinstalled. The magic is gone tho, it's not noticing GeoFences anymore, my wifes as stopped as well. iOS 15.1 doesn't solve the issue. Beta 15.2 doesn't either. It remains to be seen if Apple will get a fix into 1.5.2 but it doesn't look good.