MrBill

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

iOS broke geofences. Period. When Apple fixes the bug both Locative and Mobilinc will work again. It's not the fault of either app, the breakage is on Apple's side. 15.2 is in beta and it's reported that there is no fix there either.

-10108 isn't listed on the list of error codes, Judging by the error above it it looks like a secure socket layer/authentification problem. What else is in the error log at that time? If you can't log in with the admin console to get the error log the error log is also available in the portal. You might want to open a ticket support@universal-devices.com since -10108 isn't a listed error. Be sure to include the ISY firmware version and that you're logging into the ISY remotely via the portal.

@sdynak I don't think you'll have luck with either until Apple does something. Is apple still signing the last version of 14.x? if they are it's still possible to revert to iOS 14 and that would fix both.

Did you use you Portal credentials? It's asking for the same username and password that you log into the https://my.isy.io

Glad restore PLM worked for you. Two things to keep in mind.... 1) That maybe the PLM going bad, in other words keep your fingered crossed that it doesn't come back soon. 2) link counts have to be done when there is no other Insteon traffic or they won't be accurate. the hardest thing to stop Is wireless signals (including heartbeat). Because of this, link counts need to be done several times to prove accurate.

I can echo this, is true and I don't know why. I had re-installed Locative on both our phones, initially after re-install the geofence worked correctly on both. My wife's was first to stop working on Exit's but If I manually triggered the Exit it would then detect when she returned. Then it would do neither. All the while my phone was working correctly (for weeks now), until today, now my phone has no detected me leaving or returning. Hope Apple fixes iOS 15 soon.

This sounds like an Noise issue, something is keeping the Insteon signals from getting to the ISY. There's a couple troubleshooting pages in the wiki... 6.18.3 INSTEON Signal / Noise Troubleshooting 6.18.4 INSTEON No Status Feedback From Devices Others here are better at giving advice on this topic than I am, to be honest.

There's a couple threads, this is actually probably year old news at this point. I'm surprised, but your not the only one that didn't realize notifications were missing, there's a few posts every month where someone is just discovering the problem. Here's a thread from last December.

Blank status means it hasn't received a status since the last time the ISY was rebooted. 2421 is a version of the open close sensor. All of mine show up as 2421's also... 2843 is probably more about packaging than model of sensor enclosed. First the obvious question... are the batteries good? Does the LED on the sensor flicker when you open/close the door? Did you try different battery? (sorry for the elementary question and it does seem odd that all batteries at once would be dead, but that would be my first thing to eliminite).

I really have no comment about how the Google Calendar nodeserver works or doesn't work, It hasn't been modified by the developer in 3 years (I looked), and I don't think many people use it. On the other hand the google Calendar API may have changed in the past 3 years. The only comment that I have, which was the basis of the question above is that folder conditions will also prevent manual Run Then's from working. So that was what I was fishing for when I asked the question. I don't know if you ever used any, I don't remember mentions but folder conditions could prevent the (mo-tu-we-th-fr) program from working. Another place to look for clues is the ISY Error log.

Does right click Run Then and/or Run Else work correctly for that program?

Yea, thought so, I don't recommend anyone open ports anymore. The only two secure methods are, A) use the portal URL or B ) Use a VPN.

What happens if you open the admin console and click a node on the main tab, can you watch the status change there?

@Geddy are you suggesting to use DDNS with the portal? Or opening a port? as far a DDNS providers the only one I recommend anymore is https://www.duckdns.org/ it's free (and free of strings and ads), but supported by contributions, if using it be sure to contribute occasionally...