rick.curl Posted November 30, 2014 Posted November 30, 2014 This thread seems to have gotten quiet, but my problem still remains unsolved. Here's my setup: Controller: ISY994i (not PRO), running firmware 4.2.18 Phones: Nexus 7 running Android 5. Mobilinc Pro installed on both. Router: D-link DI-604 with external port 443 TCP forwarded to the internal IP address of the ISY. Everything was working fine. Unfortunately, the Android 5 update and the 4.2.18 firmware update happened on the same day. Now Mobilinc doesn't work most of the time, regardless of whether it is on Wi-Fi or on the cellular data network. The same thing is happening on both of our phones. I tried rolling the ISY firmware back to 4.2.5, but it made no difference. Any suggestions? Thanks. -Rick
oberkc Posted November 30, 2014 Author Posted November 30, 2014 What are your ISY settings for HTTP and HTTPS ports? What are your mobilinc local and secure settings (port and address)?
arw01 Posted November 30, 2014 Posted November 30, 2014 Rick what did you come from Version wise? I have pretty much the same issues, I have to specifically tell Mobilinc which type of connection to use each time I change. It's a real PIA and continues to make the software pretty much un-reliable. There just is no other options over on Android land..
rick.curl Posted November 30, 2014 Posted November 30, 2014 Rick what did you come from Version wise? I have pretty much the same issues, I have to specifically tell Mobilinc which type of connection to use each time I change. It's a real PIA and continues to make the software pretty much un-reliable. There just is no other options over on Android land.. I was on 4.2.5 before upgrading. Downgrading back to 4.2.5 didn't help. Manually choosing the connection type in Mobilinc didn't help either. The ISY HTTP port setting is 80, and HTTPS is 443. Mobilinc settings for local are the IP of the ISY, port 80. Secure settings are my public static IP, port 443 Port 443 is forwarded through the router to port 443 of the ISY. This has worked fine for the last year or two until the recent updates. -Rick
oberkc Posted November 30, 2014 Author Posted November 30, 2014 Mine worked fine, also, but the question I have begun to ask is not "why is it broken". Rather, it is "why did it work before?" I am curious about the use of port 890 for local. Is this a typo? Other than the port 890 question, these settings sound consistent with my understanding, assuming I understand your response. While on a cellular connection, can you access the ISY via web browswer? This should be something like: https://mypublicstaticip:443/
rick.curl Posted December 1, 2014 Posted December 1, 2014 Mine worked fine, also, but the question I have begun to ask is not "why is it broken". Rather, it is "why did it work before?" I am curious about the use of port 890 for local. Is this a typo? Other than the port 890 question, these settings sound consistent with my understanding, assuming I understand your response. While on a cellular connection, can you access the ISY via web browswer? This should be something like: https://mypublicstaticip:443/ Sorry- the port 890 thing was a typo. I just edited it. Thanks for suggesting attempting to connect via web browser. I have almost no cellular coverage here at the house, so i tried via my desktop computer using the external IP. Initially, I couldn't connect to the external port, but I could connect internally. I couldn't find anything wrong with the forwarding rule on the router. I rebooted the router but nothing changed. I deleted the rule and re-entered it and now I can connect using a web browser pointed to the external IP & port. Unfortunately, Mobilinc is still dead in the water, both on port 80 and on port 443. I'll try it again tomorrow when I'm at the office and have cellular coverage. -Rick
v101 Posted December 1, 2014 Posted December 1, 2014 Where does one set the strength of the cipher at in the ISY? I can't seem to locate this setting?
Xathros Posted December 1, 2014 Posted December 1, 2014 v101- You need the ISY Dashboard instead of the Admin console. Download the dashboard here: http://isy.universal-devices.com/994i/dashboard.jnlp -Xathros
rick.curl Posted December 2, 2014 Posted December 2, 2014 Where does one set the strength of the cipher at in the ISY? I can't seem to locate this setting? If you've got the non-Pro version (like mine), you can't change it. From the 4.2.18 release announcement: SSLv3 is now disabled. 994 Series now use TLS1.0 as default. PRO series can select up to TLS1.2
rick.curl Posted December 2, 2014 Posted December 2, 2014 Mine worked fine, also, but the question I have begun to ask is not "why is it broken". Rather, it is "why did it work before?" While on a cellular connection, can you access the ISY via web browswer? I tried it today, and after a couple of security warnings I can access it from the browser on my phone, but still cannot connect using Mobilinc. Any ideas? -Rick
oberkc Posted December 2, 2014 Author Posted December 2, 2014 Security warnings, huh? I think I may get a certificate warning, but can still access through mobilinc. If you used the same credentials as mobilinc, it must be something else. Others in this thread have described some sensitivity to ISY https client or server settings protocol (mine is TLS1.2) and strength (mine is All). Are you on the ISY pro version?
rick.curl Posted December 2, 2014 Posted December 2, 2014 Security warnings, huh? I think I may get a certificate warning, but can still access through mobilinc. If you used the same credentials as mobilinc, it must be something else. Others in this thread have described some sensitivity to ISY https client or server settings protocol (mine is TLS1.2) and strength (mine is All). Are you on the ISY pro version? I wish - Mine's the non-Pro version. On my ISY I can't change protocol or strength. -Rick
oberkc Posted December 2, 2014 Author Posted December 2, 2014 Scottx seemed to have solved the problem by upgrading to pro. I am on pro, also, but cannot say from personal experience whether this is a factor.
rick.curl Posted December 2, 2014 Posted December 2, 2014 Scottx seemed to have solved the problem by upgrading to pro. I am on pro, also, but cannot say from personal experience whether this is a factor. What I'm wondering is if this is affecting eveyone who has a non-Pro ISY and Mobilinc on Androind.If it's not, what is the difference between mine and one that is working? -Rick
Michel Kohanim Posted December 2, 2014 Posted December 2, 2014 Hi Rick, MobiLinc should work regardless of PRO. Have you contacted them to troubleshoot? With kind regards, Michel
rick.curl Posted December 2, 2014 Posted December 2, 2014 Hi Rick, MobiLinc should work regardless of PRO. Have you contacted them to troubleshoot? With kind regards, Michel Yes I have. They sent me over here. Here's the thread on their forum: http://forum.mobilinc.com/viewtopic.php?f=46&t=2896&sid=7ee29d6d504cdf02c93b4e4e486bd5f8&start=10
oberkc Posted December 2, 2014 Author Posted December 2, 2014 Forums are wonderful places, but generaly populated by users like you and me. I suspect when michel suggested contacting mobilinc, the intention was to contact them directly. I had good luck with this approach and solving my problem. Try: Support@mobilinc.com
rick.curl Posted December 3, 2014 Posted December 3, 2014 Forums are wonderful places, but generaly populated by users like you and me. I suspect when michel suggested contacting mobilinc, the intention was to contact them directly. I had good luck with this approach and solving my problem. Try: Support@mobilinc.com Will do. I'll post back here if I get any help. Thanks. -Rick
InsteonNut Posted December 4, 2014 Posted December 4, 2014 Hi Folks, I'm working with UDI to figure out exactly what's in the non-Pro model that's causing the connection trouble for Android 5 devices. From your posts by software upgrading to the PRO model and selecting "ALL" for the Client strength that seems to fix it. Can I ask that someone try the following and post your results: Try setting the Client Server Strenght to each of the settings, Low, Medium, High, All and trying MobiLinc via HTTPS for each setting to see exactly which client settings work and which do not work for clients on Android 5. Thank you! Wes
oberkc Posted December 4, 2014 Author Posted December 4, 2014 I "think" I have done this already, without seeing any setting that would cause failure of mobilinc to connect, but confidence in my memory of exact combinations not high. I will be happy to do, or do again, but next opportunity likely not until saturday. Will stay in touch.
MWareman Posted December 4, 2014 Posted December 4, 2014 FYI - the 'client' strength on ISY affects the ISY making outbound connections. This shouldn't affect the inbound connections MobiLinc makes. I would think we need to test the 'server' settings instead. Can you confirm Wes?
Michel Kohanim Posted December 5, 2014 Posted December 5, 2014 Hi Michael, Yes server settings as long as MobiLinc is local. With kind regards, Michel Hi Michael, Yes server settings as long as MobiLinc is local. With kind regards, Michel Hi Michael, Yes server settings as long as MobiLinc is local. With kind regards, Michel Hi Michael, Yes server settings as long as MobiLinc is local. With kind regards, Michel
InsteonNut Posted December 5, 2014 Posted December 5, 2014 Hi Michael, Yes, my apologies. Server setting in the ISY set to Low, Medium, High, All. Wes
oberkc Posted December 6, 2014 Author Posted December 6, 2014 Wes, Cell phone with mobilinc Nexus 5. Wifi disabled. Connected via cellular data (MVNO Cricket LTE) only. Through the ISY dashboard, I changeed HTTPS server settings to each of the available options. Verify option is unchecked. I have no certificates. After allowing for reboot of ISY to establish new settings, and restarting mobilinc after each change in ISY setting, the results were: ALL - can connect through mobilinc Low - Failed Medium - Failed (seemed to lock up and never exit the syncing process in some attempts) High - success first time! All - success In some of the failed cases, the syncing window remained in place for a LONG (10 minutes plus) time before failing, showing the spinning circle and "getting, devices, scenes, and programs" message. Sometimes, the message moved to "retrieving configuration". I decided, if the syncing process exceeded 20 minutes, to restart mobilinc and try again.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.