I have used this app (MLP) successfully for years connecting locally (HTTP) and remotely (HTTPS port forwarded) to my ISY. After the most recent (12/18/20) iOS 14.3 update to my iPhone XS, connectivity has become problematic. For years I have left MLP set on https for connecting via local wifi or remotely without any issues. After the update this would no longer connect, so I switched to http (rather than auto).  This seemed to work.

Believing the https connection to be a certificate issue, I noticed that my ISY certificate had past its expiration date. I created and installed a new self-signed certificate. I removed the ML app from my iphone and reinstalled. On installation, the app reported the new security certificate was recognized.

Connectivity is still unreliable using Mobilinc Pro either via http or https I have rebooted both the phone and my ISY several times, no change in connection reliability. I can launch and relaunch the app and eventually get MLP to connect.

I have no trouble connecting to my ISY locally or remotely from any browser. The beta UDI mobile app for android also has no issues connecting (without using the ISY portal).

I believe, something has happened to MLP with the latest iOS update (v14.3) that is adversely affecting the apps ability to connect.

Any help would be appreciated.

I do not think mobilinc pro is being updated anymore.  If an iOS update broke it, I assume it is going to stay broken.  While unrelated to your problem, I also noticed that mobilinc pro is not even available in the google play store if one is on android 11.  My guess is that it is time to find another solution.

Actually Mobilinc Pro does work with iOS 14.3  I've mostly moved on to other methods but do on rare occasions open Mobilinc Pro to do something that hasn't been planned for.  For example, after midnight last night when we got in bed I realized I had over ridden outside lighting to the 'early evening' scene and needed to move it back to the 'late night' scene, I did use Mobilinc Pro for that, worked fine.

When you say "unreliable" do you mean that it works sometimes but then for unexplained reasons you start getting a popup at the bottom of the screen that says something like "mobilinc has disconnected, attempting to reconnect"?  At that point it becomes maddening to get mobilinc to re-connect?  If so, I've been there, and so have some others in this forum.  If you open the admin console at this point in time, do you get an "Already subscribed" dialog box?  Then you reboot your ISY and it takes care Already subscribed, and mobilinc also works again.. for awhile?

The above described bug was what drove me away from Mobilinc a couple years ago.   I can't tell you EXACTLY what fixed it for me, but around a year ago I was having weird ISY issues and discovered a lot of Queue Full Errors and other things I couldn't explain in the ISY error log.  I ended up opening a ticket, it was a very frustrating experience, but eventually got it so that there are very few entries in my error log on a daily basis, since that time every time I make many changes I watch the error log like a hawk to make sure I haven't created something that creates errors (the ISY does a fabulous job of recovering from most, but some seem to have lingering effects). 

Anyway to make a long story short... I no longer have the "Mobilinc Disconnected / Already subscribed" bug.   After @TrojanHorse and others revived the topic I began opening mobilinc everyday again, attempting to recreate the issue... I can't anymore.  Knowing now that Admin Console "already subscribed" bug I was also attempting on 3 different iOS devices randomly thinking the subscriptions were just getting confused.  I could never recreate it... the only thing I can say that was substantially different is that the discovery that I could no longer recreate the maddening Mobilinc bug was right after I attacked errors in the ISY error log.

 

Thanks Mr. Bill for the detailed response. It is good to know that Mobilinc Pro is still viable on iOS. I do make use of the app on both my iPhone and iWatch daily.

Your assessment: "When you say "unreliable" do you mean that it works sometimes but then for unexplained reasons you start getting a popup at the bottom of the screen that says something like "mobilinc has disconnected, attempting to reconnect"? " is an accurate description of what I have been experiencing since I upgraded iOS.

Upon logging into the ISY admin console this morning, the "Already Subscribed" popup was visible.  This is the first time I have seen this notification despite many many accesses to the admin console recently. The only thing new in my environment is I am now hosting a local Polyglot Nodeserver on my local network.

I downloaded the ISY error log and found the following entries:

Fri 2021/01/01 08:45:21 AM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 08:46:56 AM    System    -5    Start    
Fri 2021/01/01 08:46:57 AM    System    -110022    /CONF/INSTENG.OPT    
Fri 2021/01/01 08:46:57 AM    System    -110012    /CONF/INSTENG.OPT    
Fri 2021/01/01 08:47:01 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Fri 2021/01/01 08:48:06 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:06 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:16 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:17 AM    System    -170001    UDQ:Queue Full: PDM : Task[10] HTTP_1 HTTP-Get pty=19    
Fri 2021/01/01 08:48:26 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:36 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:47 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:47 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:57 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:47:08 AM    System    -170001    [Network] Established 

After rebooting the ISY, Mobilinc seems to be performing normally.  I cleared the logs and currently only show the following errors.  I don't know how to interpret them in order to eliminate those that could be problematic, but perhaps you recognize some that should be investigated (note: the errors below were also visible in the log that were cleared following the ISY reboot):

Fri 2021/01/01 12:02:25 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:05:29 PM    System    -5012    33    
Fri 2021/01/01 12:05:29 PM    System    -5012    34    
Fri 2021/01/01 12:07:34 PM    System    -5012    36    
Fri 2021/01/01 12:07:34 PM    System    -5012    37    
Fri 2021/01/01 12:09:34 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:09:39 PM    System    -5012    38    
Fri 2021/01/01 12:15:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:20:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:22:07 PM    System    -5012    39    
Fri 2021/01/01 12:22:29 PM    System    -5012    40    
Fri 2021/01/01 12:22:39 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:22:40 PM    System    -5012    41    
Fri 2021/01/01 12:25:54 PM    System    -170001    [UDSockets] RSub:20 error:6    
Fri 2021/01/01 12:25:54 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:25:55 PM    System    -5012    42    
Fri 2021/01/01 12:25:55 PM    System    -5012    43    
Fri 2021/01/01 12:30:21 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:35:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:36:04 PM    System    -170001    [UDSockets] RSub:13 error:6    
 

I will keep a watch on Mobilinc and check the logs once again should the issue repeat itself.. Thanks again and have a very Happy New Year! 
BR/Pete

14 hours ago, vspete said:

Thanks Mr. Bill for the detailed response. It is good to know that Mobilinc Pro is still viable on iOS. I do make use of the app on both my iPhone and iWatch daily.

Your assessment: "When you say "unreliable" do you mean that it works sometimes but then for unexplained reasons you start getting a popup at the bottom of the screen that says something like "mobilinc has disconnected, attempting to reconnect"? " is an accurate description of what I have been experiencing since I upgraded iOS.

Upon logging into the ISY admin console this morning, the "Already Subscribed" popup was visible.  This is the first time I have seen this notification despite many many accesses to the admin console recently. The only thing new in my environment is I am now hosting a local Polyglot Nodeserver on my local network.

I downloaded the ISY error log and found the following entries:

Fri 2021/01/01 08:45:21 AM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 08:46:56 AM    System    -5    Start    
Fri 2021/01/01 08:46:57 AM    System    -110022    /CONF/INSTENG.OPT    
Fri 2021/01/01 08:46:57 AM    System    -110012    /CONF/INSTENG.OPT    
Fri 2021/01/01 08:47:01 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Fri 2021/01/01 08:48:06 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:06 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:16 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:17 AM    System    -170001    UDQ:Queue Full: PDM : Task[10] HTTP_1 HTTP-Get pty=19    
Fri 2021/01/01 08:48:26 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:36 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:47 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:47 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:48:57 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Fri 2021/01/01 08:47:08 AM    System    -170001    [Network] Established 

After rebooting the ISY, Mobilinc seems to be performing normally.  I cleared the logs and currently only show the following errors.  I don't know how to interpret them in order to eliminate those that could be problematic, but perhaps you recognize some that should be investigated (note: the errors below were also visible in the log that were cleared following the ISY reboot):

Fri 2021/01/01 12:02:25 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:05:29 PM    System    -5012    33    
Fri 2021/01/01 12:05:29 PM    System    -5012    34    
Fri 2021/01/01 12:07:34 PM    System    -5012    36    
Fri 2021/01/01 12:07:34 PM    System    -5012    37    
Fri 2021/01/01 12:09:34 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:09:39 PM    System    -5012    38    
Fri 2021/01/01 12:15:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:20:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:22:07 PM    System    -5012    39    
Fri 2021/01/01 12:22:29 PM    System    -5012    40    
Fri 2021/01/01 12:22:39 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:22:40 PM    System    -5012    41    
Fri 2021/01/01 12:25:54 PM    System    -170001    [UDSockets] RSub:20 error:6    
Fri 2021/01/01 12:25:54 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:25:55 PM    System    -5012    42    
Fri 2021/01/01 12:25:55 PM    System    -5012    43    
Fri 2021/01/01 12:30:21 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:35:22 PM    System    -140005    Net Module Rule: 4    
Fri 2021/01/01 12:36:04 PM    System    -170001    [UDSockets] RSub:13 error:6    
 

I will keep a watch on Mobilinc and check the logs once again should the issue repeat itself.. Thanks again and have a very Happy New Year! 
BR/Pete

For starters here is a link to the ISY error log:

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

 

@Michel Kohanim so my take is that it seems this long running problem that we've never nailed down is the result of some error in the ISY that results in confused subscriptions, and agave and ekeypad both seem immune, or actually can help resolve the problem.

to recap: Generally after the error has occurred mobilinc pro users will see "Mobilinc Disconnected... attempting to reconnect", upon subsequently attempting to open the admin console they will get the "Already Subscribed" dialog box from the admin console, there is no obvious way around that error short of rebooting ISY.  Rebooting the ISY cures all, until the error happens again.  @TrojanHorse first reported here, that ekeypad could be used to create a "fix".   I later did the same thing with agave, however I only used one phone (as opposed to his two).   Those fixes only worked tho if you didn't try to open the admin console, once you tried that you would enter the "already subscribed" area of the problem.  I can't recreate the original problem anymore to test new theories because my ISY pretty much is running error free, and mobilinc works without fail whenever I try it.   (at some point last summer I was trying hard to make the Mobilinc error occur, but couldn't because I had addressed the error log issues.)

I don't know how relevant this is but: one thing that was contributing to my error log issues (a year ago) was that I was using a wireless tags kumo app at the time to get temp/humidity data into the ISY, moving that component to a Polisy nodeserver I believe got rid of a lot of the errors.

3 hours ago, DennisC said:

For starters here is a link to the ISY error log:

https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages

 

Thanks Dennis for this link.  While I can currently always connect without the "Mobilinc Disconnected... attempting to reconnect" message, sometimes the connection is not immediate.  I have observed the connection delay issue most frequently when using the iWatch extension. The connection failure is reported on the iWatch not the iphone App.  This condition eventually clears.

I cannot correlate this phenomena to any specific logged error. I haven't seen any "Already Subscribed" messages since the reboot yesterday.  I have used Mobilinc Pro for iOS since 2015 on two different iPhones with this ISY and never experienced this issue.  I have never been unable to connect locally to my ISY via a browser, locally, via VPN, or remotely (through a forwarded https port).

I disabled uPNP on the ISY this morning as it isn't needed and rebooted. A quick look at the log shows queue full errors after the reboot, but Mobilinc connected without issue and no errors logged associated with Mobilinc connection.  

Sat 2021/01/02 09:01:15 AM    System    -5    Start    
Sat 2021/01/02 09:01:16 AM    System    -110022    /CONF/INSTENG.OPT    
Sat 2021/01/02 09:01:16 AM    System    -110012    /CONF/INSTENG.OPT    
Sat 2021/01/02 09:01:20 AM    System    -110022    /DEF/F6/I1/NLS/EN_US.TXT    
Sat 2021/01/02 09:02:17 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:17 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:27 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:28 AM    System    -170001    UDQ:Queue Full: PDM : Task[10] HTTP_1 HTTP-Get pty=19    
Sat 2021/01/02 09:02:37 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:47 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:57 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:02:57 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:03:08 AM    System    -170001    UDQ: Queue(s) Full, message ignored    
Sat 2021/01/02 09:01:27 AM    System    -170001    [Network] Established    

I have now disabled the iWatch extension and will observe behavior and logs over the next few days.

@vspete I don't think it's related to the UDQ queue full errors at startup/reboot (as signified by Start -5).... my system actually does still experience that condition.

I suspect the culrpit is this type:

Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:23 PM    System    -170001    [UDSockets] RSub:30 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:13 error:6    
Fri 2021/01/01 12:05:28 PM    System    -170001    [UDSockets] RSub:30 error:6    

but I don't know what that actually means....

@MrBill Regrettably my oldest error log entries are from early December 2020.  This was AFTER I began using network resources to control shades and several cloud hosted node servers. The -170001 particular error type was occurring at that time, but I don't recall any Mobilinc connectivity issues being present.

I was experiencing issues with my cloud based nodeservers (frequent loss of connectivity) and moved them to a server on my network. That move completely eliminated those issues. My logs currently only show three error types on a frequently recurring basis and decoupled from any Mobilinc activity:

Sat 2021/01/02 11:10:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:13:36 AM    System    -170001    [UDSockets] RSub:## error:6    
Sat 2021/01/02 11:13:46 AM    System    -5012    ##

 
 

11 minutes ago, vspete said:

@MrBill Regrettably my oldest error log entries are from early December 2020.  This was AFTER I began using network resources to control shades and several cloud hosted node servers. The -170001 particular error type was occurring at that time, but I don't recall any Mobilinc connectivity issues being present.

I was experiencing issues with my cloud based nodeservers (frequent loss of connectivity) and moved them to a server on my network. That move completely eliminated those issues. My logs currently only show three error types on a frequently recurring basis and decoupled from any Mobilinc activity:

Sat 2021/01/02 11:10:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:13:36 AM    System    -170001    [UDSockets] RSub:## error:6    
Sat 2021/01/02 11:13:46 AM    System    -5012    ##

 
 

I think but I am not positive, that Net Module Rule 4 refers to Network Resource #4.

Maybe you should open a support ticket with Wes at Mobilinc to see if he can offer any insights, or at least tag him with @ naming convention.

13 minutes ago, DennisC said:

Maybe you should open a support ticket with Wes at Mobilinc to see if he can offer any insights, or at least tag him with @ naming convention.

Wes will get notified of this because it's posted in Mobilinc, he washed his hands of this issue long ago tho.  As it turns out it seems to be more about ISY subscriptions getting confused because the admin console gets drug into the arena with the "Already subscribed" dialog box.  The interesting thing is that Agave and ekeypad both seem to be immune and can even seem to help.

Michel may be able to help more but I suspect the output from http://ISY-IP/rest/subscriptions might be a key.  Now that we've got another person getting the error I wish @TrojanHorse would also log in.

I also think this has more to do with information being posted into the ISY than outbound network resources, but I'm very interested in your theory about it being Networking module Rule 4.... I've tried to learn how to read the very cryptic error log in the past (in many cases the error table in the wiki doesn't tell you much more).

39 minutes ago, DennisC said:

Maybe you should open a support ticket with Wes@InsteonNutat Mobilinc to see if he can offer any insights

I originally posted this issue on Mobilinc's board (even though there wasn't a natural topic fit for Mobilinc Pro issues). This seems to match with @oberkc's comment early in this thread. There hasn't been any recent posts on Mobilinc's board, so I posted here. I did tag Wes per your advice.

As for Module Rule 4: I don't think your assumption is valid. My Network Resource ID #4 refers to a http command to my Hunter Douglas Powerview hub which isn't called from the ISY at anytime these "errors" are posted.

I think the best plan for me is to shutdown my nodeservers one at a time and see which error messages are affected. Will post the outcome of that experiment.

Edited January 2, 20214 yr by vspete

13 minutes ago, vspete said:

I originally posted this issue on Mobilinc's board (even though there wasn't a natural topic fit for Mobilinc Pro issues). This seems to match with @oberkc's comment early in this thread. There hasn't been any recent posts on Mobilinc's board, so I posted here. I did tag Wes per your advice.

As for Module Rule 4: I don't think your assumption is valid. My Network Resource ID #4 refers to a http command to my Hunter Douglas Powerview hub which isn't called from the ISY at anytime these "errors" are posted.

I would suggest disabling that resource for a short period and see if it disappears.

20 minutes ago, MrBill said:

Wes will get notified of this because it's posted in Mobilinc, he washed his hands of this issue long ago tho.  As it turns out it seems to be more about ISY subscriptions getting confused because the admin console gets drug into the arena with the "Already subscribed" dialog box.  The interesting thing is that Agave and ekeypad both seem to be immune and can even seem to help.

Michel may be able to help more but I suspect the output from http://ISY-IP/rest/subscriptions might be a key.  Now that we've got another person getting the error I wish @TrojanHorse would also log in.

I also think this has more to do with information being posted into the ISY than outbound network resources, but I'm very interested in your theory about it being Networking module Rule 4.... I've tried to learn how to read the very cryptic error log in the past (in many cases the error table in the wiki doesn't tell you much more).

Within the last two months I had an issue requiring me to contact UD for help with the error log. I had some 140005 Net Module Rule : x errors and I was told that was referring to my coresponding  Network Resource.

In my case, the Network Resource was also working, however, maybe it was returning a failed responded before succeeding, or something else. But I did confirm it was coming from the Network Resource. 

So, I am speculating that the same thing may be happening in this case.

4 minutes ago, DennisC said:

Within the last two months I had an issue requiring me to contact UD for help with the error log. I had some 140005 Net Module Rule : x errors and I was told that was referring to my coresponding  Network Resource.

In my case, the Network Resource was also working, however, maybe it was returning a failed responded before succeeding, or something else. But I did confirm it was coming from the Network Resource. 

So, I am speculating that the same thing may be happening in this case.

That's awesome error log info, added to my notes. 

In this case, I'm going to bet that error isn't messing up subscriptions... it's an error all the same... I'm betting on the RSub 13: Error 6 or RSub 30: Error 6.... any idea what those mean?

3 minutes ago, MrBill said:

That's awesome error log info, added to my notes. 

In this case, I'm going to bet that error isn't messing up subscriptions... it's an error all the same... I'm betting on the RSub 13: Error 6 or RSub 30: Error 6.... any idea what those mean?

Sorry, I'm out of suggestions.

9 minutes ago, DennisC said:

In this case, I'm going to bet that error isn't messing up subscriptions... it's an error all the same... I'm betting on the RSub 13: Error 6 or RSub 30: Error 6.... any idea what those mean?

I may have had a breakthrough of sorts.  I agree that the errors in my log do not appear connected to subscriptions. However, I shutdown nodeserver #4 (one of 5 nodeservers running) and haven't logged a single error of any type since. It has been 59 minutes. The longest I went before was 10 minutes without an error. In the last full hour prior to shutting down the nodeserver in slot 4, the log registered 25 errors.

I guess that's progress.

Edited January 2, 20214 yr by vspete

@vspete Which type of error?  [UDSockets] RSub:30 error:6    or Net Module Rule: 4    

21 minutes ago, MrBill said:

Which type of error?  [UDSockets] RSub:30 error:6    or Net Module Rule: 4    

ALL ERROR TYPES. I just re-launched the admin console and pulled a log as of 1:03:21.  Here are the logs last entries. I shut down the the slot #4 nodeserver at 12:21.

Sat 2021/01/02 11:13:46 AM    System    -5012    34    
Sat 2021/01/02 11:14:12 AM    System    -5012    36    
Sat 2021/01/02 11:14:43 AM    System    -170001    [UDSockets] RSub:42 error:6    
Sat 2021/01/02 11:14:48 AM    System    -170001    [UDSockets] RSub:42 error:6    
Sat 2021/01/02 11:14:53 AM    System    -170001    [UDSockets] RSub:42 error:6    
Sat 2021/01/02 11:14:58 AM    System    -5012    37    
Sat 2021/01/02 11:20:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:24:14 AM    System    -170001    [UDSockets] RSub:42 error:6    
Sat 2021/01/02 11:24:14 AM    System    -170001    [UDSockets] HTTP:43 error:6    
Sat 2021/01/02 11:24:17 AM    System    -5012    38    
Sat 2021/01/02 11:25:35 AM    System    -170001    [UDSockets] RSub:25 error:6    
Sat 2021/01/02 11:25:40 AM    System    -5012    40    
Sat 2021/01/02 11:30:22 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:35:22 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:40:22 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:45:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:50:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 11:55:23 AM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 12:10:23 PM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 12:15:23 PM    System    -140005    Net Module Rule: 4    
Sat 2021/01/02 12:20:23 PM    System    -140005    Net Module Rule: 4    
 

I restarted the nodeserver on slot #4 at 12:58 and there ISY is reporting its data correctly.  I have to say I am stumped..  THe only change made was to change the logging level from debug to error on the ISY when I restarted the nodeserver.

I just pulled the log again at 1:14 and one line had been added: Sat 2021/01/02 12:22:04 PM    System    -140005    Net Module Rule: 8

 Looks like this one entry had been sitting in a cache or queue for more than 40 minutes before posting to the error log.

I will check back in a few hours and look at the logs again.  

Edited January 2, 20214 yr by vspete

Here is the continuation of the log since the entries above:

Sat 2021/01/02 12:22:04 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 01:12:53 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 01:25:21 PM    System    -5012    43    
Sat 2021/01/02 03:20:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:25:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:30:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:40:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:41:49 PM    System    -5012    44    
Sat 2021/01/02 03:45:21 PM    System    -5012    45    
Sat 2021/01/02 03:45:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:50:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 03:55:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:00:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:02:02 PM    System    -5012    46    
Sat 2021/01/02 04:05:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:10:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:20:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:21:38 PM    System    -170001    [UDSockets] RSub:25 error:6    
Sat 2021/01/02 04:21:38 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 04:21:43 PM    System    -5012    48    
Sat 2021/01/02 04:21:43 PM    System    -5012    49    
Sat 2021/01/02 04:24:03 PM    System    -170001    [UDSockets] RSub:25 error:6    
Sat 2021/01/02 04:24:08 PM    System    -170001    [UDSockets] RSub:25 error:6    
Sat 2021/01/02 04:24:08 PM    System    -5012    50    
Sat 2021/01/02 04:25:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:25:53 PM    System    -5012    51    
Sat 2021/01/02 04:25:53 PM    System    -5012    52    
Sat 2021/01/02 04:27:58 PM    System    -5012    53    
Sat 2021/01/02 04:30:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:35:23 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:36:22 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 04:36:27 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 04:36:32 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 04:36:37 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 04:36:42 PM    System    -5012    54    
Sat 2021/01/02 04:40:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:45:24 PM    System    -140005    Net Module Rule: 8    
Sat 2021/01/02 04:56:38 PM    System    -140005    Net Module Rule: 3    
Sat 2021/01/02 05:06:47 PM    System    -170001    [UDSockets] RSub:28 error:6    
Sat 2021/01/02 05:06:47 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 05:06:47 PM    System    -5012    56    
 

We now are getting net module rule 8 and 3 entries. No more net module #4.  The UDSocket errors have returned and can be linked to attempts  (ultimately successful) to control one dimmer device and one scene using the iWatch.  I didn't use the iPhone app to control anything during the afternoon, so no idea if it would throw a UDSocket error.  No issue with the iphone app connecting to the isy on numerous tries during the afternoon.

No more information to report.

When was the last time you did a hard reboot of the device running your nodeserver? If it's been awhile maybe try rebooting it by powering it down.

16 hours ago, DennisC said:

hard reboot of the device running your nodeserver

@DennisCthe VM hosting Debian 10 / Polyglot has been up about a week.  Don't think the issues being discussed here relate to the Nodeserver as it is spitting out data to the ISY continuously around the clock and not generating any correlatable errors in the ISY log (now that all nodeservers have their ISY logging set to either off or error only).  Below is the a snapshot of my ISY error log taen at 10:59 AM this morning. What is notable is how the lack of error activity since 9PM last evening.

There are ISY programs running after 9PM sending out commands during this period of zero errors logged, but no devices changed their state as a result of the insteon commands sent. Mobilinc was not used between 9PM & 10:59AM.  The -140005  Net Module Rule: 3  message at 4:56PM corresponds to the ISY turning the front lights on at sunset and then off at 9PM based on program action.

Mobilinc was used from the iPhone at the times associated with -170001 errors shown last evening. These are associated with turning various scenes containing insteon devices on or off and/or dimming a number of scene members using the Mobilinc Pro app on the iPhone. I am beginning to believe the RSubs seem to relate to specific scenes or devices being controlled by Mobilinc.  While these errors are being logged, the Mobilinc connections were responsive and the devices responded without issue.

Sat 2021/01/02 04:56:38 PM    System    -140005    Net Module Rule: 3    
Sat 2021/01/02 05:06:47 PM    System    -170001    [UDSockets] RSub:28 error:6    
Sat 2021/01/02 05:06:47 PM    System    -170001    [UDSockets] RSub:33 error:6    
Sat 2021/01/02 05:06:47 PM    System    -5012    56    
Sat 2021/01/02 05:06:47 PM    System    -5012    57    
Sat 2021/01/02 05:15:37 PM    System    -170001    [UDSockets] RSub:19 error:6    
Sat 2021/01/02 05:15:42 PM    System    -170001    [UDSockets] RSub:19 error:6    
Sat 2021/01/02 05:15:47 PM    System    -5012    58    
Sat 2021/01/02 05:18:47 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:18:52 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:18:57 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:19:01 PM    System    -5012    59    
Sat 2021/01/02 05:20:24 PM    System    -5012    60    
Sat 2021/01/02 05:20:24 PM    System    -5012    61    
Sat 2021/01/02 05:21:03 PM    System    -170001    [UDSockets] RSub:20 error:6    
Sat 2021/01/02 05:21:03 PM    System    -170001    [UDSockets] RSub:30 error:6    
Sat 2021/01/02 05:21:05 PM    System    -5012    62    
Sat 2021/01/02 05:21:05 PM    System    -5012    63    
Sat 2021/01/02 05:21:43 PM    System    -170001    [UDSockets] RSub:27 error:6    
Sat 2021/01/02 05:21:48 PM    System    -170001    [UDSockets] RSub:27 error:6    
Sat 2021/01/02 05:21:53 PM    System    -170001    [UDSockets] RSub:27 error:6    
Sat 2021/01/02 05:21:58 PM    System    -5012    64    
Sat 2021/01/02 05:22:50 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:22:50 PM    System    -170001    [UDSockets] RSub:20 error:6    
Sat 2021/01/02 05:22:51 PM    System    -5012    65    
Sat 2021/01/02 05:22:51 PM    System    -5012    66    
Sat 2021/01/02 05:23:40 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:23:45 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:23:50 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:23:55 PM    System    -170001    [UDSockets] RSub:16 error:6    
Sat 2021/01/02 05:23:59 PM    System    -5012    67    
Sat 2021/01/02 05:24:50 PM    System    -5012    68    
Sat 2021/01/02 07:19:09 PM    System    -5012    70    
Sat 2021/01/02 07:41:55 PM    System    -170001    [UDSockets] RSub:31 error:6    
Sat 2021/01/02 07:42:00 PM    System    -170001    [UDSockets] RSub:31 error:6    
Sat 2021/01/02 07:42:05 PM    System    -5012    71    
Sat 2021/01/02 08:06:13 PM    System    -5012    72    
Sat 2021/01/02 08:08:41 PM    System    -5012    73    
Sat 2021/01/02 09:00:03 PM    System    -140005    Net Module Rule: 3    
Sun 2021/01/03 04:05:18 AM    System    -10    n/a    
Sun 2021/01/03 05:03:01 AM    System    -60006    n/a    

I haven't had any problems with connectivity since i removed the Mobilinc iWatch app.  I now believe that the iOS 14.3 update has made the iWatch app effect both its own and the iphone apps connectivity to the ISY.  To avoid connectivity/responsiveness issues, I will not be using the iWatch app going forward.

I use Mobilinc Pro and my Iphone is also at 14.3  and I have no issues (so far).

This being said, I now mostly use Home Assistant and if Mobilinc would stop working I would get over it.

Edited January 4, 20214 yr by asbril

@asbril, I have determined that the issues that prompted this topic are associated with using the Mobilinc iWatch extension after the 14.3 iOS update.  Just to confirm, did you test Mobilinc Pro on your iWatch?

I will review Home Assistant as a possible Mobilinc alternative.  Thanks...