May 30, 20169 yr Is this normal for Mobilinc to stop responding every time you switch between LTE and wifi?
May 31, 20169 yr I just tried switching back and forth between WiFi and LTE on my iPhone and it works fine. I'm connecting via the ISY Portal to my ISY. What do you mean by not responding?
May 31, 20169 yr Yep. Every app I have ever run on my android 4.4 device boots up and uses only the comm it started with. If the comm style changes the app hangs. restart it and it is fine. I think android 5 fixed this, maybe. Edited May 31, 20169 yr by larryllix
May 31, 20169 yr Author I just tried switching back and forth between WiFi and LTE on my iPhone and it works fine. I'm connecting via the ISY Portal to my ISY. What do you mean by not responding? Mobilinc says it stopped responding Yep. Every app I have ever run on my android 4.4 device boots up and uses only the comm it started with. If the comm style changes the app hangs. restart it and it is fine. I think android 5 fixed this, maybe. I'm using a galaxy s7 Maybe because it is a momentary loss of connection
May 31, 20169 yr Hi Blackbird, We've seen this behavior like larryllix mentioned and are watching it to see what solutions Android OS or the developer community come up with. Unfortunately it's a narrow problem (switching between cell and WiFi) and hasn't received much attention from Android/Google. Wes
May 31, 20169 yr Happens to me every time I use Mobilinc. Even on the local WIFI, Mobilinc will often try secured which obviously won't work.an easier button to tell it wifi or LTE would be nice on the program when it starts up if I cannot figure it out more reliably. on android 5.0
June 1, 20169 yr Hi arw01, MobiLinc only tries the HTTPS if one of the following conditions is met: - The Android device is on cellular (Not connected to Wi-Fi) - If on Wi-Fi, MobiLinc sends out a UPnP ping and waits a few seconds to hear the UPnP response back from the ISY. If no UPnP response is heard, MobiLinc uses the HTTPS path. HTTPS on local Wi-Fi will work, however, if your HTTPS path is using a Dynamic DNS address, your router must support IP Loopback. Most routers support this, but some do not. If your router does not support this, then devices inside of your network cannot address your dynamic DNS when inside of the network. Wes
June 1, 20169 yr I will check the ip loopback capabilities of the cable modem. I can be on google via wi-fi, switch to mobilinc, watch it try local, go read, switch to secure, and it's still on wifi. If I could see some logging I could tell why it thinks it cannot get there on the wifi that I was just using and am connected to nearly constantly when home. Hi arw01, MobiLinc only tries the HTTPS if one of the following conditions is met: - The Android device is on cellular (Not connected to Wi-Fi) - If on Wi-Fi, MobiLinc sends out a UPnP ping and waits a few seconds to hear the UPnP response back from the ISY. If no UPnP response is heard, MobiLinc uses the HTTPS path. HTTPS on local Wi-Fi will work, however, if your HTTPS path is using a Dynamic DNS address, your router must support IP Loopback. Most routers support this, but some do not. If your router does not support this, then devices inside of your network cannot address your dynamic DNS when inside of the network. Wes
June 1, 20169 yr Hi arw01, Almost certainly it's because of the second condition I listed. The question becomes, why is the network/router/modem/etc not sending UPnP reliably between MobiLinc and the ISY? Wes
June 1, 20169 yr Wes, Given that ISY now disables upnp, please consider switching to a better way - like SSID/BSSID detection. I suspect many people have Mobilinc unnecessarily doing SSL when on their home wifi, making the app unnecessarily sluggish. You'll also be able to eliminate the delay - since asking the OS the network details is a fast check. Michael.
June 2, 20169 yr My Android MobilInc Pro doesn't switch. When I go into town, they have free WiFi all through the downtown. However, it will not support the port or https or something else, and MobiLinc will not transfer to mobile rf, ever. I can't access any of my four devices via WiFi through port forwarding on my router.. The only way to make MobiLinc connect via mobile comm is to disable the WiFi on my mobile phone and then reboot MobiLinc. The later version of Android 4.4 added a auto-tracking function that is supposed to support comm switching it causes most of the problems. When I was setting up my Link Hub the first thing their tech support did was tell me to turn that feature off and then things clicked. Edited June 2, 20169 yr by larryllix
June 2, 20169 yr Michael, The ISY supports UPnP discovery and can't be turned off. What UDI turned off was all other UPnP functions, but discovery works well (1-2 ms) to detect if A) there's one or more ISYs on the network and if it's your ISY on the network. I've considered just using the IP Addresses set in MobiLinc and trying both to see what connects, but that comes with several other problems. The primary issue is for those that use DHCP (which most do) when the ISY's IP address changes, MobiLinc can auto-correct it's own settings for the ISY through the UPnP response. Something that just isn't possible if you don't use UPnP. The tradeoff is if UPnP fails you end up using HTTPS which does add a slight delay to connect (1-3 seconds) if using ISY cert defaults. Or, for those that use our MobiLinc Connect service, all these issues go away since we manage the entire communication chain from the app to the ISY. Wes
June 2, 20169 yr Seems to me that Mobilinc should only do upnp if the user selects a hypothetical 'auto' check box, that disables the url input. If the user entered a url to connect to - I'd expect Mobilinc to not try to 'discover' the ISY, but operate based on the URL the user entered. That may just be me though. Thanks! Michael.
June 3, 20169 yr Hi Michael, You got it! That's how it works now. If you select HTTP or HTTPS for the connect method MobiLinc uses that path always. No UPnP. Wes
Archived
This topic is now archived and is closed to further replies.