More -5011 errors

[mitch236]

So I really thought I was getting these -5011 errors from my climate module but I turned it off and am still getting these annoying errors. In fact, yesterday I logged 2727 lines of -5011 errors in 30 seconds. I don't know if this affects anything in my network but it sure looks like something is bogging down.

 

Can someone help me devise a plan to find and eliminate this? Either that or tell me it is normal!!

[mitch236]

BTW, it began at 6:03:18 pm and ended at 6:03:50 PM

[Michel Kohanim]

mitch236,

 

As we have discussed before, the best way to figure out where they come from is by disabling your iPhone/iPod applications. If they do not happen again, then rest assured the problem is that they are not unsubscribing gracefully.

 

As far as this being normal, well, the amount you have is NOT normal.

 

With kind regards,

Michel

[mitch236]

Michel, I'm sure you are right. The -5011 errors are preceded by three -5012 errors. How can I find out why there were so many errors? I've spoken with the developer of Mobilinc and understand why these errors are somewhat unavoidable, and I don't really mind a few showing up but a couple thousand tells me that something is hanging.

 

If this is basically unfixable since I need my iPhone connection, is it a big problem or can I just live with it?

[Michel Kohanim]

Hi mitch236,

 

First I would have to emphasize that this is not an ISY bug and therefore there's nothing to fix.

 

The fact that you have so many of them, although benign and can be ignored, is a little troublesome for me. I would like to find the root cause so I need to know:

1. How many MobiLinc applications do you have?

2. Are they all local?

3. Do they go to sleep on their own? Do you think there's a correlation between when your iPhone/iPod goes to sleep and these errors?

4. Do you have any other clients such as HomeSeer/mControl/etc.?

 

With kind regards,

Michel

[mitch236]

I only have one Mobilinc Pro app.

 

I use the Mobilinc both locally and via web.

 

I almost never let the Mobilinc sleep.

 

The only other client is the admin console.

 

 

Now that I'm on the hunt for how Mobilinc causes errors, I found this morning, I tried to connect to my ISY from my iPhone using Mobilinc and it wouldn't connect so I exited the app and then restarted it which was sucessful. Then I went to the log to see what happened and here's what I saw:

 

Where it starts:

 

Indoor / Thermostats / Main House / HVAC Main House Heat Setpoint 40░ Thu 2010/04/29 09:00:15 AM Program Log

Indoor / Thermostats / Main House / HVAC Main House Setpoint 80 Thu 2010/04/29 09:00:15 AM System Log

Indoor / Thermostats / Main House / HVAC Main House Heat Setpoint 40░ Thu 2010/04/29 09:00:15 AM System Log

0 null Thu 2010/04/29 09:04:20 AM System -5012

0 null Thu 2010/04/29 09:04:20 AM System -5012

0 null Thu 2010/04/29 09:04:20 AM System -5012

0 uuid:00 Thu 2010/04/29 09:04:20 AM System -5011

0 uuid:00 Thu 2010/04/29 09:04:20 AM System -5011

0 uuid:00 Thu 2010/04/29 09:04:20 AM System -5011

0 uuid:00 Thu 2010/04/29 09:04:20 AM System -5011

0 uuid:00 Thu 2010/04/29 09:04:20 AM System -5011

 

and where it ends:

 

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 uuid:00 Thu 2010/04/29 09:05:19 AM System -5011

0 null Thu 2010/04/29 09:07:18 AM System -5012

0 null Thu 2010/04/29 09:07:53 AM System -5012

0 null Thu 2010/04/29 09:08:28 AM System -5012

Indoor / Thermostats / Main House / HVAC Main House Status 81░ Thu 2010/04/29 09:18:28 AM System Log

Indoor / Master Bath / Bathroom Lights Status 100% Thu 2010/04/29 09:31:47 AM System Log

Indoor / Thermostats / Second Floor / HVAC Second Floor Status 81░ Thu 2010/04/29 09:32:26 AM System Log

 

 

As you can see, it lasted a full minute and wrote 2351 lines!! It also starts with three -5012 errors and ends with three -5012 errors which is probably the handshake of the Mobilinc (I'm guessing here). I think the Mobilinc tried to connect and then hung up while the ISY was trying to send info. If I implied that this was a bug of the ISY, I appologize. I never meant to implicate the ISY, I assumed it was a network issue on my end. Now I realize it probably is a network issue related to the communication between the ISY and the Mobilinc and can be anywhere between my router to the Mobilinc and everything in between including my ISP, At&T's network and finally my iPhone.

 

Tonight I hope to test for local iPhone connection errors. If I don't get any errors when I connect locally, I remove my router, Mobilinc and my iPhone from the problem list and that leaves my ISP and my DYNDNS service as the only remaining variables.

 

Thanks for all your help. I will get this resolved somehow.

[Michel Kohanim]

Hi mitch236,

 

Thanks so very much for the update. Again, although benign, but this is not a good use of logs. I am going to send Wes a link to this post and together we are going to figure out what's causing the error. Your suspicions are correct: while ISY is sending the events, MobiLinc is closing the connection.

 

With kind regards,

Michel

[mitch236]

Thanks Michel. I did a very short test this morning and didn't receive any -5011 errors. I did get the obligitory three -5012 errors which aren't any problem (and are common when I close the app).

 

If I don't get any -5011 errors this weekend when I test locally, I can assume it is my ISP or DynDNS that is the culprit. Seeing how so many users here use DynDNS, I doubt they are implicated.

 

Thanks for all the help!

[InsteonNut]

Hi Mitch and Michel,

 

I looked into this last night and this morning and I think I may have found the reason the ISY is logging all of the -5011 errors.

 

I believe this is only an issue on iPhones and the now the new iPad+3G. When the iPhone is asleep and the user wakes it up and launches MobiLinc right away, the iPhone is still figuring out if any of your preferred WiFi networks are in range so your current internet connection is 3G until the iPhone logs into the WiFi network.

 

So as MobiLinc is performing its startup routine by contacting the ISY for program status, weather, subscribing, etc. MobiLinc has to be able to respond to the iPhone saying, "we found a WiFi network and I'm logging into that netowrk now. All your 3G requests have been dropped and disconnected. Start using the WiFi connection."

 

My released code will cancel all connections and start the entire startup routine over again since I can't trust the data. I suspect what is happening is MobiLinc is right in the middle of receiving the initial subscription dump when the 3G data connection is closed by the iPhone thus resulting in a string of -5011 errors logged by the ISY.

 

I made a change this morning that upon the 3G data connection going away and WiFi being present, if MobiLinc is subscribed to the ISY, MobiLinc first issues an Unscubscribe message over WiFi and then proceeds to reconnect to the ISY over WiFi. With that change I no longer see the -5011 errors in my log file. I do however still see the set of three -5012 errors.

 

Maybe Michel can shed some light as to what causes these and how I can change MobiLinc so that the ISY won't log these type of errors. I've sent Michel an email detailing MobiLinc's unsubscription method.

 

Once we can narrow this down I can add this change to my next release.

 

Thanks for bringing this to my attention!

 

Wes

[Michel Kohanim]

Hi Wes,

 

Thanks so very much for looking into this and I think you are right on.

 

As far as -5012, perhaps you can use IsSubscribed service to make sure you are still subscribed before unsubscribing. I think that would alleviate some or most of the issues.

 

Thanks again and with kind regards,

Michel

[mitch236]

Wow, you guys are awesome! Thanks so much for taking the time to consider my issue. For now, I will wait until my iPhone is awake and stable before attempting to launch Mobilinc.

 

Thanks again!

[mitch236]

As much as I would like to think that the Mobilinc is the problem, I have to post what happened when I tested my local network. Tonight, I was at my desktop computer which is connected to my network by LAN. I opened my admin console, then went in to Manage my Certificates, and then created and saved a self generated certificate (because I changed from Tzo.com to Dyndns.org for my static ip service). When I reopened my admin console after the ISY rebooted, I saw this in the log:

 

Outdoor / Low Voltage / Low Voltage One On Level 100% Fri 2010/04/30 06:09:59 PM System Log

Outdoor / Low Voltage / Low Voltage One Ramp Rate 0.5 Sec Fri 2010/04/30 06:09:59 PM System Log

Theater / Receptacle / Theater SW Status Query Fri 2010/04/30 06:09:59 PM System Log

0 null Fri 2010/04/30 06:10:05 PM System -5012

0 null Fri 2010/04/30 06:10:05 PM System -5012

0 null Fri 2010/04/30 06:10:05 PM System -5012

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

0 uuid:00 Fri 2010/04/30 06:10:05 PM System -5011

 

for about 200 lines. I guess I need a new router! The care that I took to be sure the ISY has as good a connection to my network rules out that path. I have the ISY mounted in my structured cabinet right next to the router.

 

I am using a Netgear DGND3300. Does anyone know of any issues with this router?

[InsteonNut]

Hi Mitch,

 

As much as I'd like to agree with you that MobiLinc DOESN'T have an issue, I think that aside from a potential router problem you discovered there was some things I could have done better in MobiLinc.

 

I've dug into the problem some more and can report that by modifying my 3G to WiFi crossover code I've eliminated the -5011 errors and most of the -5012 errors.

 

Here's the problem with the remaining -5012 errors and the iPhone. When the user hits the home button to close out of MobiLinc, the iPhone OS gives the code a very narrow window to run to clean up variables, state, etc. Once that timer expires the iPhone OS forcefully shuts the app down no matter what it was doing at the time. So when MobiLinc is in this shutdown period, it tries to send out a network command to the ISY to unsubscribe, but the time it takes to perform that action exceeds the timer allowed by the iPhone OS. So in essence, the unsubscribe command never reaches the ISY and the ISY is left with a disconnected subscription channel. If the ISY tries to send subscription messages out that interface between the time that MobiLinc was shutdown to the time that the ISY expires the dead subscription channel, the ISY will log the -5012 errors. In my setup I'm seeing on average 0-3 of the -5012 errors each time I shut MobiLinc down.

 

Once Apple releases the iPhone OS 4 with multitasking most of the -5012 errors should go away since the iPhone would just keep MobiLinc running and connected to your ISY in the background. Unless Apple chooses a different shutdown method for Apps, I believe there isn't much else I can do to eliminate the potential for this to occur.

 

I will continue to test my code changes and will be included in my next release to Apple.

 

Wes

[Michel Kohanim]

Hi Wes,

 

Thanks so very much for your help. Indeed appreciated.

 

Mitch, one more thing about your computer/Admin Console: would you please let me know what firewall software you have?

 

Thanks and with kind regards,

Michel

[mitch236]

I am using Norton 360 firewall.

 

Thanks. I can't see how this would be a router issue, maybe a setup issue in my network. I'm not a computer savvy user, but I do have a little knowlege (which can be dangerous!).

 

If you have any suggestions about how to set my firewall to give the ISY full access, please let me know.

 

 

Thanks again,

Mitch

[Michel Kohanim]

Hi Mitch,

 

You just have to make sure ISY is in the white/allowed list.

 

With kind regards,

Michel